The Sales Pipeline Guide
A sales pipeline is supposed to be a map of where every deal sits and what needs to happen next. In most CRMs, it becomes a graveyard of stuck deals and stages no one remembers creating. This guide is about building a pipeline that actually tells you what to do today.
What a pipeline is (and isn't)
A sales pipeline is a set of ordered stages that describe where a deal sits in the journey from "not yet a customer" to "now a customer." Every deal lives in exactly one stage at a time. Deals move forward, backward, or out (closed-won, closed-lost).
What a pipeline isn't:
- A to-do list
- A list of all customers
- A CRM dashboard
- A forecasting tool (pipelines feed forecasts, they aren't forecasts themselves)
- A place to store notes unrelated to the deal
A good pipeline has 3–7 stages. Fewer than 3 means you're not tracking meaningful movement. More than 7 means you're modeling a rigid sales process that doesn't match reality.
Stages for a subscription business
If you run a subscription business — SaaS, creator products, digital services — your pipeline probably should not look like "lead → opportunity → proposal → negotiation → closed-won." That's a B2B outbound pipeline for deals that close once and stay closed.
A subscription pipeline looks more like:
- Trial signed up — Stripe trial started or free tier user created.
- Activated — reached the aha moment, completed onboarding.
- Paying — converted to paid subscription.
- Expanding — upgraded plan, added seats, or bought add-ons.
- At-risk — failed payment, declining usage, or support escalation.
- Churned — canceled subscription (hopefully temporary).
Each stage is a Stripe signal (trial started, first paid invoice, upgrade event, payment failure). A Stripe-native CRM moves deals between stages automatically. See the Stripe CRM guide for the full data model.
Stages for a services / deal-based business
If you run a consultancy, agency, or deal-based business — contracts close once and the motion resets — the traditional pipeline still makes sense:
- Qualified lead — had a first call, fits ICP.
- Discovery — scoping call, SOW drafted.
- Proposal sent — formal proposal out, awaiting response.
- Negotiation — price / scope back-and-forth.
- Closed-won — contract signed.
- Closed-lost — with a reason captured.
Reason captured is the key. Every closed-lost deal should tag why — price, timing, no decision, competitor won. Without this, your pipeline post-mortems are guesses.
Metrics that matter
Three pipeline metrics beat everything else:
-
Stage conversion rate: % of deals that move from stage N to stage N+1. If "Trial → Activated" is below 30%, onboarding is the bottleneck. If "Proposal → Closed-won" is below 20%, qualification is the bottleneck. You find the problem by looking at the conversion rate, not total pipeline value.
-
Time in stage: How many days does a deal sit in each stage before it moves? Average time in "Proposal" is usually the most useful single number. If it's growing, deals are going cold.
-
Pipeline velocity: deals closed × avg deal size ÷ avg sales cycle length. This is a single number that tells you if your pipeline is healthy. Going up = good. Going down = fix conversion or cycle length.
Everything else (pipeline value, forecast, weighted pipeline) is derivative and often misleading. Start with these three.
Pipeline hygiene
A pipeline rots when:
- Deals have no next action.
- Close dates are months in the past.
- Stages don't have owners.
- Custom fields multiply beyond what anyone fills in.
Weekly hygiene routine (10 minutes):
- Review every deal with no activity in 14 days. Move forward, move backward to "at risk", or close-lost.
- Review every deal with close date in the past. Re-date or close.
- Review every deal where stage doesn't match recent activity (proposal sent but stage is still "Discovery").
This is the boring discipline that separates CRMs that work from CRMs that become graveyards.
Automation: what to automate and what not to
Automate:
- Stage moves triggered by billing events (Stripe charge → move to "Paying").
- Task creation when deals enter a stage ("Send proposal" when deal hits "Proposal stage").
- Slack / email alerts on stuck deals.
- Auto-tag deals by MRR band, plan, industry.
Don't automate:
- Sending proposals (every proposal deserves human eyes).
- Closing deals automatically (you need to review).
- Deleting or archiving contacts (always soft-delete).
Sambandh supports all of the above — see /features for the full automation toolkit.
Multiple pipelines
Use separate pipelines for separate motions. If you run both outbound sales AND have a product-led trial funnel, those are two different pipelines with different stages, different metrics, and often different owners.
Typical setups:
- Outbound sales pipeline (traditional B2B stages)
- Trial / self-serve pipeline (subscription stages)
- Expansion pipeline (for account management)
- Churn recovery pipeline (for win-back motions)
Sambandh Pro supports 5 pipelines; Teams supports unlimited.
Dive deeper
Related posts and pages in this topic cluster.
Frequently asked questions
- How many stages should my pipeline have?
- 3–7. Fewer loses signal; more creates rigidity.
- Should I use one pipeline or many?
- One per distinct sales motion. Outbound + trial + expansion = three pipelines.
- What's the single most important pipeline metric?
- Stage-to-stage conversion rate. It tells you where the bottleneck is; total pipeline value does not.
Ready to try a CRM built for how you actually work?
Start Free Trial