Confidential · © 2026 Space-O Technologies Inc. · Prepared exclusively for DMA. Please do not copy, save or share.

Section 20 · Sales Rep Work Elimination / Zero-Entry CRM

20.23Stale opportunity detection

Built in the POC
No.
20.23
DMA's reference
Decision Book p.41
Phase
Phase 1
Autonomy
L1 · Recommend
DMA's decision
Yes

What DMA asked for · Decision Book p.41

Flag opportunities that have gone quiet.

Why it matters to DMA: A deal with no activity is decaying; the sooner someone sees it, the more can be saved.

In our words, from DMA's Product Decision Book v3, page 41.

How we do it

  • The stuck-deal rule (17.2): 60 or more days with no activity, note or contact makes an open deal stuck; late-stage deals are high severity.
  • Stuck deals appear in Pipeline hygiene with the idle days, and lower the account's place on Today.

The flow

It plays on its own while it's on screen; hover or use the controls to pause or step through.

Open dealfrom Nutshell60+ days idle?last touchStuck dealhigh if late stage
Step 1 of 3

A deal

In Negotiation.

  • Nutshell
  • Routing
  • Stored data

Where the data goes

The same six stages on every page. Nothing reaches Nutshell except through the write gate.

  1. 1Nutshell

    Source

    Deals, contacts, tasks, activities, notes and users.

  2. 2Sync

    Copies Nutshell changes into the bridge database

    Keeps the mirror current, so the rules see today's state.

  3. 3Bridge database

    A copy of the CRM data, plus what the AI works out

    One open flag per record and problem, with its details and the rule version.

  4. 4AI

    Claude models, only through DMA's own gateway

    Not needed for most flags: they are rules. The audit adds what only the notes say.

  5. 5Write gate

    The only way back into Nutshell: checked, approved when needed, sent once

    Flags don't write to Nutshell; fixes happen there, by people (or through the write gate where a field rule allows it).

  6. 6Nutshell

    The system of record

    Reps fix the record; the flag closes on the next run.

The tables behind it

Drawn from the POC's database catalogue: structure only, no data.

ai.hygiene_flagsPKiduuidsubject_typetextflag_codetextseveritytextdetailsjsonbrule_versiontextdetected_attimestampresolved_attimestamp+ 2 more columnscrm.activitiesPKiduuidtypetextsubjecttextstart_attimestampstatustext+ 16 more columns

PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)

TableWhat it holdsColumns
ai.hygiene_flagsOne open flag per record and problem (stuck deal, missing next step, former owner, bad email, duplicate), with severity, details and the rule version.10
crm.activitiesCalls, meetings and e-mails from Nutshell, mirrored for the timeline.21

Worked example

Synthetic demo data: every name, business and number is made up.

Live counts, synthetic data.

Stuck deals

SeverityDeals
High (proposal, negotiation)45
Medium119

In the running POC

localhost:13301/hygiene?hyg_flag=stuck_deal
Pipeline hygiene, filtered to stuck deals.

Pipeline hygiene, filtered to stuck deals.

  1. 1The stuck-deal filter, with its count.
  2. 2Severity: high for late-stage deals.
  3. 3How long the deal has been idle.

Dashboard · Pipeline hygiene, stuck deals. Captured from the running POC on September 25, 2026; synthetic data.

See it live

Opens the exact screen in the running POC, in a new tab.

OpenWhereWhat to try
Pipeline hygiene: stuck dealsDMA AI dashboardEvery stuck deal, highest severity first.

Status

Built in the POC

Built in the POC. This capability runs in the POC today, on synthetic data, end to end.

20.23 Stale opportunity detection · DMA AI proof