Tenancy and permissions
Accounts, organisations, roles and invitations designed once, at the start, where they are cheap to get right.
SaaS applications
We run one of these ourselves, in production, for paying customers. Tenancy, permissions, billing, audit trails, backups and the boring operational work are the parts that decide whether a SaaS survives its second year.
- Builds
- Multi-tenant platforms
- Markets
- Worldwide
- Pricing
- Quoted against a written scope
01What it is
What decides whether a SaaS survives
The demo is the easy part.
Billing that reconciles
Plans, trials, upgrades, invoices and failed payments — wired to Stripe or your processor of choice and tested against real edge cases.
Operable for years
Audit trails, backups, monitoring and a deployment path a small team can run without a platform engineer on call.
02Included
No line-item surprises
What comes with it.
We run a multi-tenant product of our own in production, so this list is what we learned we needed rather than what sounds thorough.
- 01Multi-tenant data model with per-tenant isolation
- 02Admin console for your own support team
- 03Reporting, exports and a documented API
- 04Staging and production environments with a repeatable deploy
What it costs
A SaaS build is quoted in stages: a scoped first release with a fixed price, then a monthly rate for the work after launch. Nothing is billed by the hour.
03Then what
The other two
Most builds don't stop at one.
A site sends people to an app; an app needs a platform behind it. Whatever the mix, it is one team and one quote.
04Next step
Building a product?
Tell us who pays for it and what they are replacing. We will scope a first release small enough to launch and honest enough to charge for.