Build your deal pipeline

Map your sales process into stages with probabilities. Add conditional properties so reps capture the right information at every step.

Introduction

Your deal pipeline is the single most important structure in your sales hub. It's how HubSpot represents your sales process from first conversation to closed deal, and every piece of sales reporting, forecasting, and automation depends on it being set up correctly.

Most teams either stick with HubSpot's default pipeline stages (which rarely match their actual process) or create stages based on what the sales team does rather than what the customer experiences. Both approaches create the same problem: deals get stuck in ambiguous stages, reps move them inconsistently, and your pipeline data becomes unreliable.

Getting this right takes about thirty minutes of honest conversation with your sales team about what actually happens between "new lead" and "deal closed". That conversation is more valuable than any HubSpot feature you'll configure later.

Top picks

No items found.

How deals work in HubSpot

HubSpot has four primary record types (called objects): contacts (people), companies (organisations), tickets (service requests), and deals (potential or closed sales). Deals are where revenue lives. Every deal record tracks the value, the stage, the owner, the expected close date, and every interaction that's happened along the way.

A deal pipeline is the set of stages a deal moves through from start to finish. The stages are displayed as columns in a board view, and you drag deals between them as they progress. HubSpot uses these stages for two critical things: predicting revenue (through stage-weighted forecasting) and identifying bottlenecks (where deals pile up or stall).

Every HubSpot account comes with a default pipeline, but you should replace it with one that reflects your actual sales process.

Design your stages the right way

The most effective pipeline stages share three characteristics:

They're past-tense, customer-centric milestones. Instead of "Sending proposal" (what the rep is doing), use "Proposal received" (what the customer has done). This removes ambiguity about when to move a deal forward. If the milestone hasn't happened yet, the deal stays put.

They follow the "then what?" pattern. Start with the first thing that happens when a potential sale begins and keep asking "then what?" until you reach either closed-won or closed-lost. Each answer becomes a stage.

They're mutually exclusive. A deal should never reasonably belong in two stages at once. If your reps aren't sure whether a deal is in stage 3 or stage 4, your stages overlap.

For example, a B2B pipeline might look like: Appointment scheduled > Package selected > Delivery address confirmed > Contract sent > Closed won / Closed lost. Each stage represents a clear customer action that either happened or didn't.

Set up your pipeline in HubSpot

Go to Settings (gear icon) > Data Management > Objects > Deals, then click the Pipelines tab. You can edit the default pipeline or create a new one.

For each stage, set the deal probability. This is the likelihood that a deal in this stage will close. HubSpot uses these percentages for weighted pipeline forecasting. Make sure your Closed won stage is set to 100% (won) and Closed lost is set to 0% (lost). These designations tell HubSpot the deal is no longer open.

Add conditional stage properties

Conditional properties are fields that become required when a deal moves to a specific stage. This is how you enforce data quality without slowing reps down on every stage transition.

The most important one: require a "Closed lost reason" when a deal moves to Closed lost. If you don't capture why you're losing deals, you can't fix the pattern. Create a dropdown property with your common loss reasons (price, timing, competitor, no decision, etc.) and make it mandatory at the Closed lost stage.

Other useful conditional properties: require "Amount" at the Closed won stage (so your revenue reporting is always accurate), and require "Next step" at mid-pipeline stages to keep reps thinking about deal progression.

To set this up: hover over a deal stage in the pipeline settings, click "Edit properties", then "Add a dependent property". Select the property, tick the "Required" checkbox, and click "Apply logic". Save the pipeline.

Create and manage deals

To create a deal: go to CRM > Deals, click "Create deal", fill in the required fields, and associate it with a contact and company. Always associate deals with both a contact and a company (unless you're a direct-to-consumer business). This association is what connects your sales data to the rest of your CRM.

Deals appear in a board view where you can drag them between stages. When a deal moves to a stage with conditional properties, HubSpot prompts the rep to fill in the required fields before the move completes.

Conclusion

Your deal pipeline is the backbone of your sales reporting and forecasting. Design stages as past-tense customer milestones, enforce data quality with conditional properties, and make sure every deal is associated to both a contact and a company. The thirty minutes you spend getting this right saves hours of cleaning up unreliable pipeline data later.

Related tools

No items found.

Related wiki articles

No items found.

Further reading

Sales hub configuration

Sales hub configuration

Map your sales process into stages with probabilities. Add conditional properties so reps capture the right information at every step.

No items found.