RevOps + HubSpot 5 min read

Why Deal Stages Lie About Where Your Buyer Actually Is

Deal stages like Proposal Sent track what your sales team did, not what the buyer has actually decided. Here's how to track the milestones that tell the truth instead, worked through a real Australian B2B sales cycle.

Digital Strategist
9:47
1x

Most HubSpot pipelines will show a deal sitting in "Negotiation" for three weeks and call it healthy. What that stage actually tells you is that a sales rep sent a proposal. It says nothing about whether the right people inside the buyer's business are on board, whether legal has started reviewing the contract, or whether the deal has actually stalled while everyone assumes it's still moving.

This is the gap between what your CRM shows and what's actually happening on the buyer's side, and it's why forecasts built on deal stages alone don't hold up.

Deal stages track your team. Milestones track the buyer.

Deal stages are essential for internal management, but they describe what the seller did: sent an email, booked a call, logged a proposal. They rarely tell you where the buyer actually is. Here's what's usually wrong with a set of deal stages before you even get to milestones.

A buyer milestone is different: it's a distinct, observable action the prospect takes, a moment where they engage, seek internal sign-off, or commit to a next step. "Proposal Sent" is a task your team completed. "Buyer requested a revised proposal after CFO feedback" is a milestone, and it tells you exactly who else is now involved in the decision.

A worked example: a professional services firm selling to enterprise clients

Take an Australian professional services or manufacturing business selling multi-year contracts to enterprise clients. The deal stages look standard: Discovery, Proposal, Negotiation, Closed Won. But the actual buyer journey includes moments the pipeline never captures: an internal champion is identified, procurement opens a formal review, and legal starts checking the contract terms before anyone signs.

That legal review milestone is worth naming specifically, because it's also where ownership of what gets built often gets settled without anyone noticing. Under Australian law, a contractor owns the copyright in work it creates for a client unless the contract explicitly assigns it elsewhere. If your deal includes commissioned work, custom code, a designed system, or written content, then treat "contract signed" as complete only once the assignment clause has actually been checked, alongside the signature. IP Australia states plainly that IP created by a contractor belongs to the contractor unless the contract says otherwise, so this is worth building into the milestone itself rather than assuming legal already has it covered.

Common milestones across the buyer's journey

Milestones map roughly to where the buyer's mindset is:

  • Awareness: the prospect identifies a problem and engages with substantial content, attending a webinar, downloading a detailed guide.
  • Consideration: they're looking at specific answers: requesting a demo, or returning to the pricing page repeatedly over a short window.
  • Decision: the internal approval stage. An internal champion is identified, legal or compliance review starts, and eventually, budget is approved.

Building the system in HubSpot

Step 1: Audit where deals actually stall

Before defining milestones, map your current stall points. If deals regularly die after the demo stage, you're likely missing a milestone around getting the right people on side internally, not a demo problem.

Step 2: Define milestones that are actually observable

Do your deal stages describe you or your buyer?

Most pipelines were named by whoever built them first.

Each milestone needs to be a fact, not a feeling. Don't track "Interest", it's too vague to report on. Track "Confirmed receipt of business case". It happened or it didn't.

Step 3: Build the properties

In HubSpot, create custom properties on Deals or Contacts to hold this data: date properties (for example "Date Legal Review Started", useful for measuring how long each stage actually takes), yes/no properties ("Budget Approved"), and dropdowns ("Current Decision Blockers") that give your RevOps team the why behind the what.

Step 4: Gate the pipeline on the milestone, not the stage

A deal shouldn't move to "Closing" unless "Budget Approved" is actually set to yes. That single rule keeps pipeline hygiene honest and stops a rep's optimism from inflating the forecast.

Automating milestone updates

Manually updating these fields is the fastest way to kill adoption, so put workflows to work instead:

  • A form submission for a security whitepaper can automatically set the "Security Review Initiated" milestone.
  • Reviewing sales call recordings for phrases like "I need to get this past our CFO" can flag "Seeking Internal Champion".
  • Repeated visits to a competitor comparison page can update a "Competitive Evaluation" property directly.

Once a milestone updates, the CRM can react: a buyer who hits "Security Review" can be sent a relevant case study automatically, "Budget Approved" can create an urgent task to send the final contract, and a deal stuck in legal review for more than ten days can trigger an alert to the sales director before it goes cold.

What this actually buys you in reporting

Date properties on each milestone let you measure exactly how long it takes to move from one to the next. If the gap between "Demo Completed" and "Proposal Review" is widening, look at your collateral or pricing structure for the cause. Milestone reporting also shows where you lose people, not just who converts: if everyone reaches "Demo" and nobody reaches "Pricing", the demo isn't answering what your prospects are actually asking.

A deal sitting in "Legal Review" is a meaningfully different bet to one that's merely "Negotiating", and that difference is what makes a milestone-based forecast worth more than a stage-based one.

Keeping it current

Milestones aren't fixed. If a new step starts appearing in the buyer's journey, an AI governance review is a live example for a lot of businesses right now, add it as a tracked milestone rather than letting it sit undocumented in call notes.

Marketing, sales and success working off the same definition of a milestone is also what makes the handoff between them actually work: marketing knows what content moves a buyer to the next milestone, and success knows what was promised by the time the deal reaches "Decision". That shared reference point is worth more than any dashboard built on top of it.

Where to start

Moving from deal stages to buyer milestones starts with an audit of what your CRM already measures. Here's how to read buyer intent properly, and here's how to turn that intent into an automated pipeline once the milestones are in place.

Ready to find out what your deal stages are actually telling you, and what they're not? Book a chat with us.

Forecast looks healthy and revenue keeps missing?

That gap usually starts with what the stages count as progress.

Here's our RevOps and HubSpot work.

Neighbourhood

Neighbourhood is a HubSpot Diamond Partner in Brisbane. We build AI systems and the revenue operations they run on, for businesses across Australia and New Zealand.