Skip down to the research record

Stale deal signals: 5 publishers to check before the call

Quota Forecast Editorial Team · Published · 13 min read

Freshsales, Pipedrive, HubSpot and Close each flag a stale deal with their own rule, so check your tool's named setting before the call.

Key takeaways

  • Freshsales, Pipedrive, HubSpot and Close each document a stale, rotting or stalled feature, and each defines it differently.
  • Microsoft's seven-day cycle refreshes premium forecasting predictions; it does not flag quiet deals.
  • The 25-day Freshsales figure is an example, not a default for your pipeline.
  • Pipedrive's rotting feature ignores the next activity date, so a future meeting does not keep a deal fresh.
  • Write the signal your own tool names next to the deal before the call.

Stale-deal flags differ by publisher

A deal is not quiet by a single standard across your tools. Each vendor defines the signal differently. Freshsales describes the underlying concept: as a deal ages, the likelihood of winning it diminishes, so the deal rots or stales. This is a definition of the phenomenon, not a specific day count or percentage.

The practical implication for your weekly call is that you cannot apply one threshold to all your pipelines. If you use a 25-day rule from one tool's documentation and apply it to a tool that uses a 20% stall mark, you are mixing definitions. The "quiet" state is defined by the specific field or logic in each system.

Before you open the pipeline view, identify which mechanism your current tool uses to flag inactivity. Is it a day count you type, or a percentage of expected activity? The signal is the tool's specific rule, not a universal sales metric.

Check the help documentation for your specific CRM to find the named field or feature that flags inactivity. Do not assume that a "stale" deal in one system means the same thing in another. The definition is local to the product.

How each publisher's signal works

The signal you see in your tool depends on which product you use and how that product defines "stale."

Freshsales uses a day count you type into the system. The documentation provides an illustrative example where the sales cycle is assumed to be 25 days; when the deal age exceeds that number, the deal turns red according to Freshsales. This 25-day figure is an example for that specific pipeline scenario, not a fixed standard for every user.

Pipedrive offers a Rotting feature that provides visibility into deals that have been idle for too long according to Pipedrive. This feature focuses on the duration of inactivity rather than a specific percentage of a historical average.

HubSpot uses a percentage-based stall mark, according to HubSpot. This signal is relative to the specific owner's historical performance.

Microsoft Dynamics 365 Sales recalculates premium forecasting predictions every seven days automatically, and this cannot be triggered manually, according to Microsoft. This is a forecasting refresh schedule, not a flag for how long a specific deal has been quiet.

The day count you type, and the 25 day example

Freshsales provides a specific field where you input a number to define when a deal becomes stale. In the "Deals go stale after" section, you assign the staling age of the deal in days, according to Freshsales. This is a manual entry point where you determine the threshold for your own pipeline. The documentation uses a specific number to illustrate how this mechanism functions. It states, "For example, let us assume that the sales cycle for your pipeline is 25 days," according to Freshsales. This 25-day figure is an illustrative example used to explain the logic of the setting. It is not a fixed rule or a default value that applies to every user or every sales cycle. You must type the number that matches your specific sales process into the field.

The system identifies deals based on the age you have set. "Deal stale identifies the deals that have exceeded their staling age," according to Freshsales. When the age of a deal in the pipeline exceeds the number you assigned, the deal turns red, according to Freshsales. In the example provided, if the staling age is set to 25 days, the deal turns red when it exceeds that age. This visual change helps you spot the deal before the weekly call. Red means the deal has exceeded its configured staling age.

Illustrative example: a 20-day staling age

Suppose a team sets a staling age of 20 days for its pipeline. One deal was last updated 25 days ago, so it has exceeded that age and shows as stale. A second deal was updated 10 days ago and is not flagged. Before the call, the owner of the first deal checks the underlying emails and activity, then writes the setting and the planned action next to the deal. These numbers are illustrative only.

Reference table: stale-deal signals by publisher

The table below compares inactivity indicators, activity context, and forecasting refresh schedules by publisher. Each row describes a distinct mechanism: a typed day count, a percentage-based stall mark, a 30-day activity card, a seven-day prediction refresh, or a stalled flag. These are separate signals, not one universal rule.

PublisherSignal TypeSpecific Value or MechanismSource Context
FreshsalesDay count example"For example, let us assume that the sales cycle for your pipeline is 25 days." The deal turns red when the age exceeds 25 days.Freshsales
PipedriveIdle visibility"The Rotting feature provides visibility into deals that have been idle for too long."Pipedrive
HubSpotPercent stall mark"Is Stalled After Timestamp: timestamp when Time in stage became 20% longer than the deal owner’s closed-won average for that stage."HubSpot
Freshsales30-day activity card"The card gives an overview of the recent performance of the deal and shows how the deal is performing, sales activities performed on the deal in the last 30 days, and suggests the next best action that can be carried out on the deal."Freshsales
MicrosoftForecast refresh schedule"Predictions (premium forecasting): Recalculated every seven days automatically; can't be triggered manually."Microsoft
CloseStalled flagClose describes a stalled opportunity as one that has remained in the same pipeline stage longer than expected.Close

The 25-day figure in the Freshsales row is an illustrative example of a sales cycle, not a fixed rule for every pipeline. The 30-day card in the second Freshsales row is a separate insight view, not the same stale-age field. The seven-day prediction refresh is a calculation cycle, not a rotting age. The 20 percent stall mark is a relative comparison to a deal owner’s average, not an absolute day count.

Use this table to check which signal your own tool’s help page names before the call. Write that specific signal next to the deal you are reviewing. Do not treat a red tile, a stall timestamp, or a prediction refresh as the same rule. Each documented staling or inactivity feature works differently, and the weekly forecast call should reflect those distinct definitions.

