STEP 1 · Start here
Prototype in 10 days
Describe it on a Monday. Your team is using it by Friday of the following week. Not a mockup — working software in production, on your real data.
- Format
- Fixed price
- Duration
- 10 days
- Step
- ENTRY
- Languages
- FR · EN
IN 1 MINUTE
- You get: a real workflow in production on your data, the code, and the costed build plan.
- You commit: your real data, two people for ten days, a scope signed before day 1.
- If it isn't running on day 10: fully refunded, and you keep what exists.
- If you continue with me: the prototype is credited against the build.
My commitment
You pay in one scenario out of three — and in that one, you walk away with software that works.
Doesn't run
Nothing
Full refund. You keep the code produced.
Runs, you stop there
Fixed price
The agreed amount, and the software is yours.
Runs, you continue
Nothing
Credited in full against the build.
This isn't a discount. It's ten days of my time set against a possible refund — because telling you to trust me is worth nothing while I carry no risk.
Who it's for
Companies that have outgrown what a spreadsheet can do.
- A key process runs on shared spreadsheets, with versions that drift and one person gluing it all back together by hand.
- No off-the-shelf product fits — you have looked, and everything out there asks you to change how you work.
- You have been burned before by a project that overran on time, on budget, or that never shipped at all.
- One person can decide, and has promised you two colleagues for ten days.
This isn't for you if you have an app idea with no validated budget, or if nobody on your team is available for ten days. In either case I will tell you on the first call, and I will not sell you anything.
The scope
The date holds because the scope doesn't move.
Every software project that overran, overran on scope, never on code. So here is what is in and what is out, written before we start.
What's in
- One workflow, not a system
- Three screens at most
- One data source, imported
- Simple authentication
- Deployed to production, reachable by your team
- Code, documentation and access handed over
What's out
- Real-time two-way integration with a third-party system
- Migration of your historical data
- Bespoke design — I use my design system
- Native mobile application
- Compliance, audit, certification
- Anything that depends on a third party to answer
What's out isn't refused — it's costed in the build plan you receive on day 10, and built afterwards as Platform 90.
How it runs
Ten business days, one mid-point demo, one observable handover.
-
Before day 1 · The contract
A 90-minute conversation to frame it. We write the exact scope and the sentence that defines success, together. You sign both. Nothing starts until it is clear to both of us.
-
Day 1 · Access
You give me access to your real data and the two people on your team who know the process. The ten-day clock starts here, not before.
-
Days 2 to 4 · First version
I build the skeleton of the workflow on your real data. You see something clickable by the end of day 4 — not a screenshot, a URL.
-
Day 5 · Mid-point demo
Thirty minutes. You handle what exists, you say what is off. Adjustments fit inside the scope; new ideas go into the build plan.
-
Days 6 to 9 · Finishing
The complete workflow, the edge cases that matter, deployment on infrastructure that holds. No debt left behind just to make the date.
-
Day 10 · Handover
Your named person runs the path end to end, in front of you, without me. It either works or it does not. You leave with the software, the code, and the costed build plan for what comes next.
Thirty minutes to describe your process. I tell you whether ten days is enough — and if it isn't, I tell you that too.
Book 30 min →Why now
Waiting isn't free: it's paid in hours, every single week.
A manual process isn't expensive once. It's expensive fifty-two times a year, and the price climbs with the size of the team. Ten days is enough to know what it truly costs you and whether software fixes it — instead of leaving it an open question for another quarter.
Quebec grants
A Quebec SME digital project is often funded at 40-50%.
PME en action, PSCE, ESSOR: several programs cover a large share of a digital transformation project. Few SMEs know about them, and fewer still file the application. I check your eligibility during the discovery call, at no charge.
Ask about grant eligibility →Common questions
Five honest answers.
What actually fits into ten days?
One workflow, not a system. Three screens at most, one imported data source, simple authentication, all deployed to production and reachable by your team. The exact scope is written and signed before day 1 — that is what makes the date holdable.
How do we define "it runs"?
With a sentence signed before day 1, along the lines of: "On day 10, [first name, last name, role] completes [workflow X] end to end, on your real data, without my involvement." A named person, a named path, an observable result. It is either true or false, with nothing in between.
What if my need is bigger than ten days?
That is the most common case and it is not a problem. We cut it down: the prototype covers the piece that proves it is worth doing. The rest is costed in the build plan handed over on day 10, and built as Platform 90.
What if the delay comes from my side?
The ten-day clock starts when I receive access and data, not at signature. If you get blocked, the clock stops and restarts when you unblock. I do not bill you for your wait, and you do not bill me for mine.
Do I keep the code if I stop there?
Yes. Repository, documentation and access are handed over in every case, even if you do not continue with me. You can take the prototype in-house or hand it to someone else.
Which process costs you the most hours?
Thirty minutes, no commitment. You describe it, I tell you whether ten days is enough to turn it into software — and what it takes on your side.