"A Working MVP in Two Weeks" — What That Actually Ships
Every founder has seen the ad: a beautiful working MVP in two weeks. It's not a lie — but “working” and “publishable” are two very different products, and the gap between them is where most launches die.
The promise is real. The scope isn't stated.
Two weeks is genuinely enough time to build something that runs, looks good in a screen recording, and proves a concept. What it is not is a product you can charge money for on day 15. The ad says “working”. Working means it runs. Publishable means someone who isn't you can sign up, pay, break it, and come back tomorrow to find their data still there.
Demo-grade vs publishable
| What it needs | Demo-grade MVP | Publishable MVP |
|---|---|---|
| Auth | Single hardcoded login or magic link | Real accounts, roles, password reset, session expiry |
| Data model | Whatever shape the demo needed | Migrations, constraints, indexes, seed and rollback |
| Payments | A Stripe button on the happy path | Webhooks, retries, failed cards, refunds, receipts |
| Error states | Console logs | Empty states, error boundaries, retry, offline |
| Security | Open tables | Row-level security, rate limiting, input validation |
| None | Transactional email that reliably lands | |
| SEO | Client-rendered, invisible to Google | Prerendered per route, unique titles and meta |
| Mobile | Looks fine on the founder's laptop | Tested down to 375px |
| Ops | It's on someone's laptop | CI deploy, rollback, backups, error monitoring |
| Legal | Missing | Terms, privacy, cookie handling |
Read the proof, not the numbers
Agency ads love portfolio-level statistics: products shipped, funding raised, companies acquired. Funding raised is a fact about the clients, not about the builder. A studio that worked with founders during a bull market will have a large number next to it regardless of build quality, and the founders who raised would tell you the raise came from traction, timing and their own network.
Better questions to ask any shop before you sign:
- Who owns the repository and the accounts on day one?
- What specifically happens on day 15 — is there a handoff document, or does the relationship just end?
- If the deadline slips, what do I get back, in writing?
- Can I see a live URL of a product you shipped, not a screen recording?
- What is explicitly out of scope for the quoted price?
When two weeks is exactly right
Two weeks is the correct call when you need to validate one specific assumption, when you have a funding or design-partner meeting on a date you cannot move, or when the idea is cheap enough to kill that spending more would be waste. It is the wrong call when you already have paying users waiting, when the product handles money or personal data from day one, or when you will be the one maintaining it and cannot read the code you were handed.
How we scope it
We have completed 80 jobs on Upwork. There are three entry points:
Strategy Audit
$499A one-hour scoping call, a written technical roadmap and a feature prioritisation matrix, credited toward any build, so you can take the roadmap elsewhere if you want.
Founding Client
$2,999A 14-day build with a full refund if we miss the deadline.
Publishable MVP
$4,999The complete production-ready build that ships ready to publish, with auth, payments, dashboard and core features end-to-end.
The refund is the point: a deadline promise only means something when there is money attached to it.
If you want to know which scope fits what you are trying to prove, start with a short conversation. Book the free 20-min intro call