Pipeline Stage Definitions template.

What's inside — the exact file

This is the complete template, not a sample. The rows are worked examples — replace them with your data (and delete them before any platform import).

What this template is for

This worksheet defines what each stage of a HubSpot deal pipeline actually means — in writing, agreed by the team, before the pipeline gets built or rebuilt. Pipelines fail the same way everywhere: stages mean different things to different reps, deals sit wherever feels right, and the forecast becomes fiction. The fix is boring and effective: a definition, an entry criterion, and an exit criterion for every stage.

Use it when standing up a new pipeline, cleaning up a drifted one, or onboarding reps who each brought a different CRM dialect from their last job. One row per stage; the finished sheet doubles as the training doc.

How to use it, step by step

1. List your current stages honestly. Write down the stages as they exist today, including the ones nobody uses and the “parking lot” stage every pipeline grows.
2. Define each stage by evidence. A stage definition should point at something checkable — “demo completed with decision maker present,” not “strong interest.” If you can’t verify it, reps will self-grade.
3. Write entry and exit criteria. Entry criteria say what must already be true; exit criteria say what event moves the deal forward. Every gray zone between two stages is forecast error waiting to happen.
4. Set win probabilities from history. Pull last year’s actual conversion by stage if you have it; estimate conservatively if you don’t. These numbers drive HubSpot’s weighted forecast.
5. Decide required properties per stage. The required_properties column becomes stage-gate rules in HubSpot — amount and close date by Qualified, decision maker by Demo, final amount by Proposal.
6. Build it in HubSpot and enforce it. Create the stages, set the probabilities, add the required-property prompts, and put the sheet where reps can see it. Revisit quarterly against actual conversion data.

What each column means

Common mistakes to avoid

• Stage names that describe seller activity (“Follow-up sent”) instead of buyer evidence (“Proposal under review”).
• No exit criteria, so deals advance on optimism — the classic source of 90% forecasts that close at 40%.
• Default win probabilities left untouched for years while actual conversion drifted.
• Ten-stage pipelines where three stages do all the work — more stages means more gray zones, not more precision.
• A “parking lot” stage (On hold, Nurture) inside the active pipeline, silently inflating the weighted forecast.

Questions, answered

How many stages should a deal pipeline have?

Most B2B pipelines work best with 4–6 stages. The test for each stage: does it have a distinct, verifiable exit event, and does conversion through it tell you something you would act on? Stages that fail both tests are decoration.

Should lost deals be a stage?

Closed-won and closed-lost are terminal states, not working stages — HubSpot handles both natively. What matters is requiring a closed-lost reason property, which turns losses into a report you can learn from.

How is this different from lifecycle stages?

Lifecycle stages track a contact’s whole relationship with you (lead, MQL, SQL, customer); deal stages track one deal through one pipeline. Mixing them — like a “customer” deal stage — is a modeling error. We keep a separate Lifecycle Stage Definitions template for that layer.

This is a Market Disrupt worksheet, not a vendor file. Import-format templates follow each platform's documented layout as of July 2026 — platforms evolve, so validate against current documentation before a large import.