A sales pipeline is useful when its stages describe what has actually happened. If every opportunity is labeled 'in progress,' you cannot tell which customer needs a quote, which proposal is waiting for review or which deal has stalled. Use a small set of stages with clear entry and exit rules.
Use stages that describe your process
HubSpot explains pipelines as a way to visualize a process through stages. Its deal pipeline documentation also describes stage probabilities and distinguishes won and lost outcomes. The general lesson is to make the status of each opportunity understandable; you do not need to copy another company's stage names or percentages.
Reference [1]Define a simple starting pipeline
For a service business, an example sequence is New inquiry, Qualified, Proposal sent, Decision pending and Closed won or Closed lost. Treat this as a planning example, not a universal template. A qualified opportunity should have a confirmed need and a meaningful next step; a proposal should not move to 'sent' while it is still a draft.
Write one sentence explaining the evidence required to leave each stage. For example, move from Proposal sent to Decision pending only after the customer acknowledges receipt and you know how the decision will be made. If the process differs substantially for new installations and recurring support, document those differences before creating extra stages.
Pair each open deal with a dated task
A stage tells you where the deal stands; a task tells you what to do next. After sending a proposal, record the next review date and create a follow-up task. Include the relevant location or scope in the title so that similar opportunities are easy to distinguish.
Use Lani Orbit's Deals and Tasks views to maintain that routine. Keep the contact, company, expected value and expected close date accurate as the conversation changes. An expected close date is a planning estimate, not proof that a customer has committed to purchase.
Review stalled opportunities and actual outcomes
At your weekly review, look for open deals with no recent human activity, overdue next actions or dates that keep moving without an explanation. Decide whether to continue, revise the next step or close the opportunity. Record a clear lost reason so that future decisions can use more than memory.
Compare stage movement with actual wins over time. A stage probability is an assumption until it is checked against your own historical results. Avoid treating a weighted forecast as money already earned. A smaller pipeline with accurate stages can be more useful than a larger one full of outdated opportunities.
References and further reading
Primary sources explain general CRM, pipeline and Gmail concepts. Lani Orbit instructions describe this implementation; external references do not imply endorsement or identical features.