What a SaaS MVP costs

en 2026-09-13 7 min read

A SaaS MVP with JP Studio starts at EUR 7,500, excluding VAT, and the real number is fixed after discovery. That is package 05 on our price list, and it is the only package written as a floor rather than a range.

Every other package has a ceiling because the shape of the work is known before anyone starts. A business website is 4 to 7 pages, a CMS, service pages and a booking or contact flow, so it lands between EUR 1,500 and 3,500 and takes 3 to 6 weeks. A SaaS product is defined almost entirely by what happens after someone logs in, and that surface is different every time.

Why package 05 is a floor and not a range

Package 04, the advanced site or web app, already covers login, a dashboard, an API, a CRM connection, payments and a chatbot at EUR 3,500 to 7,500. It still has a ceiling because all of those are additions to a site whose shape we can draw on day one.

Package 05 is where the product itself is the thing being designed. Nobody can price that honestly from a single conversation, and an agency that gives you a fixed number in the first call is either padding it heavily or planning to renegotiate later. We would rather name the floor and be exact about what decides the rest. The fixed quote follows once those decisions are made.

What discovery actually decides

Discovery is not a workshop for its own sake. It answers five questions, and each one has a direct effect on the quote.

• Scope. The one job the first version has to do end to end, and everything that is deliberately not in version one. This is the single biggest lever on the price, so it is the conversation not to skip.
• Auth. One user per account, or teams with invites and roles. Roles multiply the work, because every screen now has a question attached: who is allowed to see this, and what do they see instead.
• Billing. Whether money moves inside the product. Subscriptions, trials, upgrades, VAT handling, and what the product does when a payment fails. Billing looks simple to begin with and grows once the edge cases arrive.
• Admin. What you need to see and change without asking a developer: refunding a customer, or working out why a signup failed. Skipping this saves money later in the build and costs it back every week after launch.
• Deployment. Where it runs, how many environments, backups, monitoring, and who holds the keys. We build on Next.js. The code, the repository and the database are yours, and where it is hosted is something we agree with you up front: we can host it, or you can.

What moves the price

Four things move a quote on this package.

1. How much already exists. Brand, copy, a design file, an existing codebase, a validated workflow. An MVP that replaces a spreadsheet you already run is cheaper to specify than one that replaces an idea.
2. Whether it needs accounts and payments. Both, together, with roles, is the difference between the floor and something well above it.
3. How many languages. Every language is content, testing and a set of decisions about what stays in English.
4. What happens after launch. Who supports it, who ships the next version, and whether the code has to be handed to an internal team later.

What EUR 7,500 buys, and what it does not

At the floor you get a first version of one product idea, narrowly scoped, built properly: real auth, a working core flow, an admin view, and a deployment you can trust with real customers. It is production software, not a prototype that gets thrown away.

It is not a platform, and it is not a suite of modules with a mobile app beside it. If your list is long, discovery is where we work out the part that makes version one worth using, and the rest gets a place in the plan instead of a place in the invoice. That is how the timeline stays real. More on that approach on design and engineering.

How long it takes

Discovery comes first and the build is planned from its outcome, so we do not quote a week count before it. As an anchor, a package 04 build runs 6 to 12 weeks. An MVP starts there and moves up with scope, roles and billing complexity. If someone needs a date before discovery, the honest answer is that the date is being invented.

When not to spend more

Spending EUR 7,500 or more is the wrong move if any of these is true.

• You have not sold it yet. A single-page landing at EUR 600 to 900, live in 1 to 2 weeks with a form and analytics, tells you whether anyone wants this before you build it.
• You can run it by hand first. A mini-site at EUR 900 to 1,500 plus you doing the work manually behind it is a legitimate first version. Automate the part that hurts once you know which part hurts.
• Package 04 already covers you. If login, a dashboard, a CRM connection and payments is genuinely the whole product, that is EUR 3,500 to 7,500 with a ceiling and a timeline. Choosing it is not settling for less, it is buying the right thing.
• Your workflow still lives in a spreadsheet. A platform will not fix a process that is still changing. Settle the process, then build the thing that runs it.

After launch

Running software needs someone watching it. Care is EUR 100 to 300 per month and covers updates, monitoring, backups, small corrections and support in agreed hours. It is explicitly not redesign and not new features: product work after launch gets scoped and quoted like any other build. If the product also has to be found, SEO foundation is a one-off at EUR 450 to 750, and SEO growth is EUR 500 to 800 per month if you want that work to keep running.

FAQ

Can you give me a number today?

We can tell you today whether your idea lands on package 04 with a ceiling of EUR 7,500, or on package 05 above it. That is enough to plan around. The fixed quote follows discovery, because a number given before the scope exists is a guess dressed up as a price.

Is discovery a separate cost?

Discovery is how we scope package 05, and it is agreed before it starts so you know what you are committing to. It produces a written scope, the decisions on auth, billing, admin and deployment, and a fixed price for the build.

I already have designs. Does that lower the price?

It can, and how much depends on the state of them. Finished screens for the full flow with states and edge cases save real time. A homepage in Figma and a moodboard save very little, because the expensive design work in a SaaS product is the parts nobody mocks up: empty states, errors, permissions and what a half-finished account looks like.

Do I need a marketing site as well?

Yes. The product lives behind a login and Google cannot see it. A single-page landing at EUR 600 to 900 or a mini-site at EUR 900 to 1,500 can cover it at launch, and grow into a business website later.

Do you work in Dutch?

Yes. The same information in Dutch is on saas laten bouwen, and the full list of packages is on pakketten.

If you want to know which package your idea sits on and what discovery would cost for it, send the outline through the contact form and you get a straight answer back, including the case where we think you should build something smaller first.