🎯 HubSpot Lead Stage Designer

HubSpot Workflow Architecture: B2B SaaS Hybrid GTM

Diagnosis

Your HubSpot has 3 fundamental issues:

1. Stage explosion: 14 lead statuses + 9 lifecycle stages = sales doesn't know what 'qualified' means in your CRM.

2. 80 custom properties on Contact: most unused; clutters every contact view; obscures the 8-12 that actually matter.

3. Hybrid GTM not modeled: PLG signups + sales-led demos are getting forced through one funnel, breaking attribution.

Critical fixes:

1. Cut to 6 lifecycle stages + 5 lead statuses

2. Archive ~60 custom properties; keep ~20 that actually drive decisions

3. Model TWO funnel paths: PLG (signup → activation → SQL) and Sales-led (lead → MQL → SQL). Lifecycle stage is the union; lead status differentiates.

Lifecycle Stage Definition (6 stages)

All contacts move through these stages linearly. Each is a one-way ratchet (rare exceptions).

1. Subscriber

• Definition: Anyone in our CRM not yet engaged with our product or sales team.
• Entry: Newsletter signup, gated content download, conference badge scan.
• Exit: Move to Lead when they signup for trial OR request demo OR engage with sales outreach.
• Owner: Marketing.

2. Lead

• Definition: Showed initial interest. Could be product or sales-driven.
• Entry: Free trial signup, demo request, replied to outbound, MQL hit (auto-promote from Subscriber if scoring crosses 60).
• Exit: Promoted to MQL (qualified) or disqualified (back to Subscriber or removed).
• Owner: Marketing for inbound; SDR for outbound.

3. MQL (Marketing Qualified Lead)

• Definition: Meets MQL criteria (see definition below). High-quality lead worth SDR follow-up.
• Entry: Lead score crosses 60 OR demo request.
• Exit: SDR contacts; promotes to SQL or disqualifies.
• Owner: SDR (assigned within 5 min of MQL).

4. SQL (Sales Qualified Lead)

• Definition: SDR-confirmed fit. Has identified pain + budget signal + decision-making capability.
• Entry: SDR call with prospect confirms fit (BANT-lite).
• Exit: Demo booked → Opportunity. Or disqualified back to Lead.
• Owner: AE (assigned at SDR-to-AE handoff).

5. Opportunity

• Definition: Demo completed; AE actively pursuing close. Deal record exists.
• Entry: First demo with AE.
• Exit: Closed-won → Customer. Closed-lost → back to Lead (with reason captured).
• Owner: AE.

6. Customer

• Definition: Closed-won. Stripe subscription active.
• Entry: Closed-won deal moved to closed-won stage in Deal pipeline.
• Exit: Churned (separate property + segmented out for renewal-focused workflows).
• Owner: CS.

What we DON'T have: 'Demo Scheduled', 'Trial User', 'Subscriber Active', 'Re-engagement', 'Sales Hand-off'. These were stages in your old setup. They're properties, not stages.

Lead Status Definition (5 statuses)

Lead statuses describe conversational state within a Lead/MQL/SQL. They DON'T progress automatically with lifecycle stage.

1. New — never been contacted. Default for new MQLs.

2. Attempted — SDR has reached out (email + call). Awaiting response.

3. Connected — Two-way conversation in progress. SDR is qualifying.

4. Qualified — SDR confirmed fit (becomes SQL on lifecycle).

5. Disqualified — Confirmed not a fit (with reason from dropdown).

That's it. NO 'Working,' 'Hot Lead,' 'Long-Term Nurture,' 'Re-engaged' — those are properties or list memberships.

Deal Stages (Pipeline)

With win-rate-by-stage targets calibrated to your historical data (estimate; refine after 90 days):

1. Demo Scheduled (probability: 15%) — meeting booked but not yet held

2. Demo Completed (25%) — held, AE pursuing

3. Proposal Sent (45%) — pricing + scope sent to prospect

4. Negotiation (65%) — terms being discussed

5. Verbal Commit (85%) — yes, finalizing contract

6. Closed-Won (100%)

