Section 20 · Sales Rep Work Elimination / Zero-Entry CRM
20.21Old proposal extraction
Partly built — finishing in Phase 1- No.
- 20.21
- DMA's reference
- Decision Book p.40
- Phase
- Phase 1
- Autonomy
- L2 · Prepare, then wait for approval
- DMA's decision
- Yes
What DMA asked for · Decision Book p.40
Pull what past proposals said (services, prices, terms) into the account's history.
Why it matters to DMA: Knowing what DMA offered before makes the next proposal consistent and faster.
In our words, from DMA's Product Decision Book v3, page 40.
How we do it
- Built: the contracts library reads uploaded agreements (MSAs, statements of work, order forms, amendments, NDAs, DPAs), extracts key terms and clauses with the page they came from, and answers questions about them.
- Proposal facts in notes are already kept: services proposed (62) and proposal dates and values, each with its quote.
- Not yet: a document type for past proposals themselves. That needs a sample of DMA's real proposals to set what to extract.
Already in place
- Contracts library with key terms and page citations.
- Proposal facts from notes.
What the later phase adds
- Past proposals as their own document type, from a sample of DMA's proposals.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Uploaded
A statement of work.
- Person
- AI
- Stored data
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Documents
Source
Uploaded agreements (PDF or Word).
- 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 document, encrypted, with its key terms and clauses.
- 4AI
Claude models, only through DMA's own gateway
Reads the document and cites the page for each term.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Nothing is written to Nutshell.
- 6Nutshell
The system of record
Nutshell is not changed.
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 |
|---|---|---|
| docs.documents | Uploaded agreements, encrypted, with their type, parties and status. | 33 |
| docs.key_terms | Terms extracted from each document, with the page. | 25 |
How the tables connect (3)
| Column | Points to | Kept by |
|---|---|---|
| docs.key_terms.document_id | docs.documents | The database (foreign key) |
| docs.key_terms.clause_id | docs.clauses | The database (foreign key) |
| docs.key_terms.decision_id | ctrl.decision_log | The application (by id) |
Worked example
Synthetic demo data: every name, business and number is made up.
Documents in the POC's contracts library (synthetic).
By type
| Type | Documents |
|---|---|
| Statements of work | 12 |
| Master agreements | 9 |
| Notice letters | 8 |
| NDAs | 9 |
| Amendments | 4 |
| Order forms | 3 |
| DPAs | 3 |
In the running POC
The screens for this one are being captured.
Status
Partly built — finishing in Phase 1. The parts run in the POC today; the rule that joins them is being finished for Phase 1.