Practice 04
SaaS product engineering
The first version of a SaaS product is a feature set. The second is a tenancy model, a billing story and a support surface. Most teams discover the second one late.
At a glance
We build multi-tenant products end to end, and we join teams that already have one and need it to hold at ten times the load.
Tools we use most
- React
- Next.js
- TypeScript
- NestJS
- Django
- PostgreSQL
- Row-level security
- Stripe
- Chargebee
- Keycloak
- Auth0
- Kubernetes
- Terraform
- Amplitude
- PostHog
Related work
- Vendor portal to multi-tenant product
- A customer app and a rider app built for the phones people have
- Analytics across eight publishing properties
What we get called in for
- A services business turning its best delivery method into a product.
- An MVP with real customers where every new tenant needs a code change.
- Billing that has drifted out of sync with what customers actually use.
- One large tenant whose reports slow the platform down for everyone else.
- An enterprise deal blocked on SSO, audit logs, data residency or a SOC 2 question.
How we build it
Decide tenancy on purpose
Shared schema, schema-per-tenant or database-per-tenant — chosen against your compliance, noisy-neighbour and per-tenant restore requirements, and written down with the trade-offs.
Make usage measurable before you price it
Metering events land in an immutable store from day one. Otherwise every pricing change becomes a data migration.
Build the enterprise checklist early
SSO, SCIM, role model, audit trail, export and residency are architecture decisions. Retrofitting them costs several times more than including them.
Isolate the blast radius
Per-tenant rate limits, queue partitioning and query budgets, so one customer's month-end does not become everyone's incident.
Instrument activation, not just uptime
Product analytics wired to the events that predict renewal, so the roadmap argument has evidence in it.
What you get
- Tenancy, isolation and data residency design with documented trade-offs
- Onboarding, provisioning and tenant lifecycle flows including offboarding
- Metering, entitlement and billing integration
- SSO, SCIM, RBAC, audit log and export
- Load and soak test results against a defined tenant profile
- Product analytics instrumentation plan tied to activation and retention
Further reading
Next step
Tell us what you're trying to ship.
Send the brief, the RFP, or three messy sentences about the problem. You get a written point of view from an architect within two working days — not a sales deck.