How we move forward
Five ways of working together
We never start with a big commitment. A free first conversation to understand, a written diagnostic to price, a founding project to build the core, and only then (if the tool deserves to be followed) a monthly engagement. Each step is judged on what it produces, and you can stop after any of them.
The five tiers
- 01The discovery chat: free, 30 minutesWe look together at whether the subject concerns you. If not, I will gladly point you elsewhere. No account, no form.
- 02The written diagnostic: according to scopeAn hour, three hours, a day, a week: it depends on how much there is to examine. What today costs you, priced with you, and the plan out. Price and timeframe are stated before we start, and deducted from the project if it begins within 30 days.
- 03The founding project: three days to a week or more, depending on the projectShaper OS, plus the tool for your trade, in production, documented. Scope and price come out of the diagnostic: no bad surprises, the framing is already done and paid for.
- 04The transformation: several monthsFor heavy subjects: overhauling an information system, leaving a cloud, compliance, service continuity. Cut into delivered, measured stages, never one block.
- 05Piloting: monthlyWe operate and grow the tool: monitoring, evolutions, security, and repetitive tasks, handed over to it so it does them for you. It is the only long-term commitment, and it always comes after proof.
Five tiers, never a leap of faith
Swipe to see the whole diagram
What sets the price
Not the number of hours spent. What matters is the gap between your situation before and after: costs avoided, time given back to your teams, a risk removed. Work that saves you a headcount is not worth the same as work that saves half a day a month, even if it takes the same time.
I promise no figure in advance: be wary of those who do. We measure together before, measure together after, and look honestly at the gap.
An hourly rate still exists, for training, coaching and short interventions. It is given plainly when the question arises; it simply is not the right way to open the conversation.
And what you pay for belongs to you: the code of your application (the assembly of open-source building blocks and the specialisation programmed for you), your data and the documentation, with hosting, export and the backup policy written into the contract.
Frequently asked
- Why no price list?
- Because a price shown out of context is either too high for a small need or too low for a large one, and it invites comparing things that are not comparable. The diagnostic exists precisely to give a figure that means something in your case.
- Can we stop along the way?
- Yes, at the end of each stage, and that is by design. Every tier produces something usable on its own: a document, a tool in production, a month of operations. Nothing forces you to the next one.
- Is piloting mandatory after a project?
- No. Some clients take over entirely, and that is a good outcome: it is the stated goal. Piloting is for those who prefer someone to handle it while they get on with their trade.
The first step is light
Thirty minutes to see whether the subject concerns you and set an honest order of magnitude. Then you choose: diagnostic, project, or simply staying in touch for later.