SaaS development
Full product build: architecture, tenancy, billing, admin and analytics.
- Engagement
- Phased build, fixed scope per phase
- Typical timeline
- 16 weeks
- Starts with
- A one-page draft of your pricing tiers, however rough it is.
You sold the first fifteen accounts on a spreadsheet and a bank transfer, and now renewals, upgrades and refunds live in one person’s head. The product works; the commercial machinery around it does not exist yet.
A product ready to onboard paying customers.
What we build
Concrete artefacts, handed over and documented.
- 01
The plan and entitlement model: what each tier includes, what it meters, and what happens the moment a limit is passed
- 02
Subscription billing on Stripe with trials, proration, tax handling and dunning for failed cards
- 03
Usage metering that finance and the customer read the same way, invoice line by invoice line
- 04
Self-serve sign-up with roles and seat management, so an account admin adds a colleague without emailing you
- 05
Activation and feature-use tracking, wired in before launch rather than bolted on after it
- 06
An admin console for support: change a plan, issue a credit, extend a trial, every action recorded
What changes
Upgrades, downgrades and renewals happen without anyone opening a spreadsheet
Failed cards are chased automatically, which is usually the fastest revenue recovery available to a young subscription business
Pricing can change without a rebuild, because entitlements are stored as data rather than written into code
How it runs
- Weeks 1–2
01Commercial model
We write the tiers, the limits and the metering rules first. Billing decided late is billing built twice.
- Weeks 3–12
02Product build
Tenancy, sign-up, permissions, billing and the admin console, released fortnightly to an environment you can log into.
- Weeks 13–16
03Launch hardening
Card failure paths, refunds and cancellations, then a full rehearsal of the first billing cycle against test clocks.
Chosen per project. Named here so you can see the shape of it.
- TypeScript
- Next.js
- Postgres
- Prisma
- Stripe
- Sentry
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.