Picking Up Where We Left Off
In Part 1, we covered the two stages that come before you build anything real. The demo, which convinces people your idea is worth wanting, and the prototype, which shows them it works the way they’d expect. Together they let you test a concept while it’s still just a representation, cheap to change and quick to throw away. (New here? Start with Part 1.)
Now the idea gets real. This part covers the MVP and the full product, the stages where your concept becomes working software people can use and pay for. The same principle carries through: each stage answers a question before you spend the money to answer the next.
What Is an MVP
A minimum viable product is the first fully working version of your product, built with only its most essential features. This is where it separates from everything before it. A demo shows the idea and a prototype tests it, but an MVP actually works. Real users can pick it up and experience its value for themselves.
Companies build MVPs to answer the question that matters most before pouring money into full development: are people ready to use this, and pay for it? You launch a small, real version, and the market tells you the truth.
An MVP earns its place when you need to:
- Get to market fast without waiting on a finished product.
- Enter on a small budget, proving the idea before you’ve spent heavily building it.
- Gather high-quality feedback from early adopters who are using the real thing, not imagining it.
- Test whether the product holds up against actual demand in the market.
An MVP turns opinion into evidence. Everything up to this point tells you what people think they want; the MVP shows you what they’ll actually use and pay for.
Designing an MVP
Where a demo or prototype might take a few weeks, an MVP usually takes several months. That’s because it isn’t a sketch or a pitch. It’s a real product built to prove the core idea and show you how people actually interact with it, which is slower work and more valuable for it.
Building one follows a clear path:
- Research the market and your competitors so you know the landscape you’re entering.
- Interview potential and current users to pin down their real problems, needs, and expectations.
- Map how people will use it, defining the usage flows and customer journeys from first touch to finished task.
- Test your team’s assumptions against real users, not against each other.
- Design only the essential features using wireframes and prototypes.
- Organize your visual elements into a shared design system so everything stays consistent as the build grows.
Each step exists to reduce what you’re guessing at. By the time you write the first line of production code, the market research, the interviews, and the testing have already told you most of what the product needs to be.
What Is a Full Product
A full product goes past the basics to give customers more than they expected. It’s the step that comes after the MVP has done its job. Once your MVP proves feasible, and the feedback shows people don’t just like it but will pay for it, you’ve earned the green light to build it out.
Moving beyond an MVP means the work never quite stops. You keep improving the offering in small, steady iterations, shaped by what real customers show you they need as they use it.
Designing a Full Product
Once your MVP is live, users start handing you the roadmap. Their feedback, often with suggestions attached, tells you what the product needs to become. The design work from here is a loop, not a line:
- Gather feedback with your designers, through user interviews and by reading support tickets, to find the obstacles people actually hit.
- Brainstorm solutions to the problems that surface, before committing to any one of them.
- Turn the best ideas into a working prototype your designers can put in front of people.
- Test that prototype with users, measuring what works and what still needs improvement.
- Run the loop again, refining each cycle so the product moves steadily closer to its finished form.
The product is never quite finished, and that’s the point. Each pass through the loop is shaped by real people using the real thing, which is how a good product keeps earning its place instead of drifting away from what its customers need.
Bringing It All Together
You don’t have to start with an MVP. It’s a common assumption, but the smarter path usually runs through the earlier stages first, and in a deliberate order. Each one answers a question before you spend the money to answer the next.
Here’s how the sequence tends to work:
- Start with prototypes. Build a few versions of the idea and show them to as many potential customers as you can. Their feedback tells you which version solves the real problem best.
- Move to a demo. Pair the strongest version with a commercial proposal and put it in front of potential customers to see if they’d pay, and in front of investors if you need funding to keep going.
- Build the MVP. Once you have a base of customers willing to pay, a minimum viable product tests how the market actually responds to the real thing.
- Grow into the full product. If people start buying, you keep building, shaping the complete product around what your customers show you they want.
Each stage exists to make the next one less of a gamble. Demo, prototype, MVP, and full product aren’t competing choices. They’re steps on the same path, and taking them in order is how an idea becomes a product people are glad to pay for.
If you’re somewhere on that path already, with a prototype that proved the idea or an MVP that’s outgrowing the tools it was built with, that’s the point where a professionally developed product turns early traction into something built to scale.