Section 5 · Reactivate Old Leads Now
5.3Proposal graveyard mining
Designed for Phase 2- No.
- 5.3
- DMA's reference
- Decision Book p.16
- Phase
- Phase 2
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
What DMA asked for · Decision Book p.16
Search old proposals where DMA invested strategy time but never closed.
Why it matters to DMA: It recovers value from work DMA already paid for.
In our words, from DMA's Product Decision Book v3, page 16.
How we do it
- DMA's book schedules this for Phase 2, after old proposals can be extracted (section 20).
- The design reads DMA's old proposal documents, links each to its Nutshell deal, and surfaces the ones that were never closed, with what was proposed and the value, as a reactivation segment.
Already in place
- "Proposal stage reached" is already a scoring reason for deals that got to that stage.
- Contract and proposal documents can already be added to the knowledge store and searched with citations (owner and president only).
- New proposals are stored with their lines, sections and PDF.
What the later phase adds
- Extraction of old proposal documents and linking them to deals.
- A "proposal graveyard" segment in the reactivation list.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Old proposals
Extracted from DMA's files.
- Stored data
- Rule in code
- Routing
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Proposal files
Source
Old proposals (Phase 2).
- 2Sync
Copies Nutshell changes into the bridge database
Links them to Nutshell deals.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
What was proposed, and the value.
- 4AI
Claude models, only through DMA's own gateway
Reads the proposals.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved until outreach.
- 6Nutshell
The system of record
The deal gains the proposal's details.
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.proposals | Proposals made in the system today (lines, totals, PDF); old ones would be linked the same way. | 36 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ai.proposals.supersedes_id | ai.proposals | The database (foreign key) |
| ai.proposals.approval_id | ctrl.approvals | The database (foreign key) |
Worked example
Synthetic demo data: every name, business and number is made up.
Designed output (synthetic).
A proposal from the graveyard
- Proposal
- Local SEO for 5 clinics, March 2024, $60,000 a year
- Deal
- Lost: "not this year"
- Why now
- A new budget year has started
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.