HubSpot deal stages come with a default pipeline of seven stages, each with a preset probability. Most B2B SaaS teams should keep the structure but replace the stages: rename them to match real buying steps, keep a Closed won and a Closed lost stage, and set probabilities from their own win rates instead of the defaults.

This guide covers what the defaults are, what deal probability actually does, how to design stages a buyer can verify, and how to change them in HubSpot. HubSpot behavior is quoted from HubSpot's knowledge base article on pipelines (last updated October 22, 2026).

What are HubSpot's default deal stages?

HubSpot creates a default Sales Pipeline for deals. Per HubSpot, "The default pipeline has seven deal stages":

Stage Default probability Type
Appointment scheduled 20% Open
Qualified to buy 40% Open
Presentation scheduled 60% Open
Decision maker bought-in 80% Open
Contract sent 90% Open
Closed won 100% Won
Closed lost 0% Lost

These defaults describe a generic sales motion. They don't know your sales cycle, your buying committee or how often your deals actually close from each stage. That is why most B2B SaaS teams change them.

What does deal probability actually do?

It drives the weighted amount in your pipeline. HubSpot says: "Stage probability is used to determine the weighted amount shown in board view, which is calculated by multiplying the total amount in each stage by the stage probability."

So if you leave the defaults in place, every deal in Contract sent counts at 90% of its value, whether or not your contracts close that often. The weighted amount looks precise, but it is built on HubSpot's assumptions rather than your history. Once you have enough closed deals, set each stage's probability from how often deals in that stage have actually closed, and revisit it as your process changes. (Forecasting method is a bigger topic; a dedicated guide to HubSpot pipeline forecasting is coming in December.)

How should a B2B SaaS team design deal stages?

Build each stage around something the buyer did, not how the rep feels. "Demo completed" is a fact. "Feeling good about it" is not. A stage that describes a buyer-verifiable event gives you cleaner reporting, because two reps looking at the same deal will put it in the same place.

Three principles help:

  1. One event per stage. Each stage marks something that happened: a meeting held, a requirement confirmed, a proposal sent, a contract signed.
  2. Written exit criteria. For each stage, write down what must be true before a deal moves to the next one. If nobody can say what "Qualified" means, reps will use it differently.
  3. Only the stages you report on. If a stage never changes a decision or a forecast, it probably doesn't need to exist. Too many stages make deals sit in limbo and make reports harder to read.

Where a deal begins also matters. If your team uses the MQL to SQL handoff, the deal is usually created after sales accepts the lead; our guide to MQL to SQL covers that handoff.

What do B2B sales pipeline stages look like in practice?

The list below is an illustrative example, not a recommendation for every team. Your stages should match how your buyers actually buy. The probabilities are left blank on purpose: set them from your own closed deals.

Example stage Exit criteria (what must be true to move on) Probability
Discovery held A first call happened and the buyer described a problem you solve Your data
Use case confirmed The buyer agreed on the use case and who else needs to be involved Your data
Demo or evaluation completed The buyer has seen the product against their use case, or a trial or pilot has a written goal Your data
Proposal sent Pricing and scope were sent to the decision maker Your data
Contract in review The buyer is reviewing the contract (legal, security or procurement) Your data
Closed won The contract is signed Won
Closed lost The buyer chose not to buy, and a reason is recorded Lost

Notice that every exit criterion is something you could check in the deal record or the buyer's own words.

How do you require information at each deal stage?

Use conditional stage properties. HubSpot says you can "set up conditional stage logic to show certain properties when users manually create a record in or move a record to a specific stage." You can also make them mandatory: "If a property is required, users cannot create or update the record until they set a value for it."

For a B2B SaaS pipeline, that might mean asking for:

  • the use case when a deal moves to Use case confirmed;
  • the expected close date and amount when a proposal is sent;
  • a closed lost reason when a deal moves to Closed lost.

