Most teams configure deal stages during their initial CRM setup, then have an "oh shit" moment six months later when they realize the pipeline bears zero resemblance to how deals actually progress. Reps start skipping stages entirely. Forecasts become fiction. And your reports? They're showing deals parked in "Proposal Sent" for 90 days straight because nobody mapped what actually happens between sending that proposal and getting the signature.
Setting these stages up isn't rocket science. But it does require translating the actual sales process into stages that reps will use consistently. Not the sanitized version from the onboarding deck. The real one.
This guide walks through configuring stages that reflect reality, structuring pipelines when running different sales motions, and figuring out where automation actually helps (versus where it just creates busywork).
If the current pipeline feels more like a compliance checkbox than a tool that helps close deals, it's worth fixing.
What are the default deal stages in HubSpot?
Every new HubSpot account ships with seven pre-configured stages, and they're built around one specific sales motion. Chances are, it's not the right one. Here's what comes out of the box, according to HubSpot's knowledge base (2026):
- Appointment scheduled (20%)
- Qualified to buy (40%)
- Presentation scheduled (60%)
- Decision maker bought-in (80%)
- Contract sent (90%)
- Closed won (100%)
- Closed lost (0%)
Those percentages represent win probabilities - HubSpot multiplies them against deal amounts to calculate weighted pipeline value in board view, per HubSpot's knowledge base (2026). The logic assumes traditional B2B sales: book a meeting, qualify the prospect, schedule a formal pitch, get decision-maker approval, then send the contract.
But what if that's not the actual process?
If the business is selling SaaS with product-led growth, "Presentation Scheduled" doesn't exist. The stages might be trial started, trial active, usage threshold hit. E-commerce businesses don't need "Decision Maker Bought-In" - that stage is meaningless when someone's checking out online. Professional services firms might track discovery call, proposal sent, revisions requested, statement of work signed. Completely different motion.
HubSpot designed these as a starting template, not gospel. The platform actually expects customization - stage configuration lives in Settings → Objects → Deals → Pipelines, where stages can be renamed, win probabilities adjusted, conditional properties added, and separate pipelines built for different sales processes. Teams that leave the defaults untouched end up with a pipeline that doesn't reflect how their deals actually move. That turns forecasting into guesswork and renders board view pretty much useless.
Worth fixing.
Map your actual sales handoffs before opening HubSpot
Sales handoffs need to be mapped before logging into the platform. When stages are defined based on what actually happens in deals - not HubSpot's generic defaults - the result is tracking buyer progression instead of internal busywork. That's what makes forecasting data useful instead of just... there.
Mapping first means figuring out the checkpoints where prospects actually change state. Discovery completed. Proposal sent. Verbal agreement. This also involves identifying where handoffs occur between team members and documenting what each stage proves about whether the deal has momentum before configuring anything.
Sit down with whoever closes deals and map what really happens.
Not what the onboarding deck says should happen. What happens.
Figure out the checkpoints where a prospect moves forward. That might look like: inbound lead → discovery call booked → call completed → proposal sent → verbal agreement → contract signed. Each checkpoint should represent a change in the buyer's state - not an internal task that was completed. "Proposal Sent" is a stage because it means the buyer has the numbers and is deciding. "Sent Follow-Up Email" isn't a stage. That's just work that doesn't change where the deal stands.
Ask the team (or whoever closes deals) where handoffs happen. If an SDR books the call and an AE runs discovery, that's a handoff. Visibility into both sides is needed. And if sales closes the deal then passes it to implementation, mark that transition too. Pipeline stages work best when each stage answers one question: what has the buyer done or agreed to that makes this deal more likely to close?
Write this down before opening the CRM. Most teams skip straight to renaming the default stages, which is how pipelines end up tracking internal workflow instead of buyer progress - and that makes forecasting completely useless. The result? Board view shows deals stuck in "Waiting on Legal" at 80% probability when the buyer hasn't even responded in two weeks. The technical work of configuring stages takes maybe 20 minutes. The thinking work of defining what a stage actually represents? That's what determines whether pipeline data will be actionable or garbage.
Once the real process is mapped on paper, it becomes clear exactly which stages to create, where the probability jumps should be, and what properties matter at each checkpoint. Then open the platform.
Configure deal stages in HubSpot pipeline settings
Configure stages in pipeline settings
Head to Settings > Objects > Deals > Pipelines tab. That's where pipeline stages are built out - the ones that match how the team actually sells. Each stage needs a probability and can trigger automation when deals move through. The default Sales Pipeline is the starting point, but if different types of deals are in play (new business vs renewals, enterprise vs mid-market, direct vs partner-sourced), separate pipelines should be created. Different sales motions close at different rates, and forcing them into one pipeline just creates noise in reporting.
Most teams edit the default Sales Pipeline in place - rename the stages, tweak probabilities, delete whatever doesn't fit. That works if the process is consistent across all deals. But separate pipelines make sense when close rates and stage durations vary significantly between deal types. Deals can be routed to the right pipeline automatically using properties like deal source or product line. Worth it? Usually.
Stage definitions matter more than people realize. When deals move between stages, that's what triggers automation workflows. Messy stages mean messy handoffs to customer success, broken notification sequences, inaccurate forecasts. Get this right upfront.
Editing or creating a pipeline
Click Pipelines in the top menu once inside the Deals object settings. A list of existing pipelines appears (probably just the default one if this is the first setup). Click Edit to modify an existing pipeline or Create pipeline to build something new from scratch.
Give new pipelines clear names. "Renewals Pipeline" or "Enterprise Sales" - labels that tell reps exactly which deals belong there. A default pipeline can be set for new deals or workflows can assign them based on properties. If the close process differs between new logos and renewals, split them. One probability model won't accurately forecast both, and reps need stage definitions that reflect what actually happens in those deals.
Stick with one pipeline if the process is uniform across all deal types. Adding complexity for the sake of it isn't helpful.
Adding and ordering stages
Inside any pipeline, click Add stage to create a new step. Then drag stages around to match actual buyer progression - prospects don't move in alphabetical order, they move through the steps used to close them.
Connect stage changes to automation and reporting
Once stages are configured, they can be wired to automation and reporting - the elements that turn a static list of deals into a system that assigns work, fires off notifications, and shows where deals are dying.
Stage changes become triggers. When a deal hits "Contract Sent", the CFO can be automatically looped in for final review or the #deals Slack channel can be pinged. Workflows can be built that watch for these transitions - a deal enters "Proposal Sent" and suddenly there's a task on someone's calendar, or a deal closes and the onboarding sequence kicks off without anyone clicking a button.
The mechanics live in HubSpot's workflow editor (Professional and Enterprise plans only, per HubSpot's pricing page (2026)). The filter is "Deal stage is any of X" and then branching from there. If a deal goes "Closed Lost", trigger an email survey asking what went wrong. If it's "Closed Won", enroll the contact in onboarding. Pretty straightforward once the interface is visible - though most teams underutilize the branching logic.
Reporting is the other half. Deal-based reports segmented by stage show conversion rates between steps, which is how bottlenecks are found fast. Build a custom report counting deals that entered each stage in the last 30 days, add a column for how many advanced to the next step, and stage-to-stage conversion percentage is available. Dashboards showing average time per stage reveal where deals stall.
One thing that catches people: each stage has a probability percentage that feeds into weighted revenue forecasts. HubSpot's help documentation (2026) explains this, but the short version is those percentages matter if leadership relies on pipeline projections. Set them accurately or forecast numbers will be off.
The pipeline becomes the skeleton everything else hangs on - workflows react to stage movement, reports calculate what's converting (and what isn't), and real-time visibility becomes available without manually tracking handoffs.
Audit and refine stages as your sales process evolves
Pipelines need regular audits. The sales process that made sense six months ago probably doesn't match what the team actually does today.
Pull stage duration reports every quarter and look for two things: bottlenecks (where deals pile up like cars at a broken stoplight) and stages that deals blow through in under 48 hours. If something takes less than two days on average, a whole stage probably isn't needed for it.
Pipelines might work beautifully right now and become completely sideways by next quarter. New product lines change deal velocity. A different buyer persona shifts where deals stall out. And sometimes the whole thing was over-engineered from the start.
When pulling that quarterly report, watch for stages where deals sit for 30 days right next to stages averaging 2 days. That's the pipeline signaling it doesn't match reality anymore. If "Qualified to buy" holds deals for a month while "Presentation scheduled" averages 48 hours, something's off.
Talk to reps about which stages feel forced or artificial. "Decision maker bought-in" sounds great in theory, but if the team can't reliably tell when they've actually hit that checkpoint, the stage creates friction instead of clarity. Ambiguous stages wreck forecasting because everyone interprets them differently - one rep's "bought-in" is another rep's "maybe interested."
Add a stage when a new checkpoint has genuinely been added to the sales process. Like a required technical review that didn't exist before. Merge stages when two things always happen together and separating them doesn't give useful data. Delete a stage when the milestone doesn't matter to the business anymore.
Most teams build 12 stages when 6 would work better. Granular tracking sounds sophisticated until nobody bothers maintaining it and the data goes stale. Fewer, clearer stages beat a pipeline so detailed that reps ignore half of it and just guess at probabilities.
But don't strip away stages that surface real decision points. The goal isn't the smallest possible number - it's the right number for how deals actually move.
Get your deal stages working for your team
Pipelines should guide reps through the actual sales motion, not win awards for looking sophisticated. Most small-to-mid-size teams inherit the platform's seven default stages (Appointment scheduled at 20%, Qualified to buy at 40%, Presentation scheduled at 60%, Decision maker bought-in at 80%, Contract sent at 90%, Closed won at 100%, Closed lost at 0%, according to HubSpot's official help documentation (2026)) and never question them. That's fine - but only if those stages actually match how deals close. If reps skip stages, misuse probabilities, or can't tell which deal is closest to closing, it's time to rebuild them around how buyers actually move from first contact to signed contract.
When do stages become a problem? If they collect dust because nobody bothers updating them, or if forecast accuracy is worse than a coin flip, something's broken. Stages need to map directly to handoffs, decision points, and deliverables in the process. Not generic labels that sound professional but mean nothing to reps. When stages reflect real sales milestones - the kind reps can actually identify in a live deal - they make pipeline reviews faster, forecasts more reliable, and automation triggers meaningful follow-up instead of generic noise.
Gable helps businesses configure stages that reflect their real sales process, wire up automation so stage transitions trigger the right workflows, and build reporting dashboards that teams actually check. If the CRM feels like extra work instead of a tool that makes selling easier, that's fixable. Start with a CRM audit to determine whether the pipeline needs a quick tune-up or a full rebuild.
Frequently Asked Questions
What are the default deal stages in HubSpot?
The platform ships with seven stages: Appointment Scheduled, Qualified to Buy, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, and Closed Lost. Most teams replace these immediately. They're built for a generic B2B SaaS motion that probably has nothing to do with how most teams actually close business.
What's the difference between deal stages and lifecycle stages in HubSpot?
Deal stages track where a specific opportunity sits in the sales process (like "Proposal Sent" or "Negotiation"). Lifecycle stages track where a contact is in their overall journey with the company - Subscriber, Lead, MQL, SQL, Customer. One contact can have five deals in different stages, but they'll only have one lifecycle stage at any given time.
How many deal stages should I have in HubSpot?
Most effective pipelines land between 5-8 stages. Drop below 5 and visibility is lost into where deals actually stall. Go above 8 and reps won't maintain them - they'll skip stages or waste time figuring out which one fits.
Can I use different deal stages for different products in HubSpot?
Yes, and separate pipelines probably should be created if distinct product lines are being sold or different sales motions are used. Create multiple pipelines by going to Settings > Objects > Deals > Pipelines, then click "Create pipeline." Each one gets its own stages, probability percentages, and automation rules.
How do I change deal stage probabilities in HubSpot?
Navigate to Settings > Objects > Deals > Pipelines, click the pipeline name, then click the pencil icon next to each stage to edit its probability percentage. Base these on actual historical close rate at each stage, not some clean increment pattern.
Should deal stages match my CRM reports or my actual sales process?
The actual sales process. Always. If stages are built for reporting convenience instead of how reps actually advance deals, they won't update them consistently - which makes reporting useless anyway.
Gable Innovation is a technology consultancy that helps growing businesses implement and optimize CRM systems like HubSpot, Salesforce, and custom integrations. If stages are being set up for the first time or a pipeline that isn't working needs fixing, businesses can audit current setups and build something that actually reflects how teams sell. Book a 30-minute discovery call - no obligation.
We help growing businesses implement CRM, build custom software, and deploy AI tools that actually work.