1
0 Comments

If your MVP took 4+ months, it’s probably not an MVP

I know this will get pushback, but hear me out.

If your “MVP” took 4–6 months, chances are, it’s way too much. Not intentionally bad, just… overbuilt.

I’ve been there myself. You justify it: “We need proper architecture.” “It has to scale.” “We don’t want tech debt.” All reasonable, right? But together, they add months before you even see real feedback.

One of the fastest MVPs I’ve seen shipped in just two weeks. Half the backend was mocked. It was messy. People hated some parts. But it gave clear answers almost immediately — far faster than the “perfect” approach.

So here’s my question: how do you personally decide when your MVP is enough, and when you’re overdoing it?

on April 15, 2026
Trending on Indie Hackers
I built a tool that shows what a contract could cost you before signing User Avatar 118 comments The coordination tax: six years watching a one-day feature take four months User Avatar 76 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 65 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 54 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments Why I built a SaaS for online front-end projects that need more than a playground User Avatar 18 comments