Sales pipeline stages: how to define and use them

01

Define entry and exit conditions

Explain when each stage begins and which event completes it. Having a first conversation is not the same as understanding the need and decision process. Does a quote stage mean a draft exists, or that the scope has been presented to the customer? Agree that distinction. Without shared conditions, two people can place the same situation in different stages. Keep stage labels short, but make the underlying explanation easy to find. Use examples from the team’s work to check whether the definitions are interpreted consistently.

02

Keep the next task separate from the stage

An opportunity can remain in one stage for several days, while a next action needs an owner and a specific date. “Waiting for a decision” does not explain when someone should follow up. Create a task that states what is expected and who will do it. If technical information is needed, describe the information rather than writing only “contact customer.” Evaluate the context before applying the same reminder to every open opportunity. Completing a task does not necessarily mean that the opportunity has reached another stage.

03

Try a service-quote scenario

An illustrative website project might move from needs discussion to scope preparation and then quote evaluation. Scope preparation could require a documented need and an identified contact. Quote evaluation might begin once the customer has received a quote stating the work, price and terms. These are examples, not mandatory stages for every business. Product sales, consulting and longer procurement processes may need different steps. Compare the sequence with the customer’s actual decision process. Combine stages that do not represent a meaningful difference in work, evidence or responsibility.

04

Do not treat opportunity value as collected revenue

A pipeline amount describes potential business. Won work, a prepared document and received payment can represent different states. Do not silently combine different currencies into an unexplained total. State what a report measures and check where an estimated value came from. A sales meeting should examine progress and missing actions rather than simply seek a larger headline number. Hubz reporting depends on the accuracy of the underlying records and the user’s access. Keep those limits visible when interpreting a pipeline view.

05

Use the review meeting to make decisions

Ask whether the stage is correct, the next action is known and the contact and owner are current. Record the reason when an opportunity is waiting rather than asking the same question every week. Describe lost outcomes from the actual discussion instead of recording an assumption as fact. Basic opportunity and stage tracking is included across Hubz’s current packages. Catalogs, quote preparation and contracts are listed in Professional and Business. Review that broader scope when a pipeline handover extends into customer-specific commercial documents.

06

Try it with your team

Select three illustrative opportunities: a new inquiry, work with an emerging scope and a quote awaiting a decision. Ask colleagues independently which stage applies to each. If the answers differ, inspect the definitions before assuming someone has made a mistake. Write the next task, owner and date for each opportunity. The exercise should result in shared working definitions, not just new names for columns. Review whether a stage change follows progress the team can verify or merely a completed internal task that leaves the customer decision unchanged.

Frequently asked questions