What did you deliberately leave out of your MVP?
I’ve been thinking about MVPs a bit differently lately.
Most people talk about what they managed to build.
I’m more interested in what they deliberately decided NOT to build.
AI makes it really easy to keep adding things now.
Notifications? Sure.
Analytics? Why not.
Team accounts? Easy enough.
Another integration? Add it.
But at some point “easy to build” starts getting confused with “needed right now.”
If you’ve launched something before:
What’s one feature you were convinced belonged in v1, but you intentionally left out?
And did you ever come back and build it later?
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?
Really good writeup, thanks for sharing it. What's the next thing you're planning to try here?
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?
Clear and practical, thanks. Did anything surprise you along the way?
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?
Clear and practical, thanks. Did anything surprise you along the way?
Yeah — how different “working” can mean between tools surprised me.
We recently gave the same booking-app prompt to nine builders. Five produced something usable, but only Bolt and Base44 actually rejected a second booking at the server. One of the prettier outputs even allowed the same slot to be booked twice.
That made me think a lot more about what belongs in an MVP versus what just makes it look complete.
We documented the test here:
https://built.new/learn/no-code-app-builders-tested/
Nice progress. What is the next thing you are focusing on?
Right now I’m more interested in the decisions around the first version than adding more features.
What absolutely needs to exist, what can wait, and what the first real users should actually teach us.
I think getting that part right is more valuable than making v1 look bigger.
Interesting take. Would you still recommend this approach to someone starting today?
Definitely.
If anything, I think it matters more now because AI makes adding features almost frictionless.
The danger isn’t that you can’t build enough anymore. It’s that you can build too much before you’ve learned whether the core thing matters.
I’d rather ship one complete workflow and learn from it than launch ten half-tested assumptions.
Really relatable. How much time do you put into this each week?
It varies quite a bit depending on what we’re working on that week.
I try to spend less time just producing more and more, and more time looking at what people are actually asking, testing assumptions, and turning that into something useful.