Section 20 · Sales Rep Work Elimination / Zero-Entry CRM
20.33Sales admin time dashboard
Designed for Phase 2- No.
- 20.33
- DMA's reference
- Decision Book p.43
- Phase
- Phase 2
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.43
Show how much admin time the AI saves the sales team.
Why it matters to DMA: It proves the value of zero-entry CRM in hours, not claims.
In our words, from DMA's Product Decision Book v3, page 43.
How we do it
- Scheduled for Phase 2 in DMA's book.
- Counts what the AI did (calls logged, fields filled, tasks created, follow-ups drafted) and converts it with time-per-task figures DMA agrees, per rep and per week.
Already in place
- Every scribe run records its timings and cost.
- Every AI write is logged with its batch (Approvals → Written by AI).
What the later phase adds
- The time-saved view, with DMA's own time-per-task figures.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Counted
What the AI did this week.
- Stored data
- Rule in code
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Bridge database
Source
The AI's own records.
- 2Sync
Copies Nutshell changes into the bridge database
Not involved.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
Runs, writes and their timings.
- 4AI
Claude models, only through DMA's own gateway
No AI model is involved: rules decide.
- 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 |
|---|---|---|
| ai.scribe_runs | One row per logged call: the transcript's fingerprint, the account it matched, the extraction and the approval batch it produced. | 24 |
| ctrl.outbox | The write gate: each proposed Nutshell change, its approval and what it replaced. | 28 |
How the tables connect (3)
| Column | Points to | Kept by |
|---|---|---|
| ai.scribe_runs.conversation_id | conv.conversations | The database (foreign key) |
| ai.scribe_runs.approval_id | ctrl.approvals | The database (foreign key) |
| ctrl.outbox.approval_id | ctrl.approvals | The database (foreign key) |
Worked example
Synthetic demo data: every name, business and number is made up.
A designed example (synthetic).
A week (illustrative)
- Calls logged
- 40
- Fields and tasks written
- 310
- Hours saved
- Set by DMA's minutes per task
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.