A sales pipeline is a working view of individual opportunities and their position in a defined sales process. Use the record to identify a supported stage, an owner and the next action to check.
Record evidence for the stage
Salesforce’s pipeline guide describes movement between stages using specific exit criteria: requirements for completing a stage. Write down what must be confirmed before your team changes a record’s stage.
A label such as “proposal sent” can describe an action your team completed. Keep it distinct from the buyer agreeing to the proposal. If the next stage requires an agreement, identify what would substantiate that agreement and who will update the record.
A fictional opportunity record
Imagine a supplier discussing display stands with a community venue. This invented opportunity illustrates a record review; it contains no actual customer, deal value or outcome.
| Field | Fictional record | Still to confirm |
|---|---|---|
| Stage | Proposal sent. | Buyer acceptance remains unconfirmed. |
| Next action | Salesperson asks about required dimensions. | Who can confirm the venue’s requirements? |
| Decision timing | Unknown. | Ask the buyer about their decision process. |
The assigned salesperson would check who can answer the dimensions question before preparing a revised proposal. Put that action beside the opportunity so another team member can see what remains open. Sending the revision would complete a seller task; the buyer’s decision would still need its own confirmation.
Update facts and assumptions separately
Salesforce recommends keeping deal records current with information about customer need, engagement and interest. Keep the source of a new statement with your update so the next person can understand what changed.
In the fictional record, a buyer could supply the dimensions but leave decision timing unresolved. Update the confirmed requirement and retain the timing question. Avoid filling that field with the date the salesperson hopes to close.
Read potential value as an estimate
When reviewing open opportunity value, label what it represents and which opportunities it includes. Keep an estimate of future sales separate from a record of completed sales. If you use a forecast, make its assumptions and period explicit before relying on it for a decision.
An expected decision date also needs a basis. Record whether the buyer supplied it or your team estimated it. If the basis changes, review the estimate rather than leaving an old date to imply progress that nobody has confirmed.
Distinguish the view you need
Salesforce describes a pipeline as the seller’s view of active deals and a sales funnel as a buyer-journey view. That is the guide’s convention for distinguishing the two models.
For ordered event counts and rates, use Conversion Funnel. To investigate purchase questions, use Buyer Journey. The opportunity record here helps a team decide who needs to check what next.
Review the next action
During a review, ask the owner to explain the recorded stage and the next unanswered question. Choose the next action from that information. An unresolved requirement needs a clarification; it should not disappear because the record has reached an arbitrary age.
Sources
Salesforce supplies the definition, stage-criteria guidance and record-maintenance advice. The display-stand record and proposed checks are editorial illustrations, not customer research or a tested CRM workflow.