From first idea to paying customers.
Subscription products built with the plumbing in place: accounts, billing, tenants and analytics.
A SaaS dashboard with growing subscription revenue and new customers signing up.
Overview
A SaaS product is more than its main feature. It needs sign-up and login, subscription billing, multi-tenancy (each customer's data kept apart) and an admin view for your own team. We build those parts first, so the feature you care about sits on solid ground. You own the code, the infrastructure and the customer data from the first commit.
A good fit if
- A second and third customer are lined up.
- Customers ask for their own workspace, roles or single sign-on.
- Someone still sends invoices by hand, or pricing keeps changing.
- An AI-built prototype has users, but nothing stops one customer seeing another's data.
Not the right start if
- You have no paying users yet. Start with Discovery & MVP
- It's an internal tool for one company. Start with Custom Software & Integrations
- You only need billing added to an existing app. That's a smaller job. Ask us about it on the call.
Isolation
Can Acme see Beta's invoices?
Every place a customer can reach data needs its own check. Switch one off and see where the leak opens.
Acme
-
Screens
Leak
-
API
Leak
-
Exports
Leak
-
Background jobs
Leak
-
Search
Leak
-
Cache
Leak
Beta
Isolation test: blocked on 6 of 6 surfaces.
Isolation test: blocked on 6 of 6 surfaces. Isolation test: blocked on 5 of 6 surfaces. Screens: Acme changes the invoice number in the address bar and Beta's invoice opens. Isolation test: blocked on 5 of 6 surfaces. API: Acme's integration asks the API for invoice 1042 and gets Beta's. Isolation test: blocked on 5 of 6 surfaces. Exports: Acme's CSV export includes Beta's rows. Isolation test: blocked on 5 of 6 surfaces. Background jobs: The monthly summary email sends Beta's numbers to Acme. Isolation test: blocked on 5 of 6 surfaces. Search: Acme's search suggests Beta's customer names. Isolation test: blocked on 5 of 6 surfaces. Cache: Acme loads a dashboard that was cached for Beta. Isolation test: blocked on of 6 surfaces. :Every case
- All checks on
- Isolation test: blocked on 6 of 6 surfaces.
- Screens off
- Isolation test: blocked on 5 of 6 surfaces. Screens: Acme changes the invoice number in the address bar and Beta's invoice opens.
- API off
- Isolation test: blocked on 5 of 6 surfaces. API: Acme's integration asks the API for invoice 1042 and gets Beta's.
- Exports off
- Isolation test: blocked on 5 of 6 surfaces. Exports: Acme's CSV export includes Beta's rows.
- Background jobs off
- Isolation test: blocked on 5 of 6 surfaces. Background jobs: The monthly summary email sends Beta's numbers to Acme.
- Search off
- Isolation test: blocked on 5 of 6 surfaces. Search: Acme's search suggests Beta's customer names.
- Cache off
- Isolation test: blocked on 5 of 6 surfaces. Cache: Acme loads a dashboard that was cached for Beta.
Process
How it runs
You keep
- 01A tenancy decision record.
- 02A roles and permissions table.
- 03An entitlements map.
- 04A plan-change table and a failed-payment schedule.
- 05An activation event and the onboarding flow.
- 06An admin console.
- 07An event plan and a metrics dashboard.
- 08A launch checklist and test results.
-
01 of 08
Pick the tenant model.
Shared tables, a schema per customer or a database per customer, and why.
You keep A tenancy decision record.
-
02 of 08
Accounts and roles.
Sign-up, login, teams and permissions, with a path to single sign-on.
You keep A roles and permissions table.
-
03 of 08
Plans and what each one includes.
What each plan allows, kept separate from payment events.
You keep An entitlements map.
-
04 of 08
Billing.
Subscriptions, upgrades, failed cards and refunds through your payment provider.
You keep A plan-change table and a failed-payment schedule.
-
05 of 08
First run.
The moment a new customer gets value, defined and measured.
You keep An activation event and the onboarding flow.
-
06 of 08
Tools for your team.
Find a customer, act on their behalf with an audit trail, issue a credit.
You keep An admin console.
-
07 of 08
Metrics.
Revenue, churn and retention computed from your own data.
You keep An event plan and a metrics dashboard.
-
08 of 08
Launch to a first group.
Design partners first, with isolation tests running on every change.
You keep A launch checklist and test results.
Risks
The second customer is the real test
-
One customer sees another's data.
Usually a missing permission check, not a hack.
Prevented in step 1 -
Billing edge cases.
A plan change with an unpaid invoice can credit time the customer never paid for.
Prevented in step 4 -
Enterprise deals stall.
Security reviews ask for single sign-on, audit logs and evidence you don't have yet.
Prevented in step 2
9.3 of 10
The severity score given to a 2025 flaw where apps without database row rules let anyone read other users' data (CVE-2025-48757).
Deliverables
What you keep
-
Accounts and roles
Sign-up, login, teams and permissions, with single sign-on when customers ask for it.
-
Subscription billing
Plans, trials, upgrades and invoices through a payment provider.
-
Multi-tenant architecture
Each customer's data isolated and tested.
-
Admin and analytics
A back office for your team and the product metrics you decide to track.
-
Scale plan
Where the product will strain first, and what to change before it does.
Done means
- A second customer can sign up, pay, invite teammates and use the product without us.
- They can't see the first customer's data on any surface, and that's tested on every change.
- Every plan change is handled, including an upgrade mid-month and a change with an unpaid invoice.
- A failed card ends in the right access, not a free account.
- Your team can find a customer, act for them with an audit trail and issue a credit.
Sample
Tenancy decision record
| Decision | Shared database, customer ID on every row, enforced by database row rules |
|---|---|
| Why | Lowest running cost for the first 200 customers; isolation enforced in one place |
| Tested by | Isolation tests on 6 surfaces, run on every change |
| Revisit when | A customer contract requires its own database |
| Owner | Your product lead |
FAQ
Questions about SaaS Products
Still deciding?
Ask the people who would build it. We reply within one business day.
Usually yes. Adding it later means reworking the database and every query, so we design for it at the start. The exception is a product with one big customer, where a simpler setup is fine.
It depends on who should handle sales tax. With Stripe Billing you're the seller and register for tax yourself. A merchant of record such as Paddle is the seller on your behalf and charges a few points more per sale. Leaving a merchant of record later is harder, because the stored cards aren't yours.
Not until an enterprise buyer asks. We pick an auth provider that can add it per customer, so it becomes a feature of your top plan rather than a rebuild.
No agency can: an auditor issues the report. We build the controls and the change history an auditor checks, so the audit doesn't force a rewrite.
Make two accounts and try to see one from the other. Then ask us to show you the isolation tests that check the same thing on every change.
You do. Code, designs, infrastructure and data sit in repositories and cloud accounts you control, from the first commit.
Contact
Have an idea or a stuck project? Let's talk.
We reply within one business day. If we're not the right team, we'll say so on the first call.
On the first call
- Who pays, how they'll pay, and how many customers you expect in year one.
- Any enterprise or data-location requests.
- What exists today.