SaaS Product Design
Design the SaaS experience around activation, not just the signup screen.
SaaS UX for onboarding, first value, adoption, account management and subscription moments, using patterns that still hold as the product grows.
Recurring products
Signup is cheap. The first useful week is the product.
SaaS work here is judged by whether a new account reaches value, comes back, and can manage seats and billing without a support thread. We design onboarding, the weekly habit and the account surfaces as one system, then leave patterns that do not collapse when the third module ships.
Typical constraints
The product acquired the account and then lost the week.
- Onboarding is a tour of features instead of a path to first value.
- Activation depends on a champion who never finishes setup.
- Teams invite colleagues and then cannot find a reason to return.
- Billing, seats and permissions live in a leftover settings graveyard.
- Each new module introduces a different navigation idea.
- Sales demos skip the empty states customers actually meet after checkout.
What you receive
The first week, the habit and the account, designed together.
SaaS design is not a marketing site with a login. The artefacts cover activation, recurring use and the commercial surfaces that keep the account alive.
01
Activation map
The shortest honest path from signup to a moment the customer would call useful.
02
Onboarding flows
Setup, imports, invites and empty states designed as work, not as a slideshow.
03
Recurring product surfaces
Home, lists and the weekly jobs that decide whether the seat is used.
04
Account and subscription UX
Seats, roles, plans, invoices and cancellation treated as product, not as admin leftovers.
05
Scalable UI patterns
Navigation, objects and components that can absorb the next module without a restyle.
06
Handoff for product and engineering
States, permissions and notes so the next sprint does not reopen onboarding from scratch.
How SaaS UX is designed
First value, then the habit, then the account.
We do not polish the marketing site and call it product design. The sequence follows how a subscription is actually kept.
01
Map activation and first value
What must be true before the customer would defend the invoice.
02
Design onboarding without theatre
Only the setup that is required. Tours are a last resort, not a strategy.
03
Structure account and subscription UX
Seats, roles, plans and billing given the same care as the feature that was sold.
04
Pattern the recurring surfaces
The weekly jobs get a stable home, lists and empty states.
05
Review adoption drop-off
Where invites stall, where setup is abandoned, and which friction is actually optional.
06
Document scalable UI rules
So the fifth module does not invent a new product language.
Useful when
This is the brief when the revenue is a subscription.
- A product has a signup rate that sales likes and an activation rate nobody will show.
- Self-serve onboarding was bolted on after a sales-led motion.
- Multi-seat accounts cannot understand roles, billing or who owns setup.
- The product is adding modules and the original information architecture is failing.
- A design system is needed because marketing and product no longer look related.
- An audit already showed the leak, and the work is now to redesign the path.
What we judge
A SaaS experience should make staying easier than leaving.
A shorter path to first value
New accounts meet the useful moment before they meet the full feature list.
Clearer weekly use
The habit has a home. People are not hunting for last week's work.
Account UX that can be operated
Seats, permissions and billing stop generating support tickets by default.
Patterns that survive the next module
Growth adds screens without adding a second product language.
Related work
Selected SaaS product work will appear here.
Subscription product studies are published when we can show the path and the client agrees. Until then, use the Work index rather than placeholder stories.
Published case studies will appear here when they are cleared.
Related services
Work that usually sits beside this.
Questions
Buying questions, answered directly.
No. Sales-led SaaS still has activation, seats and a weekly habit. The onboarding may start with a human, but the product still has to keep the account without a weekly call.
Next move
If activation is the leak, look at the first week.
Tell us where new accounts stall and what 'value' means in your product. We will say whether onboarding, account UX or a wider pattern pass is the next move.