Section 21 · Final Revenue Multipliers & Control Plane
21.3Champion enablement kit
Designed for Phase 2- No.
- 21.3
- DMA's reference
- Decision Book p.44
- Phase
- Phase 2
- Autonomy
- L2 · Prepare, then wait for approval
- DMA's decision
- Yes
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.44
Create a short, forwardable internal business case: problem, opportunity, evidence, proposed next step, ROI logic and approved proof points.
Why it matters to DMA: It lets the person who likes DMA sell DMA inside their company when the real decision happens without a DMA salesperson.
In our words, from DMA's Product Decision Book v3, page 44.
How we do it
- DMA's book schedules this for Phase 2, after the buying-committee mapper.
- The design drafts a one-page case from the twin, the site review and DMA's approved claims, checked by the same claims check as every email, and approved before it is sent (L2).
Already in place
- Approved claims and sample case studies, and the claims check that stops unsupported numbers.
- Site reviews with evidence, and proposals priced only from the approved rate card.
What the later phase adds
- A champion kit template and draft.
- Sending it through the same approval and send governor.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
The account
Twin and site review
- Stored data
- AI
- Routing
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1The account
Source
Twin, review, claims.
- 2Sync
Copies Nutshell changes into the bridge database
Not involved.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The draft and its approval.
- 4AI
Claude models, only through DMA's own gateway
Drafts from approved content.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Logs the send to Nutshell.
- 6Nutshell
The system of record
The activity on the contact.
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).
A champion kit
- Problem
- New-patient calls down at two of three offices
- Evidence
- Location pages without maps (site review)
- Next step
- A 45-minute strategy call
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.