A CRM pipeline is a set of stages used to track records through a process. In a sales pipeline, each record is usually a deal or opportunity, with a stage, owner and next action. Other CRM pipelines can track leads, support tickets or other work; the meaning depends on the object and system.

Distinguish a contact from a deal

A contact is a person. A company is an organization. A deal is a potential sale associated with the relevant people or company. One customer can have several deals at different stages, so a single status on their contact record may not describe all the work.

A task such as “call about the revised quote” is a next action. It is not necessarily a pipeline stage. Keep the action and its due date with the deal so someone knows what to do next.

Build stages around observable progress

This fictional service-business example is illustrative, not a recommended universal stage count:

Stage Example meaning
Qualified request The team has established that a relevant opportunity exists
Scope being agreed Requirements and commercial scope are under discussion
Quote sent A specific quote version has been sent for consideration
Closed won The business’s defined acceptance condition has been met
Closed lost The opportunity ended without a sale, with the reason recorded

Define entry and exit rules from the actual sales process. Closed won does not necessarily mean paid, delivered or onboarded. Link the subsequent workflow instead of overloading one stage with every business event.

HubSpot documents separate object pipelines and customizable stages. Its deal stages use probabilities, and its reporting requires both won and lost stages. These are product-specific settings to verify, not evidence that every CRM must use the same labels. HubSpot pipeline documentation.

Understand pipeline value

If two open deals have values of $1,000 and $2,000, their unweighted total is $3,000. In an illustrative model assigning 50% and 25%, the weighted total is $500 + $500 = $1,000. That is arithmetic based on the assigned probabilities, not guaranteed revenue or a measured likelihood for those individual deals.

Keep amounts, currencies, expected dates and probabilities meaningful. A stale close date or guessed amount can make a polished report misleading.

Maintain the record without erasing history

Review missing owners, overdue next actions and deals whose circumstances changed. Record a lost or deferred outcome when appropriate rather than deleting the history to make the pipeline look cleaner.

A shared spreadsheet may be sufficient when it supports the required collaboration and history; it does not automatically fail when a second person edits it. Choose a CRM when its relationships, permissions, activity history or reporting solve an actual requirement.

Use the CRM introduction for the broader system, import mapper for moving fields, and follow-up checker for an explicit dated action list.