Atlas
  • All-in-one
  • Solutions
  • Compare
  • Pricing
PricingGet started
All guides
February 9, 2026·8 min read·Sales, Pipeline, CRM

How to Build a Sales Pipeline From Scratch

A good pipeline is not a list of hopeful deals - it is a map of the exact steps a customer takes on the way to yes, with a clear exit criterion for each one.

A sales pipeline is the visual sequence of stages a deal passes through from first contact to closed. Built well, it tells you at a glance what is moving, what is stuck, and where revenue is likely to land. Built badly, it is a graveyard of optimistic guesses that leadership quietly stops trusting.

The single mistake that ruins most pipelines is designing the stages around what your team does instead of what the buyer does. This guide builds one the right way, from scratch.

Step 1: Map how customers actually buy

Before you name a single stage, talk to your last ten closed deals - won and lost. Write down the real sequence of events from the buyer's side: the trigger that made them look, who got involved, what they needed to see before committing, and what nearly stopped the deal.

You are looking for the natural checkpoints in their decision, not yours. A stage should represent a change in the buyer's state of mind or commitment, not an internal task like "sent proposal".

Step 2: Define stages with exit criteria

Every stage needs a clear, objective condition that must be true before a deal can move to the next one. This is the difference between a pipeline that forecasts and one that lies. "Qualified" should mean something specific and verifiable, not a feeling.

A common, sturdy starting structure looks like this - adapt the names to your business.

  • New / Lead: a potential buyer has entered but has not been contacted or qualified.
  • Qualified: you have confirmed they have a real need, budget, and authority to buy. Exit criterion: those three are documented.
  • Discovery / Scoping: you understand their problem well enough to propose. Exit criterion: requirements captured.
  • Proposal / Quote: a specific offer is on the table. Exit criterion: buyer has received and acknowledged pricing.
  • Negotiation: terms and contract are being finalized. Exit criterion: verbal or written agreement on scope and price.
  • Closed Won / Closed Lost: the deal is decided, with a documented reason on losses.

Step 3: Keep it short and honest

Resist the urge to add stages for every internal nuance. Five to seven active stages is plenty for most businesses. More than that and reps spend more time classifying deals than advancing them, and the extra granularity rarely improves the forecast.

Equally important, always keep a Closed Lost stage with a required reason. The lost deals teach you more than the won ones - patterns in why you lose are the fastest route to a better process.

Step 4: Instrument it and review it

Once the pipeline exists in your CRM, start capturing two numbers per stage: conversion rate (what percentage move to the next stage) and average time in stage. These turn the pipeline from a picture into a diagnostic. A stage where deals pile up and age is a process problem you can now see and fix.

In Atlas, the pipeline, the deal record, the contract, and the eventual project live on one model, so when a deal reaches Closed Won there is nothing to re-key - the same record carries forward into delivery. That continuity is what stops the classic "the deal closed but nobody told the delivery team" failure.

Common mistakes to avoid

Two failure modes are worth naming. First, the vanity pipeline: reps leave dead deals in early stages to make the pipeline look full. Enforce that stale deals get marked lost. Second, the sandbagging pipeline: reps hide near-certain deals to lower expectations. Clear exit criteria and regular reviews fix both, because a deal either meets the criterion for its stage or it does not.

One more design choice separates a pipeline that lasts from one you rebuild every quarter: decide upfront what a deal is. Is it one opportunity per customer, or one per project, or one per product line? Teams that never settle this end up with inconsistent records where some reps log a single sprawling deal and others split the same work into five, and no report can reconcile them. Pick a definition, write it down, and hold the line - the consistency is what makes your conversion rates and forecast comparable across reps and across time.

Keep reading

  • Best Diagramming Software in 2026: The Overall Buyer Guide
  • How to Make Diagrams for Confluence
  • How to Make Diagrams for Notion
  • Free PDF tools
  • The all-in-one work OS

FAQ

Questions, answered.

How many stages should a sales pipeline have?
Most businesses do well with five to seven active stages plus a Closed Won and Closed Lost. Fewer than that and stages carry too little information; more than that and reps spend more effort classifying deals than advancing them, without improving forecast accuracy.
What is a stage exit criterion and why does it matter?
An exit criterion is the specific, objective condition that must be true before a deal can advance - for example, budget, need, and authority all documented before a deal counts as Qualified. Without one, stages become subjective and the forecast built on them becomes unreliable.
Should pipeline stages reflect what my team does or what the buyer does?
The buyer. A stage should represent a change in the buyer's commitment or state of mind, not an internal task. Pipelines built around internal activity look busy but forecast poorly, because activity does not equal progress toward a purchase.

Ready when you are

One workspace, not ten.

Atlas replaces the stack with one platform for tasks, projects, CRM, contracts, e-signature, PDF tools, and analytics. Start free.

Get started freeSee pricing
AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus