Section 13 · Relationship Graph — Follow People, Not Just Companies
13.1Job-change detection
Designed for Phase 3- No.
- 13.1
- 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
If a former DMA contact becomes, say, CMO somewhere else, show the new company as a possible opportunity.
Why it matters to DMA: Valuable, but it depends on outside people-data feeds that are costly and often out of date, so DMA's book puts it later.
In our words, from DMA's Product Decision Book v3, page 27.
How we do it
- DMA decided LATER (Phase 3). The design waits for a people-data provider DMA chooses.
- When a contact is marked as having left, the provider is asked where they went; a match with enough confidence creates a suggestion, never a record, for a person to accept.
- Accepted suggestions become a new account and contact in Nutshell through the write gate, with the source noted.
Already in place
- 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.
- Every account already shows its people, each with a contactability note (for example "Not contactable: email bounced"), on the Account 360 screen.
What the later phase adds
- A people-data provider (chosen with DMA).
- A "moved to" suggestion list that a person accepts or dismisses.
- New account and contact creation through the write gate on acceptance.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Someone left
A 2024 note says the marketing director has left the company.
- AI
- Stored data
- Routing
- Person
- Nutshell
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1CRM notes + provider
Source
"She left" in the notes; the new job from a provider (designed).
- 2Sync
Copies Nutshell changes into the bridge database
Keeps the contact mirror current.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
The suggestion and its evidence.
- 4AI
Claude models, only through DMA's own gateway
The audit already spots "left the company" in notes.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Creates the new records once accepted.
- 6Nutshell
The system of record
A new account and contact with their source.
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 |
|---|---|---|
| crm.contacts | Contacts mirrored from Nutshell, with title and account. | 20 |
| ai.hygiene_flags | Rule flags per record; "bad email" marks someone who left or bounced, with the note quoted. | 10 |
Worked example
Synthetic demo data: every name, business and number is made up.
A designed suggestion (synthetic example).
Suggestion
- Person
- Priya Raman, formerly Marketing Director at Northside Dental Group
- Now
- CMO at Lakeview Orthodontics (people-data provider, 0.86 confidence)
- Suggested action
- Create Lakeview Orthodontics as a prospect; introduce DMA through Priya
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.