The meeting everyone recognises

The same conversation happens every quarter.

The sales manager opens the pipeline review with a calm face and a slightly defensive spreadsheet. The CRO asks whether the number is real. Finance wants to know what can be committed. The CEO looks at the board target and asks the question nobody enjoys.

“So what’s actually going to close?”

On the screen, the CRM looks reassuring. Several deals are in late stage. Coverage is sitting at three times target. A few opportunities have proposals out. Procurement has been mentioned. One prospect said they were “excited to move forward”, which is sales-speak for anything from “we are ready to buy” to “please stop emailing me before Friday”.

Then the deal review starts.

The champion has not spoken to finance. IT has not signed off. The economic buyer has never joined a call. The problem is still described differently by each stakeholder. The close date is this month because that is what it said last month.

It is business Groundhog Day, only with worse coffee.

The simple answer is this: pipeline coverage fails when CRM stages measure sales activity instead of buyer commitment. A deal can look late stage because your team has sent a proposal, held a demo or discussed pricing, while the buyer is still nowhere near internal agreement.

The problem is not the number. It is what the number assumes

Pipeline coverage is meant to show whether you have enough potential revenue in play to hit your target. If you need £1m this quarter and you have £3m of pipeline, you have three times pipeline coverage.

The danger comes when leadership treats coverage as a proxy for buyer readiness.

It rarely is.

Most CRM systems, including HubSpot when it is set up in the usual way, can track deal value, stage, probability, close date and forecast category very neatly. That is useful. But the CRM can only report on the logic you put into it. If your stages are built around seller activity, your forecast will inherit that weakness.

A deal moves forward because a demo happened. Another moves because a proposal went out. Another reaches “decision stage” because the salesperson had a warm call with someone who likes the product but cannot approve the spend.

The CRM says progress.

The buying group says confusion.

That matters because B2B buying is now crowded. Forrester found that an average of 13 people are involved in a B2B buying decision, with 89% of purchases involving two or more departments. Gartner has also reported that many B2B buying groups experience unhealthy conflict during the decision process, which will surprise precisely nobody who has tried to get finance, IT, operations and legal to agree on anything before lunch.

So when your CRM says “late stage”, the real question is not “has our salesperson done enough?”

It is: “has the buyer group done enough?”

Late-stage slippage usually starts early

Late-stage slippage feels like a closing problem.

It usually is not.

By the time a deal slips at the end of the quarter, the real mistake often happened weeks earlier when the opportunity was promoted without proof. Someone had a good discovery call. A senior contact nodded in the right places. The demo went well. The prospect asked for pricing. Everyone relaxed a little.

I have seen this in businesses with excellent products and very capable sales teams. The issue is not laziness. It is misclassification.

A founder-led software company might have a brilliant technical conversation with an operations director and mark the deal as advanced. The operations director genuinely has a problem. They genuinely like the solution. They may even say the phrase every salesperson loves: “This is exactly what we need.”

But inside the customer’s organisation, almost nothing has happened yet.

Finance has not agreed the cost of the problem. The board has not accepted that now is the time to act. Procurement has not assessed risk. IT has not checked the implementation burden. The users have not agreed what success looks like.

That is not late stage.

That is early-stage interest wearing a late-stage hat.

The economic consequence is not theoretical. When 40% of late-stage pipeline slips every quarter, hiring plans, cash planning and board confidence all become distorted. The business starts making decisions against revenue that looked probable in the CRM but was never properly qualified in the buyer’s world.

Your message has to travel without you

In complex B2B deals, you are not just selling to the person on the call. You are helping that person sell the decision internally after you leave.

That is where clear messaging matters.

At Demodia, we talk a lot about the difference between explaining what you do and showing why it matters. A website, pitch deck or sales conversation can be technically accurate and still fail because it does not help the buyer recognise themselves in the problem. It describes the product, but it does not give the stakeholder a simple way to explain the risk, the cost of inaction, or the reason to change.