7. Closed-Lost (0%) — with mandatory loss reason

Win-rate targets serve forecast accuracy. Sales lead reviews actual win rates quarterly + adjusts probabilities.

MQL Definition (the yes/no test)

A contact is an MQL when ALL of these are true:

1. Company-fit signal: Company size 20+ employees (per ZoomInfo or LinkedIn enrichment) OR Domain matches a target-account list.

2. Role-fit signal: Title contains 'engineer,' 'engineering,' 'CTO,' 'VP eng,' 'director eng,' 'SRE,' or 'DevOps' (or equivalent in non-English).

3. Intent signal (any of):

- Demo request submitted

- Trial signup AND activated (used 3 core features in 7 days)

- Lead score ≥ 60 (see scoring below)

4. Not blacklisted: Email domain is not in our exclusion list (competitors, free email providers if outbound-only).

If yes to all 4 → MQL. If any no → Lead, possibly Subscriber.

This is the clear yes/no test sales has been missing.

SQL Definition

An MQL becomes an SQL when SDR confirms (during call/email):

• B (Budget): acknowledges they have budget OR confirms it's available 'this quarter' or specific timeline
• A (Authority): confirms decision-maker involvement (themselves OR specific named person they will loop in)
• N (Need): confirms specific pain matching our solution (e.g., 'on-call alerts are a problem')
• T (Timeline): indicates 'this quarter' or 'next quarter' decision timeline

3 of 4 confirmed → SQL. Less = stays MQL with notes.

Critical Handoffs + SLAs

Handoff 1: Marketing → SDR (MQL created)

• SLA: SDR responds within 5 min during business hours
• Trigger: Slack alert to SDR rotation when MQL is created
• Failure mode: MQL ages > 5 min without SDR action → escalate to SDR manager
• Why 5 min: lead-response data shows >90% drop in conversion past 30 min

Handoff 2: SDR → AE (SQL converted)

• SLA: AE first-touch within 4 business hours
• Trigger: SDR marks contact as 'Qualified' lead status; HubSpot workflow assigns to AE round-robin + Slacks AE
• Required handoff data: SDR call notes, BANT confirmation, recommended next step
• Failure mode: AE no-touch within 4h → flag for sales lead

Handoff 3: AE → CS (Closed-Won)

• SLA: CS reaches out within 1 business day
• Trigger: Deal moves to Closed-Won; workflow assigns to CS + creates onboarding task
• Required handoff data: AE deal notes, key promises made during sale, expected use cases, contract details
• Failure mode: CS no-touch within 1 business day → escalate to CS manager

Handoff 4: CS → Customer success (Activated → Healthy)

• SLA: First check-in within 30 days of close
• Trigger: Day-30 task auto-created on close
• Tracking: 'Activation Health' property: green / yellow / red
• Failure mode: Stays yellow/red >60 days → escalate to CS lead

Lead Scoring Setup

Keep simple. 7 criteria, weighted:

Firmographic (calibrated from your conversion data):
  +25  Company size 50-200 employees (your sweet spot)
  +10  Company size 20-49 OR 201-500
  +0   Other sizes (no penalty)
  +20  Title is 'Engineering Manager,' 'VP Eng,' 'CTO,' or 'Director Eng'
  +10  Title contains 'engineering' or 'SRE' or 'DevOps' (broader)

Behavioral:
  +25  Demo request submitted (instant MQL trigger if firmographics met)
  +30  Trial signup AND activated (3 features used in 7 days)
  +10  Trial signup but not activated
  +5   Visited >3 pages on website in 7 days
  +5   Downloaded gated content (case study, whitepaper)

Intent (third-party):
  +15  Apollo / Clearbit reveals high-intent topic engagement
  +10  G2 / Capterra shows research-stage signal

MQL threshold: 60. This is a v1 number; refine after 90 days based on actual MQL→SQL conversion data.

Negative scoring:

-25  Email is free provider (gmail.com, yahoo.com, etc.) — likely consumer
-15  Company size 1-10 employees (off-target)
-10  Title is 'student' or 'researcher' or no title given
-50  Email is on competitor domain list

