What is a sales pipeline? The 5 stages SMBs need

A sales pipeline is the named, ordered sequence of stages a deal moves through from first contact to a closed outcome. For a 1,50 person team, the working set is five stages, lead, qualified, proposal, negotiation, won or lost. Anything more is decoration nobody updates. Anything less is a parking lot where deals rot.

This piece is the reference. Stage by stage, with the question that lets a deal in and the disqualification rule that pushes it out. Vendor-neutral, the same five stages hold whether you run your pipeline in Google Sheets, Pipedrive, HubSpot, Notion, Airtable, or Syncek.

Most CRMs ship with twelve default stages. Most spreadsheets stop at two. Both happen for the same reason: nobody decided what each stage means. The five stages below are the decision.

What is a sales pipeline?

A sales pipeline is the visible map of every open deal your team is working, sorted by where each one is in your sales process. Each column on the map is a stage, a named bucket with a defined entry condition and a defined exit condition. Each card on the map is a deal, one prospective unit of work, owned by one person on the team, moving in one direction at a time.

A pipeline is not a list of leads. A list of leads is a contact database, that lives somewhere else, on the client record, with its own set of fields. We covered the working floor for that layer in the 14-field client-record cornerstone. The pipeline is the next layer up: it tracks the work the team is doing on those leads, not the leads themselves.

The point of having a pipeline at all is to answer three questions on a Tuesday morning:

• Where is every open deal?
• What has to happen for it to move forward?
• Which deals should not be open at all?

A 12-stage pipeline answers the first question and fails the third. A 2-stage pipeline answers neither. The five-stage shape below answers all three.

The five sales pipeline stages most SMBs actually need

Here is the working set. One stage per row. Enters this stage when is the rule that lets a deal in. Disqualification rule is the rule that says when it has to leave, forward, backward, or to lost.

#	Stage	Enters this stage when	Disqualification rule
1	Lead	Someone new, a person, a company, a referral, has shown interest. There is a name and a way to contact them.	Cannot reach them after three attempts across two channels, or no fit on basic firmographics. To Lost.
2	Qualified	We have confirmed budget, decision-maker, and timing. The deal is real.	Any one of budget, decision-maker, or timing fails to confirm. Back to Lead, or to Lost if structural.
3	Proposal	We have sent a written scope and price the buyer can react to.	No reply within the agreed follow-up window (default: 14 days), or the buyer says the proposal is wrong. Back to Qualified for a rework, or Lost.
4	Negotiation	The buyer has reacted to the proposal and is asking for changes, price, scope, terms, timing.	We cannot bridge the gap, or the buyer goes silent for the agreed window. To Lost.
5	Won / Lost	The deal has a final outcome, signed contract, paid invoice, or formal decline.	Closed-won deals leave the pipeline as customers. Closed-lost deals leave with a reason recorded.

Five stages. Lead, qualified, proposal, negotiation, won or lost. That is every deal a 1,50 team has ever closed. Anything else is a stage nobody updates.

Stage 1, Lead

A lead is a name and a way to contact them. That is the entry bar. We do not need a budget, a timeline, or a decision-maker yet, that is what the next stage is for. We just need a real person we can reach.

The cost of letting too many records into the lead stage is low (one column on a board), but the cost of letting them stay is high (the team starts to ignore the column). The disqualification rule is what protects the column from rot: three attempts across two channels, say, two emails and a call, and then a closed-lost note with a reason. Three weeks from now the lead column is current, not a graveyard.

Stage 2, Qualified

A stage without an exit rule is a parking lot. Qualified is the most-abused stage in every SMB pipeline because it sounds like progress without forcing a decision.

The harder version is this. Qualified means three things have been confirmed: the buyer has budget, the buyer is the decision-maker (or has named one), and the buyer has a timing window in which the work would happen. Confirmed, not assumed. If any one of those is missing, the deal is not qualified yet. It is still a lead.

The discipline pays back twice. First, your forecast starts to behave: only deals past Qualified get counted. Second, your team stops chasing deals where one of the three never lines up, the silent killer of small-team pipelines.

Stage 3, Proposal

A proposal stage starts when something on paper exists for the buyer to react to: a written scope, a price, a timeline. Verbal hand-waving is not a proposal. A Slack message is not a proposal. The point of this stage is the artifact, without it, the deal cannot move forward.

The disqualification rule is a follow-up window. Two weeks is a reasonable default for an SMB sales motion. After that, either the buyer reacts (move forward), the proposal needs a rework (back to Qualified), or the deal goes to lost. No fourth option. "Still thinking about it" is not a status; it is an open loop the operator pays for in attention every week.

Stage 4, Negotiation

This is where most agency and consultancy deals live longer than they should. The buyer has reacted to the proposal, but instead of yes they sent back a question. Could you do the same scope at 80% of the price? Could you start in March instead of February? Could you add a workshop?

