Product
From Idea to MVP: A Practical Guide for Founders
A clear, opinionated playbook for taking a software idea from a Friday-night conversation to a working MVP in twelve weeks.
If you're a founder reading this, you probably don't have a shortage of ideas. You have a shortage of time, focus, and signal. This guide is for cutting through that.
What an MVP actually is
An MVP isn't a half-finished version of the full product. It's the smallest thing you can ship that produces real, measurable learning about whether your idea is worth pursuing.
The mistake most teams make is shipping a small thing that looks like a real product. The better move is shipping a focused thing that answers a question.
The 12-week shape
A good MVP roadmap roughly looks like this:
| Weeks | Focus | | --- | --- | | 1–2 | Discovery, customer interviews, scope definition | | 3–4 | Information architecture, wireframes, technical spike | | 5–9 | Build the core loop | | 10–11 | Polish, instrumentation, internal testing | | 12 | Launch to a small, motivated set of users |
The weeks aren't sacred. The sequence is.
Three things to never compromise
- A genuine user. Not friends. Not investors. Someone who would pay for this.
- Instrumentation. If you can't measure what's happening, you can't learn from it.
- A clear exit criterion. Decide in advance what would cause you to pivot or stop.
The trap of "founder mode"
The work of building a product is mostly the work of saying no — to features, to opinions, to good ideas that aren't this good idea.
It's tempting to keep adding things until the MVP becomes "the product". Resist. Every feature you add before launch is a feature you can't learn from.
When you're ready to build
If you're at the stage where you have an idea, conviction, and a willingness to put it in front of real users, we'd love to be your partner. Get in touch — we usually start with a 30-minute call.
