A vendor-neutral, 6-page printable reference. Lead, qualified, proposal, negotiation, won/lost — and the disqualification rule for each one, so deals stop rotting in place.
“Every deal in negotiation has been there since February.”
Most small teams have one of two pipelines: the twelve-stage map nobody updates past stage three, or the two-stage map where every deal has been “in progress” for ninety days. Both fail for the same reason — a stage without an exit rule is a parking lot, and parking lots fill up.
The five below are the model. Each one paired with the rule that pulls a deal forward — or kills it before it rots.
Lead, qualified, proposal, negotiation, won/lost. That's the shape of every deal a 1–50 team has ever won or lost. Anything else is a stage nobody updates. Each one earns its place by carrying a single, named disqualification rule — the fact that has to be true before the deal leaves.
An inbound form, a referral, a conversation at an event, a name on a list. Real signal, not yet a deal.
Need is real, fit is plausible, and there is a path to a buying decision. The first stage where time spent has a payoff.
A specific price, a specific scope, sent to the person who can say yes. The first artifact that exists outside your head.
The buyer engaged with the proposal and pushed back on something specific. Not silence — a counter, an objection, a redline.
The deal terminated, one way or the other. Won is signed; lost is stated. Both are facts; nothing in between.
A stage's value comes from its exit rule. Same name, different rule, different forecast. Without a rule, the stage holds deals forever. With one, the pipeline tells the truth — and the weekly review takes ten minutes, not an hour.
| Stage | What enters | Disqualification rule |
|---|---|---|
| [ 01 ] |
Lead
A name, a company, a way in.
|
Has a real handle on the buyer — name, company, channel. If you can't reach them, it's not a lead. Tabs left open and business cards in a drawer don't qualify. |
| [ 02 ] |
Qualified
Budget, decision-maker, timing — all three named.
|
Budget is real, the decision-maker is identified, and there is a timing window. Missing one? Back to lead. Promoting a deal on hope is the leading cause of stale negotiation. |
| [ 03 ] |
Proposal
A written offer with price and scope.
|
A specific proposal exists outside email — PDF, doc, or signed-link — and it is in the decision-maker's hands. An emailed estimate is not a proposal. A scope conversation is not a proposal. |
| [ 04 ] |
Negotiation
A real objection or counter, in writing.
|
The buyer pushed back on price, terms, scope, or timing — concretely, in a thread you can quote. Silence is not negotiation. A deal that has “been negotiating” for thirty days with no email is stalled — name it and either revive or lose it. |
| [ 05 ] |
Won / Lost
A signed contract or a stated decline.
|
Signed agreement, paid invoice, or kickoff scheduled → won. Explicit no, vendor selected, or 14 days of silence after a chase → lost, with a reason in one of five buckets: price timing fit competitor no-decision. |
Six pages, A4 and Letter. Three columns: stage, what enters, disqualification rule. Print it, tape it next to the monitor, hand it to the next hire on day one.
Download the PDFPDFLead → qualified → proposal → negotiation → won/lost.
A pipeline model, not a sales-ops project.
Pipeline design is a Tuesday-afternoon decision, not a quarter-long initiative. Ship the five stages, run them for a month, then adjust — never the other way around.
Whatever your CRM is calling them today, map onto lead, qualified, proposal, negotiation, won/lost. Keep the data; replace the labels.
One line. The fact that has to be true before a deal leaves. Stick it on the column header in your CRM, or in a comment in your sheet — somewhere the team sees it weekly.
Not over a quarter. In one sitting. Move every deal to the stage its rule actually justifies. Most teams find at least a third of negotiation deals belong in qualified, and another third belong in lost.
No new stages. No “let's add an intro call stage just for this client.” If a question can't be answered, write it down — and revisit at week four.
One moment of “I wish I had this” is folklore. Two moments is a signal. The discipline of waiting is what keeps the pipeline at five instead of twelve.
A record has fields. A deal has stages. Two different problems. If you've already redesigned your fields, your pipeline still needs its own pass — and most “my CRM is broken” complaints are this confusion.
Short answers. The long-form reference covers the rest.
For a 1–50 person team, five: lead, qualified, proposal, negotiation, won/lost. That covers the full deal lifecycle a small team observes — something came in, it's worth working, we proposed, we're negotiating, we won or lost.
Twelve-stage pipelines tend to rot past stage three; two-stage pipelines hide every stuck deal in “in progress.” Five is the band where every stage earns its place and every deal has a clear next move.
A 6-page printable PDF. One row per stage, with what enters the stage and the disqualification rule that decides when a deal leaves it.
It's vendor-neutral by design — the same model holds whether your pipeline lives in a CRM, a Kanban tool, or a stage column on a spreadsheet.
The named exit condition for a stage — the specific fact that has to be true before a deal leaves it. Qualified, for example, requires budget, decision-maker, and timing all confirmed. Without that rule, qualified means “hopeful.” With it, qualified means qualified.
Every stage gets one rule. One line. Visible to the team. The rule is what stops a stage from becoming a parking lot.
Operators at 1–50 person teams who own the client book. Founders, ops leads, agency directors, freelancers — anyone redesigning a pipeline that has either too many stages no one updates or too few stages that hide stuck deals.
If you have a fifty-rep sales floor and a dedicated RevOps team, this card is below your floor. It's for the operator who already wears five hats and needs a reference, not a sales-ops project.
No. The five stages and the disqualification rules are vendor-neutral. The same model holds whether you run Syncek, HubSpot, Pipedrive, Notion, Airtable, or a spreadsheet. We wrote it because operators kept asking for the same model and there was no good reference to point at.
If you're curious about Syncek after reading the card, the long-form article and the product live one click away. If you're not, the card still works.
A single printable PDF. Both A4 and US Letter sized so the same file works on either side of the Atlantic. Three columns — Stage · What enters · Disqualification rule — with stage numbers in the brackets.
The English and Spanish versions are separate files. Tick whichever boxes you want when you submit the form.
No. Email is used to send the PDF and the occasional Syncek update — that's it. No phone, no company size, no drip nurture, no “just checking in” follow-ups. Unsubscribe is one click.
Honest pricing. No per-seat surprises. Same posture on the email list.
Different problem. The 14 fields describe who the client is. The 5 stages describe where the deal is. They are different design problems, and most “my CRM is broken” complaints are the two getting confused.
If you've already redesigned your fields with the 14-fields card, your pipeline still needs its own pass. See the 14-fields card.
The full article — stage by stage, with disqualification rules, common failure modes, and worked examples — is at syncek.com/blog/5-stages-pipeline-anatomy. The card is the printable. The article is the reference.
Five stages, used every week, with a disqualification rule each, beat twelve stages nobody updates. Print the card, walk your open deals against the rules, see what your pipeline actually contains.