If two reps looked at the same deal, would they put it in the same stage? If the answer is “probably not”, your forecast, your time in stage report and any AI stage suggestion are built on a guess.
Most HubSpot deal stages are named after what the rep did: a demo was booked, a proposal went out. None of that says what the buyer agreed to. This post shows how to give every stage one written exit criterion, then set up HubSpot so it holds.
Why HubSpot deal stages drift apart from reality
A stage like “Demo scheduled” is true the moment a calendar invite exists. It says nothing about whether the buyer has a problem worth solving, a budget or a date. One rep moves a deal after a friendly call, another waits for a signed plan, and both follow the rules, because nothing is written.
Everything downstream inherits that. HubSpot weights the amounts in each stage by the stage probability, as its pipeline setup guide explains, so a loose stage inflates the weighted pipeline. Reports on stage conversion rates, deal velocity and time in each stage then measure rep habits, not buyer progress.
The same goes for AI. The deal progression card uses HubSpot’s AI to suggest deal property updates from logged meetings, calls and emails. A suggestion is only as good as the stage definition behind it.
How to define deal stages for a SaaS sales process
Write the definitions before you touch the settings. For each stage, write one sentence that starts with “The buyer has…” and can be checked on the record. That is the exit criterion: the deal leaves the stage only when it is true.
A typical SaaS sequence might read like this. Adapt the wording, not the principle:
- Discovery: the buyer has confirmed the problem and who else is involved in the decision.
- Solution fit: the buyer has seen the product against their own use case and named what success looks like.
- Business case: the buyer has agreed a budget range and a decision date.
- Proposal: the buyer has received pricing and confirmed the steps to signature, including legal and security review.
- Commit: the buyer has verbally chosen you and the paperwork is in their process.
Two rules keep this honest. One criterion per stage, so there is nothing to argue about. And every criterion is something the buyer did, not something the rep did. Stage probabilities then become numbers your team writes down and reviews each quarter, not defaults nobody chose.
This keeps a process firm without making it rigid: reps sell however they like inside a stage, they just cannot leave it until the buyer has acted.
What to check in your portal
- Rename stages to match the definitions. In your deal pipeline settings you can rename stages, reorder them and set a probability per stage. HubSpot’s guide to setting up pipelines shows where.
- Make the evidence a required field. Conditional stage properties can show a property when a deal moves into a stage and mark it as required, so the rep records the budget range or decision date before the move is saved.
- Decide on pipeline rules. Pipeline rules can restrict skipping stages, restrict moving deals backwards and limit who can edit deals in certain stages. Check your subscription first: availability depends on it. Note that super admins, workflows and API updates can bypass these rules, and bulk edits of stage are blocked once rules are on.
- Add your qualification framework. If you use one, such as MEDDIC or BANT, set it up as the sales methodology so deal progression uses it as context.
- Test it on two reps. Give two reps the same five deals and ask each to stage them using the written criteria. Where they disagree, the sentence needs work, not the reps.
For the reporting side, our post on time in stage properties covers the settings. For the AI side, see how deal progression works.
Our take
The portal mirrors the process. When a forecast is off, teams usually ask for a new report or a new tool, and the pipeline still means five different things to five reps. The fix costs a meeting, not a license: the head of sales and two senior reps in a room, writing one sentence per stage.
The settings part is small in hours once the definitions exist. The ongoing part is ownership. Someone, usually the head of sales or a RevOps owner, has to review the criteria when the sales motion changes and check that required fields are filled with real answers, not placeholders. If nobody will own that, skip the strict pipeline rules for now. Rules without an owner just teach reps to find the bypass.
We would not lean on AI stage suggestions before this is done.
Process first
Your HubSpot mirrors your process
If stages, handoffs or reports keep breaking, the fix starts with the process.
FAQ
How many deal stages should a SaaS pipeline have in HubSpot?
As many as you have distinct buyer commitments, and no more. If two stages share the same exit criterion, merge them. If reps cannot say what the buyer did to enter a stage, it is an activity, not a stage.
Why is my HubSpot deal stage reporting inaccurate?
Usually because stages are defined by rep activity, so the same deal sits in different stages depending on who owns it. Written exit criteria and required stage properties fix the input.
Can HubSpot stop reps from skipping deal stages?
Yes, pipeline rules can restrict skipping stages and moving deals backwards, depending on your subscription. Deals can still skip straight to closed stages, and super admins, workflows and API updates can bypass the rules.
This week, take your current stage list and write the “The buyer has…” sentence for each one. The stages you cannot finish the sentence for are the ones distorting your forecast. Fix those first, then the settings.
Related reading
Alignify
On this page
Get the audit checklist
All 25 checks as a spreadsheet with auto-scoring.
Talk to Alignify
45 minutes, your portal on screen, no slides. We show what we would fix first.