Two ways to work over time. Three to get started.
The monthly engagement is the heart of the offer. The fixed-scope packs let you start on a real subject, at a price known in advance.
Prices excl. VATInvoiced in eurosOne senior engineer, no subcontracting
A fixed-scope pack is a first mission, not the destination. Most systems need capacity held month after month, which is what the two recurring engagements are for.
Every engagement ends with a written deliverable
What changed, why, the risks, the recommendations. Readable by a founder as much as by a developer.
- What changed, file by file and in plain words.
- Why that choice, and what was ruled out.
- The risks left open, named rather than buried.
- What I would do next, in order.
What no price on this page includes
None of this is a hard no. It is work that sits outside the figures above, so it gets quoted separately rather than absorbed quietly.
Scope added mid-mission
On a fixed-scope pack, work pauses, the change is clarified, and we decide together whether to extend or keep it as it was.
On-site presence as a routine
On-site in Paris or Berlin now and then is fine. Three days a week in the room is a different job and not this one.
Round-the-clock on-call
Blockers get escalated fast during the working week. A 24/7 rota is a commitment one person cannot honestly sell.
Product design and brand work
Interfaces get built from your design decisions. Making those decisions is not part of the figures above.
Third-party costs
Model usage, hosting, vector databases and the rest are billed to you by their providers, not marked up through me.
Hiring and training your team
Handover is included and documented. Building an internal AI team around it is a separate conversation.
Questions about the money
Why are all the prices shown as “from”?
A pack carries a scope written before the first commit. The prices shown are starting points, confirmed in writing before anything is signed.
Can I start with a pack and move to a recurring engagement?
That is the intended path. A pack lets you start with bounded risk on both sides; what comes after is the engagement.
What if the pack turns out to be bigger than it looked?
Work pauses and we look at it together. Either the change replaces something in scope, or the mission is extended with a new number.
Who pays for the models, hosting and vector databases?
You do, directly to the providers. Nothing is marked up through me, and you keep the accounts.
What happens to the capacity I do not use?
It is not carried over and it is not lost. In a quiet month it goes to a shared backlog you see in the weekly review: technical debt, documentation, inference costs, upgrades that can wait.
Is there a minimum commitment?
Three months to start, then month by month, with thirty days’ notice on either side.
Still not sure which column you are in?
That is what the call is for. Bring the system, the constraint and the deadline; you leave with a recommended entry point, or with a clear no.