Situation
The operating reality
The founders had eight pilot customers waiting and twelve weeks of runway-credible scope. The first version had to be shippable, demoable, and durable enough to survive the next 18 months.
Case study · Startups
From MVP to Series A in nine months — without the rewrite tax
Shipped a B2B SaaS MVP in 12 weeks that supported the founders through pilot, paid contracts, and a successful Series A — without a rewrite along the way.
Anonymized delivery dashboard
Startups outcome cockpit
MVP shipped
12 weeks
Pilots to paid
7 of 8
Series A raised
$11M
Before
Constraint
Build
Controlled cutover
After
Measured gain
- Client
- Pre-seed B2B startup
- Industry
- Startups
- Service
- Custom Software Development
- Engagement closed
- May 2024
Storyline
From constraint to measurable change.
Every engagement is framed around the business situation, the constraint that made it hard, and the decision that turned delivery into a controlled path to value.
Constraint
Why it was hard
The founders had eight pilot customers waiting and twelve weeks of runway-credible scope. The first version had to be shippable, demoable, and durable enough to survive the next 18 months.
Decision
The path we chose
Used a deliberately boring SaaS stack so product learning, not infrastructure novelty, consumed the runway.
Build
A boring stack chosen on purpose
Next.js, NestJS, PostgreSQL, and AWS — picked because the hiring pool was deep, the runtime was well understood, and nothing was novel. The novelty went into the product, not the stack.
Row-level security and tenant scoping were in place from the first commit, so the second customer did not require a refactor.
Outcome
Measured impact
MVP shipped in 12 weeks, on the original scope.
7 of 8 pilot customers converted to paid contracts.
What changed after launch
New behavior
The founders could sell, onboard, and raise on the same codebase instead of pausing for a rewrite after the first pilots.
Outcome
The numbers that mattered.
- MVP shipped
- 0 weeks
- Pilots to paid
- 0 of 8
- Series A raised
- $0M
“They gave us a product we could sell immediately and a foundation our first engineering hires could extend.”
Before and after
The transformation the client could see.
The work was not abstract modernization. It changed day-to-day behavior, ownership, and the evidence leaders used to make decisions.
MVP to scale
Before
- Eight pilots waiting
- Twelve weeks of credible runway
- Rewrite risk after MVP
After
- MVP in 12 weeks
- 7 of 8 pilots converted
- Series A raised without rebuilding
Architecture and delivery
A controlled path from discovery to launch.
The delivery plan made the system boundary explicit, then used rehearsals, gates, and telemetry to optimize safely before launch.
Delivery architecture
Startups control loop
Discover
A boring stack chosen on purpose
Next.js, NestJS, PostgreSQL, and AWS — picked because the hiring pool was deep, the runtime was well understood, and nothing was novel. The novelty went into the product, not the stack.
Launch
Multi-tenant from day one
Row-level security and tenant scoping were in place from the first commit, so the second customer did not require a refactor.
Build
How we shaped the work.
A boring stack chosen on purpose
Next.js, NestJS, PostgreSQL, and AWS — picked because the hiring pool was deep, the runtime was well understood, and nothing was novel. The novelty went into the product, not the stack.
Multi-tenant from day one
Row-level security and tenant scoping were in place from the first commit, so the second customer did not require a refactor.
What changed after launch
What shipped, and what it changed.
- MVP shipped in 12 weeks, on the original scope.
- 7 of 8 pilot customers converted to paid contracts.
- Series A closed at $11M nine months after MVP launch.
- Codebase carried through Series A with no rewrite; team hired against the same stack.
After launch
The founders could sell, onboard, and raise on the same codebase instead of pausing for a rewrite after the first pilots.
Stack
What we built it with.
Next.js
NestJS
PostgreSQL
Stripe
AWS
Terraform
PostHog
Related case studies
View all workSimilar delivery patterns.
A similar problem?
Let’s talk about your project.
A senior engineer will follow up within one business day with an opinionated take on the shape of the work.