Multi-tenant architecture
The data design that gives each customer company its own space inside one running product: a tenant identifier on the records, database rules that filter by it, and tests that try to cross the line. You receive: the data design, the isolation tests and a note on how a tenant is created and removed.
Subscription billing and plans
Plans, seat limits, trials, upgrades and usage allowances set up in your Stripe account, with the product reading the billing state to decide what a customer can open. Where usage is billed, it is recorded and billed through Stripe, using the integration Stripe recommends at the time. You receive: the Stripe configuration, the webhook handlers and the billing test cases.
Sign-in, roles and single sign-on
Accounts for the people inside each customer: who may invite, who sees billing, who edits and who only reads. Single sign-on through a customer’s identity provider, such as Okta or Microsoft Entra ID, is designed in and switched on for the plan that includes it. You receive: the role matrix and the sign-in flows.
Admin and support tooling
An internal console for your own staff: find a customer, see the plan, the seats and the recent activity, and open a read-only view of what the customer sees. Actions taken in it land in an audit log. You receive: the console, the staff permission list and the audit log format.
Customer onboarding
The path from the pricing page to a customer with a working account: sign-up, card entry, workspace creation, teammate invitations and a first-run checklist inside the product. Trial reminders and failed-payment notices are written with you. You receive: the onboarding flow, the email copy and the events that mark each step.
SOC 2 readiness work
The engineering side of your own SOC 2 program: access reviews, change approval, logging, backups and a restore test, each recorded so an auditor can read the evidence. The attestation itself comes from the CPA firm you hire. You receive: the readiness tracker and the evidence folder structure.