Founder had two weeks and no engineering hire. Needed a real product for a pilot with 3 launch partners.
What they were actually dealing with.
A pre-seed founder had signed three pilot partners and given them a date. What they did not have was an engineer. The previous contractor had been on the build for eleven weeks and had not shipped something the partners could open.
The date could not move, because the pilot partners had allocated their own resources against it. That inverted the usual scoping conversation: rather than asking what the product should include, the only useful question was what could be genuinely finished in fourteen days without leaving a mess behind.
The decisions that actually mattered.
Not a task list. The four calls that determined whether this worked.
Scope cut to what the pilot could actually exercise
Three partners cannot exercise a full marketplace. They can exercise listing creation, discovery, and a booking that takes real money. Everything that would only matter at scale — advanced moderation, dispute flows, analytics dashboards — was deliberately deferred rather than half-built.
Boring stack, chosen on purpose
Next.js, PostgreSQL, Stripe Connect. Nothing about a fourteen-day build justifies novel infrastructure, and every unfamiliar dependency is a day you cannot afford to lose to a surprise.
Partners in the loop from day four
The pilot partners saw a working URL on day four and every few days after. Two significant changes came out of that, both cheap at day six and expensive at day thirteen.
Built to be continued, not to be finished
Typed schema, real migrations, and tests on the payment path. The deferred features were left as clean seams rather than stubs, which is why the same squad could keep building afterwards without a rewrite.
Is this outcome remarkable or ordinary?
For calibration: the industry convention for an MVP of this shape is a three-to-six-month build cycle. The fourteen-day figure is not a faster version of that process; it is a different scope decision, made possible by cutting everything the pilot could not exercise.
Source: Comparison against conventional agency MVP timelines
“The team shipped in fourteen days what my last freelancer took eleven weeks not to finish. Same team is now our retained squad.”
If you're in the same position.
If you have a hard external date, the lever is almost never engineering speed. It is deciding what genuinely does not need to exist yet, and having someone build the remainder in a way that does not have to be undone later.
Other engagements.
You can generate an app in an afternoon.
Owning one is a different job.
30-minute scoping call. Fixed-price plan in your inbox within 48 hours. Whichever service you need, Launch, FullCode, Codify Yo!, or Teams, you're talking to the team who'll do the work.