The unglamorous half of SaaS, done properly
Every SaaS product needs the same foundation: accounts, teams, permissions, subscriptions, invoices, failed payments, trials, upgrades. It is a large amount of work that no user will ever praise, and getting it wrong quietly costs revenue for years.
Products people actually pay for
- Turning an internal tool into a product other companies pay for
- Founders who need the platform layer built once and built right
- Products where billing has become a source of support tickets
- Teams facing enterprise buyers asking for SSO and audit logs
The work this covers
Multi-tenant foundations
Organisations, teams, invitations and role-based permissions, with tenant isolation enforced at the data layer rather than trusted to application code.
Billing and subscriptions
Plans, trials, proration, upgrades, dunning and failed-payment recovery. The edge cases here are where SaaS revenue quietly leaks.
The product itself
The features people are actually buying, built on that foundation rather than squeezed in around it.
Enterprise readiness
SSO via SAML and OIDC, audit logging, data export and the security questionnaire answers your first large customer will ask for.
From first call to something you own
- 01
Model the tenancy
How organisations, users and data relate is the one decision that is genuinely expensive to change later. We settle it before writing features.
- 02
Build the platform layer
Auth, teams, permissions and billing first. Unglamorous, and it is what makes everything after it fast to build.
- 03
Ship the paid feature set
The differentiating product, released in slices, with the pricing model exercised end to end before launch rather than after.
- 04
Instrument and iterate
Activation, conversion and churn tracked from launch, so roadmap decisions come from usage rather than from the loudest customer.
What we tend to build this on
Not a fixed list. If your team already runs something else and runs it well, we work in that.
- TypeScript
- Next.js
- Node.js
- PostgreSQL
- Stripe
- Redis
- AWS
- Terraform
- PostHog
Before you ask
- Can you use our existing billing provider?
- Yes. Stripe is our default because the edge cases are best documented, but we have built on Paddle, Chargebee and Lemon Squeezy. If you are selling into the EU, the merchant-of-record question matters more than the API does.
- How do you handle tenant data isolation?
- Enforced in the database with row-level security, not only in application code. Application-layer checks are one forgotten WHERE clause away from a cross-tenant data leak.
- What does this typically cost?
- Most SaaS builds land between €70,000 and €180,000 depending on how much the platform layer needs to support. The estimator on this site will get you to a range in a couple of minutes.
Tell us what you are trying to build
A 30-minute call is usually enough to tell you whether we are the right fit, what it is likely to cost, and how long it will take. No deck, no sales script.