Web prototypes and MVPs.
You have a product idea. Krafter turns it into a first testable version: not a slide deck, not a clickable Figma mockup, a real product online, usable and measurable. In 6 to 12 weeks, in front of real users.
From idea to product. In weeks.
The problem
The first risk of any software project: building the wrong product.
The classic scenario: 40 features, a 60-page spec, an €80,000 quote. Ten months later, the product is complete, compliant, delivered. And nobody uses it, because it answers what was written, not what users actually needed.
An MVP serves one purpose: answering the only question that matters. Do real users see enough value to use it, come back, and pay? As long as that question is open, every extra feature is one more bet on the same hypothesis.
So discovery is about cutting. Anything that doesn’t directly serve validation leaves the scope: it waits for the V2, and the V1 budget stays focused on the proof.
Use cases
SaaS, mobile or internal tool: the first version that validates.
SaaS MVP
#1A subscription-based online product: authentication, core feature, user management, admin interface. Scalable architecture from day one.
Let’s talkMobile app MVP
#2iOS and Android from a single Flutter codebase, store publishing included. Testable by real users in 8 to 12 weeks.
Let’s talkBusiness app MVP
#3A custom internal tool, functional and testable in real conditions by your teams, before investing in the full version.
Let’s talkMVP for fundraising
#4A working product with real users and usage metrics: in front of investors, proof rather than projections.
Let’s talkWhy Krafter
No throwaway prototypes: first versions that hold up.
Melimelo and Trottr started exactly like this: tightly scoped MVPs, shipped fast, in front of real users. Today they are complete products, used every day by thousands of people, built on the foundations of their first version.
The low-cost MVP delivered in three weeks exists. Its architecture collapses at the first evolution, and the V2 starts by rebuilding everything. The budget saved upfront gets repaid threefold, at the worst moment: when the product starts to work.
At Krafter, an MVP is small in scope, not in quality: clean code, documented and tested, a structured database, automated deployment. If the hypothesis is validated, the V2 builds on top, without starting over.
Conviction
“A low-cost MVP whose architecture collapses at the first evolution isn’t an MVP, it’s debt. The first version of a product must already hold up for what comes next.”
François Pluchino
Co-founder & CTO, Krafter
How we work
From idea to production, in 4 to 12 weeks.
A successful MVP starts with a list of noes. The method is built to cut early, ship fast, and measure from day one online.
01 / 04
Discovery
3 to 5 daysIdentify the core problem, list and prioritize the use cases, eliminate the superfluous.
The output: a clear, quotable MVP scope, an explicit list of what waits for the V2, and a go-live date.
Design
1 weekThe user journey screen by screen. Mockups are validated before the first line of code.
Throwing away a mockup costs less than throwing away a sprint: key screens are click-tested on real usage scenarios.
Development
4 to 8 weeksShort cycles, a testable version at every iteration. Your feedback drives what comes next, no tunnel effect.
Weekly or biweekly releases, a demo every cycle. You see the product move forward continuously, not at the end.
Go-live and measurement
The product is online, in front of real users, with the tools to interpret what happens.
Signups, usage, retention, churn: metrics set up from the first deployment turn the MVP into a decision-making tool.
Method side
What is the difference between a prototype and an MVP?
A prototype is a demonstration tool: a clickable mockup that shows the concept without actually working. An MVP (Minimum Viable Product) is a real product in production: users sign up, use it, generate real data. That difference is what lets you validate a market hypothesis rather than an intention. At Krafter, the clickable mockup is a step in the design process; the deliverable is the product online, measurable, built on foundations that support what comes next.
- Prototype
- Clickable mockup, demonstration tool. A step, not a deliverable.
- MVP
- Product in production, real users, real data.
- Scope
- 5 to 8 screens, authentication, core feature, admin.
- Budget
- €12,000 to €30,000 excl. VAT for SaaS, €12,000 to €25,000 excl. VAT for mobile.
- Timeline
- 6 to 12 weeks depending on complexity, date set at discovery.
- Proof
- Melimelo and Trottr, MVPs turned into products with thousands of users.
FAQ
You have a product project? Let’s check together what it takes to launch it: 30 minutes to understand the problem, the market and the constraints.
Talk about my MVP projectBefore launching your MVP.
A prototype is a demonstration tool: a clickable mockup that shows the concept but doesn’t actually work. An MVP is a real product in production, functional, with real users and real data. At Krafter, the clickable mockup is a step in the design process, never the final deliverable.
A SaaS MVP (5 to 8 screens, authentication, core feature, admin interface) sits between €12,000 and €30,000 excl. VAT. A mobile MVP (iOS and Android from a single Flutter codebase, store publishing included): between €12,000 and €25,000 excl. VAT. The precise quote comes out of discovery, before any commitment.
Between 6 and 12 weeks depending on complexity. A simple mobile MVP ships in 8 weeks. A SaaS with several user roles and third-party integrations takes more like 10 to 12 weeks. Discovery gives you a go-live date, not a vague range.
The entire business layer built for your product is fully yours. It sits on FastEdgy, our open source foundation. You can take the code back, hand it to another vendor or build an in-house team, at any time.
Two scenarios. The hypothesis is validated: we move on to the V2 on the existing foundations, without rebuilding anything. It isn’t: you spent a controlled budget and you have concrete data to pivot with, instead of a complete product nobody uses.
A working MVP with real users and usage metrics weighs more than 50 slides. Signups, retention, user feedback: you present proof, not projections. And if the topic applies to you, Krafter also offers dev for equity.
Let’s build a product people → actually use
30 minutes on a call with a founder. Answer within 24 to 48 hours. Pitch deck optional.