That same problem shows up in pipeline.

If your champion cannot repeat your message to the CFO without turning it into fog, your deal is not late stage. If the buying group cannot agree what problem they are solving, your deal is not late stage. If the business case only makes sense when your salesperson is on the call narrating the slides, your deal is not late stage.

It is a messaging problem disguised as a forecasting problem.

HubSpot can help enormously here, particularly when it becomes the operating system for revenue rather than a digital filing cabinet. Properly set up, it gives sales management and RevOps a shared view of pipeline stages, lifecycle data, buyer activity, handoffs, forecast categories and deal risk.

But no CRM, however tidy, can rescue unclear stage definitions.

If “proposal sent” means late stage, you are measuring your own admin. If “decision maker engaged” means one senior person attended half a call while eating lunch, you are kidding yourself with better software.

The system needs buyer evidence.

What buyer evidence actually means

A true late-stage deal has proof that the customer has moved, not just that your team has been busy.

I tend to think about this through five types of buyer evidence.

Activity evidence shows the buyer has taken action, not just received something from you.

Stakeholder evidence shows the right people are involved, including those who own the budget, manage the risk or can quietly kill the deal.

Consensus evidence shows the buying group agrees on the problem.

Commercial evidence shows the business case has been tested, not simply accepted because it looked good in a deck.

Timing evidence shows there is a real reason to act now.

That is buyer evidence.

Not vibes. Not call energy. Not the salesperson’s belief that “they really liked us”.

One useful test is buyer effort. Has the customer done anything that cost them time, attention or internal political capital?

Have they shared data? Brought finance in? Introduced the economic buyer? Confirmed the approval process? Put the real decision group in a room?

If the answer is no, the deal may still be valuable. It may still close one day. But calling it late stage gives leadership false confidence.

Fix the stage logic before you fix the forecast

The practical move is to rebuild your pipeline stages around buyer decisions.

Not seller tasks. Buyer decisions.

Open HubSpot, or whichever CRM you use, and look at the deals marked late stage. Pick the five that sales management feels most confident about. For each one, ask: what has the buying group done that proves they are closer to a decision?

Not what did we send? Not what did they say? Not how positive did the call feel?

What did they do?

Here is a concrete example.

The old stage definition might be “Proposal Sent”. That tells you your salesperson has produced a document. It says almost nothing about whether the customer is ready to buy.

A stronger stage definition would be: “Commercial model reviewed with finance stakeholder and agreed success criteria documented.”

That one sentence changes the behaviour. Sales now has to involve finance, test the commercial case and clarify what success means before the deal moves forward. RevOps can inspect it. Sales management can coach against it. The CEO can trust it more than a hopeful close date and a nicely formatted PDF.

You can do the same across the pipeline.

“Demo completed” becomes “technical fit confirmed by stakeholders who can approve or reject implementation.”

“Negotiation” becomes “commercial terms reviewed with the economic buyer and approval route confirmed.”

This will almost certainly shrink your pipeline.

Good.

A smaller pipeline that reflects buying reality is far more useful than a large one that keeps embarrassing you in the final fortnight of the quarter.

The forecast improves when the story gets clearer

Most companies do not have a pipeline coverage problem in isolation. They have a shared meaning problem.

Sales thinks late stage means enthusiasm. Finance thinks it means confidence. The CEO thinks it means revenue. The buyer thinks it means they are still trying to get Karen from Legal to read the security document.

That gap is expensive.

If your stages are tied to buyer commitment, your forecast becomes less theatrical. If your messaging helps stakeholders explain the problem internally, deals move with less friction. If HubSpot is configured around the way customers actually buy, sales management gets a cleaner view of risk before the quarter starts wobbling.

This is the kind of work we help sort out at Demodia: clearer messaging, cleaner HubSpot structure, better stage criteria and sales enablement that helps buyers make decisions when you are not in the room. If your CRM says “late stage” but your revenue keeps saying “not even close”, book a diagnostic call and we’ll take a look together.