What is the difference between a forecast category and a sales stage?
Sales stage records process position. Forecast category records timing confidence. They measure different things, and a deal's value on one says very little about its value on the other.Stage answers what work has been completed. Discovery finished, technical validation passed, pricing agreed, contract in legal. It is evidence-based and it should be governed by written exit criteria that a manager can verify.
Category answers a different question. Will this deal produce revenue inside the current period? That depends on the buyer's timeline, their procurement calendar, and whether the close date has been stable, none of which appear in the stage field.
Why do teams collapse them into one field?
Because a stage-to-category mapping is easy to configure and it removes an uncomfortable conversation. Once the CRM sets category automatically, nobody has to state a personal commitment out loud.The cost is that you lose the only signal that carried judgment. Stage is largely mechanical. A rep advances a deal when the criteria are met, and the criteria are about the seller's process rather than the buyer's calendar. Category is where a human is supposed to say whether the buyer will actually sign this quarter.
Automating the mapping produces a forecast that is a restatement of stage distribution. That is a pipeline report wearing a forecast label, and it is why so many teams find their commit number and their eventual result diverge in exactly the same direction every quarter.
What do the standard categories mean?
Four categories cover most B2B SaaS pipelines, and each needs a written definition rather than a shared intuition.| Category | Meaning | Typical rule |
|---|---|---|
| Pipeline | Open, no specific in-period expectation | Close date in period but no verified buyer timeline |
| Best case | Could close if several things go right | Buyer timeline stated, at least one dependency unresolved |
| Commit | The rep will be held to it | Verified decision date, approved pricing, no open blockers |
| Closed | Already won | Signed |
Some teams add an omitted category for deals explicitly excluded from the period. That is useful, and it should be reported rather than hidden, because a growing omitted bucket is an early warning that the period is being quietly abandoned.
Can stage and category disagree?
They should disagree regularly, and a pipeline where they never diverge is a pipeline where category is not being used.A deal in the final stage with a buyer whose budget cycle opens next quarter belongs in pipeline, not commit. Late stage, low timing confidence.
A deal in an early stage with a signed order form pending only a countersignature belongs in commit. Early stage, high timing confidence. This happens constantly in land-and-expand motions where an existing customer adds seats without running the full process.
The most useful report in a forecast call is the exception list. Show every deal where stage and category disagree, in both directions, and make the owner explain each one. That list is short, and it contains most of the period's real risk.
Which one drives the forecast number?
Category drives the number. Stage drives the confidence you place in the category. Neither is the forecast on its own.A roll-up that sums commit and applies a historical commit-to-close rate is a reasonable starting point. It is only a starting point, because it covers a single source of revenue. A complete forecast has to explain what closes from existing pipeline, what gets created and closed inside the period, and what gets pulled forward from later periods at a cost to those periods. Category speaks only to the first of those.
There is a measured reason to be skeptical of the visible pipeline in general. Of the pipeline carrying in-period close dates on the first day of a quarter, roughly 20 percent closes in that quarter across ORM customers. Four fifths of the value that appears to belong to the period does not land in it. Category discipline narrows that gap and does not close it. The mechanics of building the full picture are covered in how to create a sales forecast.
How do you keep the two fields honest?
Audit stage against exit criteria and audit category against close date stability. Different checks, different owners.Stage audits belong to the frontline manager. Pull a sample of deals in each stage and verify the criteria were met. A deal in technical validation with no technical contact identified is a stage error, and stage errors propagate into every conversion rate you calculate.
Category audits belong to RevOps and they turn on one field. The clearest signal that a commit deal will not land is the rep moving the close date. Any deal that has pushed its close date and remains in commit needs an explicit justification. Two pushes on the same opportunity should force a category downgrade by default, and the pattern behind that rule is explained under deal slippage.
Track category accuracy per rep across periods. Persistent optimism and persistent sandbagging are both stable per person, which makes them correctable once you have four quarters of history. Correcting a known bias is cheaper than arguing about a single deal.
What breaks when the mapping is automated?
You lose the ability to see a problem before the period ends. An automated category moves only when stage moves, so a deal that is stalling silently keeps its category until someone advances or closes it.That is the wrong direction of travel. The earliest warning that a deal is in trouble is the absence of a signal rather than the presence of a bad one. No stage change, no close date change, no amount change, no reply from the buyer. An automated mapping is structurally blind to all four, because it only reacts to the stage field it is watching.
The practical fix costs nothing. Keep the automation as a default so reps start from a sensible category, require a reason code on any override, and report the override rate. A team with a zero percent override rate is not forecasting. It is reporting stage distribution and calling it a commitment, which is the failure mode described throughout our work on sales forecasting.
Frequently Asked Questions
What is the difference between a forecast category and a sales stage?
Sales stage describes process position. It records what has been completed on a deal, such as discovery, technical validation, or contract negotiation. Forecast category describes timing confidence. It records how likely the deal is to close inside the current period. A deal can be late stage and low confidence, or early stage and highly likely to close this month.
Should forecast category be set automatically from sales stage?
No. Automating the mapping turns two independent signals into one, and the one you keep is the weaker of the pair. A deal in the negotiation stage whose close date has moved twice does not belong in commit, and an automated rule will put it there anyway. Automate a default if you must, and let reps and managers override it with a documented reason.
What are the standard forecast categories?
Most B2B SaaS teams use pipeline, best case, commit, and closed. Pipeline covers open deals with no specific in-period expectation. Best case covers deals that could close if things break right. Commit covers deals the rep is willing to be held to. Closed covers deals already won. Some teams add omitted for deals explicitly excluded from the period.
Can a deal in commit still slip?
Yes, and it happens more than most sales leaders expect. When a deal slips from one quarter to the next it becomes less likely to close at all, even while it sits in commit. Category is a statement of confidence, not a guarantee, which is why slippage should be tracked as its own metric rather than absorbed into the next period's forecast.
Which one belongs in a pipeline review?
Stage drives the deal conversation and category drives the number conversation. Run the pipeline review on stage and exit criteria, because that is where coaching happens. Run the forecast call on category, because that is where commitments get made. Mixing them produces a two-hour meeting that resolves neither.
See how ORM turns these insights into action
ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.
Schedule a Demo