The short answer
but here's what i've learned building products for founders since i was 21, the things that get built in 48 hours are usually shells. auth, a landing page, stripe wired in. " not actually testable with real users who have real problems.
The short version
a founder slid into my dms on a wednesday. investor meeting locked for 14 days out. a notion doc, a loom walkthrough, and a cold sweat.
i read it twice and didn't reply until morning.
not because i wasn't interested, because i wanted to be honest before i was encouraging.
the question everyone asks when they're in that position is: can you actually launch an MVP in 2 weeks in 2025? and the real answer is: it depends entirely on what you mean by "MVP" and how much of your ego is attached to the feature list.
the promise everyone's selling and the reality nobody talks about
there are services out there promising a working SaaS in 24 hours. an MVP in 48. a full product over a weekend.
some of them are real.
but here's what i've learned building products for founders since i was 21, the things that get built in 48 hours are usually shells. auth, a landing page, stripe wired in. technically "working." not actually testable with real users who have real problems.
i'm not saying that's worthless. for some founders, a shell is exactly what they need to show momentum to an investor or collect emails before they build anything.
but if you're asking whether you can launch an MVP in 2 weeks that actually validates your core hypothesis with real users, yes, that's possible. i've done it. we've done it at ApexStack. but the path to getting there requires making one decision before anything else.
the decision that makes or breaks a 2-week build
scope isn't a planning exercise. it's a values test.
every founder i've worked with says they've already cut the scope. then we get on a call and there are still seven features on the list. a dashboard. an admin panel. three user roles. an onboarding flow with email sequences.
i thought founders were just bad at scoping. i was wrong. the real issue is that most founders haven't decided what question they're actually trying to answer.
an MVP isn't a small product. it's a specific answer to a specific question.
"will people pay for this?" is a different question than "can users complete this workflow without help?" those require different builds. and until you know which question you're testing, you'll keep adding features that feel necessary but aren't.
before any build starts, write one sentence: this MVP exists to find out if [specific person] will [specific action].
if you can't write that sentence, you're not ready to build yet. and that's fine. But you should know it before you pay anyone.
what actually fits in 2 weeks
i'll be direct about what's buildable in 14 days by a focused team using modern tooling.
Frequently asked questions
- what fits
- a single core workflow, end to end. one user type. one primary action. real data, not dummy content. basic auth. a deployable link you can put in front of real people.
- what doesn't fit
- multi-role permission systems. billing with multiple plans and upgrade flows. mobile apps alongside a web app. integrations with more than one external service. anything that requires a compliance review.
Talking about mvp development?
The smallest build that answers a real question about your market — with the emphasis genuinely on minimum.