The Brain / Getting started
Ten weeks, written out the way it actually goes.
Two people from your side spend about three hours in week one, one read-only credential is issued, and nothing else in your operation moves.
Who is in the room
Two weeks after the first call you hold a document saying what the Brain would have caught, and what a build costs.
The person whose hours are leaking
A function head who names the handoff that hurts.
Somebody who can issue a read credential
An administrator for the first system, who knows what it records.
Your security lead, early
One call in week one; send them the security page first.
One person who does the work every day
They can say when a surfaced item would have been noise.
The Diagnostic Sprint, day by day
Two weeks at a fixed fee, quoted before it starts; the output is a build plan with a price on it.
One system, connected read only
One read credential, for the system in the leaking handoff.
A real week, replayed
A week that already happened, run as if it were live: you watch your own last week.
Caught, stayed quiet, missed
Three lists; the third tells you which of your systems record nothing useful today.
One workflow, and a priced build plan
It must cross two systems, have a person carrying things between them, and a number somebody already tracks.
The eight weeks after
One workflow, one team, fixed price, $30K to $100K, quoted before work starts; the downside of being wrong is one team’s eight weeks.
Build, against the priced plan
The connections, a write path that stops before send or delete, judgment set against your written policy.
Shadow running, a person before every write
On day one it proposes too much and the team declines a good share; that is the design working.
Live, then handover
The code, the data and the system are yours, the same term as every build since 2018.
What we need from you
A read credential for one system
Scoped to the replay, revocable at any point.
The handoff that leaks the most hours, named
One sentence from the person who owns it.
Whatever written policy already exists
Contracts, statements of work, the old escalation note.
A number somebody already tracks
Cycle time, touches per invoice, days to first response.
Updated 15 September 2026 · WE_AINA