Negotiation is fine, it is the work. What turns it into rot is the absence of a hard cap. The disqualification rule is two-fold: a gap that cannot be bridged closes the deal lost; silence past the agreed window closes the deal lost. Whichever fires first.

Stage 5, Won / Lost

This is the only stage in which both outcomes are valid. A closed-won deal becomes a customer record (and triggers handoff to delivery). A closed-lost deal carries a one-line reason, budget, timing, competitor, no decision, that lives on the record forever.

The reason field is the highest-leverage column in the entire pipeline. It is what tells you, at the end of a quarter, whether your forecast is failing on price, timing, or qualification, and which one to fix in the next quarter.

Each stage needs a disqualification rule

The five-stage shape is half the answer. The other half is the rule on each stage that says when a deal has to leave it. Without that rule, every column eventually becomes a holding pen.

A pipeline with disqualification rules is small enough to live on a single printed card. Your time is expensive. That is one of the four operating principles we run Syncek by, and the disqualification rule is the mechanism that makes a pipeline respect it. A stage that cannot disqualify a deal is a stage that quietly costs you attention every week.

The disqualification language matters. "Push to next month" is not a disqualification, it is a postponement that erases itself. "Closed-lost: timing" is. The first sentence keeps the deal in the pipeline; the second one ends it cleanly and creates a record you can come back to in six months.

Get the printable version

We've prepared a printable reference card to keep on hand while you build or audit your CRM. One page, ready to print.

Download the printable 5-stage reference card

Fields tell you who. Stages tell you where.

A common confusion among operators redesigning their CRM is this: I added more fields and the pipeline is still broken. The two are different design problems.

A record has fields. Fields describe who the client or contact is, name, company, segment, value, owner. The 14-field set is the working floor for this layer; we wrote it up in the field-design cornerstone.

A deal has stages. Stages describe where the deal is in your sales process, lead, qualified, proposal, negotiation, won or lost. They live on a different object (the deal) and are read in a different view (the pipeline).

If you have already redesigned your fields and your pipeline still feels broken, the pipeline needs its own pass. They are two different decisions, and most "my CRM is broken" complaints turn out to be this confusion.

Why most SMB pipelines have too many stages

Two patterns dominate. Both are diagnosable in under a minute by looking at the board.

The 12-stage CRM default. Pipedrive, HubSpot, Salesforce, and many of their alternatives ship with a long default pipeline, initial contact, awareness, evaluation, presentation, demo scheduled, demo completed, proposal sent, proposal reviewed, contract sent, contract signed, paid, closed-won. The shape was built for a 50-rep sales team where each stage is owned by a different role. On a 1,50 SMB team, where the same person owns the deal from first call to signed contract, those twelve stages reduce to noise. The team updates the deal's stage three or four times in its life, and the rest of the columns stay empty.

The two-stage spreadsheet. Open and Closed, with a "stage" column nobody updates. The whole pipeline collapses into one giant lead column with a few wins at the bottom. There is no forecast and no triage. Every Monday, the operator reopens the same questions: which of these are real? where are we stuck? what should I close?

The five-stage shape sits between the two. It is enough structure to answer the three Tuesday-morning questions above. It is not so much structure that the team gives up updating it.

How to redesign your pipeline by Tuesday afternoon

Whatever CRM you use today, you can rebuild your pipeline on these five stages in a single afternoon. The work is small.

1. Open your current pipeline. Sheet, board, CRM. Look at every open deal.
2. Map each open deal to one of the five stages. Lead → qualified → proposal → negotiation → won/lost. If you cannot decide between two, the answer is almost always the earlier one. A deal that is "kind of in negotiation" is a proposal that has not been replied to.
3. Apply each disqualification rule. Walk down the deals in each stage and apply the exit rule. Three attempts across two channels for leads. Confirmed budget, decision-maker, timing for qualified. 14-day follow-up for proposals. Hard cap for negotiation. Some deals will leave the pipeline today; that is the point.
4. Rename the columns in your tool. Whether you live in Google Sheets, Pipedrive, HubSpot, Notion, Airtable, or Syncek, the work is the same: rename your existing columns to lead, qualified, proposal, negotiation, won/lost. Everything else gets archived, not deleted.
5. Run it for a week before adding anything back. A 1,50 team rarely needs a sixth stage. Most teams that "added a sixth stage" are describing a bottleneck (e.g. legal review) that belongs on the deal record as a status field, not on the pipeline as a column.

The point of the redesign is not the columns. The point is the conversation the team has on Tuesday morning when the columns mean what they say.

A note on the tool

Whatever CRM you use today, the five-stage shape is yours. Syncek ships with a Kanban pipeline view and the same data in a table view, with time-in-stage on every card and inline editing in the table, but the model in this article belongs to your team, not to the tool. Your CRM spreadsheet, supercharged. The shape works in any of them.

If you want the printable version that fits on a single page, one row per stage, with the entry rule and the disqualification rule next to each other, the lead magnet on this post is exactly that. Save it for your next pipeline review.