For a wider pre-call routine, see Stage duration: 8 checks before the weekly call.

A future meeting does not by itself keep a Pipedrive deal fresh

The Rotting feature provides visibility into deals that have been idle for too long, according to Pipedrive. Once enabled and configured, your pipeline will visually notify you of any deals that you haven‘t updated for longer than the defined rotting period, according to Pipedrive. The rotting period is based on the deal‘s last updated time, which can include marking activities as done, sending, receiving, archiving, unlinking, or deleting emails linked to the deal, according to Pipedrive. Click the “Rotting in (days)” toggle to activate it, then define the number of inactive days after which a deal in this stage is considered rotten, according to Pipedrive.

You’ll know a deal has gone rotten by the red color on the deal tile in your pipeline view, according to Pipedrive. The rotting feature disregards the next activity date, so any deal with an activity scheduled far into the future can still go rotten, according to Pipedrive. Because of visibility constraints for some actions (especially email actions), a deal may appear untouched in the changelog or stage view, while its rotting timer has still been reset, according to Pipedrive.

Check the last updated time on a specific deal before the call. If the timer shows a reset from an email action, look at the underlying email or activity evidence where available. Archiving, unlinking, or deleting an email can reset the timer without any customer interaction, and some resets do not show in the changelog. For more on how activities attach to deals, see Activity linking: 8 rules for deals and visibility.

A red tile, a 20 percent stall time, and a seven day prediction are different signals

The documented quiet-deal indicators from Freshsales, HubSpot, Pipedrive and Close do not operate under the same rule, and Microsoft's refresh schedule is a different kind of signal. Understanding the specific trigger for each system prevents you from misinterpreting a status indicator as a universal standard for deal age.

HubSpot's default deal properties include a specific timestamp that marks when a deal has stalled. The "Is Stalled After Timestamp" records the moment when the time in stage became 20% longer than the deal owner’s closed-won average for that stage, according to HubSpot. This is a percentage-based comparison against historical performance, not a fixed number of days. The system calculates this relative to the owner's own average, meaning the threshold varies by rep and stage.

In contrast, Freshsales provides a card that gives an overview of the recent performance of the deal. This card shows how the deal is performing, lists sales activities performed on the deal in the last 30 days, and suggests the next best action that can be carried out on the deal, according to Freshsales. This 30-day window is a fixed look-back period for activity review.

Microsoft's forecasting management FAQs describe predictions as being recalculated every seven days automatically, and they cannot be triggered manually, according to Microsoft. This seven-day cycle is a refresh interval for premium forecasting predictions. It is not a rotting age or a stall threshold. Separately, forecast values are only updated every 24 hours or can be refreshed manually anytime, according to Microsoft. The 24-hour update for forecast values is distinct from the seven-day recalculation of predictions.

Close's Opportunities help center defines a stalled opportunity as one that has remained in the same pipeline stage longer than expected, according to Close. This definition is qualitative, relying on the concept of "longer than expected" rather than a specific percentage or fixed day count visible in the quote.

When you review your pipeline before the weekly call, do not treat a red tile or a stall flag as a single universal metric. HubSpot’s 20% longer-than-average timestamp, Freshsales’s 30-day activity card, and Microsoft’s seven-day prediction refresh are separate signals with different underlying logic. Focus on the distinction between a percentage-based stall, a fixed activity window, and a prediction refresh cycle.

Checklist for one quiet deal

Pick one open deal that has had no note from you this week. Find the quiet-deal signal your own tool's help page names, and write that signal next to the deal before the call. Record it in a table with these columns.

ItemSignal IdentifiedAction Taken
ExampleThe indicator your tool shows for the deal, such as a red tileA note to the deal owner before the call

The "Signal Identified" column is where you record the exact indicator your tool provides. For example, if your tool uses a day count, write the number of days shown. If it uses a percentage stall mark, write the percentage. If it uses a color change, write the color. Do not copy a number from another tool's documentation into this column. The signal must come from the deal record you are reviewing.

In the "Action Taken" column, write the step you are taking because of that signal. This could be a call to the customer, an email to the owner, or a change to the close date; if the date moves, see Close date change log: why the date moved. Keep the action specific to the deal. Do not write a general policy statement. The goal is to have a clear, documented reason for why this deal is on your list for the weekly call.

Your next step today

Open one deal in your pipeline now, find the stale, rotting or stalled setting named in your tool's help page, and write it next to the deal.

FAQ

How do I see that a deal has gone quiet before the call?

Check the stale or stalled indicator your tool names for that deal, such as a red tile or a stall flag. Each system defines inactivity differently, so review the specific signal your tool provides for the deal in question.

What is the 25 day line on the Freshsales page?

The 25-day figure is an example used to illustrate how the staling age field works, not a fixed rule for all pipelines. The documentation states, "For example, let us assume that the sales cycle for your pipeline is 25 days" according to Freshsales. Do not apply this specific number as a universal standard for your own pipeline.

Does a future activity keep a Pipedrive deal from rotting?

No, a future activity does not prevent a deal from going rotten. The rotting feature disregards the next activity date, so a deal with an activity scheduled far into the future can still go rotten, according to Pipedrive.

What does HubSpot's 20 percent stall mark mean?

It is a timestamp indicating when the time in stage became 20% longer than the deal owner’s closed-won average for that stage according to HubSpot. This metric helps identify when a deal is taking significantly longer than the owner's typical performance in that specific stage.

What does Microsoft say refreshes every seven days?

Premium forecasting predictions are recalculated every seven days automatically and cannot be triggered manually, according to Microsoft. Forecast values follow a separate rule: they are updated every 24 hours or can be refreshed manually anytime.

Sources