Solutions architect
The data model, the integrations, and the build order are decided before a line of code, so the scope you see is the scope you get.
A SaaS MVP is not a marketing site with a login button. You need accounts, a subscription plan, the one workflow people pay for, and an admin view to watch it work. Lab Twelve builds SaaS MVPs as a fixed package: auth, Stripe subscriptions, the core product path, and an admin console, all after the scope chat writes the feature list down. Most SaaS first versions land on MVP Sprint because they need Postgres, Redis, background jobs, and billing in one build. You get the price before checkout, and source code you own at handoff. One person scoped, designed, and shipped it, with a human pass before anything reaches production.
One fixed price buys a whole product team in one: architect, designer, and AI-native engineer.
The data model, the integrations, and the build order are decided before a line of code, so the scope you see is the scope you get.
Interface, flow, and brand are designed for this build, not dropped onto a template. The finished app looks like it was meant to ship.
Senior execution at AI speed, in production with the source code in your hands. One builder with the range of a whole product team.
| Account signup + auth | Included |
|---|---|
| Stripe subscription billing | Included |
| Core paid workflow | Included |
| Admin metrics console | Included |
| Production deployment | Included |
Account signup + auth: Tenant model decided in scope
Stripe subscription billing: Plans wired and test-mode proven
Core paid workflow: The one job people subscribe for
Admin metrics console: Watch usage and accounts
Production deployment: Railway baseline, source in your repo
| Multi-tenant white-label suite | Not in base scope |
|---|---|
| Usage-based metered billing | Not in base scope |
| Native mobile apps | Not in base scope |
Multi-tenant white-label suite: Different architecture, flag it upfront
Usage-based metered billing: Scoped as an add-on when defined
Native mobile apps: Responsive web for v1
A representative ScopeSpec ticket. Yours is assembled live from the scope chat, priced by the engine, and locked before you pay.
Scope lock + quote
Plans, core workflow, and OUT list signed.
Accounts + core path
Auth, the workflow people pay for, data model.
Billing + admin
Stripe subscriptions, admin metrics, jobs.
Harden + ship
Production deploy, runbook, revision round.
Yes. Stripe subscription wiring is part of the MVP Sprint scope for SaaS, proven in test mode before live keys. Complex metered billing is quoted as an add-on.
Start with one or two paid plans. Pricing tiers and feature gates are named in the scope chat so the build matches what you sell.
If you have not validated the one job people will pay for, we will say so before you buy. A SaaS MVP is for a workflow you can already describe.
No agency to manage, no roster to assemble. The whole team, one number, source code in your hands.