What I Learned Shipping 20+ MVPs (Lessons from a Founder-Led Studio)

Hourly billing punishes the founder for asking questions. Fixed pricing punishes the developer for sloppy scoping. Fixed pricing wins because the discipline of scoping precisely is where most of the project's value gets created - both sides are forced to think hard before code starts.

Founders sometimes push back on fixed pricing thinking they'll "lose" if the project goes faster than expected. That's the wrong frame. The fixed price reflects the value of the deliverable, not the hours spent. A 4-week MVP that ships in 3 weeks is more valuable to the founder, not less.

20+ projects in, I've never regretted a fixed-price engagement. I've regretted the few I quoted hourly to start.

It almost never feels like scope creep in the moment. "Just one more screen." "Can we also add notifications?" "What if we let users export to PDF?" Each one is small. Cumulatively, they push the launch by 2-4 weeks.

The fix is process, not willpower. Every new request goes in a v2 doc. If something is genuinely critical that wasn't scoped, we agree on a fixed change-order fee in writing before any new code. The friction of writing it down is enough to filter out 80% of additions.

Founders who ship are the ones who say "v2" more than they say "can we add."

Every project's biggest variance isn't the developer's velocity. It's the founder's response time. "I'll get back to you on the auth flow" said on Monday becomes a Friday email. That delay alone costs a feature.

Founders who ship are the ones who answer Slack within hours, not days. They review staging URLs the day they're sent, not the week they're sent. They make decisions in 5-minute calls, not 5-day async threads.

Communication norms matter as much as feature scope. If your developer asks a yes/no question, give them yes or no within 6 hours. The cumulative effect across a 6-week build is enormous.

I've shipped MVPs that were beautiful, well-architected, and hit zero users. I've shipped MVPs that were rough, opinionated, and grew quickly. The difference was always the founder's pre-launch user work, not the build quality.

Founders who shipped 0-1 should be doing user discovery during the build. Walk 5 prospective users through the staging URL in week 4. Note their words. The launch tweet copy and the onboarding microcopy should use those words verbatim.

Code is the easy part. Finding users who care is the hard part. The build doesn't fix that.

The polish phase - week 5 in a 6-week build - takes longer than founders intuit. Empty states, loading states, error messages, edge cases, real copy in every screen. None of it is feature work, and all of it is required.

I budget polish at 25-30% of total project time. Founders often imagine polish at 10%. The difference is what "polished" means - functional polish (everything works, no broken states) vs aesthetic polish (animations, micro-interactions, brand consistency). MVPs need functional polish; aesthetic polish can wait for v1.5.

If your developer says "week 5 is polish," they mean it. Don't try to squeeze extra features into that week.

Of the 20+ projects shipped, exactly 0 founders looked back and said "I should have hired an agency for $30K-$100K instead." Many said the opposite - they had hired an agency previously, gotten burned, and came to a solo studio after.

Agencies are optimized for billable hours and multi-team coordination. MVPs are optimized for ruthlessness. The two structures don't align. The same product output costs 5-20x more at an agency for structural reasons (PMs, juniors, overhead) that have nothing to do with code quality.

If you're a non-technical founder considering an agency for a 4-6 week MVP, you're almost certainly overpaying for overhead you don't need. Pick a founder-led studio or a senior freelancer instead.

Every project ships with: README, deployment runbook, environment variable docs, architecture overview, post-launch maintenance notes. Not because clients ask - they usually don't - but because the next developer (the founder might hire) needs them.

I've inherited too many projects from agencies and freelancers where the docs were a single README that said "npm install." Don't accept that. Real handoff includes real docs. It's part of the engagement.

If a builder won't include docs in the fixed scope, that's a red flag. The cost of writing docs at the end is small; the cost of not having them is enormous.

30 minutes on a video call decides whether the project succeeds. Not because of magic - because that's when scope is locked, expectations are aligned, and the founder gets a real read on whether the developer can ship.

Founders who ship are the ones who come prepared to the discovery call: 1-page spec, target user clear, success metric defined, budget written down. The call is for clarifications and trade-offs, not for figuring out what they're building.

Founders who stall are the ones who arrive with "I have an idea, what do you think?" The developer can't scope on a feeling. They need words.

I always recommend hiring a designer for the long-term product. For MVP stage, a senior developer with design taste can usually carry it - especially with modern tools (Tailwind, shadcn/ui, Framer Motion). The MVP needs to look professional, not bespoke.

Founders who insist on a custom designer for the MVP often add 2-3 weeks to the timeline. The design becomes a bottleneck the developer waits on. By v1.5, the design is irrelevant anyway because the founder has learned what users actually want.

Pragmatic move: ship the MVP with a developer-led design (clean, modern, slightly generic). Hire a designer in v1.5 when you have user signal to design against.

The day the MVP launches is day 1 of the real work. Founders who think launch = done are setting up for disappointment. Launch is when you finally get the data to know what to build next.

I include 2 weeks of post-launch support specifically because that's when the real bugs surface. Real users do unpredictable things. Real loads expose performance issues a staging environment never showed. The 2 weeks aren't a generosity - they're a structural part of the engagement.

After 20+ MVPs, the pattern is consistent: the ones that succeeded long-term were the ones where the founder treated launch as a starting line, not a finish line.