Skip to CRM content
121 CRM

Guide · Sales pipeline design

Build a pipeline around decisions, ownership and the next action.

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.

Subscribe to 121 CRMSeller, billing and cancellationExplore sales pipelines

Decision-led pipeline

Put stage meaning, ownership and the next action in view.

The illustrative board supports the guide without prescribing a universal stage sequence.

121

Northstar Joinery

Know what needs to happen next

AR
OverviewContactsInboxPipelineAutomation

Know what needs to happen next

See each opportunity's stage, owner and next action in one view.

6 open2 need review

New enquiry

2

Harbour Clinic

Review non-clinical brief

Jamie1 day

Field & Form

Assign an owner

Unassigned3 hours

Discovery

2

Bramble Studio

Call · Thu 11:30

Amina2 days

Oakfield Homes

Site visit · Fri

Tom4 days

Proposal

1

Marlow Works

Decision due Friday

Tom6 days

Outcome

1

Hill & Co

Reason recorded

AminaClosed
Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

CRM building blocks

Connect the advice to day-to-day CRM work.

These are the practical tools behind the guide, with enough context to decide where they can help and where people still need to take responsibility.

Capability 01

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 use it
Makes the sales process visible so follow-up is based on stage rather than memory.
Plan for
Pipeline position is only reliable when users and workflows update it consistently.
Your team owns
A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.
Capability 02

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 use it
Separates progress through a process from the final commercial outcome.
Plan for
Pipeline position is only reliable when users and workflows update it consistently.
Your team owns
A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.
Capability 03

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 use it
Shows which customer conversations are active commercial work rather than general contacts.
Plan for
Pipeline position is only reliable when users and workflows update it consistently.
Your team owns
A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.
Capability 04

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 use it
Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for
Pipeline position is only reliable when users and workflows update it consistently.
Your team owns
A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.
Capability 05

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 use it
Helps a team review the few measures needed for the next decision.
Plan for
A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns
A person must interpret results, investigate gaps and decide what action is justified.

What a pipeline is for

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.

Design useful stages

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.

Human judgement

Exception path

Decide what happens to no-response, poor-fit, delayed, duplicate and sensitive opportunities.

Pipeline review

Inspect ageing and due work with defined measures.

Counts and values are fictional; the useful discipline is making definitions and limitations visible.

121 CRM · Reporting summary

Journey summary

New

24

Illustrative

Owned

21

Illustrative

Due

4

Illustrative

Website
Referral
Direct
Illustrative exampleFictional figures only. Definitions, access, data quality and interpretation determine whether a view is useful.

Operate the pipeline

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.

Measure carefully

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.

No certainty claim

Forecast boundary

Treat values and probabilities as decision inputs with known assumptions, not promised revenue.

Questions about this page

Useful answers, without the sales fog.

1. 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.

2. 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.

3. 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.

4. Does pipeline value forecast revenue?

Not reliably by itself. Values, probabilities, timing, definitions and data quality all affect interpretation, and outcomes remain uncertain.

Read all CRM questions

Continue the journey

Sales pipeline featureReporting and visibilityCRM vs spreadsheets

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.