SaaS Design, Without the Agency
SaaS lives or dies on the first ten minutes and the tenth return visit. I design onboarding, core workflows, and the design system underneath them, then build the front end so it actually ships.
What you get
Onboarding that reaches first value
The screens between signup and the moment the product proves itself. Most SaaS loses people here, and most of it is fixable.
The core product, not just the marketing site
Dashboards, settings, billing, empty states, the unglamorous screens that decide whether people stay.
A design system your team can extend
Tokens in Figma, components in React, documented so the next feature reuses the system instead of inventing a fourth button.
How it works
Find where users drop
Analytics if you have them, a walkthrough of the flows if you do not. We start where the money leaks, not where the design bothers you.
Design and review
Flows, then screens, in tight loops. You see work every few days.
Build and hand off
Production React in your codebase, or a reference implementation your engineers own from day one.
Scoped per project after a short call. Fixed quote and timeline in writing before we start.
Work behind the offer
Common questions
Why not use a SaaS design agency?
An agency gives you a team, a process, and a markup. I give you one senior designer who also writes the front end. For most SaaS teams that is faster and closer to the code.
Do you redesign existing products or only new ones?
Mostly existing. The interesting work is in products that already have users, real data, and a specific place where those users give up.
How fast can you ship?
A focused flow redesign is usually two to four weeks from first call to working code. Bigger work gets scoped with a timeline you get in writing.
Can you work with our engineers?
Yes. I write the same stack they do, so reviews are about the product, not about translating a Figma file.
Ready when you are.
A 20 minute call, no deck required. I respond within 12 hours.
Book a 20 minute call