How do I detect deal risk signals with Claude Code?
The workflow scans your active pipeline for risk patterns and flags deals that need immediate attention. In Claude Code, type:What are the six deal risk signals?
Priority: P0-P1 | 30-day decay | 24h SLAHow should I escalate based on risk stacking?
The number of simultaneous risk signals on a deal determines the escalation level.How do I combine multiple buying signals into one outreach?
Don’t send separate touches for each signal. Combine them into one contextual message.
In Claude Code, type:
What are the rules for signal-based account management?
These rules prevent over-contacting accounts.- Max 1 signal outreach per account per 14 days. Multiple signals on the same account go into one message, not multiple touches.
- Combine signals into ONE message. Never send separate emails for each signal. The combined context makes the outreach land.
- 30-day cool-off after a reply or meeting booked. Once you get engagement, switch to the sales process. Stop signal-triggered outreach.
- 3+ signals per month on the same account = manual AE review. High signal density either means the account is genuinely hot or your signal definitions are too broad. AE reviews before any outreach.
What does the deal risk workflow do step by step?
1
Pull active pipeline
Load all open deals from CRM via MCP. Include deal value, stage, close date,
contact associations, and activity history.
2
Calculate stage benchmarks
Compute average time-in-stage for each pipeline stage across all won deals.
This becomes the baseline for stall detection.
3
Score each deal for risk
Check each deal against the six risk signals. Count the number of active
signals and assign a risk score.
4
Enrich single-threaded deals
For deals with only one contact, use enrichment to find additional
stakeholders at the company. Look for the economic buyer, technical
evaluator, and end user.
5
Generate risk report
Output a ranked list of at-risk deals with specific signals, recommended
actions, and escalation level.
6
Push alerts to CRM
Update deal records with risk scores and create tasks for AEs and managers
via MCP.
Frequently Asked Questions
How often should I run deal risk analysis?
Weekly. Pipeline health changes fast. Set up a Monday morning scan so AEs start the week knowing which deals need attention.What is the best way to re-engage a cold deal without “just checking in”?
Share something specific: a case study, a new feature that addresses their stated concern, an industry benchmark, or a warm intro to a peer who solved the same problem. Give them a reason to respond, not just a reminder that you exist.How do I multi-thread a single-threaded deal?
Use enrichment to find other stakeholders at the company. Look for the economic buyer (usually a VP or C-level), a technical evaluator (usually a manager or director), and the end user. Reach out to each with role-specific messaging. Ask your existing contact for introductions — “Who else on your team should be involved in this evaluation?”When should I kill a deal instead of trying to save it?
When you see 3+ risk signals, the close date has been pushed twice, and the primary contact is unresponsive. Zombie deals corrupt your forecast and waste AE time. Close it out, note the reason, and set a re-engagement reminder for 90 days.How do I prevent over-contacting high-signal accounts?
Follow the 14-day rule: max one signal-triggered outreach per account per 14 days. If multiple signals fire in the same window, combine them into one message. After any positive response (reply or meeting), switch to the regular sales cadence and stop signal-triggered outreach for 30 days.Related: Champion Tracking | Hiring Signals | Fundraising Signals | Competitive Intelligence | Lead scoring and signal discovery