Skip down to the research record

Stale deals: 5 checks before your next forecast call

Quota Forecast Editorial Team · Published · 9 min read

Run five checks before, during and after each forecast call: find idle leads, set nudges, bulk-update deals, log calls and watch CRM hygiene.

Key takeaways

  • start with the open deals and leads that show no logged activity, using a threshold you wrote down before the call.
  • treat Copper's 60-day example as one publisher's starting point, not as the right threshold for every firm.
  • give each re-engagement reminder a named owner, so the review ends with names attached.
  • keep bulk changes in one pass that you read back before saving.
  • review activity logging and CRM hygiene measures on the same day each week, before the call.

Why stale deals distort the number

A forecast call works from the records in front of the group. If an open deal shows an old stage or a close date that nobody has revisited, the figure on the screen may describe a conversation that stopped some time ago. The aim of the five checks is to find those records before the call rather than during it.

Each open deal should show when someone last touched it, and that date is the first thing to read before the call. A deal with a recent note but an old close date raises a different question from a deal with no activity at all. Keeping them in one pile tends to blur the discussion, so review them as separate lines.

Before choosing a threshold, write down the rule you are applying, including the date you ran the review. Keep that note with the list, so the next review can use the same definition. For how forecast categories are defined, see forecast categories explained. The five checks below follow the order of a typical call: find idle records, set nudges, update deals, keep activity logged and watch hygiene.

Before the call: find idle records

The first check is a segment of stale leads. Copper's guide gives it as one pro tip: create a segment of “stale leads” with no activity in 60 days, plus a reminder to re-engage them once a quarter, according to Copper.

Use the 60-day window and quarterly cadence as a starting point, then choose the window and cadence that fit your team's sales cycle. Record the threshold and re-engagement cadence alongside the segment, so you can apply both consistently at the next review.

When you build the segment, include the deal owner, the stage and the date of the last logged activity. Those three details let the review start with named records instead of a general list. Decide whether the segment covers leads, deals or both, so that the review matches the list the forecast draws from.

Before you build the segment, pull a second list of open deals whose expected close date has already passed. A close date that has slipped without a new note deserves a close look, because the date on the screen may no longer match the conversation behind it. For why a close date moved, see the close date change log. Compare each passed date with the last logged activity, and mark the records where the two disagree. Those marked records should be the first items the group discusses.

Once the segment exists, rerun it before each call rather than building a new list each time. A saved view makes it easier to compare this week's idle records with the last review. Sort the segment by owner before the call, so each person can speak to their own records first. The group can then move on to the records without clear owners.

Each record in the segment should show a live next step. A record with no next step needs a reminder or a decision before the call, and that decision belongs in the call notes. Separate leads from deals on the review list. A lead with no activity and a deal with an old close date can need different responses.

Before the call: set follow-up nudges

The second check uses a 3-day no-response window. Copper describes a “3-day no response” automation that nudges you to follow up when a lead has not replied, without you having to remember.

Use the reminder to identify leads awaiting a reply and assign the follow-up before the call. Check your own CRM for a comparable reminder before you plan around one.

If your buyers reply on a different schedule, choose a different window and record the reason in the call notes. A window set for fast inbound replies may not suit a longer buying process, so write down which kind of lead the window was chosen for.

Start the nudge list by recording, for each lead, the date of your last message and the date of the last reply. Keep those two dates in separate columns, so the reviewer can see at a glance who has been waiting longer. A lead whose last message came from the seller and has no reply is the clearest case for a follow-up. A lead that replied recently may need no nudge at all.

Assign each nudge to a named owner. A reminder that reaches nobody in particular leaves the follow-up open, which is the gap this check is meant to close. Before the call, read a sample of the nudges that fired and note whether each one led to a follow-up or a reply. That sample gives the group a concrete basis for keeping or changing the window.

Keep the nudge list separate from the idle-records list. A lead that has been nudged once has not necessarily been re-engaged, so the two lists should not be merged into one count. When a nudged lead replies, note the reply on the lead record, so the next review starts from the latest contact.

Each nudged lead still needs a stated action in the call notes; the owner must decide what to do next.

During the call: update deals in bulk

The third check is a bulk update of deals while the list is open in front of the group. Aviso describes retrieving and updating all deals: “From the reps perspective, just being able to go up and pull all of your deals and being able to update all of them.”

Updating all deals does not necessarily mean editing them in bulk. Confirm the feature in your own CRM before you plan the call around it.

Switching between tools during the call has a cost of its own. Copper's Gmail guide says studies show it can take up to 23 minutes to fully refocus after each switch. The same guide refers to the 2–3 minutes you would normally spend toggling between Gmail and your CRM (Copper).

Keep the bulk list and the call notes in one view, so you are not moving between the forecast and the CRM for every change. Record each change in the list as the group agrees it, then read the list back before saving. A single review pass at the end gives the group one list to check, instead of a run of separate edits.

Before you open the list, choose the one field you intend to change, such as a stage or a close date, and leave the other fields alone. Mixed changes in one pass are harder to read back and harder to explain later. Keep a copy of the list as it looked before the changes, so the group can compare the before and after values during the call.

If a change applies to several deals, write the reason beside it so the reviewer can check each record against that reason.

Changes that a deal owner has not confirmed should wait until that owner confirms them. Mark those rows as pending in the list, so the forecast still shows which numbers are open.

After the call: keep activity logged

The fourth check is to log calls and texts so that records reflect recent contact. Copper's guide for construction companies puts it plainly: “Log calls and SMS automatically so accounts are always up to date.”

That guide is written for construction companies, so treat it as one publisher's description rather than a standard for every team. For a sales team, the practical question is simple: after each call, confirm that the call and any texts appear on the right record.

Ask each rep to name the record that every call and text belongs to. A call with no matching activity on the deal is a gap to fix before the forecast is reviewed. Check the logged activity after each call rather than at the end of the week, since the details are still fresh.

After the call: watch CRM hygiene

The fifth check is to watch CRM hygiene metrics. Aviso describes its Leaderboard this way: “Aviso's Leaderboard enables sales leaders to track sales efficiency over 25+ metrics across deal risk management, forecast accuracy, deal progression, conversation skills, CRM hygiene, and email activity.”

Use these tracking categories to choose your team's measures, rather than to predict a result. Choose the two or three hygiene measures your own CRM reports, and review them on the same day each week so the call starts from current numbers. Write each chosen measure down with the value your team wants it to hold, so the review compares the same thing each time. Agree on who owns the hygiene review before the forecast call, and name that person in the call notes.

Illustrative example: review an idle list

Suppose your saved segment returns 10 leads using a 60-day no-activity threshold. Sort them by owner, then compare their last activity with their next steps. Put leads needing follow-up on the nudge list. Keep deals with passed close dates on a separate review list, so different problems do not become one count.

Your next step today is to build a stale-lead segment using the no-activity threshold you wrote down, and review it before your next forecast call.

Questions

How long without activity makes a lead stale?

A lead is stale once it has gone longer than your chosen threshold without activity. Copper's guide uses 60 days as its example. Treat that as one publisher's example, and set the threshold that fits your own sales cycle.

What does a 3-day no-response automation do?

If a lead has not replied, the CRM nudges you to follow up without you having to remember, according to Copper.

How much time does context switching cost?

Copper gives up to 23 minutes to fully refocus after each switch and 2–3 minutes spent toggling between Gmail and a CRM.

Can deals be updated in bulk?

Only if your CRM offers it. Confirm it in your own CRM before the call. Until you have confirmed it, prepare the changes as a list the owners can review by hand.

Sources