If your team disagrees about what “qualified” means, adding another pipeline stage will not settle the disagreement. The useful design work is deciding what evidence makes an opportunity ready to advance.
We recommend writing that evidence before changing the pipeline. A stage should help a seller and a manager reach the same conclusion about the opportunity, including what still needs to happen.
TLDR: Define each deal stage through an observable buyer milestone, entry condition, exit evidence and exception rule. Test the definitions against representative opportunities before configuring the pipeline. Keep deal progression separate from contact lifecycle and lead-status decisions.
Describe the change in the buyer's situation that the stage represents. “Demo completed” describes an activity. “The buyer has confirmed the problem and agreed to evaluate the proposed approach” describes evidence that may matter to your sales process.
Neither phrase is universally correct. The distinction helps you decide whether a stage records work performed, buying progress or an internal administrative step. State which purpose you intend rather than mixing them without explanation.
HubSpot's sales pipeline guide offers a stage-based framework for evaluating opportunities. Use it as context for your design, not as a requirement to copy every stage into your account.
Our guide to a sales funnel in HubSpot provides broader context. This exercise should end with the evidence your team will actually use to advance a deal.
Use a sentence that a reviewer can test: “The opportunity may advance when the following evidence exists and the remaining exception has an agreed owner.” Then specify the evidence.
Avoid making a field nonempty the entire definition of readiness. The value still needs to be accurate and meaningful. A seller should know why the information matters, not only that the system asks for it.
Hypothetical example: Your team is defining the exit from an evaluation stage. The proposed rule requires a confirmed use case, an identified decision process and a mutually agreed next step.
| Opportunity | Available evidence | Recommended review outcome |
|---|---|---|
| Example A | The buyer confirms the use case and decision process and agrees to the next meeting. | Eligible to advance under the proposed rule. |
| Example B | A seller delivered a demo, but the buyer has not confirmed the decision process. | Remain in evaluation or document an approved exception. |
| Example C | The buyer declines the proposed approach and requests a different scope. | Reassess the opportunity instead of advancing it automatically. |
These outcomes are illustrative, not a universal sales methodology. Ask your team to debate the cases. If two reviewers reach different answers using the same facts, clarify the rule before building around it.
A contact can have a relationship with your business that is broader than one opportunity. Your pipeline definition should therefore describe the deal being worked, not try to carry every contact-level status inside a stage name.
Document how your deal process relates to the lead-management process without making them interchangeable. For context, see tracking leads in HubSpot. Keep the actual relationship and ownership rules specific to your implementation.
This separation is especially useful when one account has more than one commercial opportunity. Ask which deal the evidence concerns and who is responsible for maintaining it.
Stage definitions should account for an opportunity that stops moving, changes direction or reopens. Decide when the team reviews stalled work and which evidence is needed to retain, move or close it.
Do not invent a universal aging threshold. Choose a review condition that fits the process and document the reason. If a deal moves backward, retain the explanation rather than treating backward movement as a data-quality failure by itself.
Ask how these decisions affect reporting. A stage redesign can change the meaning of comparisons unless the team documents the old and new definitions. Review the consequences before modifying existing records or interpreting a trend.
A useful deal stage tells the sales team what is known, what remains uncertain and what must happen before the next stage. Clear exit criteria make deal movement explainable. They do not guarantee forecast accuracy or prevent every judgment call.
Build a short stage guide before changing pipeline settings. For each stage, include the buyer milestone, required evidence, accountable sales rep and exception route. Sales managers should be able to use that guide in a pipeline review without inventing a new definition for each opportunity.
Labels such as “Appointment scheduled” or “Presentation scheduled” describe an event on a calendar. If you use them, specify what that event means in your sales process. Is the buyer merely attending a meeting, or has the buyer confirmed a problem and agreed to evaluate a possible solution?
A label such as “Decision maker bought-in” also needs a testable definition. Identify the decision makers, what they have agreed to and where the supporting interaction is recorded. Verbal confirmation may be sufficient for one transition and insufficient for another. Have the business owner set that rule explicitly.
Likewise, “Contract sent” and “Contract signed” describe different evidence. Decide which stage represents each event and what else must be true before a deal is treated as closed won. Do not let a seller's completed task silently stand in for the buyer's decision.
HubSpot documents conditional stage properties for displaying fields when users manually create or move records into a stage. Fields can be required in that interaction; read-only calculation or score properties are not eligible stage-property choices. Verify permissions and current options before implementation. HubSpot pipeline configuration.
Map each proposed required property to a decision someone will use. A field labeled “Next step” is not useful merely because it contains text. Your acceptance test should distinguish a specific buyer-agreed action from an entry such as “follow up.” Check both the presence and the business meaning of the value.
Test other routes independently. If an integration, import or deal-based workflow can affect the stage, do not assume that a manually displayed prompt proves the same behavior on that route. Document the workflow trigger, intended deal progression and evidence to inspect before approving automated deal movement.
HubSpot recommends separate pipelines for processes with genuinely different stages; teams following the same process can use the same pipeline. Compare the buying steps before creating separate pipelines for a region, seller or team. When to create another pipeline.
For example, new business and existing customers might follow different commercial decisions, or they might share the same stages with different account context. Write both paths before deciding. Multiple pipelines create multiple definitions to maintain, so record why a new pipeline is necessary and who will own its guide.
HubSpot uses stage probability in its weighted-amount calculation. That configuration is not evidence that an individual buyer has completed the stage's requirements. Review the selected probability and the stage definition as related but separate decisions. Deal probability and pipeline stages.
Use relevant historical data when evaluating your forecasting assumptions, and document the population and period. A stage redesign changes the meaning of that history unless old and new definitions can be compared. Do not advertise more precise revenue projections simply because the new board looks cleaner.
When deals stall, ask what evidence is missing and whether the agreed next action still exists. The answer may be to retain the stage with a documented exception, reassess the deal, or close it under the approved outcome definition. Moving deals forward to clear an aging report does not resolve the missing buyer evidence.
Define closed lost as carefully as closed won, including the information needed for later analysis. For reopened opportunities, decide what must be reconfirmed. Treat pipeline health as an ongoing process involving sellers and sales leaders, with a short decision log that explains why a deal moved or stayed.
Before editing sales pipeline stages, have the leadership team agree how the deal pipeline will be used for revenue forecasting and resource allocation. Ask which reports depend on pipeline data and which assumptions sit outside it. Better visibility into uncertain opportunities is useful even when it does not raise the forecast.
Inspect pipeline analytics using the same definitions sellers use in meetings. Forecasting tools cannot settle an unresolved disagreement about what a stage means. Review any calculated property or deal probability used downstream, and retain the before-and-after definitions so a later comparison does not mix unlike populations.
When you introduce the revised sales pipeline, set expectations for the first review. Ask each sales rep to explain one proposed move using the buyer evidence. Discuss differences before making bulk changes. Closing deals remains the commercial objective; the purpose of the stage guide is to make decisions about progress and uncertainty consistent.
Prepare a mapping from the current stages to the proposed stages, including ambiguous cases. Identify affected reports, automation and connected systems. Approve the change set and its acceptance tests before execution.
Use a controlled test of the agreed scenarios and inspect both the visible stage and the downstream behavior you intend to preserve. The HubSpot Portal Audit Scorecard can help organize the dependencies that need review.
Keep open exceptions visible at handover. A stage configuration can be technically complete while the team still needs a decision about how to classify particular opportunities.
Only if it satisfies the agreed exit criteria. Sending a proposal records a seller action; it does not by itself establish what the buyer agreed to do next. Define the evidence your team requires for that transition.
No. We recommend stages for meaningful deal progress and separate tracking for supporting work. Test whether a proposed stage tells the team something distinct about the buying process before adding it.
Apply the documented exception or reassessment rule. Record the missing evidence, accountable owner and next action. Do not leave an unsupported stage in place simply to preserve the appearance of progress.
We recommend a short stage guide that includes the definition, evidence, next action and exception route. Have sellers and managers use it together during a pipeline review before treating it as final.
If you need help defining that process, review HubSpot Sales Hub services. Bring a few representative opportunities and ask whether the proposed criteria produce decisions your team can explain consistently.
Primary-source context checked August 30, 2026. The stage criteria and fictional opportunities are recommendations for review, not tested configuration or sales-performance claims.