

A SaaS sales pipeline in HubSpot needs five stages: Discovery, Demo, Negotiation, Closed Won and Closed Lost. Create the deal when a qualified discovery meeting is booked, give every stage an exit rule a rep can repeat, and require a reason on every lost deal. Six or seven stages is the ceiling.
| Stage | What happens | Move on when |
|---|---|---|
| Discovery | The deal is created when a qualified discovery meeting is booked. The rep learns the problem, who decides, and when. | The need is confirmed, and budget, decision-maker and timeline are filled in. |
| Demo | A demo built around what discovery found, not a product tour. | The buyer agrees it fits, and a next step is booked with the decision-maker. |
| Negotiation | Proposal, pricing, security review and terms. | The contract is signed, or the deal is lost. |
| Closed Won | Signed. The deal hands off to onboarding. | Customer success picks it up in the service pipeline. |
| Closed Lost | The deal ended without a signature. | A loss reason is required: bad timing, budget, competitor, not a fit, no interest, a prior bad experience, or technical limits. |
Rename the stages to match how your team talks. Keep the exit rules. They are what make every report count the same thing. How our framework sets them →
Start on paper, not in HubSpot.
The pipeline follows the map, not the other way around.
Create the deal when a qualified discovery meeting is booked. By then the lead is qualified, the BDR and AE are both involved, and a sales conversation is confirmed.
Deals created from form fills fill the pipeline with records that never move. Work before the meeting belongs on the contact or the Lead object. When to use the Lead object instead of Lead Status →
Split pipelines only when sales motions differ in kind, such as SMB and enterprise, where the cycle, the buyers and the steps all change.
If the difference is product line or industry, keep one pipeline and use a property such as Segment or Product type.
The traps: ten or more stages nobody can define, deals that skip required data, and deals left untouched for 30 to 60 days.
Expect them. Keep the deal in its stage and set a next-step date. If nothing is booked by that date, close it as lost and record why. No-shows and timing conflicts form a pattern you can fix once you can see it.
Deal counts don't make a forecast.
For board-level numbers, see investor-ready SaaS reporting in HubSpot.
If Discovery to Demo converts at 60% and Demo to Negotiation at 20%, the problem isn't lead volume. It's qualification or the demo.
Five: Discovery, Demo, Negotiation, Closed Won and Closed Lost. Each stage needs an exit rule a rep can repeat, and Closed Lost needs a required reason. Add a stage only when your sales motion has a real extra step, and stop at six or seven, or stages start to blur into each other.
When a qualified discovery meeting is booked. Before that, the work belongs on the contact or the Lead object, not in the pipeline. Deals created from form fills fill the pipeline with records that never move, and the forecast stops meaning anything.
Only if they sell the same way. Split them when the cycle, the buyers and the steps differ, as they often do between SMB and enterprise. If the difference is product line or industry, keep one pipeline and report on it with a property such as Segment or Product type.
Building HubSpot for a SaaS team? See HubSpot for SaaS, or book a free 30-minute review and we'll look at your stages with you.