Properties to Track (max ~20 per object)

Contact (custom properties beyond defaults)

1. Lead Source (single-select: Inbound Form, Outbound, Conference, Referral, Other)

2. Specific Source (text — campaign name, conf name, etc.)

3. Trial Started Date (date)

4. Trial Activated Date (date — null if not activated)

5. Activation Type (multi-select: which features they used)

6. SDR Owner (user)

7. AE Owner (user)

8. Last Engagement Date (date — auto via HubSpot)

9. Slack-Connected? (boolean — for B2B Slack-Connect users)

10. Disqualification Reason (single-select: dropdown of 8 reasons)

Company

1. Industry (enum)

2. Employee Count Range (single-select with bands)

3. Tech Stack — Alerting (multi-select: Sentry, Datadog, PagerDuty, etc.)

4. Account Type (single-select: Target / Customer / Competitor / Other)

5. Annual Contract Value (currency — once a customer)

6. Total Contracted Engineers (number — for per-seat billing tracking)

Deal

1. Lead Source (mirror Contact)

2. Loss Reason (single-select — required if Closed-Lost)

3. Discount % Applied (number)

4. Contract Term (single-select: monthly, annual, multi-year)

5. Custom Pricing? (boolean)

6. Time-in-Stage (auto via HubSpot — flag stuck deals)

7. Decision-Maker Identified (text — name)

8. Champion Identified (text — name; can be different from decision-maker)

Archive everything else from your current 80-property mess.

Automations Worth Building (8 workflows)

1. New MQL → SDR alert + assignment

• Trigger: Lifecycle stage = MQL
• Actions: Round-robin assign SDR Owner, send Slack DM to that SDR, create task 'Follow up with [Name]', set 'New' status
• Why: the 5-min SLA depends on this firing

2. SQL conversion → AE handoff

• Trigger: Lead Status = Qualified (set by SDR)
• Actions: Round-robin assign AE Owner, transfer task ownership, Slack DM AE, copy SDR notes to AE-visible field

3. Trial activation → MQL fast-track

• Trigger: App DB syncs 'activation' event for a trial user
• Actions: Update Activation Date property, increment lead score by +30, evaluate MQL threshold, alert SDR if newly MQL

4. Demo no-show → re-engagement

• Trigger: Calendly meeting marked 'no-show' AND status was 'Demo Scheduled'
• Actions: AE task to follow up, deal stage stays at Demo Scheduled, mark in deal notes

5. Closed-won → CS handoff

• Trigger: Deal stage = Closed-Won
• Actions: Update Lifecycle Stage to Customer, create CS owner assignment, create 'Day-1 onboarding' task, send Slack DM to CS, kick off onboarding email sequence

6. Long-aging deals

• Trigger: Deal in any non-closed stage for >30 days
• Actions: Daily Slack reminder to AE owner, weekly digest to sales lead, prompt for explicit 'Why is this stuck?' note

7. Trial expired without close

• Trigger: Trial Started Date + 14 days, Lifecycle Stage still in Lead/MQL/SQL
• Actions: Email customer about trial extension or close, task to AE, segment for re-engagement campaign

8. Quarterly health check (CS automation)

• Trigger: Days since last contact > 90 for Customers
• Actions: CS task to schedule quarterly check-in, evaluate Activation Health, prompt for renewal-prep if approaching contract anniversary

Reporting + Dashboards

Per-role dashboards

SDR Dashboard:

• My open MQLs (table)
• My SLA hit-rate this week (single number, target >95%)
• My SQL conversion rate this month (vs SDR team avg)
• Recent disqualified (with reasons — for pattern recognition)

AE Dashboard:

• My pipeline by stage (table)
• My closed-won this quarter (single number)
• My pipeline coverage (3-4× quota target)
• Stalled deals >14 days no activity

Sales Lead Dashboard:

• Team pipeline by stage
• MQL→SQL conversion by SDR
• SQL→Closed conversion by AE
• Pipeline by source (inbound vs outbound)
• Loss reasons breakdown

CS Dashboard:

