Launching a startup MVP — without the six-month fantasy
A pragmatic guide to shipping your first version in 4 weeks. What to cut, what to keep, and why your MVP isn't your product.
Every founder I've talked to has a version of the same story: the MVP was supposed to take two months. It took seven. Half the features in it were never used, two of the three things that actually mattered got cut for time, and the launch was a whimper instead of a bang.
The problem isn't ambition — it's that "MVP" has quietly become a euphemism for "v1 of the product", and v1 of a product is a much bigger thing than the word "minimum" suggests.
This guide is the way I wish someone had explained it to me the first time. It's opinionated, it's short, and it assumes you want to ship something real within a month.
What MVP actually means
An MVP is the smallest thing you can build that lets you learn whether your idea is worth pursuing. It is not the first version of the polished product. It is an experiment.
That framing changes everything. If the goal is to learn, then:
- You don't need real auth if you can hand-create accounts for test users.
- You don't need an admin panel if you can use the database console.
- You don't need billing if you can invoice the first three customers manually.
- You don't need email if your existing inbox works.
Every one of those things will exist in v1 of the product. None of them need to exist in the MVP.
If the goal is to learn whether people want what you're building, the only features that matter are the ones that deliver the thing people want.
The four-week shape
Here's how we structure an MVP build at Studio Club tier — roughly Startup-tier in our subscription lineup.
Week 1 — Setup
- Kickoff call
- Brief locked in
- Domain + email configured
- Staging environment live
- Design direction agreed
This is the week that feels like nothing is happening. It is. The work is in making sure we don't ship the wrong thing.
Week 2 — Skeleton
- Core page structure
- Navigation
- Primary "happy path" end to end (even if ugly)
- First round of content in place
By end of week 2 you should be able to load the site on your phone and walk through the main thing it does. It'll look rough. That's fine.
Week 3 — Substance
- Design polish
- Responsive passes
- Real integrations (forms, analytics, email, whatever's core)
- Content filled in
- Performance budget met
Week 4 — Ship
- QA pass across browsers + devices
- Content review
- DNS cutover
- 14-day polish window begins
The polish window is important. No launch is a hard edge — you keep tweaking for two weeks after go-live, and we include that time in the tier.
What to cut
A non-exhaustive list of things I routinely cut from an MVP:
- Multiple user roles. Just make everyone an admin at first. Role logic is high-complexity, low-learning.
- Sophisticated onboarding. A text email explaining how to use the thing is fine for your first five users.
- Account settings. If a user wants their name changed, just change it for them. You'll have eight users.
- Marketing pages beyond the essentials. Home + one pricing page is enough. Blog, FAQ, About Us can wait.
- Analytics dashboards for the admin. A SQL query you run once a week is sufficient for the first month.
What not to cut
The inverse list — things that feel safe to cut but rarely are:
- Trust signals. Even for an MVP, people won't sign up if your copy feels sketchy or there's no indication who's behind it. Spend an afternoon writing a clear About block.
- Basic security. HTTPS, rate limiting on signup, proper password hashing. These are table stakes, not nice-to-haves.
- A way to collect feedback. An email address in the footer, a Cal.com link, something that gets you direct input from the first users.
- A way to charge money, if that's the model. You don't need Stripe Checkout on day one, but you need a way to take payment, because free users and paying users behave differently.
The month after
This is the part guides tend to skip: what happens after the MVP ships.
Roughly: you'll have opinions from your first ten users within two weeks of launch, and those opinions will matter a lot. Half of them will surprise you. Some of them will contradict your original brief.
The best pattern I've seen: give yourself a month of minimal feature work after launch. Don't build anything new. Just talk to users, fix the confusions that keep coming up, tweak the flows they get stuck in. Then, after a month of that, you have enough signal to know what v2 should actually be.
The MVP isn't the product. The MVP is how you figure out what the product is.
Picking a plan
For most MVPs in the 4-6 week range, Startup Club (R4,000/mo) is the sweet spot — a proper marketing site with the integrations real businesses need. If there's a real app involved with auth, data, or custom software, Studio Club (R8,000/mo) or Enterprise Club (R20,000/mo) is where to land.
Whatever you pick, the first month gets you from brief to launch. Month two is polish + the first real users. Month three is where you decide what to build next — and you can always switch tiers at that point if the answer is "more than we thought".
Cheers, — Daniel