A CRM pipeline built from a default template rarely matches how your team actually sells. Stage architecture is the foundation everything else is built on, automation, scoring, reporting, so it is built around your real sales motion from the first conversation.
Standard Stage Structure
- New: a contact has entered a sequence but has not yet engaged
- Contacted: sequence is actively running, no reply yet
- Replied: any reply received, positive, neutral, or objection, routed here for triage
- Qualified: reply has been reviewed and the contact fits your ICP and shows genuine interest
- Call booked: a discovery or sales call is scheduled
- Closed won or closed lost: the deal has resolved, with a lost-reason field captured for pattern analysis
Customizing Beyond the Standard Structure
Many teams need additional stages: a “nurture” stage for qualified-but-not-ready contacts, a separate track for inbound versus outbound leads, or multiple pipelines for different product lines or service tiers. Stage architecture is built to match whatever structure your sales process actually requires, not forced into six generic boxes.
Why Stage Definitions Need to Be Precise
Vague stage definitions, where “qualified” means something different to every rep, quietly destroy reporting accuracy over time. Each stage is defined with clear, specific entry criteria during setup, so pipeline data stays consistent regardless of who is moving deals through it.
Output
A fully configured pipeline inside GoHighLevel or HubSpot, with every stage defined, entry criteria documented, and your team trained on exactly when and how a deal moves from one stage to the next.