On this pageJump to a section
A pipeline stage is a claim about a buyer.
"Proposal sent" claims that a specific person received a specific offer. "Verbal yes" claims they said so. "Hot" claims nothing at all, which is why it is the most popular stage in most CRMs. The trouble starts when claims get entered without evidence, because then the whole pipeline becomes a collection of opinions that look like data. That is why I call a typical CRM a crime scene: plenty of traces that something happened, and nobody who can say what.
I have watched many sales processes from the ad side, and the same pattern repeats. The stages are named after the salesperson's hopes, nobody removes dead deals, and the forecast is a mood. This Operator Note is about fixing it.
What is a pipeline stage supposed to mean?
It is a checkpoint on the buyer's journey that you can verify.
A useful stage answers two questions: where is this person in the process, and how do I know? The second answer is your evidence. If you cannot answer the second one by pointing to a message, a booking, a payment or a recording, the stage is a guess.
Seller-view stages versus buyer-view stages
Seller-view stages describe your effort: "Follow-up 1," "Pitched," "Waiting." Buyer-view stages describe their behavior: "Replied," "Booked," "Showed," "Asked for terms," "Paid." The second kind survives a handoff. If someone else read the record, they would know what happened without asking you.
Why do most pipelines read like a list of hopes?
Because moving a deal forward feels good and nothing forces you to move it back.
The optimism problem
Every deal that advances makes the pipeline look healthier. Every deal that gets closed-lost makes it look worse. So deals advance easily and die slowly. After a few months you have a pipeline full of conversations that ended weeks ago.
The vagueness problem
Stages with names like "Interested" or "Warm" mean different things to different people, including you on different days. If two people cannot independently agree which stage a deal is in, the stage is not defined.
Too many stages
Fifteen stages sound rigorous and produce confusion. The Harvard Business Review piece on customer decision-making argues that too much information and too many messages can overwhelm customers.1 The same is true inside your own team. Complexity in the CRM becomes a reason not to update it.
How do you define stages by buyer actions?
Name the stage after the action, and require proof of that action.
| Stages built on hope | Stages built on evidence |
|---|---|
| Interested | Replied to a message or form follow-up |
| Warm | Booked a call (calendar event exists) |
| Hot | Showed to the call (attendance recorded) |
| Proposal sent | Offer sent and opened, or discussed live with terms |
| Verbal yes | Deposit or first payment received |
| Closed (whenever it felt right) | Paid, or lost with a recorded reason |
A starter stage set for a coaching or service business
- New lead: a form fill, DM or inquiry exists.
- Contacted: you replied and the person replied back.
- Booked: a call is on the calendar.
- Showed: the call happened (more on engineering that step).
- Offer made: terms were presented and the buyer understands the price.
- Paid: a first payment cleared.
- Lost: with one reason chosen from a short fixed list.
Adjust the names. Keep the principle: each stage is a thing that happened.
What are entry and exit criteria?
The facts that must be true to enter a stage, and to leave it.
- Write the entry criterion for each stage in one sentence, as a fact: "A call is booked and on the calendar."
- Write the exit criterion: "The call took place, or the buyer cancelled."
- Name the required fields. A deal cannot enter "Offer made" without a price and a date recorded.
- Block the shortcuts. If your CRM lets you, make required fields mandatory. If not, review weekly.
- Record the loss reason. Closed-lost requires one reason from a fixed list so you can learn from it.
Why exit criteria matter
Without them, deals sit in a stage forever because nothing defines when they are done. Exit criteria turn "waiting" into either "move" or "close."
How do aging rules keep the pipeline honest?
By putting a clock on every stage.
An aging rule says how long a deal may sit in a stage before something must happen. For each stage, pick a number of days that fits your sales cycle, and write the consequence: the deal gets a task, gets re-qualified or gets closed.
Speed is part of the story
Harvard Business Review researchers found most companies are not responding to new leads nearly fast enough, which is a reminder that time is not neutral in a pipeline.3 The longer a deal sits without a conversation, the less likely it is to be what the stage says it is. It is the same handoff problem I described in leads are not the product.
A simple weekly sweep
Every week, sort by days in stage. Anything over the limit gets a decision: next step with a date, move back, or close. If the rule feels harsh, remember what it prevents: a forecast padded with deals you quietly gave up on.
How do you turn stages into a forecast?
With history, not feelings.
Count how many deals entered each stage over a past period and how many moved to the next. That is your real stage-to-stage conversion. Multiply the deals currently in each stage by those rates and by your typical collected value, and you have a forecast with a basis. It will be rougher than a spreadsheet full of percentages you made up, and a great deal more honest.
Forecast collected, not contracted
Use cash you expect to collect, not the face value of agreements. Contracted and collected are different, and the difference is where surprises live. My Q4 cash discipline piece shows how to build that view.
Sharran Srivatsaa described a daily metric habit in a clip posted on September 3, 2024. Each recruiter on a morning call gave two numbers: "The first number was how many appointments did I have yesterday? And the second number was how many appointments do I have scheduled today?"4 Two numbers, same order, every day. A pipeline review does not need more than that to be honest about what is moving.
What should you track weekly?
Fewer things than you think.
Frederick Reichheld argued in Harvard Business Review that companies spend heavily on complex tools to measure customer satisfaction and end up measuring the wrong thing, and that a single number can better guide growth.2 I take the spirit of that to a pipeline: pick a short list you will actually look at.
- Deals entering the pipeline, per week
- Conversion from each stage to the next
- Days in stage, for anything over the limit
- Collected revenue against forecast
A pipeline should be able to disappoint you. If it never does, it is not measuring anything.
Clean stages, written criteria and a weekly sweep take an afternoon to set up and about twenty minutes a week to run. The payoff is a forecast you can plan around. The stage list above is how I would start in any CRM. If you want to work through yours with someone, begin at ekaistone.com.
Keep building.Ekai
Questions people ask
What are CRM pipeline stages?
They are the steps a prospect moves through from first contact to paying customer. Good stages are defined by something the buyer did, with evidence in the record, not by how the salesperson feels about the deal.
How many pipeline stages should a small business have?
As few as describe real, distinguishable buyer behaviors. For many coaching and service businesses that is five to eight active stages, plus a closed-won and a closed-lost with reasons. More stages usually means more guessing.
What are entry and exit criteria for a pipeline stage?
Entry criteria are the facts that must be true before a deal can move into a stage. Exit criteria are the facts that must be true before it leaves. Writing both removes opinion from stage changes.
What is an aging rule in a CRM?
An aging rule says how long a deal may sit in a stage before it must move, be re-qualified or be closed. It stops dead deals from inflating the forecast.
Sources
- 1
- 2
- 3
- 4
