Quick answer
To build a sales pipeline, start from how you actually sell, turn that into a short list of stages (usually four to six), and write a clear entry and exit criterion for each one. Load your real deals, keep only the fields you will maintain, and review it weekly. The hard part is not drawing the stages, it is keeping them honest, so a deal never sits in a stage it has not truly reached. Get this right and forecasting, coverage and scoring all become possible on top of it.
What is a sales pipeline?
A sales pipeline is the set of stages a deal passes through from first contact to closed, plus the deals currently in each one. It is a map of your selling motion and a live snapshot of where every opportunity stands.
Done well, it answers three questions at a glance: how many real opportunities do we have, where are they stuck, and what is likely to close. Done badly, it is a list of wishful entries that tells you nothing. The difference is almost entirely in the discipline of the stages and the criteria behind them.
Step 1: Map how you actually sell
Before you touch a CRM, write down the real sequence of events in a deal that closes. Not the ideal, the actual. Who reaches out first, what has to happen for a prospect to take a call, what they need to see before they will talk price, who signs.
This matters because a pipeline copied from a template describes someone else's business. Your stages should fall out of your own motion. If most of your deals start with outbound, your early stages look different from a founder living on inbound demos. For how the selling motion sits inside the wider system, see RevOps for startups.
Step 2: Turn the motion into stages
Now collapse that sequence into a short list of stages. Each stage should mark a real change in buyer commitment, not an internal task. "Sent follow-up email" is an activity; "Prospect agreed there is a problem worth solving" is a stage.
For most early-stage B2B startups, four to six stages is the right range. A common illustrative shape:
| Stage | What it means | Exit criterion |
|---|---|---|
| New | A fit account you have identified | Contact made and acknowledged |
| Qualified | Real problem, right person, worth time | Discovery call completed |
| Evaluating | Buyer is actively assessing you | Solution reviewed, next step set |
| Proposal | Terms and pricing are on the table | Proposal sent and discussed |
| Closing | Decision in progress | Verbal yes or redlines in motion |
Treat that as a starting point, not a prescription. For a deeper walk through stage design and a fuller example set, see sales pipeline stages and CRM pipeline stages.
Step 3: Write entry and exit criteria
This is the step most startups skip, and it is the one that makes the pipeline trustworthy. For every stage, define what has to be true for a deal to enter it and what has to be true to move on.
Good criteria are observable, not a feeling. "Rep thinks it is going well" is not a criterion. "Buyer confirmed budget and a decision date" is. When a deal cannot meet the exit criterion for its current stage, it does not advance, full stop.
The payoff is that stage data starts to mean something. When every deal in "Proposal" genuinely has a proposal out, the number of deals in that stage becomes a real signal instead of a guess.
Step 4: Decide the few fields you will maintain
Capture only what you will report on and actually keep updated. At minimum you usually want deal value, stage, expected close date, and the account and contact it belongs to.
Every required field you do not use is a tax on the seller forever, and worse, it teaches people that the CRM is busywork. Fewer fields that are always filled beat many fields that are half-empty. If you are setting up the system from scratch, the field and hygiene decisions sit alongside your stage design; see CRM pipeline stages.
Step 5: Load real deals and review weekly
Put your current opportunities in, placed at the stage they have genuinely reached, not the stage you hope they are at. A pipeline seeded with optimism is worse than an empty one, because it hides the real state of the business.
Then review it on a fixed cadence, weekly for most teams. In each review you are doing three things: moving deals that have met an exit criterion, being honest about deals that have stalled, and noticing where the pipeline is thin. This is also where you start watching coverage, the ratio of open pipeline to your target, so you see a shortfall early rather than at the end of the quarter. See pipeline coverage explained.
Step 6: Build the forecast on top
Once the stages are honest, a forecast becomes possible. Keep it simple at the start. A weighted view by stage plus a rep-by-rep commit is usually enough, and far more useful than a complex model built on a handful of deals.
Do not over-engineer this. With twelve open deals, trends matter more than decimals. The forecast gets more accurate as the pipeline gets cleaner, not as the spreadsheet gets fancier. For methods that fit a startup, see sales forecasting for startups.
Common mistakes to avoid
A few failure modes show up again and again:
- Stages that are tasks, not commitments. If a stage does not reflect a change in what the buyer believes or has agreed, it is noise.
- No exit criteria. Without them, every rep advances deals on instinct and the pipeline drifts into fiction.
- Deals parked to look busy. Dead deals left open inflate coverage and poison the forecast. Close them lost and move on.
- Too many fields. Reps stop maintaining what they do not value, and then the whole system degrades.
Where Enablemnt fits
Everything above is the work. The question is whether you assemble it yourself over a few messy weeks, or have operators who have built this before stand it up with you.
Enablemnt is your embedded RevOps team. In a fixed 14-day sprint we build the CRM, the pipeline stages with real entry and exit criteria, and the reporting that sits on top, so your forecast is grounded in a clean pipeline rather than guessed. You own all of it at the end, documented, and can run it in-house or keep us on to operate it.
If you want a pipeline built right the first time, tell us about your startup and we will map your GTM blueprint on a short call.
Follow Enablemnt AI on LinkedInShort, practical posts on GTM, outbound and RevOps for early-stage B2B founders.FollowFrequently asked questions
- What are the steps to build a sales pipeline?
- Define how you actually sell, turn that into a short list of stages, write entry and exit criteria for each stage, decide the few fields you will maintain, load real deals, and then review it weekly. The order matters: get stages and criteria right before you worry about forecasting or automation, because everything downstream depends on clean stage data.
- How many stages should a sales pipeline have?
- For most early-stage B2B startups, four to six stages is enough. Each stage should mark a real change in buyer commitment with a clear exit criterion. Too few stages and you cannot see where deals stall; too many and reps guess, so your data stops meaning anything.
- What is the difference between a pipeline and a forecast?
- A pipeline is your defined stages plus the deals moving through them. A forecast is your honest read of which of those deals will close and when. The forecast is only as reliable as the pipeline underneath it, so a clean pipeline is the prerequisite for a forecast you can act on.
Keep reading
- Sales pipeline stages for B2B, explainedWhat the stages of a B2B sales pipeline mean, with an example stage set, clear exit criteria, and how to adapt them to how your startup actually sells.
- Sales forecasting for startups: a practical guideA practical guide to sales forecasting for early-stage startups: which methods actually work with thin data, how to keep it honest, and what to avoid.
- Pipeline coverage explained (the 3x rule and when it applies)What pipeline coverage means, how to calculate it, and how to read the common 3x rule of thumb: when it applies, when it misleads, and what to use instead.
- CRM pipeline stages: how to define themHow to define CRM pipeline stages that match how you actually sell, with clear exit criteria and an example stage set you can adapt to your own motion.
Filed under RevOps & sales infrastructure. Written by Enablemnt AI.