HubSpot Sales Pipelines: Stages, Exit Criteria and Ownership

A useful sales pipeline reflects how a buyer moves towards a decision. If the configured stages follow internal administration alone, forecasts become harder to interpret. Start with buyer behavior and define the evidence required to advance each deal.

Here's how to build a pipeline that reflects reality and gives you forecasting data you can trust.

Use stages for distinct buying decisions

A stage is useful when it reflects a decision, changes the next action or supports a necessary control. Revisit stages that merely record administrative tasks; keep distinct stages where the business needs a different owner, approval or commitment.

The number of stages follows the buying process. The example below is a starting point for discussion. Its probabilities are illustrative: calibrate forecasting assumptions with your own historical outcomes and revisit them when the process changes.

Here's a framework I use as a starting point, adjusted based on each company's sales cycle:

Qualified (10%): The lead has been vetted and meets your criteria for a sales conversation. Budget, authority, need, and timeline have been initially assessed.

Discovery (20%): A meaningful conversation has happened. You understand their problem, their current solution, and their decision process.

Solution Presented (40%): You've shown them how your product or service solves their specific problem. They've seen a demo, received a proposal outline, or reviewed a solution document.

Proposal Sent (60%): A formal proposal or quote has been delivered with specific pricing and terms. The buyer has something concrete to evaluate.

Negotiation (80%): The buyer has engaged with the proposal. They're asking questions about terms, requesting modifications, or running internal approvals. The deal isn't done, but both sides are working toward close.

Closed Won / Closed Lost: Self-explanatory, but critical to track separately. Every closed-lost deal should have a reason — this data is essential for pipeline improvement.

Define entry criteria for every stage

A deal should only move to the next stage when specific, verifiable criteria are met. Not "I feel good about this one" — actual evidence that the deal has progressed.

In HubSpot, use required properties on deal stage change to enforce this. When a rep moves a deal from Discovery to Solution Presented, require them to fill in the decision maker name, budget range, and expected timeline. If they can't fill these in, the deal isn't actually at that stage.

This creates friction — and that's the point. A little friction at stage transitions prevents a lot of fiction in your forecast.

Set up deal properties that drive insight

Beyond the default HubSpot deal properties, there are a handful of custom properties that make pipeline management significantly better. If you haven't run a CRM audit recently, start there before adding new properties.

Next step and next step date. What's the next concrete action, and when is it happening? This turns pipeline reviews from status updates into action-planning sessions.

Competition. Who else is the buyer evaluating? Knowing you're up against a specific competitor changes your strategy. Knowing you're the only option changes your pricing confidence.

Decision process. How does this company make purchasing decisions? Single decision maker, committee, procurement process? A deal with a procurement step needs different forecasting assumptions than a founder-led purchase.

Closed-lost reason. A dropdown with five to eight specific reasons: lost to competitor, no budget, bad timing, chose to do nothing, went with internal solution, and so on. Free-text reasons are useless for analysis — structured data lets you identify patterns.

Automate the admin, not the selling

Use HubSpot workflows to handle the repetitive admin work around deals, so reps spend their time selling. Good process design matters here — automate what's repeatable, not what requires judgment:

Task creation on stage change. When a deal moves to Proposal Sent, automatically create a follow-up task for three days later. When a deal enters Negotiation, create a task to confirm contract terms.

Stale deal alerts. If a deal hasn't moved stages in 14 days (adjust based on your sales cycle), send the deal owner a notification. Deals that sit too long without activity are dying quietly.

Manager notifications. Alert sales managers when high-value deals enter negotiation or when deals are marked as closed-lost. This keeps leadership informed without requiring manual updates.

Deal rot automation. After a deal has been inactive for 30 days, automatically reduce its close probability or move it to a "stalled" stage. This keeps your pipeline honest and your forecast accurate.

Build reports that drive action

Three reports every sales team needs from day one:

Pipeline velocity by stage. How long do deals spend at each stage on average? If deals consistently stall at Solution Presented, you have a demo or proposal problem. If they stall at Negotiation, you have a pricing or procurement problem.

Win rate by source. Which lead sources produce deals that close? If referrals close at a significantly higher rate than paid ads — which they typically do — that should inform your marketing spend.

Closed-lost analysis. What are the top reasons for losing deals? Track this monthly and act on the patterns. If "lost to competitor X" is trending up, you need competitive intelligence, not more pipeline.

A pipeline is only as good as the decisions it enables. Build it to reflect reality, enforce discipline at transitions, and let the data tell you where to focus. That's what separates companies that forecast accurately from those that guess.