// GuidesHow-to
How to identify at-risk deals before they slip: 12 signals (2026)
Short answer
A deal is at risk when three or more of twelve observable signals are true at the same time: the close date pushed, no logged activity for 14 days, no next step, time in stage above your usual, a stage moved backward, the amount cut, one contact on the deal, slower buyer replies, a meeting canceled or moved twice, the rep gone quiet on the deal, the champion gone, and a last call that ended without a decision. At-risk deals usually show warning signs 2 to 4 weeks before they slip, per Sybill, which is enough time to act if you look every week. Count the signals on every open deal, review any deal at 3 of 12 this week, and run the 20-minute routine below every Monday.
What are the early warning signs a deal is at risk?
The early warning signs are the twelve in the table below. Roughly half of them live in fields the rep types into the CRM. The rest live in what the buyer does: reply, show up, bring colleagues, agree to a next step. A deal that looks fine in the CRM and wrong in the buyer’s replies and meetings is the one that slips. Sybill’s at-risk guide puts the window plainly: "At-risk deals show warning signs 2-4 weeks before they slip."
| Signal | Where it shows up | Threshold or rule | What to do |
|---|---|---|---|
| Close date pushed | CRM close-date history | Two or more pushes on the same deal (Sybill). | Ask what the buyer said that moved it. No buyer event named means the date was a guess; re-forecast it. |
| No logged activity | CRM tasks, calls, emails, meetings | Nothing in the past 14 days (Sybill); shorter or longer by sales cycle, see below. | Check for unlogged work first, then agree on one re-engagement step with a date. |
| No next step | CRM next-step field, plus the calendar | Next step blank or "follow up", or no future buyer meeting on the calendar. | The rep books the next step this week, or the deal drops a forecast category. |
| Stuck in stage | CRM stage history | Time in stage "twice as long as your average" (Mixmax). | Re-check the stage exit criteria with the rep; if they are unmet, move the deal back. |
| Stage regressed | CRM stage history | Any backward move. | Treat it as a new deal at the earlier stage and find out what the buyer learned. |
| Amount changed | CRM amount history | A cut after the proposal, or a round number that never had a quote behind it. | Ask whether scope shrank or budget did. Forecast the number a quote supports. |
| Single-threaded | CRM contact roles; who is on the email threads | One contact on the deal. Forecastio: "If that contact goes silent or leaves, the deal is at high risk." | Get a second person into the next meeting: the champion’s boss or a future user. |
| Buyer replies slower | Email threads | Replies that used to come within hours now take two or three days (Sybill). | Send something the buyer needs, such as a summary of what they told you and the decision they still owe. |
| Meeting canceled or pushed | Calendar | A cancel with no new date within a week (our rule of thumb), or a second reschedule (Mixmax). | The rep proposes two slots the same day. No answer within a week means escalate to the sponsor. |
| Rep went quiet on the deal | CRM activity by rep; the Slack deal channel | The rep stopped logging touches or mentioning the deal; Highspot: "skipping follow-ups on a late-stage deal". | Ask the rep directly. Often it is a deal they have given up on without saying so. |
| Champion left or changed role | Email bounce or auto-reply; the CRM contact record | The main contact is out, moved, or has handed the deal to someone new. | Re-map the buying group before the next step. A new contact restarts qualification. |
| Last call ended without a decision | Call recording or transcript; the rep’s call notes | No agreed next step, an open pricing or legal objection, or "we will circle back". | Coach the rep on the next call. If the deal is in commit, join it. |
Read roughly the first half of the rows as the rep’s account of the deal and the rest as the buyer’s. When the two disagree, believe the buyer. Use only calls recorded under your company’s recording policy and the consent rules where your reps and buyers are.
Watch out
The mistake most managers make
Scoring risk only from the CRM. Stage, close date and forecast category are the rep’s opinion, and an optimistic rep keeps them green until the day the deal dies. The earliest signals are in the buyer’s replies and meetings: a reply that took three days, a meeting moved twice. Put at least one buyer-behavior signal in every review.
How many days without activity is a red flag?
Fourteen days is the line to start from. Sybill’s at-risk guide tells managers to "identify deals with no activity (no calls, no emails, no meetings) in the past 14 days." The right line depends on your sales cycle. A starting point you can adjust after a quarter:
| Typical sales cycle | No-activity line | Reasoning |
|---|---|---|
| Under 30 days | 7 days | A week of silence is a quarter of the cycle gone. |
| 30 to 90 days | 14 days | The line Sybill uses. Two weeks is one missed follow-up plus one missed reply. |
| Over 90 days | 21 days | Long cycles have quiet weeks by design; three in a row is a pattern. |
Two cautions. First, "no activity" means no logged activity. Ask the rep to check their inbox and calendar before you act; a rep who had a call yesterday and did not log it needs a nudge about logging, and the deal comes off the list. Second, too long a line and you find out in the last week of the quarter; too short and reps learn to log a throwaway email every ten days. Forecastio’s pipeline guide puts the hygiene half plainly: deals "that have no activity, no next step, or outdated close dates should be corrected or removed."
How do I score deal risk in Salesforce or HubSpot? The 3-of-12 rule
Count, do not weight. Score every open deal against the twelve signals and review this week any deal with three or more. The 3-of-12 line is our rule of thumb, not an industry standard. A count is something you can explain to a rep in one sentence, and it needs no history to calibrate.
- 0 to 2 signals: the rep owns it. If you noticed something, leave a one-line note for the 1:1.
- 3 or more: on this week’s review list, whatever the stage or the forecast category says.
- Hard signals that put a deal on the list alone: stage regressed, champion left, close date pushed for the second time. Each one means the deal you had is gone.
- Commit deals: review at 2 of 12. The forecast is already leaning on them.
Six of the twelve can be saved as a CRM report or view on standard fields. In Salesforce, turn on field history tracking for Close Date and Amount first, or the history report is empty. Sort by close date.
| Signal | Salesforce filter | HubSpot filter |
|---|---|---|
| Close date pushed | Opportunity Field History report on Close Date | Deal property history on Close date |
| No logged activity | Last Activity older than your line (7, 14 or 21 days by sales cycle, see above) | Last activity date older than your line |
| No next step | Next Step is blank | Next step is unknown |
| Stuck in stage | Stage Duration (report column) above your usual for that stage | Date entered (stage) older than your usual for that stage |
| Amount changed | Opportunity Field History report on Amount | Deal property history on Amount |
| Single-threaded | Contact Roles: one contact on the opportunity | Associated contacts: one on the deal |
If you prefer a graded score, NBH’s HubSpot recipe grades each deal 1 to 5 on three questions, starting with "Is the next step defined or just a ‘follow up’?", and reviews the five worst-scoring deals. It is a good tie-breaker when more deals hit 3 of 12 than you can review in a week. Neither CRM sees the buyer half of the table; the rep counts that half from their own inbox and calendar, or you count it from the threads logged on the deal.
What should a manager do once a deal is flagged?
Pick one action per flagged deal, matched to the signal that fired, and write down who does it by when. A flagged deal with no owner and no date is a flag you will see again next week.
- Verify before you act. Open the email thread logged on the deal (or ask the rep for it) and the calendar. If the CRM signal is a logging gap, the action is a one-line reminder to the rep, and the deal is off the list.
- Re-qualify in the buyer’s terms. Ask the rep what the buyer has to do next, whether the buyer agreed to it, and by when. If the answer is what the rep plans to do, the deal has no next step.
- Multi-thread. Single-threaded and champion-changed deals get the same fix: a second contact in the next meeting, ideally the person who signs or the person who will use it.
- Move the forecast, then the deal. A deal at 3 of 12 does not belong in commit. Move it to best case now; a miss is better found in week 3 than in week 12.
- Join the next call on the largest deals. For the two or three biggest flagged deals, get on the next buyer call. You will hear in ten minutes what the CRM could not tell you in three weeks.
Tip
A worked example
Say a $48,000 deal has sat in Proposal for five weeks against your usual two, the close date moved from June 20 to July 15 last Tuesday, and the buyer’s last reply took four days. That is three of twelve. The actions are a re-qualification call with the rep today, a request to the champion for 20 minutes with the budget owner, and a move from commit to best case until that session is on the calendar.
The 20-minute weekly at-risk deal routine
Twenty minutes, same time every week, before the pipeline review or the forecast call. Pull, count, cross-check, choose, decide, send.
- Minutes 0 to 3: pull the exceptions. Open the saved CRM view: close date pushed since last week, no activity past your line, next step blank, stage entry older than your usual. Sort by close date.
- Minutes 3 to 8: count signals. Walk the list against the checklist below and write the count next to each deal. Anything at 3 of 12, or carrying one hard signal, goes on the review list.
- Minutes 8 to 12: cross-check outside the CRM. For each deal on the review list, open the email thread logged on the deal (or ask the rep for it) and the calendar. An unlogged call or a meeting booked yesterday takes the deal back off.
- Minutes 12 to 15: pick the deals that matter. Rank by amount and close date and keep 3 to 5, the number Sybill recommends a pipeline review focus on. The rest go back to the rep with a note.
- Minutes 15 to 18: decide one action per deal. Use the "what to do" column. One action, one owner, one date.
- Minutes 18 to 20: send and schedule. One line to each rep: the deal, the signal, the ask, the date. Put a check on your own calendar for that date.
A deal on the list two weeks running with no action taken has become a conversation about the rep’s follow-through rather than about the deal.
The 12-signal checklist (copy it into your review doc)
- Close date pushed for the second time
- No logged activity past your line (14 days for a one-to-three-month cycle)
- No next step, or no future buyer meeting on the calendar
- Time in stage above your usual for that stage
- Stage moved backward
- Amount cut, or a round number with no quote behind it
- One contact on the deal
- Buyer replies slower than they used to
- Meeting canceled with no new date, or moved for the second time
- Rep stopped logging touches or mentioning the deal
- Champion left, changed role, or handed off
- Last call ended with no agreed next step or an open objection
How diffi helps
diffi does the pull-and-count half of this routine for you. It connects to Salesforce or HubSpot (read-only; it does not write to your CRM) and records what changed on each deal as plain facts: a close date pushed, a stage regressed, an amount changed, a meeting rescheduled or canceled, and, from Salesforce, a deal with no change for 21 days. Slack, mail and calendar feed each rep’s file and the signals, not the deal facts. When those facts add up it raises a deal-risk or pipeline-risk signal, shows the evidence behind it, and ranks which reps need attention first. You can ask it in plain language which deals changed this week or who needs attention, and the answer links to its sources. Once you confirm, it can message the rep on Slack, book the follow-up meeting with an invite, or open a tracker for next week’s check. Book a demo to see it on your own pipeline.
See it on your own teamHow is deal risk different from deal slippage?
Deal risk is a judgment about an open deal that looks unlikely to close as forecast. Deal slippage is a measurement after the fact: the deal did not close in the period it was dated for, and its close date moved out. Risk is the leading indicator and slippage the lagging one.
ORM Technologies defines the slippage rate as "the share of pipeline dated to close in a period that moves to a later period instead" and gives the formula as slippage rate = value of deals pushed past the period ÷ value of deals dated to close in the period at period start. Run the same ratio by deal count if your deal sizes are similar.
Say 20 deals worth $600,000 were dated to close this quarter on day one, and by the last day 7 of them, worth $250,000, had moved to next quarter. By value the slip rate is 250,000 ÷ 600,000, or 42%; by count, 7 ÷ 20, or 35%. Track it by rep and by quarter.
Use both. Risk, counted weekly, tells you which deals to work now. Slip rate, measured quarterly by rep, tells you whose close dates to trust and whether the weekly routine catches deals early enough. Forecastio gives the reason: warning signs such as stalled activity or slipping close dates seldom correct on their own.
Frequently asked questions
What are the early warning signs a deal is at risk?
A pushed close date, no logged activity for 14 days, no next step, a deal stuck in a stage longer than usual, a stage moving backward, an amount cut, a single contact, slower buyer replies, canceled or repeatedly moved meetings, a rep going quiet on the deal, a champion leaving, and a last call that ended without a decision. Roughly half are visible in CRM fields; the rest are in email, the calendar, Slack and call recordings.
How many days without activity is a red flag?
14 days is the usual line for a sales cycle of one to three months, and it is the number Sybill’s at-risk guide uses. Use 7 days for cycles under a month and 21 days for cycles over three months. Ask the rep to check their inbox and calendar before acting, because "no activity" often means "not logged".
How far in advance can you tell that a deal will slip?
Usually two to four weeks. Sybill puts the warning signs of an at-risk deal two to four weeks ahead of the slip, which is why a weekly check catches most of them and a monthly one does not.
How do I score deal risk in Salesforce or HubSpot?
Count signals rather than weighting them. In Salesforce, save an opportunity report filtered on Last Activity, an empty Next Step and Stage Duration, and turn on field history for Close Date and Amount. In HubSpot, save a deals view on Last activity date, Next step and Date entered (stage). Review any deal with 3 of 12 signals this week (our rule of thumb, not an industry standard); the buyer-side signals (replies, meetings, champion) the rep counts from their own email and calendar, or you count from threads logged on the deal.
What should a manager do once a deal is flagged?
Verify the signal outside the CRM, then pick one action matched to it: re-qualify the next step with the rep in the buyer’s terms, get a second contact into the next meeting, move the deal out of commit, or join the next buyer call on the largest deals. Write down who does what by when, and check it the following week.
How is deal risk different from deal slippage?
Deal risk is a judgment about an open deal that looks unlikely to close as forecast. Deal slippage is the measured outcome: the close date moved out of the period. ORM Technologies defines the slippage rate as the value of deals pushed past the period divided by the value of deals dated to close in the period at period start. Track risk weekly and slippage quarterly.