We call it Customer Relationship Management (CRM), but how much of the typical CRM pipeline is actually designed around the customer?
Look at how most sales pipelines are structured:
Lead → Demo → Proposal → Negotiation → Closed Won/Lost.
Now look at those stages more closely. Almost every milestone reflects an activity completed by the salesperson. A demo has been conducted, a proposal has been sent, or negotiations have started. The opportunity moves forward because something has happened on the seller’s side.
But has the buyer actually moved closer to making a decision?
That is the question I believe we need to ask more often. We have built systems that track selling activity and then treat that activity as evidence of buying progress. The two are not the same, and confusing them is one reason sales pipelines can look healthier than they really are.
We’ve confused selling activity with buying progress
Consider a few familiar situations.
A salesperson completes a demo and moves the opportunity to the next stage. But the buyer hasn’t confirmed whether the solution addresses the business problem. The demo went well, the prospect was engaged, and everyone left the meeting on good terms. Yet there is no agreement on whether the product is a fit.
Another salesperson sends a proposal. The opportunity advances because a commercial document has been shared. But has the buyer agreed on the business case? Is the problem important enough to justify the investment? Is there a compelling reason to act now rather than six months later?
Then there’s the verbal commitment. The salesperson believes the deal is nearly closed, but the budget hasn’t been approved, the decision-making group isn’t aligned, and procurement or security hasn’t completed its review.
These aren’t unusual situations. Most sales teams have encountered them.
The problem isn’t that demos, proposals, or verbal commitments are unimportant. They’re necessary parts of the typical B2B sales process. The problem is treating their completion as proof that the buyer is ready to move forward.
A completed demo proves that a demo happened. It doesn’t prove product fit. A proposal proves that pricing and scope were presented. It doesn’t prove that the buyer has a business case. And a verbal commitment doesn’t necessarily mean the organisation is ready to purchase.
Yet these milestones often influence opportunity stages, pipeline reviews, and forecasts.
We’ve built a process that makes it easy to measure what salespeople do, but not always what buyers have decided.
What if we designed CRM stages around the buyer’s journey?
Imagine flipping the model. Instead of asking what the salesperson has completed, we ask what the buyer has acknowledged, validated, agreed to, or completed.
The pipeline could look something like this:
1. Problem acknowledged
The buyer has identified a specific business problem and can explain its impact. There is a reason to explore a solution beyond general interest or curiosity.
2. Success defined
The buyer has helped define what a successful outcome looks like. The expected business impact, desired results, and criteria for evaluating a solution are understood.
3. Solution validated
The proposed solution has been evaluated against the buyer’s actual requirements. The buyer has confirmed that it addresses the relevant problem, rather than simply expressing interest after a polished demonstration.
4. Decision group aligned
The relevant stakeholders understand the problem, agree on the proposed direction, and are aligned on the decision. This doesn’t necessarily mean every stakeholder agrees on every detail, but the salesperson has evidence that the buying process is progressing beyond a single enthusiastic contact.
5. Approved and cleared
The necessary approvals are in place, including budget authorisation and applicable legal, security, and procurement requirements. The opportunity is supported by evidence that the organisation can proceed with the purchase.
These stages are illustrative, not a universal template. A transactional sale with one decision-maker won’t need the same process as a complex enterprise deal involving multiple departments, a security review, and a lengthy procurement cycle. The stages should reflect how customers actually make buying decisions in your business.
The principle, however, remains the same: an opportunity should advance because there is evidence of buyer progress, not simply because the salesperson has completed another activity.
Does this mean we stop tracking sales activities?
Absolutely not.
Calls, emails, meetings, demos, proposals, and follow-ups still matter. They help managers understand the effort being invested, the engagement taking place, and the actions required to move an opportunity forward.
But activities and stages serve different purposes.
Activity tracking tells us what the salesperson has done. Buyer-centric stages tell us what has changed in the customer’s decision-making process.
Both are important, but they shouldn’t be confused.
A demo can be completed while the opportunity remains at the same stage because the buyer hasn’t validated the solution. A proposal can be sent without advancing the deal because the business case hasn’t been agreed upon. Conversely, a buyer might make significant progress between meetings by securing internal alignment or obtaining budget approval.
The CRM should capture that progress instead of assuming it from the seller’s activity.
This also means each stage needs clear entry criteria. Salespeople should be able to explain what evidence supports the stage they’re claiming, whether that evidence comes from the buyer’s stated requirements, agreed success criteria, stakeholder discussions, or completed approval steps.
Without these criteria, changing the stage names alone won’t solve anything. You’ll simply have a buyer-centric label sitting on top of the same seller-centric process.
What could this change about pipeline reviews and forecasting?
Think about a typical sales review. A manager asks, “Have you completed the demo? Have you sent the proposal? When are we expecting the closure?”
These questions are useful, but they don’t tell the whole story.
A buyer-centric review would ask: What has the customer agreed to since our last conversation? Has the business problem been quantified? Have the success criteria been confirmed? Who is involved in the decision, and are they aligned? What approvals remain, and what evidence supports the expected close date?
The difference is significant. Instead of relying on a salesperson’s interpretation of deal momentum, the manager can examine what has actually happened in the buyer’s decision process.
That won’t eliminate uncertainty from forecasting. Buyers can change priorities, budgets can disappear, and decisions can be delayed for reasons outside a salesperson’s control. But it can expose weak assumptions earlier, improve qualification, and make pipeline conversations more evidence-based.
It also changes the coaching conversation. Rather than asking a rep to send another follow-up or schedule another demo by default, the manager can help identify the actual obstacle preventing the buyer from progressing.
Sometimes the right next step is another meeting. Sometimes it’s engaging a missing stakeholder, validating the business case, or discovering that the opportunity isn’t worth pursuing.
That’s a much more useful basis for managing a pipeline.
Perhaps we’ve been asking the wrong question all along
The purpose of a CRM isn’t simply to document the sales team’s work. It’s to help the business understand its customer relationships and make better decisions about revenue.
If our pipeline stages primarily reflect internal sales activities, we risk mistaking motion for momentum. We end up with opportunities that look advanced in the CRM but are still stuck in the buyer’s decision process.
The solution isn’t necessarily to replace every conventional pipeline stage or adopt one standard model across the organisation. It’s to examine what each stage represents, define the evidence required to advance, and make sure the process reflects how customers buy.
HubSpot, Salesforce, and other CRM platforms provide the tools to structure and track a pipeline. But the underlying sales methodology still needs to make sense.
Perhaps we’ve been designing pipelines around how we sell when we should have been designing them around how customers buy.
What do you think? Should CRM stages be based primarily on seller activities, buyer progress, or a combination of both?