What Does an MVP Actually Cost? A Realistic Breakdown

The most common question I get from founders before we start any serious conversation is some version of: "So what would something like this cost?" It's a fair question, but it's also one that's almost impossible to answer without pushing back a little first.

MVP development cost isn't a single number. It's the output of a handful of decisions, most of which founders haven't made yet when they ask. This post is my attempt to make those decisions visible, so you walk into any conversation with a developer or agency knowing what drives the number, and what you can control.

Why Quotes Vary So Wildly

You might get one quote for €8,000 and another for €80,000 for what feels like the same project. That gap isn't just developer greed or freelancer inexperience. It usually comes down to three things: scope interpretation, tech stack choice, and who's doing the work.

When you describe your idea verbally, two developers will picture two different products. One imagines a bare-bones prototype with a handful of screens. The other imagines a polished, production-ready application with user authentication, payment processing, an admin dashboard, and email notifications. Neither of them is wrong. They just filled in your gaps differently.

This is why getting a quote before writing a spec is almost always a waste of everyone's time.

Breaking Down What You're Actually Paying For

Let me split a typical MVP into its real components, with rough cost ranges based on what I've seen in practice. These are freelancer rates at European market pricing. Agency quotes will run two to three times higher for equivalent scope.

Authentication and user accounts (login, registration, password reset) is table stakes for most products. If you're using an existing solution like Devise in Rails or NextAuth in a Next.js app, this is largely boilerplate. Expect €500–€1,500 depending on complexity, more if you need OAuth (Google/GitHub login) or role-based access from day one.

Core feature set is where most of the budget lives. This is whatever makes your product actually do the thing it's supposed to do. For a simple CRUD application (think a booking tool, a job board, or a client portal), you're looking at €3,000–€8,000. If the central feature involves something like real-time updates, third-party API integrations, or complex data processing, that number climbs.

Basic UI/UX covers making it usable without making it beautiful. A functional interface using a component library like Tailwind CSS or shadcn/ui is not the same as a custom-designed product with a proper design system. If you have a Figma file ready, development is faster and cheaper. If you don't, either budget for a designer (€1,000–€3,000 for MVP-level work) or accept that your developer will make reasonable choices you may want to revisit later.

Deployment and infrastructure is often forgotten entirely until someone asks where the app actually lives. For an MVP, a platform like Render, Railway, or Fly.io is usually fine. Cheap, manageable, fast to set up. Budget €300–€800 for initial setup, and ongoing hosting costs of €20–€100 per month depending on usage.

Admin tools and internal views are frequently underestimated. If you need to manage users, review submissions, or see any kind of operational data, you need some kind of admin interface. Rails gives you options like ActiveAdmin or a custom-built dashboard. This is easily €1,500–€4,000 of additional work if it wasn't in the original scope.

A Realistic Total Range

Putting that together, a minimal but functional MVP, one that real users can sign up for, use the core feature, and that you can manage on the backend, sits somewhere between €8,000 and €20,000 when built by an experienced solo freelancer. If you need anything close to a polished experience, or if the central feature is genuinely complex, you're looking at €20,000–€40,000 before you even talk to an agency.

These aren't scare numbers. They're what real work actually costs when done properly. The €3,000 MVPs you occasionally see quoted are either no-code tools stitched together (which is sometimes the right answer) or they're underscoped to the point where you'll be paying again in six months to rebuild what was skipped.

What Actually Drives the Cost Up

In my experience, the three biggest cost drivers are rarely the features themselves. They're the decisions made around the features.

Undefined requirements are the biggest one. Every hour a developer spends asking clarifying questions, waiting for answers, or building the wrong thing because the brief was vague is billable time that produces nothing. A clear spec with user flows, even a simple written document rather than a formal technical spec, can shave 20–30% off a project cost.

Scope creep mid-build is the silent killer of startup budgets. "Can we just add a notifications tab?" is rarely just a notifications tab. Mid-project additions interrupt the build, require architectural decisions that weren't planned for, and compound into delays that cost real money. Agree on scope before work starts, document it, and change it formally if you need to.

The wrong tech choice for the timeline matters more than most founders realise. Building an MVP in a framework that's powerful but unfamiliar to your developer, or choosing a microservices architecture when a monolith would have done fine, adds weeks. For most early-stage products, a monolithic Rails or Next.js application is the right call. If you want the longer argument, here's why Rails in particular earns its keep.

A Real Scenario: The Client Portal

A client of mine runs a small consulting firm. Their workflow was entirely managed in Excel: project tracking, client deliverables, invoice status, all in one increasingly unwieldy spreadsheet that three people were editing at the same time. (The longer diagnostic for that situation is when Excel is enough.)

They came to me wanting a "client portal." What they actually needed, once we talked through it, was two things. A way for clients to log in and see their project status, and a way for the internal team to update that status without emailing each other.

That's a far smaller MVP than "client portal" implies. We built it in Rails with a simple two-role authentication system (client view and staff view), a status dashboard, and a file upload feature for deliverables. No payment processing, no automated notifications, no reporting, all of which they'd mentioned wanting but agreed weren't needed to validate the idea.

Total cost: around €9,500 and four weeks of work. It replaced a process that was costing them hours of manual coordination every week.

The key was knowing what the MVP needed to prove. That clients would actually log in and use a portal rather than emailing for updates. Everything else could wait.

If you're trying to scope an MVP and aren't sure which components you genuinely need versus which ones are nice-to-haves dressed up as requirements, get in touch. A short conversation usually turns a vague idea into a budget you can plan around.