Section 13 · Relationship Graph — Follow People, Not Just Companies
13.2Former-client champion detection
Designed for Phase 3- No.
- 13.2
- DMA's reference
- Decision Book p.27
- Phase
- Phase 3
- Autonomy
- L1 · Recommend
- DMA's decision
- Later
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.27
People who liked working with DMA at one company can be strong introductions at their next one.
Why it matters to DMA: Same dependency and risk as job-change detection, so the book puts it later too.
In our words, from DMA's Product Decision Book v3, page 27.
How we do it
- DMA decided LATER (Phase 3), after 13.1.
- A former client contact counts as a champion when the history shows a good relationship: a won deal they were on, positive notes, no complaint. The audit already reads these signals.
- When a champion moves (13.1), the suggestion says so and ranks higher, with the evidence quoted.
Already in place
- The audit already classifies former clients and quotes positive or negative notes as evidence.
- The audit already reads the CRM notes for signs that someone left or an email bounced, quotes the note as evidence, and stops outreach to that person.
What the later phase adds
- A champion marker from the relationship evidence.
- Champion moves ranked first in the 13.1 suggestions.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
A good history
A former client's owner signed twice and wrote a thank-you note.
- Nutshell
- AI
- Stored data
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1CRM history
Source
Won deals and notes.
- 2Sync
Copies Nutshell changes into the bridge database
Keeps the history current.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The champion marker and its quote.
- 4AI
Claude models, only through DMA's own gateway
The audit reads the relationship evidence.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Creates records only after a person accepts.
- 6Nutshell
The system of record
The new prospect, with the champion noted.
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.extracted_facts | Facts from the notes, each with its evidence quote. | 15 |
| ai.account_twin | One current profile per account: lifecycle, class, tier, next best action. | 16 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ai.extracted_facts.prompt_id | agent.prompts | The application (by id) |
| 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 champion evidence (synthetic example).
Why she counts as a champion
| Fact | Evidence |
|---|---|
| Signed twice | Won deals in 2022 and 2023, both with her as the contact |
| Positive note | "Priya was thrilled with the new location pages" (note, June 2023) |
In the running POC
There is no screen for this one yet: it is designed for Phase 3, as DMA's book decides. The parts listed under “Already in place” run in the POC today.
Status
Designed for Phase 3. DMA's book schedules this for Phase 3 (decision: later). The design is ready and builds on parts that already run in the POC.