Analyze · Pipeline Review & Deal Risk

Audit Pipeline for Single-Threaded Deals

Find every deal in your pipeline relying on a single contact and quantify the dollar exposure.

managerfounderIntermediate1 hour/month
When to use
Run monthly. If your CRM tracks contacts per deal, this prompt instantly tells you how much pipeline dollar value is hanging on a single point of contact — the most common reason agency deals die suddenly when someone changes jobs.
The prompt
You are a sales operations lead at a digital marketing agency. You know single-threaded deals (one contact, one relationship) are the #1 cause of 'the deal vanished' surprises.
Agency: [AGENCY_NAME] — [SERVICES]
What counts as 'multi-threaded' here: [MULTITHREAD_DEFINITION]
Pipeline + contacts export:
[PIPELINE_WITH_CONTACTS]
For each open deal, count the number of distinct contacts engaged (per [MULTITHREAD_DEFINITION]). Flag every deal that is single-threaded. Rank flagged deals by amount. Calculate total dollar exposure that is single-threaded.

- Use ONLY the contacts present in [PIPELINE_WITH_CONTACTS].
- 'Engaged' must match [MULTITHREAD_DEFINITION] — don't count contacts that only got CC'd once.
- If contact-engagement data is missing for a deal, output 'unknown — needs CRM hygiene' rather than guessing.
- Output is for a manager — keep ranking tight.

## Headline Exposure
Total single-threaded pipeline: $[X] across [Y] deals ([Z]% of open pipeline by $).

## Single-Threaded Deals (ranked by $)
| Deal | Amount | Stage | Sole Contact | Owner | Days in Pipeline |

## Data Quality Gaps
[deals where contact data was missing]
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — Services you sell
  • [MULTITHREAD_DEFINITION] — e.g. '2+ contacts with at least one email exchange in last 30 days'
  • [PIPELINE_WITH_CONTACTS] — CSV with deal, amount, stage, owner, list of contacts engaged, days in pipeline
Example input
Agency: Northwind Digital — SEO + paid social
Multi-thread = 2+ contacts with email exchange in last 30 days
Pipeline:
deal,amount,stage,owner,contacts_engaged,days_in_pipe
Acme,6500,Proposal,Jamie,"Sarah (coord)",30
BlueTrail,4000,Discovery,Priya,"David (MP); Lisa (ops)",74
Cedar,15000,Negotiation,Jamie,"Mike (mkt dir); CEO",40
Delta,2500,Discovery,Marcus,"Tom (owner)",53
Echo,8000,Proposal,Marcus,"Karen (cmo)",32
Example output
## Headline Exposure
Total single-threaded pipeline: $17,000 across 3 deals (47% of open pipeline by $).

## Single-Threaded Deals (ranked by $)
| Deal | Amount | Stage | Sole Contact | Owner | Days |
| Echo | $8,000 | Proposal | Karen (CMO) | Marcus | 32 |
| Acme | $6,500 | Proposal | Sarah (coord) | Jamie | 30 |
| Delta | $2,500 | Discovery | Tom (owner) | Marcus | 53 |

## Data Quality Gaps
None — all deals had contact data.
Pro tips
  • Echo at $8K with only a CMO is risky in a different way than Acme at $6.5K with only a coordinator — the CMO can sign but can leave; the coordinator can't sign at all.
  • If single-threaded % is >40% of your pipeline dollars, your team has a multi-threading skill gap.
  • Run this output as a coaching list, not a punishment list — most reps don't realize they're single-threaded.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts