# Sales Pipeline Guide for Small Businesses > Build pipeline stages around real decisions, owners and next actions, then review ageing and exceptions without inventing certainty. A sales pipeline is a working view of active opportunities. Useful stages describe a genuine change in the customer journey; they do not predict the future or replace qualification and relationship judgement. ## A decision-led opportunity path 121 practical guidance. Stage names and measures must be defined for the actual business. ## Capabilities explained ### Pipelines Defines an ordered sales process through which opportunities can be reviewed and moved. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Makes the sales process visible so follow-up is based on stage rather than memory. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Stages and statuses Uses configured stages plus open, won, lost and abandoned statuses to describe the state of a deal. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Separates progress through a process from the final commercial outcome. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Opportunities Represents a potential sale or deal linked to a contact, value, owner and pipeline position. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Shows which customer conversations are active commercial work rather than general contacts. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Tasks Creates assigned, dated and optionally recurring actions against contacts or opportunities. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Turns the next step into owned work instead of leaving it inside notes or inboxes. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### Dashboards Combines supported widgets and filters into an operational view for ongoing monitoring. **How it works:** Aggregates eligible source data into configured dashboards, reports or exports. **Why a business would use it:** Helps a team review the few measures needed for the next decision. **Limitations:** A report reflects available source data and configuration; it does not prove causation or data completeness. **Human responsibility:** A person must interpret results, investigate gaps and decide what action is justified. ## Help the team understand current work and what must happen next. A pipeline should make ownership and movement easier to inspect without turning uncertain opportunities into guaranteed revenue. ### Shared position Show where an opportunity sits using a stage definition the whole team understands. ### Owned action Keep a named owner, next action and due point beside every active opportunity. ### Reasoned outcome Record why work progressed, paused, was lost or was won so later review has context. ## Use evidence of progress, not a universal seven-stage template. The right number and names depend on how the business sells, what the customer must decide and which hand-offs matter. ### Entry condition Define what must be true before an opportunity enters the stage and who checks it. ### Exit decision Name the customer or business decision that justifies movement rather than relying on activity alone. ### Exception path Decide what happens to no-response, poor-fit, delayed, duplicate and sensitive opportunities. ## Make review a working habit rather than an occasional clean-up. A short regular review can focus on overdue actions, ageing, missing ownership and decisions that need help. ### Due work first Address missing and overdue next actions before discussing optimistic totals. ### Ageing with context Use time in stage as a prompt for investigation, not automatic proof that an opportunity is dead. ### Clean closure Close, pause or disqualify work with a meaningful reason rather than leaving inactive records in active stages. ## Define the question before choosing a pipeline metric. Counts, values, rates and duration can mislead when stages, dates, values or exclusions are inconsistent. ### Stage movement Review how work enters, progresses and exits using a stable period and definition. ### Source and fit Compare recorded sources and qualification outcomes only where collection and categorisation are reliable. ### Forecast boundary Treat values and probabilities as decision inputs with known assumptions, not promised revenue. ## Frequently asked questions ### How many stages should a sales pipeline have? There is no universal number. Use the fewest stages needed to describe meaningful decisions and hand-offs in the actual customer journey. ### Should activities such as “email sent” be stages? Usually an activity is evidence or a next action rather than a change in opportunity state. Use a stage only when the underlying decision or position has genuinely changed. ### How should stalled opportunities be handled? Review the context, owner, last meaningful event and customer expectation. Set a new action, pause with a reason or close appropriately rather than moving records automatically without evidence. ### Does pipeline value forecast revenue? Not reliably by itself. Values, probabilities, timing, definitions and data quality all affect interpretation, and outcomes remain uncertain. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/features/sales-pipelines](https://121.direct/crm/features/sales-pipelines) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.