DaybyDay Insurance

Problem

Insurance was built for predictable salaries, so it fails the people who need flexibility most. Language is dense, plans are rigid, and most apps feel like digital paperwork, heavy and intimidating for freelancers whose income shifts month to month.

Approach

I started with user interviews and competitor research. A clear pattern emerged: people don't buy policies, they buy peace of mind. I mapped journeys for everyday users, including freelancers, and pinpointed the moments where confusion and anxiety spiked.

Solution

The product is organized around a simple model: Policies are your plan, Coverages are what you protect. Jargon was rewritten in plain language, claims were surfaced as a core flow, and onboarding shifted from education to reassurance, protection without fear.

DaybyDay turns insurance from something people tolerate into something they understand. By designing around real-life income patterns, it feels less like managing a contract and more like having protection that moves with you.

Conclusion

If you're building in a complex or trust-heavy space and want it to feel clear, human, and grounded, feel free to reach out or book a short call to discuss your project.