On this page
What HubSpot supports natively
| Setting | Where | Notes |
|---|---|---|
| Create a pipeline | Settings > Data Management > Objects > Deals > Pipelines | Needs Edit property settings permissions |
| Stages and probability | Pipeline editor, + Add stage | Each deal stage has a probability; you must include both a Won and a Lost stage |
| Conditional stage properties | Conditional logic rules column | Show properties when a deal is created in or moved to a stage; mark them required |
| Pipeline rules | Pipeline Rules tab | Limit where deals can be created, block skipped stages, block moving backward, limit who edits deals in certain stages |
| Deal approvals | Pipeline Rules tab | Sales Hub Enterprise |
| Access | Actions > Manage access | Restricting by team needs Professional or Enterprise |
| Clone a pipeline | Actions > Clone | Professional or Enterprise |
| Internal stage IDs | Hover over a stage, internal name icon | Used by integrations and the API |
HubSpot’s default Sales Pipeline has seven stages, from Appointment scheduled (20%) to Closed lost (0%). Super Admins and users with Edit property settings permissions can bypass pipeline rules other than deal approval.
How to set up a HubSpot deal pipeline correctly
- Map the buyer’s steps, not your activities. A stage should mean the buyer committed to something: agreed a meeting, accepted a proposal, started legal review. “Called them” is an activity, not a stage.
- Keep it short. Five to seven open stages is enough for most sales teams. Each stage needs a clear exit test everyone can apply.
- Set honest probabilities. Start with your actual historical win rates by stage if you have them. Won is 100%, Lost is 0%.
- Require what the next stage needs. For example, require Amount and Close date when a deal enters Proposal sent, and Closed lost reason on Closed lost. Don’t require so much that reps avoid moving deals.
- Add pipeline rules. Block skipping stages if forecasting depends on every stage, and block moving backward past key stages if you report on stage conversion.
- Decide on more pipelines only when the process differs: new business, renewals, partner deals.
- Restrict access if teams shouldn’t see each other’s pipelines.
- Note the internal stage IDs before building workflows, reports or integrations on them.
Common mistakes
- Stages for every internal task. Use tasks and activities instead.
- Deleting a stage with history. Move the deals first, and expect stage-based reports to change.
- One pipeline per rep. It breaks reporting and multiplies maintenance; use owners and teams.
- Mixing up deal stage, lifecycle stage and lead status. They track different things and need different owners.
Once the design is settled, we recommend building it with Jetstack AI Projects rather than by hand; see how Projects compares with manual implementation.
Where Jetstack AI fits
To build a new pipeline, use Jetstack’s Projects. Put the stages, probabilities, movement rules and the properties required at each stage in a brief (for example, Amount and Close date required on Proposal sent), approve the plan Jetty (the Projects assistant) writes, then approve deployment separately. Projects also builds the pipeline’s movement rules: blocking skipped stages, blocking backward moves and limiting which stages deals can be created in, for every stage or only the ones you name. It builds the properties before the stage requirements that use them, and the receipt confirms each asset, rules included, by reading it back from HubSpot. Deal approvals and pipeline access stay in HubSpot’s settings. Projects is currently in limited release; see what Projects can build. To standardise a pipeline you’ve already built (see copying a pipeline to another account), Portal reuse matches an existing pipeline by name, adds missing stages without overwriting existing stage settings, and remaps stage IDs for the workflows that use them. You can deploy the same setup to multiple destination portals, reviewing each portal’s mappings. See how pipelines are deployed.
Sources
- Set up and customize pipelines (HubSpot Knowledge Base)
- Set up pipeline rules (HubSpot Knowledge Base)
- Pipelines (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
HubSpot admin
Turn the brief into approved HubSpot assets.
Projects plans the build against the client portal, generates the assets and deploys them only after you approve.
Explore Projects