Section 16 · Management Intelligence — Ask the Business Questions
16.3Revenue-at-risk report
Designed for Phase 2- No.
- 16.3
- DMA's reference
- Decision Book p.31
- Phase
- Phase 2
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
What DMA asked for · Decision Book p.31
Show the hot deals dying from inactivity, slow response or missing next steps.
Why it matters to DMA: Directly actionable and cheaper than the plain-English tool; the book suggests pulling it earlier.
In our words, from DMA's Product Decision Book v3, page 31.
How we do it
- Scheduled for Phase 2. Its inputs already run in the POC: the nightly hygiene rules flag every open deal with no activity for 60 days (a stuck deal) and every open deal with no open task (a missing next step), severity higher for late-stage deals.
- The report adds those flags up by value and owner, highest value at risk first, and sends it with the daily money report through the send governor.
- Each line names the deal, its value, why it is at risk and one next step.
Already in place
- Stuck-deal and missing-next-step flags on every open deal, from rules run with the audit (section 17).
- The daily money report, sent through the send governor with one-click approval links.
What the later phase adds
- A "revenue at risk" block in the daily report, by value and owner.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Flags
Rules flag stuck deals and deals with no next step every night.
- Rule in code
- Screen
Where the data goes
The same six stages on every page. Nothing reaches Nutshell except through the write gate.
- 1Nutshell
Source
Open deals, activities and tasks.
- 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 hygiene flags and the stored daily reports.
- 4AI
Claude models, only through DMA's own gateway
Not needed: rules and SQL.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved.
- 6Nutshell
The system of record
Reps fix the deals there.
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.hygiene_flags | Rule flags per record, e.g. stuck deal or missing next step, with severity. | 10 |
| ai.money_reports | Each daily money report as sent. | 7 |
Worked example
Synthetic demo data: every name, business and number is made up.
A designed report block (synthetic example).
Revenue at risk
| Deal | Value | Why at risk |
|---|---|---|
| Summit Legal — PPC | $54,000 | Proposal stage, no activity for 64 days |
| Pinecrest Clinics — SEO | $36,000 | No next step booked |
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.