HubSpot says to "ensure the dependent property exists prior to configuring conditional stage logic," so create the properties first. Pipeline-level rules and automations are set from the Pipeline Rules and Automate tabs; our guide to HubSpot RevOps workflows for B2B SaaS covers the automation side.

Do you need one pipeline or several?

Usually one. HubSpot's guidance: "Separate pipelines are only recommended if your processes have unique stages that require different pipelines. Otherwise, you can use the same pipeline across multiple users and teams and manage access via user permissions."

In B2B SaaS, a separate pipeline can make sense for a process with truly different steps, such as renewals or a self-serve motion. Different teams or regions working the same steps can usually share one pipeline. Restricting a pipeline by team requires a Professional or Enterprise subscription, and the number of custom pipelines you can create depends on your subscription and pricing model, so check HubSpot's pipeline limits for your portal.

What is the difference between a deal stage and a lifecycle stage?

A deal stage tracks a deal. A lifecycle stage tracks a contact or company. HubSpot's lifecycle stages article says the Lifecycle stage property "shows you where a specific contact or company is in your processes." Its default stages run from Subscriber and Lead through Marketing Qualified Lead, Sales Qualified Lead, Opportunity and Customer, with Evangelist and Other after.

The two connect: HubSpot defines Opportunity as "a contact or company that is associated with a deal" and Customer as "a contact or company with at least one closed deal." But they are separate properties, and changing your deal stages does not change your lifecycle stages.

What are the most common deal stage mistakes?

  • Keeping the default probabilities. Your weighted amount then reflects HubSpot's assumptions, not your win rates.
  • Too many stages. Deals stall in stages that don't change any decision.
  • Stages with no exit criteria. Reps interpret them differently, and reports drift.
  • No closed lost reason. You lose the most useful data in the pipeline.
  • A new pipeline for every team. HubSpot recommends separate pipelines only when the stages differ.
  • Removing Won or Lost. HubSpot says that "to ensure all sales reports, custom deal or revenue reports, and sales analytics tools process your deals correctly, you must include stages for both Won and Lost under Deal probability."

How do you edit deal stages in HubSpot?

HubSpot's steps, from its pipelines article:

  1. Click the settings icon in the top navigation bar.
  2. In the left sidebar, under Data Management, click Objects.
  3. Select Deals from the Select an object dropdown.
  4. Click the Pipelines tab, then the name of the pipeline.
  5. Click + Add stage to add one, click a stage's name to rename it, or drag a stage to reorder it. For each deal stage, choose a probability from the Deal probability dropdown, or enter a custom value.
  6. Click Save.

Before you delete a stage, check its Used in column: HubSpot lists blocking references there, such as records in the stage or conditional properties in use. And note that "You can't delete a pipeline if it contains records or is used in other HubSpot tools or integrations."

Frequently Asked Questions

What are HubSpot's default deal stages?

Appointment scheduled (20%), Qualified to buy (40%), Presentation scheduled (60%), Decision maker bought-in (80%), Contract sent (90%), Closed won (100%, Won) and Closed lost (0%, Lost), per HubSpot's knowledge base.

What does deal probability do in HubSpot?

HubSpot multiplies the total amount in each stage by the stage probability to calculate the weighted amount shown in board view.

Do I need Closed won and Closed lost stages?

Yes. HubSpot says you must include stages for both Won and Lost so that sales reports and analytics tools process deals correctly.

How many deal pipelines can I have in HubSpot?

It depends on your subscription and pricing model. HubSpot lists the limits on its pipelines article; the count is shared across objects and excludes each object's default pipeline.

Should I make a separate pipeline for renewals or expansion?

Only if the steps are truly different. HubSpot recommends separate pipelines only when processes have unique stages; otherwise use one pipeline and manage access with permissions.

Need help redesigning your HubSpot pipeline?

If your deal stages no longer match how your buyers buy, we can help you rebuild them around exit criteria your team will use. See our HubSpot revenue operations service, read about HubSpot implementation for B2B SaaS and outbound attribution in HubSpot, or book a GTM assessment.

Sources