Click through a full HubSpot sales pipeline build, from buyer-verified deal stages and win probabilities to required fields, stage automations and stalled-deal coaching. Built by JayOh on fictional data, so you can see exactly where each setting lives before you touch your own portal.
What you’ll learn
Use Next or your arrow keys. Click the numbered markers in the guide to jump to each setting. This is a JayOh training walkthrough with fictional data, not the HubSpot product.
We audit HubSpot portals that have run for years. The same six pipeline problems show up in most of them, usually in portals managed by experienced admins. If your stage list needs a rethink first, start with our guide to sales stage architecture.
"Proposal Sent" or "Following up" can be reached without the buyer doing anything, so deals pile up and weighted pipeline inflates.
Good: Every stage is a past-tense buyer event: Discovery Completed, Proposal Reviewed, Next Step Confirmed.
Trial sign-ups, downloads and renewals all become deals, so AEs wade through cold records and nobody trusts the board.
Good: Leads object for pre-qualification; deals only with an amount, a decision-maker and a close date.
Default percentages stay in place for years, so the weighted number leadership forecasts from is fiction.
Good: Probabilities set from your own stage-to-close history and reviewed every quarter.
Contracts go out with no amount, and closed-lost deals have no reason, so you cannot see why you lose.
Good: Conditional stage properties require Amount, Closed Lost Reason and Next step on the stage move.
"In negotiation" with loose entry rules collects deals that stopped moving and props up the forecast.
Good: A tight entry definition plus a workflow alert when a deal sits in one stage for more than 14 days. Both, not one.
Stage-change automations and AI agents layered onto vague stages just move bad deals faster.
Good: Stages, probabilities and required fields first; automation once reps use the structure consistently.
| Area | Weak | Acceptable | Strong |
|---|---|---|---|
| Stage definitions | Named for rep actions | Mix of rep and buyer events | Every stage is a verifiable buyer event, past tense |
| Probabilities | Never changed from defaults | Set once at launch | Recalibrated quarterly against actual close rates |
| Required fields | None | Amount only | Amount, Next step and Closed Lost Reason enforced on stage moves |
| Stalled deals | Found in pipeline review by accident | Reviewed when someone remembers | Stalled Deals view reviewed weekly plus a 14-day stage alert |
A clean pipeline is the base for an honest forecast. See how we approach pipeline forecasting hygiene, the lifecycle automation that feeds leads into it, and CRM deduplication before you layer AI on top.
JayOh builds HubSpot pipelines, required fields and stage automations for B2B SaaS and PE-backed revenue teams, then measures whether the forecast got more accurate.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.