Tracking · Pipeline Stages & Exit Criteria

Build a Stuck-Deal Definition per Stage

Define how many days in each stage equals "stuck" so your CRM can flag rot automatically.

managerIntermediate6 hours of pipeline cleanup per quarter
When to use
Use when your pipeline shows $400K of "open" deals but half haven't moved in 60 days. This produces stage-specific aging thresholds (3 days in Discovery vs 21 days in Proposal Sent) plus the automated flag, alert, and rescue play for each.
The prompt
You are a sales manager at a digital marketing agency obsessed with pipeline hygiene. You know a fake pipeline is worse than a small one.
Agency: [AGENCY_NAME] | Avg sales cycle: [SALES_CYCLE_DAYS] days | Pipeline stages: [STAGE_LIST] | Avg deal size: [AVG_DEAL_SIZE] | CRM: [CRM_TOOL]
For each pipeline stage, define the day-count threshold at which a deal is considered STUCK, the CRM automation that flags it, the rescue play the rep must run, and the auto-close rule if the rescue fails.

- Thresholds must reflect typical agency velocity per stage (Discovery should age fast; Proposal can sit longer waiting on buyer).
- Each threshold must be defensible — tie it to a multiple of stage median (e.g., 2x median time-in-stage).
- Every stuck-deal flag must have a SPECIFIC rescue action, not "follow up".
- Include an auto-close rule: if no movement N days after stuck flag, deal moves to Closed-Lost with reason "Stalled".
- Account for buyer-side blockers (e.g., procurement, holiday freeze) with a one-time "Pause" status that resets the clock.

Table: | Stage | Stuck Threshold (days) | CRM Flag | Rescue Play | Auto-Close After |
Variables
  • [AGENCY_NAME] — Your agency name
  • [SALES_CYCLE_DAYS] — Median full-cycle days
  • [STAGE_LIST] — Your ordered pipeline stages
  • [AVG_DEAL_SIZE] — Average new-client ACV
  • [CRM_TOOL] — HubSpot, Pipedrive, Close, etc.
Example input
Agency: Pivot Performance Marketing | Cycle: 45 days | Stages: New Lead, Discovery Booked, Scoping, Proposal Sent, Verbal Commit | Avg deal: $6K/mo | CRM: Pipedrive
Example output
| Stage | Stuck Threshold | CRM Flag | Rescue Play | Auto-Close After |
|---|---|---|---|---|
| New Lead | 5 days | Red dot + email to SDR | Triple-touch in 48h: call, personalized email, LinkedIn DM | +7 days |
| Discovery Booked | 3 days past meeting | Slack alert to AE | Send recap + 2 next-step options within 24h | +5 days |
| Scoping | 10 days | Manager dashboard flag | Force buyer reply: send 3-option proposal preview, ask which to formalize | +14 days |
| Proposal Sent | 14 days | Yellow at 14, red at 21 | Loss-aversion email: "closing the file Friday unless we hear back" | +10 days |
| Verbal Commit | 7 days no signature | Manager + Founder alert | Pick up phone, identify procurement blocker, offer DocuSign + start-date incentive | +14 days |

Pause status available for buyer-stated holds (max 30 days).
Pro tips
  • Run the stuck report Monday 9am — it becomes the agenda for your pipeline meeting.
  • Track Auto-Close-Lost-Stalled as a separate loss reason so you can see how much of your 'pipeline' is fiction.
  • Reduce stuck thresholds quarterly as your team gets faster — don't let them inflate.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts