What are HubSpot deal stages?
HubSpot deal stages are the steps of a deal pipeline, from first qualified conversation to Closed Won or Closed Lost. Each stage carries a win probability that feeds the weighted pipeline and forecast. Good stages describe what the buyer has committed to, have a clear exit criterion, and are enforced with required properties and pipeline rules.
This guide is for sales leaders and HubSpot admins setting up a pipeline for the first time or fixing one that reps no longer trust. It covers the design decisions first, then the HubSpot settings that hold the design in place.
How many deal stages should you have?
Five to seven open stages is enough for most B2B sales processes, plus Closed Won and Closed Lost. Fewer and the forecast cannot tell an early deal from a late one; more and reps skip stages or move deals in bulk at the end of the month, which makes the stage data useless.
Two tests help. If deals almost always pass two stages on the same day, merge them. If one stage regularly holds deals for very different lengths of time, it is probably hiding two steps, so split it. The time in deal stage report shows both patterns once you have a few months of data.
What makes a good deal stage?
A good stage is defined by something the buyer did, it has one exit criterion anyone can check on the record, and it means the same thing to every rep. "Demo completed with the decision maker" is a stage. "Following up" is an activity, and activities belong in tasks, not in the pipeline.
An example pipeline for a B2B service sale, to show the pattern rather than a template to copy:
| Stage | Exit criterion (what must be true to move on) | Required on entry |
|---|---|---|
| Discovery booked | Discovery call held and the need confirmed | Source, company |
| Qualified | Budget range, timeline and decision maker known | Amount estimate, close date |
| Solution presented | Decision maker has seen the proposal or demo | Decision maker contact associated |
| Proposal sent | Written proposal or quote delivered | Final amount, proposal date |
| Negotiation | Verbal yes, contract terms in discussion | Expected start date |
| Closed won | Signed contract or paid invoice | Contract value, products |
| Closed lost | Buyer declined or went silent past an agreed date | Lost reason |
Write the exit criteria into the stage descriptions your team sees and into your sales SOP. Our article on why pipelines stop reflecting reality covers what happens when they are left vague.
How should you set deal stage probabilities?
Start from your own win rates by stage, not HubSpot's defaults. The probability on each stage multiplies the deal amount into the weighted amount that pipeline reports and the forecast use. If deals that reach your proposal stage close a third of the time, a 90% probability there will inflate every forecast.
When we checked HubSpot's documentation in October 2026, its default pipeline used 20%, 40%, 60%, 80% and 90% for the open stages, with 100% for Closed won and 0% for Closed lost. A pipeline needs both a won and a lost stage for reports to work. If someone edits a deal's probability by hand, it stops updating with the stage until the deal closes, so leave probability to the stage. Review the numbers once a quarter against what actually closed.
How do you make reps follow the stages?
Use required properties and pipeline rules rather than reminders. Conditional stage properties make reps fill in the exit-criterion fields when they move a deal, and pipeline rules on Professional and Enterprise can block skipping stages, moving deals backwards, or editing deals in late stages.
When we checked HubSpot's documentation in October 2026:
- Conditional stage properties: properties that appear when a deal enters a stage, each of which can be marked required. Setting them needs Edit property settings permission.
- Pipeline rules (Professional and Enterprise, set by Super Admins): limit which stages deals can be created in, block skipping stages (moving to a lost stage is still allowed), block moving backwards, and limit who can edit deals in chosen stages. A deal approval process needs Sales Hub Enterprise.
- Super Admins, users with Edit property settings, workflows and the API can bypass the rules, apart from approvals. While rules are on, deals in that pipeline cannot have their stage bulk edited.
Start with required properties on two or three stages that matter most for the forecast, usually qualification and proposal, before adding rules.
What should happen automatically at each stage?
The admin work, not the selling. When a deal enters a stage, HubSpot can create a task, send an internal notification or update a property, so reps do not have to remember the follow-up steps. Pipeline stage automation is available from Starter, and deal-based workflows from Professional.
- 01 QualifiedTask: send discovery recap
- 02 Proposal sentTask: follow up in 3 business days
- 03 NegotiationNotify the sales manager
- 04 Closed wonHandover task and notify delivery
- 05 Closed lostLost reason required; nurture enrollment
Pipeline stage automation is set from the board view by hovering over a stage and choosing Automate, and needs Sales or Service Hub Starter or above. Deal-based workflows on Professional and Enterprise handle anything more conditional. On Professional and Enterprise, stage calculated properties such as "Date entered current stage" and "Time in current stage" make good workflow triggers for stalled-deal alerts.
When do you need more than one pipeline?
When the sales motion is genuinely different: new business and renewals, direct and partner deals, or a product with a separate buying process. Products sold the same way belong in one pipeline with a property, so the forecast, the stage reports and the rep's board all stay in one place.
Custom pipelines need Starter or above, and HubSpot sets a limit per account that is shared across objects. Pipelines can be restricted to teams on Professional and Enterprise. Our CRM architecture blueprint covers how pipelines fit with lifecycle stages and objects.
How do you change stages on a live pipeline?
Plan it like a small migration. A stage cannot be deleted while deals or conditional properties still use it, so map every old stage to a new one, move the deals, then delete. Turn on the new stage calculated properties before you start, and tell the team what changed and why.
- Check what uses the stage: the stage table's "Used in" column lists deals and settings that block deletion.
- Keep history: each deal's property history keeps its old stage changes with dates and sources.
- Watch reports: dashboards filtered on a removed stage need updating the same day.
Is your pipeline overdue a redesign? Bring your current stages to a free 30-minute call and we will show you where deals get stuck.
Deal stage checklist
Key takeaway: Stages are only as useful as their exit criteria. Define each one by what the buyer did, enforce it with required properties, and the forecast starts meaning something.
Frequently asked questions
How many deal stages should a HubSpot pipeline have?
Usually five to seven open stages, plus Closed Won and Closed Lost. Each stage should mark something the buyer did, such as agreeing to a demo or receiving a proposal, not an activity your rep performed. If two stages are always passed on the same day, merge them; if one stage hides weeks of different work, split it.
What are HubSpot's default deal stages?
When we checked in October 2026, HubSpot's default Sales Pipeline had Appointment scheduled (20%), Qualified to buy (40%), Presentation scheduled (60%), Decision maker bought-in (80%), Contract sent (90%), Closed won (100%) and Closed lost (0%). Every stage can be renamed and its probability changed.
Can you stop reps skipping HubSpot deal stages?
Yes, on Professional or Enterprise. Pipeline rules can block skipping stages, block moving deals backwards, limit which stages deals are created in, and limit who can edit deals in a stage. Only Super Admins can set them, and moving a deal straight to a lost stage is still allowed.
How do you make fields required at a deal stage?
Add conditional stage properties in the pipeline settings: choose the properties that appear when a deal moves into a stage and mark them required. A rep then cannot move the deal into that stage without filling them in, which is how exit criteria get enforced rather than just written down.
Should we have more than one deal pipeline?
Only when the sales process is genuinely different, for example new business versus renewals, or direct versus partner sales. Different products sold the same way usually belong in one pipeline with a property, so forecasting and reports stay in one place.
Sources
HubSpot documentation behind the feature and tier notes above, checked October 2026. HubSpot changes features and tiers often, so check your own portal too.