The Lie We All Agreed To Tell Each Other
MVP. Minimum Viable Product. The word minimum is right there, doing nothing.
Ask any founder how long their MVP took. Three months. Five months. Eight months and a pivot. The word minimum has been stretched so far it no longer means anything. It's a comfort word now — something you say so the scope doesn't feel embarrassing.
I timed mine. Every session, every feature, every rabbit hole. What I found made me uncomfortable enough to write this.
What I Was Building
Syra — an AI-powered idea validation tool. The core premise: founders pick the wrong ideas, build for months, then discover too late there's no real demand. Syra returns a build / kill / wait verdict backed by a real 48-hour proof test — not a guess, not a vibe.
Scope going in: a backend, a frontend, some LLM calls. Should be fast.
It was not fast.
The Timer
I tracked every work session with a simple log. Category, duration, notes.
Here's where the hours actually went:
| Category | Time Spent |
|---|---|
| Core backend + API | 38 hrs |
| Prompt engineering | 24 hrs |
| Frontend (UI/UX) | 61 hrs |
| Auth + Security | 14 hrs |
| Testing + edge cases | 11 hrs |
| Copy, positioning, naming | 9 hrs |
| Launch prep (PH assets, etc.) | 8 hrs |
| Total | 165 hrs |
165 hours. For an MVP.
Where I Thought It Would Go
I estimated maybe 60–70 hours. One good month of evenings and weekends.
The frontend alone was over 9,000 lines. Custom-built. No component library. Every interaction deliberate. That wasn't in the plan — it became the plan because I couldn't ship something that felt wrong.
That's the trap.
The Real Culprit: Scope Doesn't Creep. Standards Do.
Everyone talks about scope creep like it's features sneaking into the backlog. That's not what happened to me.
The features were locked. What expanded was my standard for what "done" meant.
- The verdict color system had to be reactive — green, red, amber shifting with the output.
- The fonts had to feel like a product, not a portfolio project.
- The prompts had to return falsifiable claims, not optimistic fluff.
None of that was in the spec. All of it was right.
This is the thing nobody tells you: the minimum in MVP is a moving target anchored to your taste.
What Actually Qualifies As Minimum
Here's the test I wish I'd used from day one:
Does removing this break the core promise of the product?
If yes — keep it. If no — kill it, or defer it.
The core promise of Syra was: give founders a clear verdict fast, with a real test behind it.
The verdict-reactive color system? Doesn't break the promise. Could've shipped without it.
The parallel async pipeline that cuts response time in half? Breaks the promise if removed. Essential.
The custom About page narrative? Beautiful. Week two, not week one.
Most of those 165 hours were spent on things that didn't break the core promise. They made the product better — but they weren't minimum.
The Honest Verdict
Here's what I actually built in 165 hours:
- A FastAPI backend with multi-LLM orchestration (Groq as a cost gate before OpenAI)
- Parallel async architecture for Quick Mode
- JWT + CSRF + Argon2 security stack
- A full custom frontend (~9,000 lines)
- Two distinct modes: Quick Mode (48hr test + verdict) and Deep Mode (full strategic analysis)
- A Product Hunt launch
Was any of that unnecessary? Individually, no.
Collectively? I built a V1.5 and called it an MVP.
The verdict on myself: guilty.
What I'd Do Differently
1. Write the core promise in one sentence before touching code.
Mine: "Return a build/kill/wait verdict with a real test behind it in under 2 minutes." Everything that doesn't serve that sentence is post-launch.
2. Set a hard hour budget, not a feature list.
Feature lists expand. Hour budgets force prioritization.
3. Ship the ugly version first to one person.
Not Product Hunt. One founder. Watch them use it. Build from what breaks, not from what bothers you aesthetically.
4. Treat taste like technical debt.
It's real, it matters, and it should be paid down in sprints — not front-loaded into launch.
Why It Was Still Worth It
Syra launched on Product Hunt on April 13th. It didn't win the day. It did get return users, unprompted shares, and payment requests — which are the only signals that actually matter.
The product is tight. The positioning is sharp. The UX doesn't embarrass me.
Would a scrappier version have told me the same things? Probably. Would I have believed them? Probably not.
Sometimes you build the real thing to trust the signal.
The Actual Minimum
The minimum isn't a feature count. It's a signal threshold.
You need just enough product to generate a signal you can trust.
Everything beyond that is a bet — sometimes a good one, sometimes not. Know which one you're making.
I'm Yogya — solo founder and full-stack developer. Building Syra and writing about what actually happens when you ship alone. My Portfolio: Yogya