Section 5 · Reactivate Old Leads Now
5.2Former-client win-back
Built in the POC- No.
- 5.2
- DMA's reference
- Decision Book p.15
- Phase
- Phase 1
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
What DMA asked for · Decision Book p.15
Identify good former DMA clients worth winning back, remembering why they left.
Why it matters to DMA: Former clients already know DMA's work, so the sales cycle is shorter than with cold prospects.
In our words, from DMA's Product Decision Book v3, page 15.
How we do it
- An account that was won and later lost, or is tagged as a former client, is recognised as one. The AI reads why they left, with the quote.
- Code decides whether that reason is fixable: budget, timing, reporting, communication or a change of owner are fixable; a cheaper provider, going in-house or disappointing results are not. Only fixable churn adds points.
- The win-back email starts from the history ("when we worked together…") and addresses the reason they left, using DMA's approved claims only.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
A former client
Northside Dental Group: won in 2022, renewal lost in 2024.
- Nutshell
- AI
- Routing
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Past clients
Source
Won deals, later losses, and notes.
- 2Sync
Copies Nutshell changes into the bridge database
Mirrors them.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The churn reason, whether it's fixable, the score.
- 4AI
Claude models, only through DMA's own gateway
Reads why they left.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
The next step to Nutshell.
- 6Nutshell
The system of record
The win-back shows on the account.
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 | Each account's record type (lost deal, former client, forgotten lead) and next step. | 16 |
| tax.classifications | Lost reasons and churn reasons, each with its evidence. | 19 |
| ai.scores | The score, with the reason the record is revivable. | 20 |
How the tables connect (4)
| Column | Points to | Kept by |
|---|---|---|
| ai.account_twin.prompt_id | agent.prompts | The application (by id) |
| tax.classifications.node_id | tax.nodes | The database (foreign key) |
| tax.classifications.prompt_id | agent.prompts | The application (by id) |
| ai.scores.prompt_id | agent.prompts | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
Northside's win-back
What you see
1.Why it scores well
"Former client, fixable churn" is one of the reasons, with its points.

What happens in the system
- Rule engine
churn check"unhappy with reporting" matches a fixable reason; 13.5 points.
Northside Dental Group in the demo data (synthetic).
A former client worth winning back
- History
- SEO client from 2022; renewal lost in June 2024
- Why they left
- "unhappy with reporting"Fixable, so it adds 13.5 points.
- Why now
- Their current contract ends March 2027
- Score
- 85, tier A: win-back email to Dana
In the running POC

1 / 2Why? on Northside's score.
- 1Reasons and points.
- 2Factors.
- 3Could be wrong if.
- 4How it's counted.
Dashboard · Accounts, Northside Dental Group, why the score. Captured from the running POC on September 25, 2026; synthetic data.
See it live
Opens the exact screen in the running POC, in a new tab.
| Open | Where | What to try |
|---|---|---|
| Accounts | DMA AI dashboard | Former clients and why they left. |
Status
Built in the POC. This capability runs in the POC today, on synthetic data, end to end.