Salesforce funnel stages should help a team understand how prospects become customers and what is happening in open opportunities. Start by deciding which of those questions a report must answer. A marketing funnel and an opportunity pipeline can use different records, definitions and measures.
A funnel can show conversion between agreed steps. A pipeline view shows the opportunities currently being worked. Neither view explains a customer’s decision on its own; the team still needs evidence from the account.
Define Salesforce opportunity stages for your process
Salesforce explains in its opportunity guidance that stages can differ between companies. It also associates a probability with the selected stage. Do not treat an example stage list as a mandatory process or the default probability as a verified forecast for each deal.
Agree what must be known before an opportunity enters a stage and what evidence allows it to move on. Use definitions that representatives and managers can apply to the same case without reaching different conclusions.
Use stage names that describe meaningful progress
The following is an illustrative structure, not a prescribed Salesforce configuration. Adapt it to the work and buying decisions your team needs to track.
Qualified opportunity
The team has established a relevant need and a reason to pursue it. Record what the customer has confirmed and what remains uncertain. An enquiry or downloaded document alone may not meet your qualification standard.
Requirements and evaluation
The customer and seller are clarifying the requirement and how the proposed solution will be assessed. Identify who is involved, what evidence they need and what would rule the offer out.
Proposal and decision
The proposed scope and commercial terms are under review. Record the customer’s decision process and unresolved concerns. Sending a quote does not prove that the customer is ready to buy.
Closed outcome
Agree the evidence needed to mark an opportunity won or lost. Keep that definition consistent across the team. Delivery, onboarding and renewal may need their own records and ownership rather than extra stages in the original sale.
Make stage changes explainable
Consider a fictional team whose representatives move every deal to “Proposal” as soon as a document is sent. The manager cannot tell which customers are actively reviewing an offer and which have not replied.
The team could require a confirmed review step before using that stage. It would still record that a proposal was sent, but it would avoid treating a seller’s activity as proof of a buyer’s progress.
Check a sample of real opportunities before changing the configuration. If the team cannot apply a definition consistently, improve the definition before building automation around it.
Measure conversion without mixing populations
State which records and period a conversion rate covers. A count of today’s opportunities in each stage is different from tracking what happened to a group that entered the pipeline last quarter.
Decide how to handle reopened deals, stage changes and records with missing dates. Explain those choices in the report so that a change in the calculation is not mistaken for a change in performance.
Use the reporting guide to check filters and access before sharing the result.
Review stalled opportunities with the account owner
Look for missing next steps, repeated close-date changes and unresolved decisions. Ask what changed at the customer and whether there is still a reason to pursue the opportunity.
Update the record to reflect what is known. Moving a deal to a later stage to improve the dashboard will make the next review less useful. A reliable pipeline review should help the team decide where to investigate, act or stop.
