Define Sales Pipeline Stages by What the Buyer Does

Give Each Stage an Entry and an Exit

Use the stage to describe the buyer's current position. Write what must be true to enter it, then the action needed to leave it. Keep the supporting email, meeting note, or agreement with the opportunity so another person can understand the position without guessing.

The names matter less than the conditions. If discovery complete means different things to different sellers, the column cannot support a consistent review. Agree the conditions with the people who sell and the people who will deliver the service.

Here is a starting structure I'd adapt for an MSP selling managed services. These are suggested operating rules, not a claim that every buyer follows the same sequence.

Keep Discovery Separate From a Promising Conversation

Say a hypothetical prospect likes the idea of a monthly service and asks you to send a proposal. You still haven't established the environment, required scope, or how the purchase will be approved. Move the opportunity according to what you know, rather than treating the request as completed discovery.

Try this: Before I price the service, we need to confirm the environment and the work you want us to own. Who can help us gather that information, and who needs to review the proposed scope? Record the answer as the next action.

If the buyer can provide only part of the information, record what remains unknown. Give the internal technical review its own task and owner. A buyer's confirmation of a business need does not replace checking whether your MSP can deliver the proposed scope.

Do Not Promote a Deal Because the Proposal Left Your Inbox

Keep proposal delivery as an activity on the record. Move into proposal reviewed when you have the buyer's discussion or specific feedback. A delivery receipt alone cannot tell you whether the right person has considered the offer.

If your contact says it has gone to the owner, ask: What will the owner need to decide, and how will we know whether anything needs changing? Use the answer to identify the next action. Don't invent a decision date because your forecast needs one.

When a proposal changes, keep the version under discussion clear. If the buyer changes the requirements substantially, return to the relevant scope work. Moving backward can be the accurate update; leaving the old stage untouched can conceal a new decision.

Distinguish No Decision From a Lost Deal

An explicit decline belongs in a lost outcome with the stated reason. Use the buyer's explanation as the reason they gave, rather than adding a theory about price or competitors. If no reason was supplied, record that gap.

No response is different. Follow your own review and follow-up rules, then record a closed or inactive outcome that says why you stopped treating it as a current opportunity. Silence does not establish that another MSP won the work.

A future opportunity needs a reason to reopen. If the prospect confirms that a renewal or another event governs the timing, record that event and the agreed contact. Keep it separate from an active buying decision so it doesn't carry the same forecast meaning.

Use this line when timing has changed: Is there still a decision underway, or should we close this opportunity for now and revisit it when the situation changes? Save what the buyer says. The point is an accurate record, not a clever way to force a yes.

Keep the Decision Date Separate From the Start Date

Record the buyer's expected decision date when they give you one. Record the service start separately and check it with delivery. An accepted proposal can still require transition work, information, or scheduling before support begins.

For won deals, hand over the agreed scope, accepted price, exclusions, client commitments, and open questions. Identify who owns the transition. A stage change should not require the service lead to reconstruct the deal from the seller's inbox.

If the planned start moves, update the delivery and revenue forecast without rewriting the history of the buyer's decision. Keeping those events separate lets you inspect whether a delay happened before acceptance or during transition.

Review the Evidence and the Next Action

Paul Green suggests reviewing goals, progress on agreed actions, obstacles, and the next actions, then assigning responsibility and a deadline. I'd apply that meeting discipline to deal review. Keep the discussion on what happened and what someone will do next.

For a deal that appears stuck, ask the seller: What did the buyer do that puts it in this stage, and what are they expected to do next? Open the supporting record. If the only answer is that you followed up, update the activity without upgrading the stage.

Use your actual sales history if you assign probabilities or compare time in stages. Define the stages consistently before treating the past results as comparable. A probability entered in the CRM remains an estimate, even when the buyer has met the stage conditions.

Start with the stage most likely to contain ambiguous deals. Write its entry condition and exit rule, review the records against them, and correct the current opportunities. Then apply the same method through the rest of the pipeline before using the columns to support a forecast.