Offer 03
Five days to a build plan specific enough to price.
This is step one of a build, sold separately so you are not committing to the whole thing on a guess. Five working days produce a map of the process as it really runs, a ranked list of what to automate, honest build-or-buy calls, a cost model with token caps in it, and a governance note. If you go ahead with the build, the fee comes off it.
- Price
- €3,000–6,000 fixed
- Duration
- 5 working days
- the work arrives
- agent does the routine part
- cost cap checked
- your team decides
- system of record updated
- logged, measured, reported
◆ marks a point where a person decides. Nothing passes it on its own.
What you get
The five deliverables
Documents, not slides. Written so that another supplier could execute against them — which is the test of whether discovery was worth its fee, and the reason you are not locked in to us.
- Process map
- How the work actually flows today, including the spreadsheet nobody mentions and the approval that happens over chat.
- Ranked candidate list
- Every automation candidate scored on value and on feasibility, with the reasoning shown. The bottom of the list matters as much as the top.
- Build or buy, per candidate
- Where an off-the-shelf tool already wins, we say so and name it. We are not the right answer to everything on the list.
- Cost model with caps
- Build cost, run cost, and token spend modelled with a ceiling, so the number you take to a budget holder is a number and not a range.
- Governance note
- Where a person must stay in the loop, what data leaves your systems, and the retention posture. One page, written for a non-technical reader.
The terms
The commercial terms
- Price
- €3,000–6,000 fixed. 5 working days.
- Credited against the build
- In full. Commission the build and the discovery fee comes off its price — you paid for step one of a deliverable, not for an opinion.
- Scope
- One part of the business — a department, or a process chain end to end. Not the whole company.
- Excludes
- Any building. This week produces the plan the build is priced from.
- If you stop here
- You keep all five documents and owe nothing further. They are written for another supplier to execute, so stopping is a real option rather than a polite one.
- Who runs it
- Fred, who designed the agent system this company runs on.
- Cross-border
- One clean price. 0% Thai VAT on export of services.
The sequence
How the week goes
Two days listening, two days modelling, one day writing. The interviews are with the people who do the work, not only with the people who own the budget.
- 01
Interviews with the people doing the work
Two days. What they actually do, what they work around, and where the time goes. This is where the real process appears.
- 02
Process map, back to you for correction ◆ your call
You read the map and tell us where it is wrong. An audit built on a map nobody checked is worthless.
- 03
Candidate list, scored
Value against feasibility, with the reasoning visible so you can disagree with a score rather than with a conclusion.
- 04
Build-or-buy and cost model
Per candidate: build it, buy it, or leave it alone. Costs modelled with a token ceiling included.
- 05
Governance note
Where a human gate is required, what data moves, and what the retention posture is.
- 06
Walkthrough and your decision ◆ your call
We present it, you decide what happens next — including deciding that nothing does.
Fit
Who this is for
- An operator who has been told to "do something with AI" and wants to start from the process rather than the technology.
- A team about to commit real budget and wanting an outside read on where it should go.
- A company of 10 to 200 people with one department worth mapping properly.
Who it is not for
- Anyone who already knows exactly what to automate and can specify it. Go straight to the build; this would be a detour you pay for.
- A whole-company transformation programme. That is not what five days buys, and we would rather scope one department properly.
Objections
The questions we get asked
Is this a consulting engagement?
No — it is the first week of a build, invoiced on its own. You get five documents: a process map, a scored candidate list, build-or-buy calls, a cost model with token caps, and a one-page governance note. The test we hold ourselves to is that a different supplier could execute from them, and the fee comes off our build price if you use us.
How is this different from the rescue discovery?
Rescue discovery reads a build that already exists and tells you whether to save it. This one reads a process that has no build yet and tells you what to build, buy, or leave alone.
Why should we believe you know how agents behave in production?
Because we run this company on them, and we will show you rather than assert it: the dispatcher, the approval gates, the action log and an evaluation run. It is the one claim on this website you can check in ten minutes.
So what does the build actually cost, net?
The build price minus the discovery fee. A €20,000 build after a €4,000 discovery sprint is €16,000 more, not €20,000 more — the discovery already did the build's first week. We put that arithmetic in the proposal rather than leaving it as a hint.
What if the honest answer is that we should not automate this?
Then the candidate list says so, with reasoning, and you have saved a great deal more than the fee. That is a normal outcome and we would rather reach it in week one than in month three.
Pick one department.
Thirty minutes to work out whether five days on it is worth your money. If you already know what to build, skip this and go straight to the build.