Sales pipeline: how to structure yours in 5 stages (with examples)

Every business has a sales pipeline — even those that never drew one. There is always a path between first contact and money in the bank. The difference is that, without structure, that path is invisible: you don't know where deals stall, what your open opportunities are worth, or why you lost the last ten.

Structuring the pipeline makes that path visible and manageable. In this guide, we show how to design yours in 5 stages, with clear exit criteria and the metrics that matter at each step.

What a sales pipeline is (and isn't)

A sales pipeline represents the stages an opportunity moves through until it becomes a customer. Each stage has an objective entry and exit criterion — and that's what separates a pipeline from a wish list.

"Interested customer" is not a stage: it's an opinion. "Proposal sent" is a stage: either it was sent, or it wasn't. When designing your pipeline, always prefer verifiable milestones over a rep's impressions.

The 5 essential stages

Names vary by industry, but almost every B2B or services sales process fits into these five stages:

• 1. New lead — the contact arrived (form, WhatsApp, referral) and hasn't been approached. Exit criterion: first conversation held;
• 2. Qualification — you confirm need, budget and decision-maker. Exit criterion: problem and context recorded, fit confirmed;
• 3. Proposal — the client received a formal proposal with scope and price. Exit criterion: proposal opened and discussed;
• 4. Negotiation — terms, timelines and objections under active discussion. Exit criterion: verbal agreement or refusal;
• 5. Closing — contract signed or payment confirmed. Won or lost — and if lost, with the reason recorded.

Exit criteria: the rule that saves the pipeline

The mistake that kills most pipelines is leaving stage transitions to each rep's judgment. When "negotiation" means something different to every person, the pipeline becomes fiction and reports lose their value.

Write each stage's criterion in one sentence and hold the team to it. Example: a deal only enters Proposal when a proposal with final pricing has been sent. That simple — and the same for everyone.

The metrics for each stage

With a structured pipeline, three numbers tell your operation's whole story:

• Conversion rate per stage: out of every 10 qualified leads, how many get a proposal? How many close? This is where you find the real bottleneck;
• Average time per stage: deals sitting longer than X days in a stage deserve action — or honest disqualification;
• Loss reason: record it on every lost opportunity. Three months later, that field is gold for adjusting pricing, pitch and targeting.

Common mistakes when building a pipeline

• Too many stages: more than 6 or 7 becomes bureaucracy and the team stops updating;
• Mixing sales and post-sales in the same pipeline — create separate ones (that's why Triction supports multiple pipelines);
• Not wiring the entry channel to the pipeline: if leads arrive on WhatsApp and someone has to type them in manually, half get lost;
• Treating the pipeline as a report for the boss instead of the rep's daily working tool.

How to keep the pipeline alive

A good pipeline is one the team updates effortlessly. Two practices solve it: first, capture automatically — forms and WhatsApp conversations should create cards on their own, no typing. Second, automate the routine: moving cards, creating follow-up reminders and notifying owners is machine work, not people work.

In Triction, you build that pipeline by dragging stages, connect forms and WhatsApp to feed the top automatically, and let automations handle the routine — while your team handles selling.