Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Join
3
Likes
0
Bookmarks
2
Comments
Report
How many iterations should be done for your MVP before the Product Launch
by
Paul-Simon Emechebe
I've heard three iterations is the sweet spot.
Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing
111 comments
The coordination tax: six years watching a one-day feature take four months
73 comments
My users are making my product better without knowing it. Here's how I designed that.
63 comments
A simple LinkedIn prospecting trick that improved our lead quality
50 comments
I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer?
39 comments
Why I built a SaaS for online front-end projects that need more than a playground
15 comments
There is no special launch. when you finish your first iteration and get feedback from one or more potential customers that was the launch. after that you improve, get feedback, learn, improve further until you either give up or are a big enterprise 😅
Matthias is correct, there's definitely no right amount of refinement.
What is an MVP there to do? Allow you to prove you have the solution to a problem worth solving, that people will pay for.
Before you create an MVP make sure you spell out your objectives and what you're trying to achieve, what evidence you need to consider that MVP a success worth investing more time and effort into. Keep refining until you get that.
Bonus: Don't just write out success criteria, but define failure criteria. What evidence if obtained would highlight this is not the right idea. Don't fall prey to confirmation bias.