Why pay for scoping instead of getting a free quote?

A free quote is a guess priced to win the work. A scope is the work of deciding what to build, and it is where most of the money in an MVP is saved: the first conversation is usually about what to leave out. You keep the document whatever you decide.

What if I decide not to build with you?

The scope is yours. It is written so another team could price and build from it, and that is deliberate. If you do build with us, the €900 is credited in full against the build.

I already have a prototype built with Lovable, Bolt or v0. Do I need this?

Maybe not first. Start with the €99 Prototype Check, which tells you within 48 hours whether what you have is safe to build on. If it is, the Scoping Sprint plans the rest.

Where will my MVP be hosted?

In the EU. We deploy client products to EU data-centre regions, and the hosting plan in the scope says exactly where and what it costs to run.

Do you work in regulated industries?

Yes, including fintech and healthtech. The scope is where licensing, health-data and other compliance questions get identified, so the build plan accounts for them before anyone writes code. It is orientation, not legal advice.

MVP Scoping Sprint · €900

Know exactly what to build, and what it costs.

Two weeks, €900, fixed price. We work out the smallest version of your product that answers the question you need answered, write down what stays out, plan the stack and EU hosting, and give you a fixed price and timeline for the build. The scope is yours to keep, and the €900 is credited in full against the build if you build it with us.

What you get, in writing

The question: The one thing the first version has to find out, and what result would change what you do next.
The smallest product that answers it: The feature list for version one, each item tied to that question.
What we leave out, on purpose: Written down, with the reason, so it does not creep back in during the build.
The main user flows: Sign-up to the moment of value, for each kind of user, step by step.
The technical and hosting plan: Stack, integrations and where it runs, hosted in the EU, with what it costs to keep running.
A fixed price and timeline for the build: Most MVPs we build come to €5,000 to €25,000 and four to twelve weeks. Yours gets an exact figure.

How it works

1
You fill in the form
What you are building, who it is for and where you are now. Nothing to pay yet.
2
We reply within one business day
With a payment link for €900 and two or three times for a kickoff call.
3
About two weeks of scoping
A kickoff call, then questions and drafts in writing, and a second call to agree what goes in and what stays out.
4
You get the scope document
Yours to keep. Build it with us and the €900 comes off the build price; build it with someone else, or not at all, and the document is still yours.

Not sure yet? Get a rough range from the MVP cost calculator, read what an MVP costs in Europe, or see how we build MVPs.

Request a Scoping Sprint

Questions

Why pay for scoping instead of getting a free quote?: A free quote is a guess priced to win the work. A scope is the work of deciding what to build, and it is where most of the money in an MVP is saved: the first conversation is usually about what to leave out. You keep the document whatever you decide.
What if I decide not to build with you?: The scope is yours. It is written so another team could price and build from it, and that is deliberate. If you do build with us, the €900 is credited in full against the build.
I already have a prototype built with Lovable, Bolt or v0. Do I need this?: Maybe not first. Start with the €99 Prototype Check, which tells you within 48 hours whether what you have is safe to build on. If it is, the Scoping Sprint plans the rest.
Where will my MVP be hosted?: In the EU. We deploy client products to EU data-centre regions, and the hosting plan in the scope says exactly where and what it costs to run.
Do you work in regulated industries?: Yes, including fintech and healthtech. The scope is where licensing, health-data and other compliance questions get identified, so the build plan accounts for them before anyone writes code. It is orientation, not legal advice.