When did you know your MVP was ready to ship?
I think “ready” is one of the hardest words in product building.
There’s always one more thing you could fix.
One more screen.
One more edge case.
One more integration.
One more feature that would make the product feel more complete.
But at some point, keeping it private teaches you less than putting it in front of real people.
So I’m curious:
What was the moment you decided your MVP was ready to ship?
Was it a checklist?
A deadline?
A specific core flow finally working?
Or did you just reach the point where more building wasn’t teaching you anything?
Interesting. How are you measuring whether it is working?
Curious how long it took before you saw the first real results?
What made you pick this stack over the alternatives?
Good point. Did you test that with users before committing to it?
Appreciate the honesty here, most people only share the wins.
Curious how long it took before you saw the first real results?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
For me, it’s ready when the main problem is solved and people can actually use it. If you keep waiting for everything to be perfect, you might never end up shipping it.
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Thanks for sharing the numbers, that makes it much easier to follow.
Interesting take. Would you still recommend this approach to someone starting today?
Appreciate the honesty here, most people only share the wins.
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Good write-up. What would you do differently if you started again?
Interesting approach. What was the hardest part to get right?
Interesting take. Would you still recommend this approach to someone starting today?
Nice, this makes a lot of sense. What's been the most surprising part of it so far?
Makes sense. Are you planning to charge for it, or keep it free for now?
Makes sense. Are you planning to charge for it, or keep it free for now?
Makes sense. Are you planning to charge for it, or keep it free for now?
When I could use it myself every day without hitting a wall. Not when it looked finished.
Makes sense. Are you planning to charge for it, or keep it free for now?
Clear and practical, thanks. Did anything surprise you along the way?
Interesting approach. What was the hardest part to get right?
Great breakdown. What feedback have you had from early users?
Clear and practical, thanks. Did anything surprise you along the way?
Clear and practical, thanks. Did anything surprise you along the way?
Nice work shipping it. What has been the biggest challenge since launch?
Great breakdown. What feedback have you had from early users?
deadline did it. one flow that actually did the job, no extras. if you need a checklist you're stalling. put it in front of people before it feels ready.
Yeah, I like that framing. “One flow that actually does the job” is probably a better shipping test than a huge checklist.
Especially now that AI makes it so easy to add “just one more thing.” A deadline almost forces you to separate what the product needs from what would simply be nice to have.
Ship the core, then let real usage decide what earns its way in next.