Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 37 ยท Sales Hub

HubSpot Deals and Sales Pipelines

Create and manage HubSpot deals: pipeline stages, deal amount and close date, probability, required properties, multiple pipelines and the board and table views.

A deal is a potential sale. A pipeline is the sequence of stages that deals move through from first contact to closed. Together they are the heart of Sales Hub: they show every rep what to work on and show managers what revenue to expect.

Anatomy of a deal

A deal record has these key properties:

Property Purpose
Deal name A recognizable label, such as `Bluefin
Pipeline Which process the deal follows
Deal stage The current step
Amount Expected revenue (in company currency)
Close date When you expect to close
Deal owner The responsible rep
Deal type New business or existing business
Priority Optional ranking

Deals are associated with the contact(s) involved, the company, line items, quotes and tickets (see associations).

Create a deal from the Deals index (Create deal), from a contact or company record, or automatically through workflows and forms.

Pipelines and stages

The default Sales pipeline has these stages:

  1. Appointment scheduled
  2. Qualified to buy
  3. Presentation scheduled
  4. Decision maker bought-in
  5. Contract sent
  6. Closed won
  7. Closed lost

You can edit these in Settings > Objects > Deals > Pipelines. Rename stages, change their order, add new ones, or create additional pipelines (for example "Renewals", "Partnerships"). The number of pipelines you can have depends on your edition.

Two stages are special: Closed won and Closed lost. They mark the deal as finished. Everything before is "open".

Probability

Each stage has a deal probability: the percentage of deals in that stage that are expected to be won. Defaults increase through the pipeline (for example 20%, 40%, 60%, 80%, 90%, then 100% for won and 0% for lost). Weighted amount equals amount times probability and feeds forecasts (see forecasting). Adjust probabilities to match your real history, not wishful thinking.

Designing good stages

A strong pipeline stage is:

  • Buyer-centered: based on what the buyer has done ("Agreed to trial"), not only what the rep did ("Sent email").
  • Verifiable: a stage is entered when specific evidence exists.
  • Mutually exclusive and ordered: a deal is in one stage at a time.
  • Few: five to eight is typical; more stages create noise.

Write an exit criterion for each stage, and use HubSpot's required properties setting to enforce it: in the pipeline settings, choose a stage and add "required properties when entering" (for example Amount and Close date before "Qualified to buy"; Contract details before "Contract sent").

Views: board and table

Deals appear as a board (cards in stage columns; drag a card to move it) or as a table (rows with property columns, sortable and filterable). Cards show amount, close date and next activity. Boards are great for daily work; tables are better for bulk edits and reviews. Save views such as "My open deals", "Closing this month" and "Stale deals (no activity for 14 days)".

Closed won and closed lost

When a deal moves to Closed won, HubSpot records a close date and an amount, and workflows can move contacts to Customer, create an onboarding ticket and notify the team. When moved to Closed lost, a Close lost reason property can be required, which is invaluable later: "price", "no budget", "competitor X", "no decision".

Pipeline hygiene

  • Close dates in the past on open deals indicate neglect. Review weekly.
  • Deals with no next step (no upcoming task or meeting) will stall.
  • Amounts of zero distort forecasts.
  • Duplicate deals for the same opportunity inflate pipeline.
  • Zombie deals that never close: add a rule, such as "close lost after 60 days with no activity", and automate a reminder.

Pipeline math (stand-in)

The stand-ins below model a pipeline. They are not HubSpot, but they reproduce the arithmetic of weighted amounts and stage conversion that you will see in reports.

JS Stand-in: weighted pipeline value by stage

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Stand-in: stage conversion and cycle length

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Conversion between stages tells you where deals leak, and average cycle length tells you how long to wait before judging a campaign's revenue.

Multiple pipelines

Add a second pipeline when the process really differs: renewals, upsells, partner deals, or a different product line. Do not add one just for a different team or region; use a property and teams instead, otherwise reporting across pipelines gets harder.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What are the two special deal stages?

    They mark the deal as finished and drive revenue and win-rate reporting.
  2. 2. What does weighted amount equal?

    Weighted amount reflects how likely the deal is to close, which feeds forecasts.
  3. 3. How do you stop deals advancing without an amount?

    Required properties on stage entry enforce data quality.
  4. 4. When is a second pipeline justified?

    Different processes need different stages; differences in team or region are better handled with properties.

Summary

  • A deal tracks a potential sale through pipeline stages to Closed won or Closed lost.
  • Stage probability times amount gives the weighted pipeline used in forecasts.
  • Design buyer-centered stages with exit criteria and required properties.
  • Keep close dates, amounts and next steps accurate through weekly hygiene.

Next: Sales outreach and sequences