Pricing
Discovery is fixed at €18,000 and can end in no. Everything after it is quoted against evidence rather than a brief.
Start here
Recommended
For teams who have a problem and a suspicion, not a spec.
€18,000
2–3 weeks Fixed. Not an estimate.
Then
For a decision already made and a system that has to hold in production.
€60,000 — €250,000
From 6–10 weeks Quoted after discovery, never before.
After
For systems in production that need someone watching the drift.
Monthly, quoted
Rolling, cancel anytime Optional. Thirty days of warranty come free.
What each one delivers Compare the three See the capabilities
Method
Discovery costs €18,000 whatever it finds. That price is fixed because the deliverable is, and because the decision it produces has to be worth buying on its own — including when it tells you to stop.
A build price quoted before that work is fiction. Padded, it costs you money you did not need to spend. Sharp, it becomes a renegotiation once you are committed. Quoted after, it is scoped against your data.
Compare
Sixteen lines, grouped four ways. A matrix nobody can read persuades nobody.
| Included | Discovery | Build | Retainer |
|---|---|---|---|
| Scope | |||
| Problem framing and data audit | Included | Included | Not included |
| Feasibility spikes on your data | Included | Included | Not included |
| Production system build | Not included | Included | Partly included |
| Interface and front-end delivery | Not included | Included | Partly included |
| Delivery | |||
| Written recommendation | Included | Included | Not included |
| Live staging environment | Not included | Included | Included |
| Evaluation harness | Not included | Included | Included |
| Traces and observability | Not included | Included | Included |
| Handover | |||
| Pairing with your engineers | Included | Included | Included |
| Code, evals and documentation are yours | Included | Included | Included |
| Thirty-day defect warranty | Not included | Included | Not applicable |
| Drift monitoring | Not included | Not included | Included |
| Commercial | |||
| Price fixed up front | Included | Not included | Not included |
| Works under NDA | Included | Included | Included |
| Runs in your infrastructure on request | Included | Included | Included |
| Cancel without penalty | Not applicable | Not included | Included |
Objections
Asked on nearly every first call. Answered here so you do not have to spend the call on them.
Because a number given without context commits nobody. Before we have seen your data we would be pricing a guess, and the two ways to make that safe are both bad: pad it heavily, or quote low and renegotiate once you are committed. Discovery is priced precisely so you can buy the number rather than the guess.
Then it has done its job and the engagement ends there. It has happened, and it is the cheapest outcome available to you — two to three weeks against a year of building the wrong thing. You keep the recommendation, the audit and the spikes.
No, and we would rather say so plainly than bury it. Discovery is real work with its own deliverable, not a sales expense. What it does change is the build quote: scoped against evidence, it is both tighter and lower-risk than one priced off a brief.
That is what discovery is. If you mean a scaled-down production system, we will say no more often than yes — a pilot that skips evaluation and grounding teaches you that a demo works, which you already knew.
Not on rate. We do reduce scope, and we will tell you which third of a plan is not worth paying for. That is the same conversation as a discount with a better outcome, and it is usually available.
Discovery is fixed price, so overrun is our problem. On a build, scope is reviewed every two weeks against the live staging environment, which is what stops an overrun from being discovered at the end. Where we get an estimate wrong, we say so in the review it surfaces, not in an invoice.
Yes. NDA by default, and we run inside your infrastructure where required. We have delivered under GDPR, HIPAA-adjacent and financial-services constraints. Data residency and retention are settled in week one rather than retrofitted.
Access to the data and one person who can answer questions about the domain without booking a meeting. Engineering time from your side is welcome from week one and required by handover — if your team cannot maintain what we build, we have failed.
Contact
One business day for an answer, including when the answer is that you do not need us.