Rapid prototyping and MVP
Bordeaux and Nouvelle-Aquitaine, remote across France
You have a product idea and one question: is it worth investing in? I step in as a Product Owner who codes to answer it in a few weeks rather than several months. I build a clickable prototype or an MVP cut down to its essential journey, put it in front of real users, synthesise their feedback, and hand you a go / no-go decision with the reasons behind it. Not a mock-up for show: something people can actually test.
Book a free callThe problem I solve
Many ideas die in a requirements document. Between the first meeting and the first line of code, months go by in specifications, quotes and trade-offs, and nobody has yet seen a user touch the product. When the final version ships, it answers perfectly a question nobody asks any more. The other failure is the opposite: a hacked-together prototype that charms in a demo, with no structured feedback, used as the basis for decisions it cannot carry. I shorten the loop: build small, test fast, decide on facts.
How I work
Framing the hypothesis
Everything starts from one question the prototype must answer: who has this problem, what do they do instead today, and what would make them switch. I write that hypothesis down, with the criterion that will say whether it holds.
Building the prototype
I code the prototype or MVP myself, in Next.js and Python, shipped in a Docker container so it can be deployed anywhere. I cut the scope down to the journey that carries the hypothesis: everything else is simulated or left aside.
Testing with real users
I put the prototype in front of target users, in one-to-one sessions or on their own, with a precise scenario. I watch what they do, not what they say they want, and note every blockage, every detour, every moment of hesitation.
Synthesis and decision
Feedback is grouped by theme, weighted by frequency, and set against the criterion defined at the start. I hand you a go, no-go or pivot recommendation, with reasons, and what it would take to move to the next version if you carry on.
Real example
Where this comes from: since 2024 I have been building Patrimoine 360 myself, a multi-client wealth tracking platform in Next.js, extended with a monitoring module for DeFi positions (TVL, APR, threshold alerts). Multi-tenant architecture, authentication, automated tests on the critical path: the same foundation I deliver on a client MVP.
Read the case studyWho it is for
- Founders who want to test their idea before hiring a technical team
- Heads of product who must choose between several options with limited means
- Intrapreneurs who need something concrete to convince their management
- Business teams with a clear need and no developer available
What you get
- A written hypothesis, with the success criterion set before any code
- A clickable prototype or a deployed MVP, whose code you keep
- A test scenario and the notes from each user session
- A synthesis of the feedback, grouped by theme and frequency
- A go, no-go or pivot recommendation, written and reasoned
Frequently asked questions
Clickable prototype or real MVP?+
It depends on the question to test. A clickable prototype is enough to check that a journey is understood and wanted: a few screens, dummy data, no business logic. An MVP becomes necessary when the value depends on real processing: a calculation, an integration, live data. I settle that point at framing, not afterwards.
What happens to the code after the assignment?+
It is yours. Git repository, Docker container, deployment notes: you can hand it to an in-house team, to another contractor, or ask me to carry on. An MVP is written either to be thrown away or to be extended, and I tell you honestly which of the two applies at the end of the assignment.
How long does an assignment take?+
A few weeks, depending on the question to test and the number of users to meet. Framing the hypothesis takes a few days, building takes most of the time, testing and synthesis close the loop. If a prototype needs several months, it is no longer a prototype.
How much does it cost?+
Fixed price, on a quote basis, set after the hypothesis is framed: the price depends on the scope of the prototype and the number of user sessions. The fixed price covers the build, the tests, the synthesis and the recommendation. The first call is free and serves to frame all of this.
An idea to test before investing
Book a free first call. You tell me the idea, I tell you which question to test first and what would need to be built to answer it.