Shadow mode: how a Brain earns its place before it touches real work
Weeks of running beside the real work, a record that writes itself, and a go-live that is deliberately dull. What our proving period actually looks like from inside.
Every supplier says their system works. We prefer not to be believed: we prefer to be checked. That is what shadow mode is for, and since it is the part of our way of working that firms ask about most, here is what it actually looks like from inside.
The setup
Once a Brain's first workflow is built, it does not go live. It runs beside the real work instead: reading the same intake the team reads, preparing the same dossiers, drafting the same first versions, matching the same demand against the same supply. Everything it produces lands in a place only the firm and we can see. No client receives anything. No process depends on it. The working day of the firm does not change by a minute.
What the shadow produces
A record. Day by day, the Brain's output sits next to what the team actually did, and the comparison writes itself: where the Brain prepared in minutes what took an afternoon, where it surfaced the thing nobody had connected, and, just as importantly, where it was wrong. Every miss gets examined at the table: was the memory incomplete, was a rule mis-stated, was the source noisy? The Brain is corrected, and the next week's record shows whether the correction held.
This is also where the firm's own rules get their edges. In the map, a rule like nothing about pricing leaves without a partner is a sentence. In shadow, the rule meets a hundred real cases, and the cases sharpen it: which situations count as pricing, which people count as partners, what happens on a Friday evening. By go-live the rules are not a policy document. They are tested behaviour.
How it ends
Shadow mode ends in one of two ways, and both are fine. Either the record shows, week after week, that the work arrives right, and the firm decides, with evidence on the table, to let the Brain act, still with a person in approval wherever the firm wants one. Or the record shows something that changes the plan, and the plan changes: a workflow re-scoped, a source repaired, occasionally a build paused. A firm that has watched the record form knows exactly what it is switching on, which is the entire point.
The go-live that follows is deliberately dull. Nothing new happens on the day; the Brain simply starts delivering to people instead of to the shadow, under the same log it has kept from the first hour. How the full journey runs, from the Map to that day, is on the implementation page.