Empty workspace after signup
The happy path assumes an admin who already knows the product. New tenants hit a blank state and leave — or open a ticket that should have been a first-run path.
Service · Multi-tenant UX
Two products. One family.
Admin and customer surfaces that stay in the same system as tenants grow — workspace context, permissions people can explain, and patterns engineering can ship without forking the product.
Admin · customer · roles Live SaaS, phased UK & US teams
Demo Interface pattern · no client data
Where it stalls
The product works. The tenant does not stick.
Live SaaS rarely fails on visual polish. It fails when admin, customer, and roles drift into three products nobody can explain.
Permission fog
Roles were added for sales and security. New users hit “you don’t have access” with no path to the person who can grant it.
A change hits every workspace
Teams freeze UI work rather than ship incrementally, so the product stalls between releases. Continuity is the constraint, not a mood board.
Product thinking
Tenant-aware before we draw a screen
Who is in this workspace, what they can do, and which surface they are on — named before UI, so admin and customer stay one family.
Workspace, not a user
Every view knows which tenant it is in. Empty states, nav, and billing copy change with that context — not with a one-size home.
Permissions people can say out loud
Owner, admin, member, guest — in language the champion can repeat on a sales call. Hidden actions include a path to the person who can unlock them.
Admin and customer share a system
Type, density, and components stay in one family so a visual change does not fork the product into two roadmaps.
UX / UI
The three surfaces we actually design
Admin, customer, and the permission model between them — as one kit, not three briefs.
An admin console the champion can run
Members, billing, and integrations in language that matches how the team actually joins — not a policy matrix dumped into settings.
- Invite flows that match how seats are bought
- Safe defaults before enterprise policy
- The same type and density as the customer app
A customer product that inherits the kit
Workspace home, empty states, and next actions that know the tenant and the role — so “you don’t have access” is never a dead end.
- Role-aware empty states, not a blank canvas
- A path to the person who can grant access
- Patterns that survive a new module next quarter
A role model sales can explain
Four roles most B2B products actually need. Advanced policy waits until someone asks for it — after first value, not before.
- Plain-language roles before SSO sprawl
- Hidden actions named, with an ask path
- A matrix engineering can implement once
Product systems
A kit engineering can phase into a live tenant
Phased rollouts are the default. Continuity over a big-bang launch that breaks a workspace.
Selected work
PayrollPro · permissions 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 the job
- Focus
- Role model, admin vs customer kit
- 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.
Adjacent
Related services
This service owns tenant-aware UX. These are the briefs that often sit next to it.
01
Product Design & UX
Whole-product story, flows, and launch-ready UI when the product is new or being rebuilt.
→ 02Dashboard Design
The morning scan: hierarchy, filters, and exceptions — not the first-run or the role model.
→ 03SaaS Product Solutions
Activation, onboarding, and MVPs when the leak is signup-to-first-value, not the kit itself.
→Need the published payroll case? PayrollPro.
FAQ
About this service
How this differs from Product Design and Dashboard Design — and how we ship into a live tenant.
Ask us directly→Yes. Phased rollouts are the default. We work inside the live product so a tenant is not broken by a rewrite. Shared components, flagged variants, and a sequence engineering can ship without a big-bang cutover.
Product Design owns the whole-product story for new or rebuilt products. This service owns tenant-aware UX, permissions, and admin versus customer surfaces on a live SaaS. Many engagements start here when the product is already shipping.
Dashboard Design owns the morning scan: hierarchy, filters, drill-downs. This service owns workspace context, roles, and the relationship between admin and customer UI. A live SaaS often needs both.
Yes. The brief is usually the gap between them: an admin console that drifted, a customer product that never inherited the same patterns, and permissions that only make sense to the person who built the role model.
Start a project
Need both surfaces in one family?
A short fit call or a written brief. You leave with a clear yes, no, or not-yet.
◆Reply within one business day ◆NDA on request ◆No commitment required