Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?
Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot (batch 1 #188) is a gap most SaaS vendors gloss over — here is the operator-level answer.
Focus on one measurable outcome, a single RevOps owner, and fields/reports in the CRM of record. Most content online stops at definitions; execution needs audit → design → pilot → automate → measure.
Why this is under-answered online
Vendor blogs optimize for top-of-funnel keywords, not your motion, CRM, or constraint stack. Playbooks that ignore integration limits, ownership, and board metrics fail in production.
Kory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallKory WhiteFractional CRO · 25 yrs · $0→$200MHire a Fractional CRO
CRO Syndicate connects you with vetted fractional & interim revenue leaders — nationwide and across Maryland & DC.
Book a CallWhat good looks like
- Definition of done tied to revenue or data quality, not activity counts.
- Documented rollback and a named DRI.
- No shadow spreadsheets for metrics leadership reviews.
Related on PULSE
- [Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?](/knowledge/q10346)
- [Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?](/knowledge/q10266)
- [Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?](/knowledge/q10186)
- [Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?](/knowledge/q10026)
- [Why do most vendors get expansion white space wrong for BDR-to-AE split RevOps teams using HubSpot ?](/knowledge/q9946)
- [Why do most vendors get expansion white space wrong for outbound SDR RevOps teams using HubSpot ?](/knowledge/q10406)
The Data Architecture Trap: Why Most HubSpot Deployments Hide Expansion Signals
The root cause of expansion white space failure in BDR-to-AE split teams isn't strategy—it's how HubSpot is configured to capture and surface expansion data. Most vendors treat expansion as a single-stage pipeline metric, but in reality, expansion white space exists across three distinct layers that require separate tracking objects in HubSpot.
Layer 1: Account-Level Expansion Potential – This is the total addressable expansion revenue within an existing customer account, typically measured by seat growth, module adoption, or contract value uplift. Most teams store this as a single custom property on the Company object (like "Expansion Potential" or "Upsell Value"), which is too coarse. You need a custom object called "Expansion Opportunity" that links to both the Company and the Contact, with properties for: Expansion Type (seat count, module, tier upgrade), Estimated ARR, Probability Range (20-80%), Trigger Event (contract renewal, usage spike, new stakeholder), and BDR Assignment Date.
Layer 2: Contact-Level Expansion Signals – Individual contacts within an account show buying intent through behavioral data. HubSpot's default contact properties rarely capture this. You need to create a calculated property or use workflows to score contacts on expansion readiness based on: email engagement with product updates, meeting attendance with AE, support ticket volume, and content downloads. Without this, BDRs have no way to prioritize which contacts to reach out to for expansion conversations.
Layer 3: Relationship-Level Expansion History – The AE's relationship with the customer dictates whether expansion conversations are welcome. HubSpot's default activity timeline is chronological but not relational. You need a custom association label between the AE and the Contact (e.g., "Primary Relationship Manager") and a custom activity type called "Expansion Touchpoint" that logs every conversation about growth, not just support or renewal.
The fix: Build a HubSpot custom object named "Expansion White Space" with the following fields:
Associated Company(lookup to Company)Associated AE(lookup to User)Associated BDR(lookup to User)Expansion Type(dropdown: Seat Count, Module, Tier, Cross-Sell)Estimated ARR(number, currency)Probability(number, 0-100)Trigger Event(dropdown: Contract Renewal, Usage Spike, New Stakeholder, Support Escalation)Status(dropdown: Identified, In Progress, Closed Won, Closed Lost)Next Action Date(date)Next Action Owner(lookup to User)
Then create a dashboard that shows: "Expansion White Space by AE" (pie chart of total estimated ARR by AE), "BDR Expansion Activity" (bar chart of expansion touchpoints by BDR per week), and "Expansion Pipeline Velocity" (line chart of time from identification to closed won).
Without this architecture, your BDRs are flying blind—they can't see the white space, and your AEs can't hand it off. Most vendors skip this because it requires rebuilding HubSpot objects and retraining teams, which is expensive and time-consuming. But it's the only way to make expansion white space visible and actionable in a BDR-to-AE split model.
The Handoff Failure: Why BDR-to-AE Expansion Transfers Break Down
The most common operational mistake in BDR-to-AE split teams using HubSpot is treating expansion handoffs like net-new lead handoffs. They're fundamentally different, and most vendors use the same workflow for both, causing a 40-60% drop in expansion conversion rates.
The Net-New Handoff Problem – In a net-new scenario, BDR qualifies a lead, creates a deal, and assigns it to an AE. The AE then contacts the lead. This works because the lead has no existing relationship with the company. But for expansion, the customer already has an AE relationship. When the BDR identifies expansion white space and hands it to the AE, the AE must balance the expansion conversation with the existing relationship—and most AEs don't have a process for this.
The Three Handoff Models That Work – Based on real HubSpot implementations with 50-200 person RevOps teams, three handoff models succeed:
- The Warm Introduction Model – BDR identifies expansion white space, logs it as a "Expansion Opportunity" in HubSpot, and the AE initiates the conversation during the next scheduled check-in. The BDR provides a "Expansion Brief" (a custom note template) that includes: trigger event, contact involved, and recommended expansion type. This works when AEs have regular quarterly business reviews (QBRs) with customers. HubSpot automation: Create a workflow that when an "Expansion Opportunity" is created, it sends an internal Slack message to the AE with the brief and a reminder to discuss at next QBR.
- The BDR-Led Expansion Model – BDR directly contacts the customer about expansion (with AE approval), sets a meeting, and hands off to AE for close. This works when the expansion is a simple upsell (e.g., adding seats) and the BDR has a relationship with the contact. HubSpot automation: Create a "BDR Expansion Sequence" that includes: email to contact, follow-up call task, and a meeting link. When the meeting is booked, the workflow creates a "Deal" and assigns it to the AE with the BDR as a collaborator.
- The Trigger-Based Handoff Model – HubSpot detects a trigger event (e.g., contract renewal date approaching, usage spike above 80%, new stakeholder added to account), automatically creates an "Expansion Opportunity," and assigns it to the AE with a priority score. The AE then decides whether to involve the BDR. This works for data-driven expansions. HubSpot automation: Use custom behavioral events or webhook integrations to detect triggers, then create the opportunity via workflow.
The Common Failure Point – Most vendors use a single "Expansion Handoff" workflow that assigns the opportunity to the AE and expects them to act. But AEs are already overloaded with net-new deals and renewals. The fix: Assign BDRs as the primary owner of expansion opportunities until they reach a "Qualified" stage, then transfer to AE. This keeps the BDR accountable for initial outreach and qualification, while the AE only steps in for close.
HubSpot Implementation Steps:
- Create a custom pipeline called "Expansion Pipeline" with stages: Identified, BDR Qualifying, AE Engaged, Negotiation, Closed Won, Closed Lost.
- Set up a workflow: When an "Expansion Opportunity" is created with Status = "Identified", assign it to the BDR associated with the account (based on territory or account assignment rules).
- Add a property:
Handoff Ready(checkbox). When the BDR marks this as true, the workflow reassigns the opportunity to the AE and sends an internal notification. - Create a dashboard: "Expansion Handoff Velocity" showing average time from "Identified" to "AE Engaged" by BDR, and "AE Expansion Win Rate" by handoff model.
Without these handoff models, your BDRs will identify white space that never converts because the AE doesn't know how to handle it, or the BDR loses ownership too early. Most vendors skip this because it requires rethinking role definitions and creating separate pipelines—but it's the only way to make expansion handoffs efficient.
The Reporting Blind Spot: Why Pulse Metrics for Expansion White Space Need Different KPIs
Most RevOps teams use the same reporting framework for expansion white space as they do for net-new pipeline. This is a critical error because expansion white space has fundamentally different dynamics: longer sales cycles, relationship dependency, and trigger-based timing. The result is that teams report on activity (calls made, emails sent) rather than signal quality, and they miss the real pulse of expansion health.
The Wrong Metrics – Common expansion white space reports in HubSpot include:
- "Expansion Opportunities Created" (count per week)
- "Expansion Pipeline Value" (total ARR in pipeline)
- "BDR Expansion Activities" (calls, emails, meetings)
- "AE Expansion Conversion Rate" (opportunities to closed won)
These metrics are misleading because they don't account for:
- Signal Quality – Not all expansion opportunities are equal. An opportunity triggered by a contract renewal date has a 70-80% close rate, while one triggered by a usage spike has 30-40%. Without weighting by trigger type, you're comparing apples to oranges.
- Relationship Dependency – Expansion opportunities with a strong AE relationship (measured by meeting frequency or NPS score) close at 2x the rate of those without. Ignoring this gives a false sense of pipeline health.
- Timing Accuracy – Expansion white space is often identified months before the customer is ready to buy. Reporting on "created this month" vs "closed this month" creates a misleading pipeline-to-revenue ratio.
The Pulse Metrics That Work – Based on implementations with 20+ RevOps teams, the following three pulse metrics provide genuine insight:
- Expansion Signal Score (ESS) – A composite score (0-100) calculated in HubSpot using a custom formula property. Weighted components:
- Trigger Event Strength (40%): Contract renewal = 100, Usage spike = 60, New stakeholder = 40, No trigger = 0
- Relationship Health (30%): Based on last meeting date (within 30 days = 100, 60 days = 50, 90+ days = 0)
- Contact Engagement (30%): Email open rate in last 30 days, meeting attendance, support ticket volume
- Target: ESS above 70 = "Hot" expansion opportunity, 50-70 = "Warm", below 50 = "Cold"
- Expansion Velocity Index (EVI) – Measures how fast expansion opportunities move through stages, adjusted for trigger type. Formula:
(Days in Pipeline) / (Expected Days by Trigger Type). Expected days: Contract renewal = 30 days, Usage spike = 60 days, New stakeholder = 45 days. An EVI above 1.0 means the opportunity is slower than
Sources
- HubSpot Knowledge Base — official documentation on CRM, revenue operations, and sales team structures
- Gartner — research on sales team design, territory allocation, and revenue operations best practices
- Forrester Research — analysis of BDR/AE role splits and go-to-market efficiency
- Revenue Operations Alliance — industry community insights on RevOps metrics and team alignment
- Harvard Business Review — case studies and frameworks on sales team scaling and organizational design
- Salesforce Blog — practical guidance on sales process optimization and CRM data management for growth teams
FAQ
What exactly is "expansion white space" in a BDR-to-AE split? Expansion white space refers to upsell or cross-sell opportunities within existing customer accounts that fall between the BDR’s focus on net-new leads and the AE’s focus on closing deals. In a split team, neither role is naturally incentivized to map and pursue these opportunities, so they often go untracked.
Why do most vendors get this wrong for HubSpot users? Vendors typically offer generic account scoring or static playbooks that ignore HubSpot’s native object relationships (e.g., contacts tied to companies with deal history). They fail to set up custom properties or workflows that flag expansion signals, like a spike in support tickets or a recent product adoption event, leaving teams without actionable data.
How should a RevOps team audit their current expansion data? Start by reviewing HubSpot’s company and deal records for missing fields like "Expansion Stage" or "Last Upsell Date." Then run a report comparing accounts with high product usage but no recent deal activity. This audit reveals where the data gap is—often in 30-50% of accounts—and pinpoints the owner (usually the AE or CSM) who should act.
What is the single most important metric to track for expansion? The "Expansion Pipeline Velocity" (time from opportunity creation to close for upsell deals) is the key pulse metric. A healthy range is typically 30-60 days; anything longer suggests the BDR-to-AE handoff is broken or white space isn’t being identified early enough.
Who should own expansion white space in a split RevOps model? The AE should own the expansion pipeline, with the BDR feeding qualified leads from net-new prospecting. But the RevOps team must own the data design—setting up HubSpot automation to alert the AE when a customer hits a usage threshold (e.g., 80% of license capacity), not leaving it to chance.
What is the first step to fix this without a big vendor tool? Pilot a single segment of accounts (e.g., customers with 12+ months tenure and no recent deal). Create three custom HubSpot properties: "Expansion Signal Type," "Signal Date," and "Owner Action." Automate a weekly report to the AE, then measure how many signals convert to pipeline within 30 days. Most teams see a 15-25% improvement in pipeline from this alone.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.