Why your CRM pipeline numbers look wrong
A large CRM pipeline is not a revenue forecast. Check stale deals, stage evidence, deal values, close dates, and actual win rates before trusting the number.
Your CRM says the pipeline is healthy, but the team cannot name the next step for half the deals. Is the number wrong?
First check what it measures. Open pipeline value is usually the sum of amounts on open deals. A weighted pipeline applies a probability to those amounts. A revenue forecast asks which deals may close in a specific period, for what amount, with what evidence. None of these is cash in the bank.
If a dashboard combines old opportunities, hopeful deal amounts, and dates nobody updates, the calculation may be correct while the decision it suggests is wrong. Here is how to audit the gap without deleting history or pretending every sale follows the same timeline.
1. Find deals that are open on paper, not in practice
Filter open deals by time since the last meaningful reply, meeting, or agreed next step. Do not count an automatic reminder as progress. For a small sample, open the record and ask:
- Has the prospect responded recently?
- Is there a named owner and a dated next action?
- Is there evidence they are still considering the work?
- Is a contract, renewal, or service issue keeping this deal active outside the usual sales cadence?
Move unclear records to a review queue, not straight to lost. Choose a review interval from your actual sales cycle; a 90-day silence might be unusual for one service and normal for another. After a person checks the record, mark it active with a real next step, deferred with a reason and review date, or closed with the right outcome. Keep the history.
For a broader check of how work moves through the business, the 30-minute operations audit is a useful starting point. This article stays focused on whether the pipeline number can support a sales decision.
2. Define what each stage proves
A stage such as “Proposal sent” says what your team did. It does not say whether the prospect reviewed it. That stage may still be useful operationally, but it should not be treated as the same evidence as “Proposal reviewed with buyer.”
Write one entry rule and one exit rule for each stage. Make the rule observable enough that two people would classify the same deal the same way.
| Stage label | Evidence to check before advancing |
|---|---|
| Meeting booked | A time is confirmed; attendance is not yet assumed. |
| Discovery complete | The conversation happened and the need and decision process were recorded. |
| Proposal under review | The buyer received it and a review or decision date is agreed. |
| Agreed, awaiting signature | The buyer confirmed intent; contract approval is still outstanding. |
This is not a required set of stages. A repeat customer, a tender, or a short phone sale may need a different path. The useful question is whether the stage represents an event you can verify, not whether its name sounds advanced.
3. Check the amount and the likely close period
Open a few of the largest deals. Compare the amount in the CRM with the actual proposal, scope, or agreed fee. Is it the signed amount, a current estimate, or the best-case package? If the scope is uncertain, record what the amount assumes rather than quietly choosing the biggest option.
Then inspect the close date. If it is still last month, the deal should not silently roll into this month's forecast. Ask the owner for the next decision date, what could delay it, and whether any part of the amount belongs in a later period. For recurring work, make clear whether the deal amount means one month, a contract term, or something else.
Do not replace every value with a “floor” and then also apply a probability without explaining both adjustments. A conservative deal amount answers how much; a probability answers how likely. Changing both can understate the same uncertainty twice.
4. Calibrate probabilities instead of guessing
Some CRMs show a weighted amount by multiplying the deal amount by its probability; HubSpot's forecast settings documentation describes that calculation for its forecast tool. The formula is simple. Choosing a useful probability is not.
Start with comparable deals that reached each stage in the past, including those later lost. Check how often they actually closed, and separate materially different services or deal sizes when you have enough history. If you do not have enough data, label the stage probability as an estimate and review it as outcomes arrive. A manager may also need to flag a deal whose evidence differs from the usual stage; do not ban exceptions just to make a dashboard look consistent.
Illustrative example, not a client result: three deals at $20,000 each make a $60,000 open pipeline. One prospect has declined, leaving $40,000 genuinely open. If comparable deals at that stage historically closed one in four times, the two remaining deals would total $10,000 when weighted at 25%. That is not a promise of $10,000 in revenue this quarter: their decision dates may be later, and a small sample can make the rate unreliable.
5. Compare past forecasts with what happened
Save a snapshot of deals for a defined month or quarter: stage, amount, expected close date, owner, and the evidence behind the next step. At the end of the period, compare the snapshot with closed-won and closed-lost outcomes. Ask which deals slipped, which amounts changed, and whether any late arrivals closed without appearing in the snapshot.
Do this across several periods before changing every probability. A single large project can distort a small team's numbers. The goal is to find a repeatable mismatch, such as proposals consistently taking longer than the CRM's close dates suggest.
A 20-minute pipeline check you can do now
- Choose the period you actually need to plan for.
- List open deals with their owner, last meaningful contact, stage evidence, amount, close date, and next step.
- Put records with missing evidence in a review queue; have an owner resolve them rather than auto-closing them.
- Separate all open value, deals with current evidence, and in-period forecast on the dashboard. Label each number.
- Recheck the same view next week, then compare a saved snapshot with outcomes when the period ends.
A smaller number after review is not itself a success. A useful pipeline is one the team can explain and update, with enough evidence to make staffing and follow-up decisions. Even a carefully weighted forecast is an estimate, not a cash-flow guarantee.
If you want another set of eyes on where your stages, ownership, and reporting diverge, bring a few anonymized deal examples to a Growth Systems Review. We can map the gaps and decide what to fix first.