• Activation Health by customer
• At-risk customers (yellow/red Health)
• Renewal coming in 90 days
• Recent closed-won handoffs

Marketing Dashboard:

• Lead source attribution (inbound channels)
• MQL volume by source
• MQL→SQL rate by source (which sources convert)
• Cost per MQL (if ad spend tracked)

Implementation Order

Week 1: Audit + cleanup

• Audit current 80 properties; identify the ~20 to keep
• Audit current 14 lead statuses + 9 lifecycle stages; identify what they really mean
• Document migration mapping (old → new)

Week 2: New schema setup

• Configure 6 lifecycle stages with definitions
• Configure 5 lead statuses
• Configure 7 deal pipeline stages with probabilities
• Set up the ~20 custom properties

Week 3: Migration + cleanup

• Bulk-update existing contacts to new lifecycle stage mapping
• Archive unused properties
• Deduplicate contacts (HubSpot has dedup tool)

Week 4: Automations

• Build the 8 workflows above
• Test each with sample data
• Document for team

Week 5: Scoring + dashboards

• Implement lead scoring rules
• Build the 5 role dashboards
• Train team on each dashboard

Week 6: SLA enforcement

• Slack alerts for SLA breaches
• Sales lead 1:1s using new dashboards
• Capture initial baseline metrics

Week 7-8: Iteration

• Adjust scoring thresholds based on actual MQL→SQL data
• Refine deal stage probabilities based on actual win rates
• Address team friction points

Migration Plan from Your Current Setup

Your 14 lead statuses + 9 lifecycle stages map roughly to:

Document the mapping in a spreadsheet first. Validate with sales lead. Then bulk-update via HubSpot's import.

For aging records (no activity in 90+ days): mark 'Disengaged' (a property), keep at current stage but exclude from active workflows.

What This Setup Won't Solve

• Won't replace data integrity discipline. If reps don't fill in disqualification reasons, scoring degrades. Culture > tooling.
• Won't fix attribution gaps. If marketing campaigns aren't tagged with UTM parameters consistently, source data is unreliable. Fix tagging before relying on Marketing dashboard.
• Won't auto-prevent stage skipping. Reps will sometimes mark Closed-Won without the deal going through Negotiation. Quarterly audits catch this; perfect prevention requires HubSpot Enterprise tier with stricter validation.
• Won't handle complex multi-buying-committee deals. Enterprise deals with 5+ stakeholders + multiple meeting threads need custom objects (HubSpot Pro Tier limits this).
• Won't build itself. This document is the architecture. Implementation requires 4-6 weeks of focused RevOps work.

Maintenance Cadence

Weekly (RevOps, ~30 min):

• Verify automations didn't fail (HubSpot has workflow run history)
• Spot-check 5 random new MQLs for data quality
• SLA hit-rate review

Monthly (RevOps + Sales Lead, ~1 hour):

• Disqualification reason review (any patterns?)
• Loss reason review
• Score threshold check (is 60 the right MQL bar?)
• Property usage audit (any properties going unused?)

Quarterly (~3-4 hours):

• Full pipeline metrics review (conversion rates, win rates by stage)
• Recalibrate scoring weights based on data
• Recalibrate deal stage probabilities
• Workflow audit
• Survey sales team: what's working, what's friction?

Annually:

• Architecture re-evaluation. Is hybrid PLG+sales-led still right? Did GTM motion shift?
• Property audit (cleanup unused)
• Tier evaluation (do you need Enterprise?)
• Vendor evaluation (still HubSpot? Or evaluate Salesforce/etc.?)

Key Takeaways

• 6 lifecycle stages + 5 lead statuses (not 9 + 14). Cleanup first; configure second.
• MQL definition = yes/no on 4 specific criteria. No 'maybe' MQLs.
• SLAs at every handoff. 5-min for MQL→SDR, 4h for SDR→AE, 1 day for AE→CS.
• Simple lead scoring v1 (7 criteria). Refine after 90 days of data.
• <20 custom properties per object. Archive 60+ unused properties from your current setup.
• 8 workflows are enough. Don't over-automate; you'll spend more debugging than you save.