01 · Two working days, before a Sprint
What is The Scan?
A Sprint proves in ten days whether AI can carry out one bounded piece of work. That takes one sharp question, and it is not always there: the subject is still too broad, the knowledge sits with a few people or in files nobody has an overview of any more. The Scan makes the question sharp. Two working days with the people who know the work, and at the end three things you can check, instead of a document nobody dares to act on.
The map
What is rule work and what is judgement, where the knowledge sits and with whom, and which systems and files are involved. On one page, so everyone at the table has the same picture.
One trial
On the part where the doubt is greatest, I run one first trial. A macro read and described, one key figure recalculated from the source, one integration called. Small, but real, on your own material.
The proposal
What the next step is and what it costs: a Sprint, straight to a Build, or nothing. With a fixed price, and with half of the Scan credited if you go ahead.
The trial is small, but it is what sets this apart from an advisory call. At the end you see something work, not just something described.
What a Scan is and is not.
- You know something has to happen, but the subject is still too broad for one question.
- The knowledge sits with a few people or in files nobody fully understands any more.
- You first want to know, at a small cost, whether a larger engagement is worth it.
- It is not a discovery phase, but two days for a fixed price, with a priced proposal at the end.
- It is not yet proof that it works, because that is the Sprint; the trial shows where that proof has to be delivered.
- It is not an AI roadmap for the whole organisation, but one process and one concrete reason.