Sales forecasts are only as strong as the definitions behind them. When a deal is marked as “commit,” what does that actually mean? For many teams, the answer varies, not just across the organization, but from one salesperson to the next.
This article explores what happens when sales progression is based on belief rather than evidence, why that distinction matters more than most leaders realise, and how organizations can design systems that turn subjective inputs into shared, verifiable standards.
Everyone Thinks They Know What ‘Commit’ Means
There is a peculiar kind of fiction that takes root inside B2B sales pipelines. It’s not a lie, exactly, more a shared delusion performed in good faith. You see it every quarter, embedded in Salesforce dashboards, and surfaced in pipeline review decks. A deal is marked “commit” so it is forecasted to close, and becomes a number.
But these numbers are often inaccurate. You can see this in a new Forrester study commissioned by Clari which finds 85% of B2B firms regularly miss their monthly sales forecast by more than 5%.
Ask three salespeople what “commit” means, and you’ll get three different answers. One had a promising demo with a senior stakeholder where no paper process agreed, but the energy was good. Another’s Champion offered a verbal “we’re aiming to sign this month,” though procurement hasn’t responded in three weeks. And a third is just clinging to hope, because hope is easier to report than uncertainty.
All three enter the same field value, so all three deals flow upstream into the same forecast.
This isn’t rare. According to Gong, more than 80% of companies missed their sales forecast in at least one quarter over the last two years. The research shows that one of the key issues contributing to this is the practices that many companies are still using to develop their forecasts. At SalesMethods, we think one of the reasons behind this is deals being marked as “commit” which lack critical validation or buyer engagement. The CRM accepts these entries at face value, as if their meanings were aligned. But what the system presents as coherence is often a mixture of unaligned assumptions.
This is not a matter of poor individual judgment. Your team is behaving rationally inside a system that never demanded proof. They’ve been conditioned to interpret ambiguous stages, to perform confidently, and to offer leadership something that looks solid enough to report. In the absence of an enforced, shared definition of what “commit” requires, subjectivity fills the void. And that subjectivity is never consistent.
The consequences are subtle at first, but they compound. Pipeline reviews become exercises in translation, not decision-making. Coaching sessions are essentially useless and leaders are left guessing the reality from tone and patterns they can spot in their team over time, not evidence.
The question is not whether your salespeople can be trusted, but why the system isn’t built for them to have something to trust in.
The Importance of Evidence
In any well-functioning system, progress must be verifiable.
Code cannot be deployed because it “feels done.” Revenue cannot be booked because someone just believes a deal will close. Financial planning, procurement, and engineering all depend on defined criteria, reviewable checkpoints, and clear lines of accountability. Claims must be supported.
Sales, somehow, remains an exception.
When a salesperson advances a deal in the pipeline, they are not recording a confirmed event. They are making a claim. “We’re finalizing legal.” “We’re 90%.” These statements may reflect reality, or they may not. The CRM won’t know because it’s not designed to know. It simply records the claim.
And because there is no requirement for validation, no structured prompt for evidence, that claim is accepted into the system as fact. The forecast absorbs it and leadership reports on it. Operational plans are built on it even though nothing has been confirmed.
We think this is a design flaw in the workflow itself. If the inputs are unexamined assumptions, then the precision of the analytics is irrelevant.
And yet, sales progression is still largely governed by informal signals and optimism. The pipeline becomes less an operational system and more a narrative structure. Deals move forward not because they’ve cleared agreed criteria, but because “it’s time” or “we need it to.”
A serious forecast cannot rest on that kind of logic. Nor can coaching, planning, or accountability. In the absence of a structural demand for evidence, sales progression becomes a performance, a ritual gesture toward progress, disconnected from any standard of proof.
What Counts as Evidence?
Sales is not exact, it can’t be. Every deal is a moving target, shaped by people, not rules. Judgment is not a flaw in the process, it is the process. But that doesn’t mean anything goes.
Stages may always carry a degree of interpretation but they don’t have to be vague. And they don’t have to be unprovable.
What makes interpretation dangerous is when it’s undocumented, when a rep says “we’re in” and no one knows what that actually means. Evidence doesn’t eliminate judgment, it frames it. It introduces structure without stripping away the nuances of your deals.
What counts as evidence? That depends on your motion. But it’s not “the buyer was excited” or “we’ve sent them something.” That’s the narrative. Evidence is something concrete, verifiable, and tied to a named action or signal. For example:
- Budget confirmed with X in finance — not inferred from a stakeholder’s optimism.
- Procurement contact named, and redlines acknowledged — not just “we’re waiting to hear back.”
- Paper process agreed in writing — with steps, owners, and timing spelled out.
These are the questions great managers already ask. What’s missing is a system that asks them for you, consistently, and in the same language. That’s what Plan2Close is built to do.
It’s native to Salesforce. It lets you define, stage by stage, what evidence matters for your deals. Not someone else’s playbook, yours. It doesn’t block progression. It asks for proof and it makes that proof structured and reviewable for everyone.
It’s how you build shared reality.
Your System Must Ask the Right Questions
Sales is full of smart people building workarounds for systems that never asked enough of them. Managers pull deal intelligence from Slack threads, write their own inspection templates, and maintain shadow forecasts on spreadsheets. Salespeople, meanwhile, do their best to interpret shifting expectations from one pipeline review to the next, speaking with confidence when confidence is what gets rewarded, and adjusting their language to the manager in front of them. These are not the actions of bad operators. They are the predictable behaviors of people using a system that never clarified what it needed in the first place.
The deeper problem isn’t inconsistency, it’s silence. CRMs allow deals to progress without demanding rationale. Fields capture movement, not justification. A deal moves from stage three to four, and the only evidence of why is whatever the rep decided was enough that day. Maybe the buyer verbally agreed to the next steps. Maybe legal was looped in on an email. Maybe someone said, “we’re aiming to sign this month.” There is no structural requirement to show what’s been confirmed, who confirmed it, or whether the criteria for that stage were even met.
Like we discussed before, in any other function, this would be unthinkable. The difference isn’t talent, it’s workflow. These functions are designed to ask the right questions at the right moments. Sales, by contrast, relies on habit, memory, and tone.
If evidence is to become real infrastructure, not just an idea floated in meetings, then the system itself has to carry the weight. That means building progression logic that prompts, inspects, and stores the rationale for why a deal moves forward. Not after the fact, or in coaching, but at the point of progression.
Plan2Close enables this. You can use our world-class methodology, or operationalize your own. Sales leaders define the evidence that matters and Plan2Close makes that logic visible, enforceable, and brings it inside Salesforce. Your team isn’t asked to remember what matters, they’re shown. Managers aren’t left to guess what’s been confirmed. They can see it. Leaders aren’t forced to interrogate the forecast line by line. They can inspect the reasoning behind each number.
Summary
Sales has always been a function that rewards conviction. Teams are taught to project confidence, to push through uncertainty, to stay optimistic until the deal is done. There’s value in that. Judgment and persuasion are not soft skills, they are essential tools. But they are not, on their own, a system.
The mistake isn’t in trusting your team. It’s in trusting a process that offers no way to confirm what’s real. When deal stages advance without shared criteria, when forecasts absorb claims without interrogation, when coaching becomes a matter of interpretation rather than inspection, what you have isn’t a workflow.
This isn’t a call for rigidity. Sales is not accounting, and it shouldn’t try to be. But a mature sales organization needs more than intuition. It needs a way to see not just what the salesperson believes, but why they believe it and whether that belief is grounded in anything real.
Evidence provides that grounding. It doesn’t eliminate ambiguity, but it makes ambiguity visible. It doesn’t guarantee success, but it forces clarity. Most of all, it gives sales leaders, managers, and salespeople a shared language for progress.
If the deals in your commit column don’t have proof behind them, if you can’t inspect the logic behind your own forecast, then the number you’re reporting isn’t a forecast. It’s a story.
And stories, however well told, don’t close. If you’re interested in seeing how Plan2Close works, get in touch!