An empty dashboard
The account exists. The workspace is named. Nothing useful is on screen, so a tooltip tour stands in for the product.
SaaS product design · UK & US
Signup is not the product.
We design the first run so B2B users reach a real outcome — not an empty dashboard and a product tour they skip.
Onboarding · roles · home Pre-seed to Series A Design + Next.js
Demo Illustrative first run · no client data
Where signup leaks
Users signed up. Then they left.
Activation is not “completed setup.” It is the first outcome they came for. Most products lose people in the same three places.
Permissions before value
SSO and role sprawl push admin setup ahead of the job. The buyer never reaches the moment that proves the product.
No shared “activated”
Growth, product, and design track different events. Nobody can say what first value is, so nobody can design for it.
What we design
The surfaces that decide whether people stay
Onboarding, roles, and the daily home — designed as one first run, not three products bolted together.
First value before the tour ends
Collect only what creates a workspace. Route the checklist from role and intent. Design the empty state as a path, not a blank canvas.
- Progressive setup matched to who is signing in
- One guided action that delivers the job they came for
- Activation events product and design can both name
Roles people can explain out loud
Multi-tenant access has to stay understandable when SSO and enterprise policy arrive. Default safe roles. Defer advanced admin until someone needs it.
- Plain-language roles before policy matrices
- Invite flows that match how teams actually join
- Admin that does not block first value
A home for the morning scan
Dashboards and admin panels designed for exceptions and next actions — density that holds up in a demo without becoming a metrics museum.
- Hierarchy for what needs a decision today
- Patterns that survive new modules and roles
- Demo-ready without visual noise
Proof
PayrollPro · first value after SSO
Case Pattern from the published PayrollPro study
Progressive onboarding and permission clarity for a UK & EU payroll platform after SSO pushed setup ahead of first value.
- Sector
- B2B SaaS · payroll
- Trigger
- SSO made permission setup block first value
- Focus
- Progressive onboarding, role clarity
- Scope
- Onboarding paths, permissions, integration health
PayrollPro is a published case study. Client labels may be portfolio names. Signed-off numeric outcomes appear only on FleetFlow.
How we engage
Start with the leak. Then ship the first run.
Written gates, weekly demos, and one team on the call and in the code.
Services
Related services
The building blocks most B2B SaaS products pull together after the first run is named.
01
SaaS Product Design
Multi-tenant UX, admin versus customer surfaces, and permissions that stay explainable.
→ 02Product Design & UX
Research, flows, and launch-ready UI for the path from signup to first value.
→ 03Dashboard Design
Morning-scan homes and admin panels for exceptions — not a metrics museum.
→ 04CRMPulse
A published SaaS dashboard case for pipeline clarity and daily use.
→Need finance sync rather than product UX? See QuickBooks & Xero integrations. Related reading: onboarding patterns.
Before the call
Questions founders actually ask
Including whether you need design only, or design and build.
Ask us directly→Yes. We work with teams from pre-seed MVPs through to Series A scaling. Team size and engagement model are tailored to your stage and runway.
Yes. We typically roll out redesigns in phases to reduce risk and maintain user continuity.
Both. Many clients start with product design and extend into Next.js development with the same in-house team.
Yes. The UK is our primary SaaS market, but we regularly support US product teams with overlapping hours and the same delivery model.
A scoped discovery + design sprint, or a fixed MVP build with weekly demos. We recommend the lightest path that answers your biggest risk: activation, demo readiness, or technical feasibility.
Next step
Where does signup lose people?
A short fit call. You leave with a yes, no, or not-yet — and whether the leak is onboarding, roles, or the home screen.
◆Reply within one business day ◆NDA on request ◆No obligation