// for founders who need to show, not tell
Your MVP in 24 hours
Twenty-four hours after scoping you get something to open: a working journey, with demo data. A website, a web app, an iOS and Android mobile app or a desktop application, depending on what your idea calls for.
// the contract
What 24 hours actually means
A deadline promise is worthless unless someone says when the clock starts and what is inside it. Here are both lists, the same ones written into the proposal.
When the clock starts
At the end of scoping, not at signature. Scoping is a one-hour video call: together we write the main journey, the screens, and above all what we are not building. Until you have approved that list, the clock does not run.
Inside the 24 hours
- A website, a web app, an iOS and Android mobile app or a desktop application
- One main user journey, from the first screen to the last
- A responsive interface in your brand, not an off-the-shelf theme
- A CMS so you can change your copy and images without a developer
- Realistic demo data, prepared with you
- Something to open it with: a private staging link on web, a TestFlight or APK build on mobile, an installable executable on desktop
- Your current site reused as a starting point, if you have one
- The code in your GitHub repository, in your name, from the first commit
- A demo call at the end and the written list of what is left
Not inside the 24 hours
- Going to production: what you get is staging, not a product open to the public
- Wiring it to your real data and your existing tools
- User accounts, taking payments and invoicing
- Load handling, full GDPR compliance, hosting of sensitive data
- App Store and Google Play releases
- Signing and notarising desktop applications, which depend on certificates in your name
Nothing on that second list is abandoned: it is the work that comes after, quoted separately and without urgency. See the production step
// how
Why the deadline holds
Speed is not about fingers on a keyboard. It is about decisions taken beforehand, and safety nets that catch mistakes without me.
The scope is written first
Projects slip because the need gets discovered while building it. We write it down first, in one hour, and we hold the line. Ideas that show up during the 24 hours are noted, not added.
A stack decided in advance
Next.js or Astro depending on the need, Supabase for data, AWS or Cloudflare for hosting and CDN, React Native for mobile. No technical choice to debate mid-sprint: the same building blocks from one project to the next, and I know their traps.
Your current site is a good starting point
Already have a site? That is not an obstacle, it is material: the copy is written, the structure is known, the search ranking is earned. I start from there to rework the design, straighten out the SEO or add what is missing. Your live site keeps running, untouched.
A CMS from day one
The prototype is not frozen in code. Your copy, images and pages go through a CMS you log into: you fix a headline without calling me, and the day the product goes to production, that piece is already in place.
Mocked data, no integration
In 24 hours the time does not go into plumbing. The data is fake but realistic, prepared with you so the demo speaks. Wiring the real thing comes later, and convincing people is a different job from connecting systems.
A rehearsed workflow, not a lucky run
I write, review and test with Claude Code, specialised agents and MCP servers wired into my own tools. That workflow is rehearsed on my own projects before it serves a client. It is what turns ten days of work into one, and it is what explains the price.
Automated checks on every build
The project rules (no dead links, no page without a title, no forgotten copy) are verified at build time. The build fails before you do. Speed without a safety net just ships bugs sooner.
One person to talk to
No project manager, no daily status report, no team meeting to fund. You talk straight to the person writing the code, and that person has ten years of production behind them.
// already done
Two projects, two clocks
Both sites were built this way, and the durations come from the Git history, not from an after-the-fact estimate. Neither was a 24-hour deliverable: they are complete projects, run at that pace.
Site and CMS in under 14 h
Art Fusion Sénégal
Dance, percussion and roller-skating school, Ouakam (Dakar)
A single Astro page, 56 KB, served statically so it stays readable on a mobile connection in Dakar, plus a CMS so the client can change her own schedule. First commit at 00:28, last one at 14:21 the next day. The domain switches over when the school is ready.
Live in under 48 h
Le Monde en Couleur
Children's theatre show, Un'Pact company
Under 48 hours between the first commit and the live site: fourteen pages, a quote form wired to a serverless function, a sitemap, landing pages per audience (nursery, preschool, works council) and automated checks on every build. Every merge to the main branch ships to production on its own.
lemondeencouleur.fr// pricing
Pricing
Fixed price
€500
Five hundred euros, announced before we start and payable at the demo. It covers scoping, the 24 hours of building, the CMS, the staging link and the final call. If your scope does not fit the format, I tell you during scoping, before you have paid anything.
- Clickable prototype 24 hours after scoping
- Website, web app, iOS and Android mobile app or desktop application
- One-hour scoping call, scope written down and frozen
- Responsive interface in your brand, not an off-the-shelf theme
- CMS included: change your copy and images without a developer
- Realistic demo data, prepared with you
- Staging link, TestFlight build or executable depending on the platform
- Your current site reused as a starting point, if you have one
- Source code in your GitHub repository from the first commit
- Demo call and a written list of what is left to do
// references
Enterprise Clients
10+ years of experience working with leading industry groups.
// frequently asked
MVP in 24 hours: your questions
An MVP in 24 hours, isn't that just talk?
It is a fair question. The answer has three parts: the scope is written and frozen before the clock starts, the data is mocked so no time goes into plumbing, and I reuse building blocks I know inside out. The Art Fusion Sénégal site, CMS included, was built in under fourteen hours. The dates are in the Git history and I can walk you through them on a call.
Why only €500?
Because my workflow is rehearsed. Scoping is scoped, the stack is decided in advance, the building blocks carry over from one project to the next, and the build is assisted by Claude Code and agents I wrote for my own needs. One day with that tooling produces what used to take a week without it. The price follows the real time, not what it would cost someone starting from scratch. It is also a way to meet over a deliverable rather than a quote.
I already have a site, is this still useful?
Yes, and it is often the best starting point: the copy is written, the structure is known, the search ranking is earned. In 24 hours we can rework the design, restructure it for SEO or add the missing feature, all on staging. Your live site keeps running, untouched.
What is not in the 24 hours?
Going to production, wiring your real data, user accounts, payments, load handling, full GDPR compliance and app store releases. The deliverable is a private staging link, not a site open to the public. The full list is higher up this page, and it is repeated in black and white in the proposal.
What if my idea is too big for 24 hours?
Then we do not do 24 hours. During scoping we either find the journey that fits the format, or I offer you a longer engagement on the same fixed-price principle. You pay nothing until that is settled.
Do I own the code?
Yes, 100%. The GitHub repository is in your name from the first commit, along with the documentation and hosting access. No dependency on me: any developer can pick the project up the next day.
What happens after the 24 hours?
You have a link to show and a written list of what is left. Three ways forward: you stop there and test your market, we take the prototype to production with your real data (that is the Prototype to Production offer), or we keep going with a recurring engagement if the product takes off.
Do you work remotely?
Yes, fully remote, for clients in France and internationally. Scoping on video, progress visible continuously on the staging link, final demo on video. Based in Paris if meeting in person makes sense.
Ready to see your idea running ?
Book thirty minutes. We look at whether your idea fits the 24-hour format, and I tell you straight if it does not.
// not your profile?
Discover our other offerings
Fractional CTO
Startups & Scale-ups
A senior technical leader who owns your stack, architecture decisions and product roadmap. For growing startups & scale-ups.
First Mobile Engineer
Startups launching their app
A senior React Native engineer (TF1, PMU, Zeturf) who designs, builds and ships your iOS & Android app, then hires your team.
Prototype →
Pros & makers who prototyped a tool
Your Lovable, Cursor or v0 prototype turned into a live, secure app ready for your users. Three tiers depending on your needs.