Case Study · B2B software
Confidential: B2B SaaS
From prototype to 820 seats
A tenancy-first architecture that let the customer onboard without engineering.
Tools
- Figma
- React
- Node.js
- PostgreSQL
- Stripe
Time duration
18 weeks
Overview
A revenue-intelligence prototype had to become a sellable multi-tenant product: billing, roles, audit trails and an onboarding path that did not require engineers for every new customer.
Problem Statement
Early B2B SaaS teams often ship charts before tenancy. The tenth customer then needs a custom deploy, permissions leak across accounts, and billing is a spreadsheet. Buyers stall when onboarding takes weeks and the product cannot answer who owns which data.
Solutions
- Design the data model around tenancy before the first production screen.
- Ship billing and entitlements with the MVP.
- Default dashboards to one weekly signal instead of a wall of charts.
- Make the tenth customer an afternoon of configuration, not a sprint.
Design process
Empathize
- Founder interviews
- Pilot customer calls
- Support themes
- Competitor teardown
Define
- Tenancy rules
- Role matrix
- Pricing hypotheses
- Success metrics
Ideate
- Onboarding flows
- Dashboard concepts
- Billing states
- Empty states
Design
- App shell
- Admin surfaces
- Design tokens
- Responsive tables
Test
- Pilot onboarding
- Permission audits
- Billing dry-runs
- Launch checklist
-71%
Time to insight
820
Seats deployed
1 day
Onboarding time
Discovery insights
Survey responses gathered during discovery that ranked jobs, friction and priorities before we committed to flows.
What blocks you from rolling out a new SaaS tool to the team?
Painful onboarding / setup
39%Unclear ROI in first week
27%Security / access concerns
21%Price
13%
How many tools do you check for revenue signals each week?
One primary dashboard
34%2-3 tools
41%4+
18%Spreadsheets only
7%
Audience research
How people split across channels, screens and decision criteria. Used to weight information architecture and first-release scope.
Who must approve a new analytics vendor?
- Founder / CEO36%
- RevOps / Finance31%
- Engineering19%
- Team lead alone14%
Ideal time from signup to first useful insight?
- Under 1 day48%
- 2-3 days29%
- One week16%
- Longer is fine7%
Outcome
What the client said, and how the engagement landed after launch.
The tenth customer took an afternoon instead of a sprint.
Multi-tenancy was designed before the first screen. Every query carries a tenant boundary enforced at the database layer.
Billing and entitlements shipped with the MVP, which meant pricing experiments never required a release.
The product reached 820 seats within a year of first launch.