A forecast can look healthy while hiding a weak sales process. If reps use “Commit” for deals that are still in discovery, your number becomes a wish list with a dashboard.
Salesforce forecast categories give every opportunity a shared confidence label. For a B2B SaaS team, the goal is simple: forecast recurring revenue with rules that sales reps can follow and managers can trust.
The setup starts in Salesforce, but accuracy comes from how your team defines evidence for each stage.
How Salesforce Forecast Categories Work
Salesforce connects opportunity stages to forecast categories. A rep changes the opportunity Stage, and Salesforce assigns the category that your admin mapped to that stage.
That distinction matters. Reps should update real deal progress, not pick a forecast label that makes the weekly call easier.
The standard forecast buckets
Salesforce includes five standard categories: Pipeline, Best Case, Commit, Omitted, and Closed. Its forecast category customization guidance also covers the optional Most Likely category in Lightning Experience.
Here is how the standard labels work in practice:
- Pipeline contains open opportunities that remain possible but lack enough proof for a manager’s forecast.
- Best Case includes deals that could close in the forecast period, although important risk still exists.
- Commit is the amount the seller and manager are willing to call as likely to close.
- Closed captures Closed Won opportunities.
- Omitted keeps opportunities out of forecast totals. Closed Lost commonly maps here.
Most Likely can sit between Best Case and Commit. It helps teams that need a visible middle ground, but it also adds another judgment call. Small sales teams often get more value from fewer, consistently applied categories.
What Salesforce does, and what your process decides
Salesforce handles the mechanical part. It maps a Stage value to one forecast category, then uses that category in forecasting totals.
Your sales process sets the meaning. Salesforce does not decide whether a security review, verbal approval, or legal redline deserves Commit status. Your team does.
A category is only as reliable as the deal evidence required to enter the stage mapped to it.
The Salesforce guidance on stage-to-category mappings shows the familiar default pattern: Prospecting through Value Proposition map to Pipeline, Proposal/Price Quote maps to Best Case, Negotiation/Review maps to Commit, Closed Won maps to Closed, and Closed Lost maps to Omitted.
Prepare Your Forecast Design Before Setup
Start with the buying events that change your confidence. B2B SaaS sales cycles can include technical validation, an executive sponsor review, procurement, information security, and legal review. A stage should capture a real shift in the deal, not a vague activity.
Define evidence for each late-stage move
Keep early stages broad. For example, a “Discovery” stage can cover qualification, problem confirmation, and early stakeholder work. However, late stages need stricter requirements because they affect the forecast.
A practical SaaS mapping may look like this:
| Opportunity stage | Forecast category | Required deal evidence |
|---|---|---|
| Discovery and qualification | Pipeline | Problem, potential value, and next meeting are confirmed |
| Solution validation | Pipeline | Use case and evaluation path are documented |
| Business case or mutual plan | Best Case | Buying process, champion, and target close date are known |
| Proposal and commercial review | Best Case | Pricing is shared and decision criteria are confirmed |
| Procurement, legal, or final approval | Commit | Commercial terms are agreed and a named approval path exists |
| Closed Won | Closed | Contract is signed or your revenue policy permits booking |
| Closed Lost | Omitted | Opportunity is no longer active |
This approach keeps a promising pilot out of Commit until the customer has moved beyond interest.
Decide what amount you are forecasting
Recurring-revenue businesses often confuse contract value, annual recurring revenue, and first-year revenue. Salesforce can forecast opportunity amounts, but your team must decide what the Amount field means.
If Amount is total contract value for a three-year agreement, a $120,000 deal does not equal $120,000 of new ARR. Use a governed ARR field in reports and planning if ARR is the executive metric. Do not assume a custom ARR field automatically appears in every native forecast grid.
For a young company, use one rule consistently. You might forecast first-year recurring revenue for new business and annualized uplift for expansions. Document that choice in the opportunity field help text and manager forecast process.
Configure Salesforce Forecast Settings First
An admin needs to set up the forecasting feature before stage mappings can produce useful rollups. Salesforce configuration can differ by edition, enabled products, and whether you use territory forecasting, so confirm what your org supports before changing production settings.
Set up access, hierarchy, and quotas
In Setup, go to Feature Settings > Sales > Forecasts > Forecast Settings. Enable Forecasts, select the forecast types your team needs, and make the Forecasts tab available in the relevant Salesforce app.
Then create the forecast hierarchy. It controls whose opportunities roll up to each manager. It does not have to match your role hierarchy, which is useful when a founder, head of sales, or sales manager needs a different reporting structure.
Set quotas by forecast period and forecast type if you want attainment to appear in the forecast view. A monthly quota paired with a quarterly sales cycle can still work, but managers should review the same period they use to judge performance.
Salesforce supports single and cumulative forecast rollups. With cumulative rollups, a higher-confidence total can include lower rows such as Closed and Commit, depending on the selected category. Therefore, train managers to read the labels in their own forecast grid before comparing totals.
Use a small number of forecast types
Separate forecast types when the revenue motions have different owners, targets, or confidence patterns. For example, a SaaS company may need one view for new business and another for renewals or expansion.
Avoid creating a new forecast type for every segment. Each extra view creates more quota maintenance and more places for a rep to update incorrectly. Start with the views that drive actual leadership decisions.
Map Opportunity Stages to Forecast Categories
This is the core configuration step for Salesforce forecast categories. Salesforce lets you change the category attached to each Opportunity Stage value, while the category framework itself remains structured around its standard buckets.
Change the stage mappings
Use this sequence in Salesforce Setup:
- Open Object Manager, then select Opportunity.
- Choose Fields & Relationships, then open the Stage field.
- Under Opportunity Stages Picklist Values, review every active stage.
- Select Edit beside a stage and choose its Forecast Category.
- Save the mapping, then test it with a sample opportunity.
Map multiple stages to the same category when they carry similar forecast confidence. For example, “Technical Validation” and “Business Case” can both stay in Pipeline if neither proves commercial intent.
Salesforce’s pipeline forecasting best practices recommend mapping stages to categories and adjusting close probabilities using historical data. Keep those two controls separate. Probability estimates deal likelihood, while the forecast category communicates the team’s call.
Add Most Likely only with a clear rule
Most Likely is useful when Best Case has become too broad. A team might use it for deals with a confirmed buying process, a champion, and a proposed solution, but no agreed commercial path.
Don’t add it merely because Salesforce offers it. Reps need to tell the difference between Best Case, Most Likely, and Commit in one sentence. If they cannot, the extra category will weaken your forecast call.
Also, category renaming does not repair a vague process. A label such as “Confident” still needs an objective entry rule.
Handle New Business and Expansion Revenue Separately
A $30,000 new logo deal and a $30,000 seat expansion have different risks. New business may depend on competitive selection and a first-time security review. Expansion depends more on product adoption, budget ownership, and renewal timing.
Forecast new logos with commercial proof
For new business, map discovery, demo, and trial activity to Pipeline. Move an opportunity to Best Case when the team has identified the decision process, commercial scope, and target signature date.
Commit should require late-stage confirmation. That could mean approved pricing, a completed security review, procurement engagement, and an identified signer. A verbal “we love the product” is not a Commit criterion.
Use a separate “New Business” opportunity type or record type so reporting can distinguish it from existing-customer revenue. If your forecast configuration offers an opportunity-type forecast view, use it only after testing its rollup behavior against your sales model.
Keep expansion opportunities honest
Expansion revenue can look safer than it is. A happy product user does not always control budget, and a renewal negotiation can shrink before signature.
Create stages that match the account-growth motion, such as “Expansion Identified,” “Scope Confirmed,” “Commercial Review,” and “Closed Won.” Then map them to the same confidence logic used for new business.
For example, an existing customer that verbally agrees to add 200 seats remains Best Case if procurement has not reviewed an order form. Move it to Commit after scope, pricing, approval route, and signature timing are confirmed.
Run a Weekly Forecast Process That Holds Up
Configuration alone will not fix stale close dates or missing decision-makers. Managers need a short operating rhythm that checks the deals behind each category.
Review Commit deals line by line
During the weekly forecast call, inspect every Commit opportunity. Ask for the next customer action, signer, commercial blocker, and close-date reason. If the seller cannot show current evidence, move the opportunity back to Best Case or Pipeline.
Managers should also inspect category movement. A deal that stays in Commit for four weeks without a customer milestone needs a revised close date or a lower category. Forecasts are more accurate when the system records changed conditions instead of preserving last week’s promise.
Read totals in the right context
Salesforce can display Open Pipeline as the total of open opportunities in Pipeline, Best Case, Most Likely, and Commit categories. Its Sales Performance definition of Open Pipeline confirms that it is broader than a manager’s Commit number.
That difference prevents common reporting mistakes. Open Pipeline measures available coverage. Commit measures the team’s near-term call. Closed measures booked outcomes. A board report should label each one clearly.
Keep forecast adjustments separate from opportunity evidence. A manager adjustment can be useful for a top-down call, but it should not become an excuse to leave weak opportunity data untouched.
Troubleshoot Mismatched Stages, Access, and Totals
When a forecast total looks wrong, start with the opportunity record. Check its Stage, Forecast Category, Amount, Close Date, owner, currency, and forecast type. One incorrect value can move revenue into the wrong period or remove it from a manager’s rollup.
Fix a stage and category mismatch
If an opportunity’s category does not match expectations, inspect the Stage mapping in Object Manager. A rep may be using an older stage label, or an admin may have mapped a newly created stage to the wrong category.
Also check record types. A record type can limit the stages a user sees, while the overall Stage picklist still contains other values. Keep active stages, sales playbooks, automation, and category mappings aligned whenever you change the process.
Avoid workflow logic that changes Stage based only on an email, task completion, or quote creation. Those activities can happen without a real buying decision.
Resolve missing forecasts and wrong rollups
A rep who cannot see a forecast row may lack access to the Forecasts tab or may sit outside the forecast hierarchy. Review both before changing opportunity ownership.
If a manager’s total omits a deal, verify that the opportunity owner belongs under that manager in the forecast hierarchy. Then confirm the Close Date falls inside the selected forecast period and the deal matches the selected forecast type.
Finally, check whether the page uses cumulative or single-category rollups. A Commit figure may include different underlying category amounts based on that setting. Compare like with like before treating a total as an error.
Build Trust Through Consistent Categories
Reliable Salesforce forecast categories turn weekly forecast meetings into decisions about real risks, not debates over spreadsheet totals. The strongest setup uses clear stages, narrow Commit rules, and a shared definition of recurring revenue.
Review mappings when your sales motion changes, but don’t revise them after every missed quarter. Consistency gives the team a baseline, and that baseline makes forecast accuracy easier to improve.
