Skip to content
Capra Digitals

Sales pipeline design where every stage means something

If two reps can look at the same deal and put it in different stages, your forecast is fiction. Good pipeline design makes the stage a fact about the buyer, not an opinion about the rep's confidence.

Stage count
Five to seven for most B2B motions
Criteria
Defined by buyer actions, not seller optimism
Probabilities
Set from historical conversion, reviewed quarterly
Included
Hygiene automation, forecast views and rep training

In short

What makes a good sales pipeline?

A good pipeline has stages defined by observable buyer actions rather than seller intentions, objective exit criteria for each stage, probabilities based on historical conversion, and hygiene automation that flags stalled deals. Between five and seven stages is usually right; more than that and reps start guessing. Capra Digitals designs pipelines against your actual sales motion and builds them in HubSpot.

  • Stage count: Five to seven for most B2B motions
  • Criteria: Defined by buyer actions, not seller optimism
  • Probabilities: Set from historical conversion, reviewed quarterly
  • Included: Hygiene automation, forecast views and rep training

Signals

Pipeline problems we see constantly

  • Deals live in one stage forever

    Half the pipeline sits in 'Proposal Sent' with no defined way out.

  • Stage means confidence, not fact

    Reps move deals based on how the last call felt rather than what the buyer did.

  • Forecast is always wrong

    Stage probabilities are HubSpot defaults nobody ever adjusted.

  • Multiple motions, one pipeline

    New business, renewals and partner deals all crammed into the same stages.

What you get

What pipeline design covers

01 /

Sales motion mapping

We sit with reps and managers and map how deals genuinely progress, including the steps nobody documents.

Explore
  • Rep and manager interviews
  • Win and loss path analysis
  • Separate motions identified
  • Buying committee and approval steps
02 /

Stage architecture

Stages defined by observable buyer actions, with written exit criteria and required fields at each step.

Explore
  • Stage names and definitions
  • Objective exit criteria
  • Required properties per stage
  • Separate pipelines per motion where needed
03 /

Probability and forecasting

Probabilities set from historical conversion, plus weighted and committed forecast views managers can defend.

Explore
  • Historical conversion analysis
  • Stage probability calibration
  • Weighted and committed views
  • Forecast submission process
04 /

Hygiene automation and rollout

Stalled deal alerts, missing field prompts and the training that makes the new pipeline stick.

Explore
  • Stale deal alerts by stage
  • Required field enforcement
  • Manager hygiene dashboard
  • Rep training and migration of open deals

How it runs

Designing and landing the change

  1. 01

    Map the real motion

    Interviews plus analysis of won and lost deals, because the documented process and the real one are rarely the same.

  2. 02

    Design the stages

    Draft stages and exit criteria, tested against a sample of recent deals to check every one can be classified unambiguously.

  3. 03

    Build and migrate

    New pipeline configured, open deals mapped across, automation and dashboards built alongside.

  4. 04

    Train and enforce

    Rep training on the criteria, manager training on the hygiene dashboard, then a review after a full sales cycle.

Questions

Straight answers

The questions we get asked on almost every call about this work.

How many deal stages should we have?

Five to seven for most B2B motions. Fewer loses visibility, more invites guessing. If you need more detail, use required properties within a stage rather than adding stages.

Should we have separate pipelines?

Yes when the motion genuinely differs — new business versus renewals versus partner-sourced. Not for segments or territories; those are filters, not pipelines.

What happens to deals already in flight?

We map each open deal from the old stages to the new ones as part of the migration, and reps review anything ambiguous before go-live.

How do we stop reps sandbagging or inflating?

Objective exit criteria plus required evidence fields make stage position checkable. Managers coach against the criteria rather than against a feeling.

How often should stage probabilities be revisited?

Quarterly, against actual conversion rates. They drift as the product, pricing and market change.

Next step

Make the forecast defensible

Show us your current stages and a handful of open deals. We can usually tell within one call where the forecast is leaking.