Pricing
Fifteen packages, with what is in them and how long they take.
Four of them say price after review instead of a number. The review is the step that produces that number, and it sits in the table with a price and a duration like everything else.
Why these are published
Most firms in this category publish nothing, and the reasoning is understandable: a price on a page loses the deals where the number was wrong for that buyer, and it removes the conversation where the number could have been explained.
We publish anyway, for two reasons. Most B2B buyers would rather reach a decision without talking to a salesperson first, and a price on a page ends the conversations that were never going to close — on both sides, before either of us has spent a week on it.
Compare these against what the work costs you now, rather than against a software licence. What a delayed order costs, and what a line that goes out wrong costs — both are numbers you already have, and the review puts them on paper.
The same five steps, whichever line you are in
- 0 · Conversation — free, 45 minutes. An opinion and a proposal; the engineering begins one step later.
- 1 · Review — paid, 3 days to 2 weeks. Credited against the project within 60 days.
- 2 · Pilot — 3 to 6 weeks, fixed, to real use.
- 3 · System — 8 to 14 weeks, fixed after the review or by milestone.
- 4 · Running it — retainer, priced by volume handled rather than by people assigned.
Custom systems
| Package | Duration | Price |
|---|---|---|
| A2 · Discovery — architecture, integration map, decomposition, fixed estimate for the build | 2 weeks | €14,500–18,000 |
| A3 · Build | from 8 weeks | price after discovery |
Agents in operations
| Package | Duration | Price |
|---|---|---|
| B1 · Agent audit — 60 questions, failure catalogue, attribution report | 2 weeks | €7,900 |
| B2 · Pilot on one process | 5 weeks | €30,000 |
| B3 · Agent system | 10–14 weeks | price after review |
| B4 · Agent QA — regression and drift | retainer | €3,500–6,500 / month |
The data layer
| Package | Duration | Price |
|---|---|---|
| C0 · Five-order teardown | 3 days | €1,900 |
| C2 · Flow diagnostic | 1 week | €4,900 |
| C3 · Pilot on one flow | 3 weeks | €14,900 |
| C4 · Project — all formats, catalogue matching, ERP delivery, exception queue | 8–12 weeks | €34,000 + €2,500 per additional format |
| C5 · Specification matching | 6–10 weeks | from €38,000 |
| C6 · Exception Desk | retainer | €2,900–4,900 / month |
Airports
| Package | Duration | Price |
|---|---|---|
| V1 · Finding the hour | 2 weeks | €19,800 |
| V2 · Terminal pilot | 12 weeks | price after V1 |
| V3 · Rollout and operation | per terminal | price after pilot |
Why four of them have no number
Because a fixed price quoted before anyone has read your systems rests on how much of your problem we have solved before. On the parts we have built many times the estimate is solid; on the parts specific to you it is a guess, and the party that guesses low delivers a worse system rather than a cheaper one.
So the sequence is inverted. You buy 2 weeks of engineering judgement first, and what it produces is a number that holds — with the assumptions that would change it written down beside it.
A package exists only where reuse is high enough that the estimate does not float. Where reuse is low, what is being sold is time, and we call it that rather than dressing it as a package.
What you keep if you stop at the review
Every paid review — A2, B1, C0, C2, V1 — carries the same terms, and is credited against the project that follows it within 60 days.
If you stop there, what it produced is yours: the feasibility opinion, the architecture, the integration map with every connector named and flagged, the milestones estimated in weeks, and the assumptions that would reopen the estimate. That is a document another supplier can build from.
What every package leaves out, and what it costs separately
Reconfiguring your ERP · data cleanup beyond the agreed volume · integrations not named in the statement of work · licences · presence on site · support outside working hours · training beyond two sessions.
Each is available and priced separately. Naming them here is cheaper for both of us than discovering them in month three.
Terms
- [PLACEHOLDER — VAT]
- [PLACEHOLDER — invoice currency]
- [PLACEHOLDER — payment terms]
- [PLACEHOLDER — travel]
Questions
- Do you discount?
- On scope, not on rate. If the number is wrong for you, we will look at whether the scope can be smaller — a pilot on one flow instead of a project, a review before anything. The rate holds, because the only way to quote the same work for less is to deliver it worse.
- Can we start with the build and skip the review?
- No. Not as a favour, not for a reduced scope, not for a client we like.
- What if the review finds that we should not do this?
- Then it has done its job, and you have paid a small amount to avoid a large one. The document is yours either way, including the reasons not to build — which is the part that saved the money.
- Are the retainers priced per seat?
- No. By volume handled — exceptions resolved, questions regressed. What is sold is a system that runs, not people who are available. A retainer priced per person is a seat with a different name.
- Why is C0 only €1,900?
- Because it costs us roughly that. It is not a source of margin — it is a qualifier, and a buyer who has paid converts to the next step far better than one who has not.
Forty-five minutes. Bring the problem and we will tell you which line on this page it is, and whether it is worth starting.