Section 21 · Final Revenue Multipliers & Control Plane
21.8Strategic-account war room
Designed for Phase 2- No.
- 21.8
- DMA's reference
- Decision Book p.46
- Phase
- Phase 2
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.46
A living account plan for the top 25 to 50 targets: stakeholders, history, incumbent, trigger watch, opportunity hypothesis, open risks and next actions.
Why it matters to DMA: Large accounts get a different treatment and senior attention where one win can matter a lot.
In our words, from DMA's Product Decision Book v3, page 46.
How we do it
- DMA's book keeps this for later: the Account Digital Twin, the buying-committee mapper and the "Why now?" engine already cover the core account intelligence.
- The design is a plan page per strategic account, assembled from the twin, with the open risks and next actions owned by named people.
Already in place
- The Account Digital Twin and Account 360 for every account.
- Why-now facts, next best actions and the timeline.
What the later phase adds
- A strategic-account list and plan page.
- Owned risks and actions, reviewed on a cadence.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Top targets
25 to 50 accounts
- Stored data
- AI
- Routing
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Strategic accounts
Source
Chosen by DMA.
- 2Sync
Copies Nutshell changes into the bridge database
Keeps them current.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The plan, from the twin.
- 4AI
Claude models, only through DMA's own gateway
Drafts the plan from the twin.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved.
- 6Nutshell
The system of record
Unchanged.
The tables behind it
Drawn from the POC's database catalogue: structure only, no data.
PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)
| Table | What it holds | Columns |
|---|---|---|
| ai.account_twin | The Account Digital Twin these features build on. | 16 |
How the tables connect (1)
| Column | Points to | Kept by |
|---|---|---|
| ai.account_twin.prompt_id | agent.prompts | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
Designed output (synthetic).
An account plan
- Hypothesis
- Local search for all 12 clinics before their contract ends
- Open risk
- The economic buyer hasn't been met
- Next action
- Josh: introduce via the champion
In the running POC
There is no screen for this one yet: it is designed for Phase 2, as DMA's book decides. The parts listed under “Already in place” run in the POC today.
Status
Designed for Phase 2. DMA's book schedules this for Phase 2. The design is ready and builds on parts that already run in the POC.