Blueboard
Board governance and director recruitment platform. MVP delivered in 11 weeks, 4,000 users by month three.
Prototyping and production launch
MVP development
A product your users can open, use and pay for, delivered in sixty days at a fixed price. Here is the price, what the scope covers, what it excludes, and why most projects overrun.
Key facts
- Fixed price from €29,000, delivered in 60 days. The price is published, not reserved for the sales call.
- An MVP is a complete product on a narrow scope — not an incomplete product on a broad one. That distinction is the difference between validating a hypothesis and losing six months.
- Code, infrastructure and documentation transfer to you from the first euro invoiced, not on delivery.
- Two days of scoping first, then a quote within five working days. If scoping shows the project is not ready, I will say so.
- Ten or more projects a year, in FinTech, PropTech, EdTech and applied AI.
Why the pricing question is the wrong one
"How much does an MVP cost" is every founder's first question, and it is the wrong one. Not illegitimate, but it expects a number where there is only a sequence of decisions. The same product can cost €25,000 or €120,000 depending on three or four trade-offs usually made without weighing them.
The first is scope. An MVP with five features rarely costs twice one with three: it costs three times as much, because every added feature interacts with all the others. The second is the nature of the data handled: as soon as payments, identity or regulated data are involved, cost changes category. The third is the level of polish expected at launch, which is almost always overestimated.
That is why I do not quote before scoping. Two days of workshop reduce the scope to what is genuinely needed to test your hypothesis — and that is where real savings are made, not in negotiating a day rate.
What "minimum viable" actually means
Most founders remember the word minimum and forget the word viable. The result is a half-working product that proves nothing: users give up before producing the signal you were looking for, and you wrongly conclude the market is not there.
A properly designed MVP does the opposite: it is complete on a deliberately narrow scope. One user journey, but one that goes all the way through, payment included if needed. That is the only configuration that produces a usable signal.
In practice this means accepting cuts. The admin dashboard can wait. Notifications can be manual at first. The mobile app can be a responsive site. These cuts do not weaken the validation, they make it possible within budget.
The sixty days, broken down
The fixed price covers eight weeks of work, in three phases.
The first two weeks go to scoping and architecture: final scope, data model, technical choices, wireframes of the key screens. Nothing is built yet, deliberately — one week of scoping saves a month of rework.
The next five weeks are the build itself, delivered in visible increments every week. You watch the product take shape, you can react early, and the gap between what you imagined and what is being built does not accumulate.
The final week is the production launch: hosting, domain name, analytics, transfer of access and documentation. At the end you do not have a demo on my server, you have a product live on yours.
Why projects overrun
On the projects handed to me for rescue, the causes repeat with striking regularity.
A scope never written down, therefore never settled: every conversation adds a feature and nobody measures the total. A supplier who agrees to everything, because refusing is commercially uncomfortable. A technical choice made for first-month speed that becomes a ceiling by month six. And the costliest of all: no user consulted before launch.
The fixed price is my answer to that. A written scope, a firm price, a date. If you want to add something along the way, we discuss it and remove something else, or push it to a separately quoted phase.
What the fixed price includes, and what it does not
| Included in the 60 days | Out of scope | |
|---|---|---|
| Design | Scoping, written scope, data model, wireframes of key screens | Full brand identity, visual guidelines, logo creation |
| Build | One complete user journey, authentication, minimal back-office, payments if required | Native mobile app, secondary modules, multiple integrations |
| Launch | Hosting configured, domain name, backups, analytics | High-availability infrastructure, security certifications |
| Handover | Code, documentation, infrastructure access — progressively, from the first euro invoiced | |
| After delivery | Two weeks of defect fixing | Feature evolutions, long-run maintenance, user support |
What follows is handled either as a separately quoted phase, or under a technical leadership engagement if you need a lasting presence.
Two worked examples
Coddect
Automated case file analysis. Turnaround divided by 14, costs divided by 30, 60 files processed per month.
Frequently asked questions
How much does MVP development cost?
At Workfutur the fixed price starts at €29,000 for delivery in 60 days. The final figure depends on the scope settled during the two scoping days, billed at €4,900 and credited if the project goes ahead. Across the French market, published ranges run from a few thousand euros for no-code to several hundred thousand for a regulated product: the gap comes from scope and data sensitivity, rarely from technical quality.
How long does it take to build an MVP?
Sixty days in my case, including two weeks of scoping and architecture before the first line of production code. A shorter timeline is possible on a very tight scope, but below six weeks you generally sacrifice scoping — the most expensive saving available.
What is the difference between a POC, a prototype and an MVP?
A POC answers "is this technically possible". A prototype answers "what would it look like". An MVP answers "does anyone use it and pay for it". Three distinct questions, three distinct budgets, and confusing them is the most common source of misunderstanding on a quote.
Do I own the code?
Yes, from the first euro invoiced, and the transfer happens progressively rather than on delivery. You receive the code, documentation and infrastructure access as we go. If we stop midway, you leave with what has been built.
What happens if the scope changes along the way?
We discuss it, and the trade-off is explicit: either we remove something equivalent to hold the date, or the request moves to a next phase with its own quote. What I will not do is silently agree and deliver late.
Do you work with no-code?
Only when it is the right tool, which happens more often than my profession likes to admit. No-code works well to validate a simple hypothesis or automate an internal process. It becomes a trap as soon as you need specific business logic, volume, or any serious data processing. The choice is made at scoping, not on principle.
And after the sixty days?
Two weeks of defect fixing are included. After that, either you take over with your own team — which is why the handover is progressive —, or we quote a next phase, or I stay on in a technical leadership role while you build the team.
Next step
Got a project to turn into a product?
Book 30 minutes, or describe your idea in a few lines. We reply within 5 business days with free scoping — scope, risks, timeline and engagement pricing.
Book a 30-min call
Brief us on your project
Firm quote within 5 business days · contact@workfutur.com