The method
Three steps, each with its price, its timeframe and its exit.
You decide on the next one from what the last one produced. Nobody signs a six-month commitment against a promise.
- 01 10 days
Diagnostic
€9,500 excl. VAT · fixed fee, one area of the business
Know exactly where generative AI would save you time, what it costs, and what to build first.
Three half-days of interviews with your teams, and read access to your tools.
- 02 4 to 6 weeks
Pilot build
from €18,000 excl. VAT · fixed fee, one system in production
A first system genuinely running, used by your teams, with its gain measured.
One person from the business for an hour a week. No training needed first.
- 03 fixed fee or monthly
Industrialisation and handover
on request · depending on what you take over
The system scales, it is monitored, and you take the controls at your own pace.
How much you take over is decided at the end of the pilot, not at the start.
Step 01
The diagnostic, day by day
Ten days spread over three to four weeks, so your teams are never blocked. The deliverable stands up without me: you can hand it to your board or to another supplier.
- 01 Days 1 to 3
Find out where the time goes
Interviews with the people who do the work, not only with the people who manage it. We reconstruct how a real week runs, noting every re-keying, every wait and every round trip.
- 02 Days 4 to 6
Look at the data rather than the opinions
Read access to your tools: CRM, mailboxes, management software, analytics. We count what can be counted. An irritation that adds up to two hours a month is not a build.
- 03 Days 7 and 8
Cost the levers and settle data privacy
Each lever is estimated in hours freed and in effort to build. Alongside that, we decide for each one what data would leave, where it would be processed, and what that implies.
- 04 Days 9 and 10
Report back, and name the first build
A ninety-minute session with the people concerned, a document that stands up without me in the room, and a clear recommendation on what to build first.
Step 02
The pilot build, week by week
One system, put into production and used. Not a mock-up, and not a proof of concept asleep in a test environment.
- 01 Week 1
Set the gain and the exit
We write down what will count as success and how it will be measured. Without that sentence, a build can neither be stopped nor judged.
- 02 Weeks 2 and 3
Build in the open
One demonstration a week, on the real system. You watch the build advance and you correct course while there is still time to.
- 03 Weeks 4 and 5
Put it in the hands of users
The system goes to the people who will use it. That is when the real problems surface, and that is why this phase sits inside the fixed fee.
- 04 Week 6
Measure, then decide what follows
We compare the before figure with the after figure. Then, on that evidence, we decide whether to industrialise or to stop there.
The exchange
What it asks of you, and what it hands back.
The load on the client side is what sinks most projects. So it is written down here, and by design it is light.
| What you provide | What you receive |
|---|---|
| Three half-days of interviews with your teams | A map of the time actually spent on the area audited |
| Read access to your tools | Each lever costed in hours freed, ranked by effort and by gain |
| One person from the business, an hour a week during the build | The system built, deployed and connected to the tools you already use |
| A decision at the end of each step | The before and after measurement, and the documentation to take over |
Step 03
Handover is prepared from the first day.
A supplier you cannot do without is a risk, not a partner. Independence is built up in stages, and how far you take it is decided at the end of the pilot build, once you know what the system really asks for.
You watch
During the build, your teams sit in on the demonstrations and ask questions. Nobody has anything to maintain yet.
You make changes alongside me
The first changes are made together, in your own code repository, with the operating documentation to hand.
You lead, I stay in the background
You evolve the system and I answer questions. Plenty of clients keep a light monitoring retainer at this point, because watching over automated processing is the first thing to get dropped.
The limits
What I do not do.
An offer that never states its limits says nothing at all. Here are my four.
I do not sell licences, and I take no commission on any tool I recommend.
I do not start a build whose gain I cannot measure. If the gain will not be measurable, the build waits.
I do not run catalogue training courses. People come up to speed on your own tool, once it exists.
I do not keep hold of your system. The code sits in a repository you own, from day one.
The method
The questions people ask before we start
Do we need to prepare anything before the diagnostic?
No, and that is deliberate. A company that has to assemble a file before it can start puts the whole thing off indefinitely. I need to talk to people and look at the tools as they are, not as they would have been tidied up for my visit.
What happens if the diagnostic concludes there is nothing worth doing?
It happens, and it is a useful result. You get the map of where the time goes and a costed demonstration that the subject lies elsewhere, which spares you a build that would have returned nothing. The fee is still due, and I tell you straight rather than selling you the next step.
Do you work on site or remotely?
The diagnostic interviews happen on site, because that is the part that deserves it. The build happens remotely, with a weekly demonstration. I travel at no extra charge within Hauts-de-France, and elsewhere in France with actual expenses added.
Who hosts the system once it is built?
You decide. On your premises, on your cloud, or on mine for a transitional period. The choice turns mostly on how sensitive the data is and on whether you have someone in house able to run the system.
What if we want to carry on alone afterwards?
That is the stated aim. Handover is gradual: first you watch, then you make changes alongside me, then you lead and I stay in the background. Plenty of clients keep a light monitoring retainer, because watching over automated processing is the kind of job everyone forgets.
Are your rates negotiable depending on our size?
The diagnostic is a fixed fee because its scope is fixed. The pilot build depends on what has to be built, and the amount is set against that scope when it starts, once the diagnostic has said precisely what to build.
Next step
Ready to find out where you stand?
The online questionnaire takes five minutes and hands you a map of your levers, whether you take it further or not.
Diagnostic
Étape 110 days
€9,500 excl. VAT · fixed fee, one area of the business
- A map of where the time actually goes in the area audited
- Each lever costed in hours freed, ranked by effort and by gain
- The data note: what leaves your systems, and where it is processed
- A three-month plan, naming the first system to build