Section 18 · Testing, Reporting & Learning
18.3Industry cohort analysis
Designed for Phase 2- No.
- 18.3
- DMA's reference
- Decision Book p.33
- Phase
- Phase 2
- Autonomy
- L1 · Recommend
- DMA's decision
- Yes
◆ Amended in v3 of the book.
What DMA asked for · Decision Book p.33
Learn which industries and services convert best.
Why it matters to DMA: It tells DMA where to focus content, ads and sales; the book sequences it after core measurement.
In our words, from DMA's Product Decision Book v3, page 33.
How we do it
- Scheduled for Phase 2, on top of 18.2.
- Every account already carries its industry and the services it fits (from the audit); the Measurement screen already splits waves by segment and by tier.
- The design adds an industry and service split over all outcomes (chat, outreach and closed deals), with a minimum number of deals before a cohort is shown.
Already in place
- The Measurement screen already has "by segment" and "by tier" views of every wave.
- Industry and service lanes are recorded for every account.
What the later phase adds
- An industry × service split of outcomes, with a minimum sample.
The flow
It plays on its own while it's on screen; hover or use the controls to pause or step through.
Outcomes
Every measured outcome.
- 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.
- 1Measurement
Source
The outcomes from 18.2.
- 2Sync
Copies Nutshell changes into the bridge database
Keeps outcomes current.
- 3Bridge database
A copy of the CRM data, plus what the AI works out
Industry and service per account; the cohort figures.
- 4AI
Claude models, only through DMA's own gateway
Not needed: SQL.
- 5Write gate
The only way back into Nutshell: checked, approved when needed, sent once
Not involved.
- 6Nutshell
The system of record
Unchanged.
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.accounts | Accounts with their industry. | 17 |
| ctrl.decision_outcomes | Outcomes linked to decisions. | 13 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ctrl.decision_outcomes.decision_id | ctrl.decision_log | The application (by id) |
| ctrl.decision_outcomes.experiment_id | ctrl.experiments | The database (foreign key) |
Worked example
Synthetic demo data: every name, business and number is made up.
A designed cohort table (synthetic example).
By industry
| Industry | Meeting rate | Won |
|---|---|---|
| Dental | 7.2% | $96,000 |
| Legal | 4.1% | $54,000 |
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.
See it live
Opens the exact screen in the running POC, in a new tab.
| Open | Where | What to try |
|---|---|---|
| Measurement | DMA AI dashboard | Waves by segment and by tier 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.