Playbook

    The HubSpot Deal Stages That Actually Match How a GC Wins Work

    4 min readBy ServiceIQ
    A project manager checking his phone at a desk with blueprints and a toy VW bus inside a jobsite office trailer

    Quick answer: HubSpot ships with default deal stages built for a straightforward sales motion most GCs don't run. A stage list that matches bid-to-build work separates Invited to Bid from Estimating in Progress from Bid Submitted, because that middle stage is where unbillable estimating hours accumulate and win rate becomes worth tracking. The mistake worth avoiding is creating a stage for every internal task; a stage should represent a real change in the probability of winning, not a checklist item.

    Key Takeaways

    • ●HubSpot's default deal stages, qualify, meet, propose, negotiate, close, assume a sales motion most GCs don't actually run.
    • ●A bid-to-build stage list needs to separate Invited to Bid from Estimating in Progress from Bid Submitted, because that middle stage is where unbillable hours accumulate.
    • ●Tracking win rate by the stage a deal reached, shortlisted but never awarded, for instance, surfaces a different problem than never getting invited to bid at all.
    • ●A common mistake is creating a stage for every internal task. A stage should represent a real change in probability of winning, not a to-do list.
    • ●Too many stages makes the pipeline report meaningless, because it stops reflecting where a deal actually stands commercially.

    HubSpot ships with default deal stages, qualify, meet, propose, negotiate, close, built for a straightforward sales motion: one buyer, one decision, a short cycle. A GC's path from lead to signed contract doesn't look like that, and forcing it into those stages is a common reason construction HubSpot portals end up with a pipeline nobody actually trusts.

    Why the Default Stages Don't Fit

    "Proposal sent" doesn't capture what's actually happening during a multi-week competitive bid, and "negotiation" could mean anything from minor value engineering to a full GMP renegotiation. The defaults describe a sale. A bid describes a process with its own distinct phases, and those phases deserve their own stages.

    A Stage List Built Around How Bids Actually Move

    A stage list closer to reality looks like: Lead or Opportunity Identified, Invited to Bid, Estimating in Progress, Bid Submitted, Shortlisted or Interview, Contract Negotiation, Awarded Pending Signature, and Closed Won or Closed Lost. Separating Estimating in Progress from Bid Submitted matters more than it looks: that middle stage is where a large amount of unbillable estimator hours accumulate, and it's worth tracking win rate against specifically, not folded into a generic "in progress" bucket. Shortlisted or Interview deserves its own stage too, because a bid that gets shortlisted but loses at interview is failing for a completely different reason than a bid that never gets past estimating, and lumping the two together hides which problem is actually costing you work.

    What to Actually Track at Each Stage

    Stage duration, how long bids sit in estimating before a decision to submit, reveals where effort is going. Win rate by the furthest stage reached tells a different story than overall win rate alone: a deal that gets shortlisted but never awarded is a different problem than a deal that never gets invited to bid in the first place, and the fix for each is not the same.

    The Mistake Worth Avoiding

    Don't create a stage for every internal step. A stage should represent a real change in the probability of winning, not an internal task someone has to complete. A pipeline with fifteen stages representing a checklist, rather than five or six representing commercial reality, stops being something anyone can read a report from.

    None of this requires custom code. It requires sitting down once and mapping how bids actually move before building the stages around that, rather than the other way around.

    AI Questions You're Too Busy Running a Business to Ask

    AI Questions You're Too Busy Running a Business to Ask

    If you're already modernizing how your sales stack works, this is the plain-English breakdown of what's actually worth paying attention to in AI, free.

    Get the free eBook
    ServiceIQ

    Ready to take on more premium projects without adding to your overhead?

    Lock in your flat-rate, unlimited-user fee with ServiceIQ today.

    Start your free trial

    Frequently asked questions

    ServiceIQ

    Ready to take on more premium projects without adding to your overhead?

    Lock in your flat-rate, unlimited-user fee with ServiceIQ today.

    Start your free trial