What has to ship in a first version, what each line costs at 2026 rates, and the four things founders keep paying for that don't help them find their first customers.
An MVP costs $25,000 to $60,000 with a senior team billing $60 to $90 an hour: roughly 400 to 800 hours of work over 6 to 12 weeks. At US agency rates of $120 to $250 an hour the same build is $55,000 to $120,000. Under $15,000 is possible with no-code tools or a junior offshore team, and both tend to come with a rebuild bill within a year. What moves the number isn't the rate, it's what founders put on the list. Below is what has to ship, what it costs line by line, and the four things people pay for that they shouldn't.
What an MVP has to ship
The word "minimum" gets argued about endlessly. In practice the list is short and it's the same on almost every product we've built:
- Sign-up, login and password reset that work on a phone.
- One core workflow, end to end. The thing the customer would pay for, and nothing beside it.
- One way to pay. A monthly plan through Stripe Checkout, one currency.
- Email that arrives: verification, receipts, the password reset above.
- A basic admin screen so you can see users, refund someone and log in as them when they report a problem.
- A handful of tracked events, so week two is decided by data and not by opinion.
- A deployment pipeline with backups, and the terms and privacy pages the payment provider will ask for.
Everything else is a version two feature until a paying customer says otherwise.
The cost, line by line
These hours are our estimates from the MVPs we've shipped, not a measured industry average. The core workflow row is the one that moves; the rest barely changes between products.
| Line | Hours | At $75 an hour |
|---|---|---|
| Define: scope, flows, data model | 20 to 40 | $1,500 to $3,000 |
| Design: wireframes to screens | 40 to 80 | $3,000 to $6,000 |
| Accounts and login | 30 to 60 | $2,250 to $4,500 |
| The core workflow | 150 to 350 | $11,250 to $26,250 |
| One billing path | 30 to 60 | $2,250 to $4,500 |
| Email and notifications | 15 to 30 | $1,125 to $2,250 |
| Basic admin | 30 to 50 | $2,250 to $3,750 |
| Event tracking | 10 to 20 | $750 to $1,500 |
| QA, deployment, launch | 40 to 80 | $3,000 to $6,000 |
| Total | 365 to 770 | $27,375 to $57,750 |
Published guides for 2026 put a typical MVP at 500 to 1,000 billable hours over 8 to 12 weeks with two or three developers, which lines up with the top of this table. The bottom of it is a product with one tight workflow and a founder who says no a lot.
Where the rate comes from
Hourly rates published by agencies and contractors this year: $120 to $250 for senior developers in the US, $90 to $180 in the UK, $45 to $90 in Eastern Europe and $30 to $65 in South Asia. Multiply the table by your rate and you have your range.
One warning about the low end. A team that has shipped Stripe billing before does that row in 30 hours. A team learning it on your project does it in 90 and gets a webhook wrong. Cheap hours that turn into more hours aren't cheap.
What running it costs before revenue
The monthly bill for a launched MVP at 2026 list prices: Laravel Forge from $12 a month plus a $24 to $48 server, Sentry for error tracking at $26, Postmark for email at $15 per 10,000 messages, and a Figma seat at $16 if you keep a designer around. Call it $100 to $150 a month, and a managed database adds about $53 when you need one. Stripe then takes 2.9% plus 30 cents per US card payment, or 1.5% plus 20p in the UK.
The four things founders pay for and shouldn't
1. Native iOS and Android apps in version one
Two more codebases, or one cross-platform one, on top of the web app. Apple's developer programme is $99 a year, Google Play is $25 once, and both stores take 15% to 30% of anything sold inside the app. Then there's review: a rejected build costs you a week. A responsive web app covers most first customers, and the day someone asks for an app you'll know which three screens it needs. In our experience this one line is the difference between a 10-week launch and a 20-week one.
2. Scale engineering for users you don't have
Microservices, Kubernetes, multi-region databases, a message queue for every event. A single $48 server running a well-built Laravel app serves thousands of daily users without noticing. The time to split things up is when a graph tells you to, not when a deck does.
3. A custom design system before anyone has used the product
Senior product designers charge $120 to $200 an hour, and a bespoke design language is 100 hours or more before a single screen is built. Use a solid component library, put one mid-level designer on it for 40 to 80 hours to make the core workflow clear, and spend the branding budget after you've watched ten people use it. The screens will change anyway.
4. Enterprise features before an enterprise customer
Single sign-on runs $125 a month per connection at WorkOS. A SOC 2 Type 1 audit costs $28,000 to $58,000 all-in. A permissions matrix with custom roles is a fortnight of work. All of it is easy to add when a customer with a purchase order asks for it, and all of it is dead weight until then. Keep the door open (role-based access, an audit log, encrypted backups) and leave the rest.
What about no-code?
We build code, so read this knowing that. Bubble's Starter plan is $32 a month on monthly billing, Growth is $134, and each plan includes a fixed pool of workload units (175,000 on Starter) with overage at about $0.30 per thousand. For testing whether anyone wants the thing, that's a good deal and we'd tell you to take it.
The ceiling shows up in three places: billing edge cases (proration, failed payments, refunds), performance once real usage eats the workload units, and export. The database and logic live inside the platform, so moving off it means rebuilding, not migrating. If your MVP is a demand test, go no-code. If it's the first version of the product you'll run for five years, build it.
How to keep the number fixed
The biggest cost risk in an MVP isn't the rate, it's the scope drifting for three months. Our fix is boring: week one ends with a written scope and a fixed price. If a feature isn't on that page it's in version two, and the founder sees working software every week from week two, so there's no eight-week silence followed by a surprise.
Ask for the same from anyone you hire. A quote with a range and no scope is a quote for whatever it turns out to cost.
A worked example
An illustrative build so the arithmetic is visible: a booking and payment tool for mobile dog groomers. Define 30 hours, design 60, accounts 40, core workflow (availability, booking, reminders) 240, billing 40, email 20, admin 40, tracking 15, QA and launch 60. That's 545 hours: $40,875 at $75 an hour, live in about ten weeks with a team of three, running at about $130 a month. The founder wanted an iOS app in version one. Leaving it out saved roughly 300 hours, about $22,500, and the first 40 customers booked from their phones through the web app anyway.
If you want this table filled in for your idea, see how we take an MVP from idea to launch and book a 30-minute call. You'll leave with a scope and a fixed price. And when the first version is earning, the full SaaS build is the same team adding the next layer.
Questions founders ask before they commit
How much does an MVP cost in 2026?
$25,000 to $60,000 with a senior team at $60 to $90 an hour, based on 400 to 800 hours. US agency rates of $120 to $250 an hour put the same build at $55,000 to $120,000. The core workflow is the line that moves; accounts, billing, email and admin cost about the same on every product.
How long does an MVP take to build?
6 to 12 weeks with a team of two or three, provided the scope is fixed in week one and there's one core workflow. Plans that run longer usually include a native app or features for customers who don't exist yet.
Can I build an MVP for $10,000?
Yes, with no-code tools or a junior offshore team, and it's a fair way to test demand. Be clear with yourself that it's a test. The billing edge cases, performance and data export are where those builds run out, and most get rebuilt within a year.
What should an MVP include?
Login, one core workflow end to end, one way to pay, email that arrives, a basic admin screen, a few tracked events, and a deployment with backups. That's the whole list. Everything else waits for a paying customer to ask.
Should I build the mobile app first?
Almost never. A responsive web app reaches every phone on day one with no store review, no $99 a year Apple fee and no 15% to 30% commission on in-app payments. Build the native app when customers tell you which three screens they'd use on the move.
What does it cost after launch?
Hosting, email and error tracking come to about $100 to $150 a month at 2026 prices, plus Stripe's fees on each payment. Budget 15% to 20% of the build cost per year for maintenance and the small changes your first customers will ask for.
