Zero to Shipped in 10 Weeks
A founding team with a great idea, a runway deadline, and no engineering team.
STACK
01 — THE PROBLEM
A two-person founding team — one clinician, one business person — had raised a pre-seed round and needed to ship an MVP in 10 weeks before a major healthcare conference. The product: a scheduling and patient intake platform for independent physiotherapy clinics. The constraints: tight timeline, strict regulatory considerations around patient data, and a budget that couldn't afford mistakes. They'd gone through two freelancers who'd built nothing usable.
02 — THE APPROACH
Week one was not about code. I ran a structured scoping session with the founders to separate "MVP" from "version 1.0" from "what we eventually want to build". This produced a ruthless feature list: 7 features in scope, 23 features explicitly deferred. The founders were uncomfortable cutting scope. I showed them a timeline math exercise: each deferred feature bought back one week. That convinced them.
I chose Next.js with a PostgreSQL backend with Prisma for the data layer — predictable, well-documented, and fast to move in. The patient data architecture was designed upfront with GDPR and healthcare data handling in mind: field-level encryption for PII, full audit logs on every mutation, and role-based access that was over-specified relative to MVP needs but would prevent painful migrations later.
I built in weekly demos with the founders — every Friday, something clickable. This isn't just a "nice to have" — it's a forcing function that prevents the classic startup trap of building in isolation for 8 weeks and discovering you solved the wrong problem. Two of the 7 features changed direction based on these feedback sessions. That's the system working correctly.
03 — THE OUTCOME
Shipped to private beta on day 68. The founders demoed it live at the conference. Three clinics signed up as paying customers in the first two weeks after the demo.
THE TAKEAWAY
Speed and quality aren't opposites if you're ruthless about scope. The 10-week constraint wasn't a problem — it was a feature. It forced every decision. Most projects don't fail because the engineering was bad. They fail because nobody had the discipline to say "not yet" to the right things.