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 #428) 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.
<!--pillar-weave-->
Related on PULSE
- [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/q10106)
- [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 Three Hidden Data Silos That Kill Expansion Visibility
Most vendors fail at expansion white space because they treat HubSpot as a single source of truth when it actually operates as three disconnected data layers. The BDR team works in a prospecting view, the AE works in a pipeline view, and the RevOps team works in a reporting view — and none of them natively connect expansion signals across these layers. Here is exactly where the breakdown happens and how to fix it.
Layer 1: The Contact-Level Blind Spot
HubSpot’s default object model encourages teams to think of contacts as individual records, but expansion white space lives in the relationships between contacts. When a BDR books a meeting with a contact at an existing account, most HubSpot instances have no automated way to flag that this contact belongs to a customer account with an active AE. The BDR sees a qualified lead; the AE never sees the cross-object trigger.
The fix: Create a custom “Account Relationship” property on the contact object that auto-populates based on the associated company’s lifecycle stage. Use a workflow that checks: if associated company lifecycle stage = “Customer” AND contact lifecycle stage ≠ “Customer”, then set a property called “Expansion Potential” to “Yes — Active Customer.” This single field, when added to the BDR’s meeting booking form and the AE’s pipeline view, creates the first bridge between silos.
Layer 2: The Deal-to-Account Disconnect
Standard HubSpot reporting shows deals in a pipeline, but expansion white space requires seeing deals in the context of the entire account relationship. Most vendors build reports that show “Deals by Company” without factoring in whether that company already has closed-won revenue, active support tickets, or a renewal date approaching. This means AEs chase new business at accounts that are about to churn, while BDRs cold-call into accounts where the AE is already negotiating an expansion.
The fix: Build a custom “Account Health Score” calculated property using a formula that weights three factors: days since last closed-won deal (negative weight), number of active support tickets (negative weight), and number of open expansion deals (positive weight). Display this score as a column in both the BDR’s prospecting list view and the AE’s pipeline view. When the score drops below 50, automatically suppress the account from BDR prospecting lists and flag it for AE retention outreach instead.
Layer 3: The Activity Timeline Gap
HubSpot tracks activities per object, but expansion white space requires tracking activity patterns across objects. A BDR might send 50 emails to a contact at a customer account, but the AE only sees the contact’s individual activity timeline — not the pattern of engagement that signals expansion intent. Most vendors miss this because they build reports on object-level metrics (emails sent to contact X) instead of pattern-level metrics (account-wide engagement velocity).
The fix: Create a custom “Engagement Velocity” dashboard that shows week-over-week change in total email opens, meeting requests, and website visits across all contacts at a customer account. Set a threshold: when engagement velocity increases by 30% or more over a 14-day period, automatically create a high-priority task for the AE titled “Expansion Signal Detected — Review Account Activity.” This turns a data point into an actionable workflow.
Why Most Expansion Automation Fails at the Handoff Point
The most common mistake vendors make is automating the BDR-to-AE handoff based on meeting completion alone. In HubSpot, this typically means a workflow that changes the contact’s lifecycle stage from “Lead” to “Marketing Qualified Lead” (MQL) or “Sales Qualified Lead” (SQL) after a meeting is marked “Completed.” For expansion white space, this automation is actively harmful because it strips context from the handoff.
The Context Loss Problem
When a BDR books a meeting with a contact at a customer account, the meeting notes might include: “Contact mentioned they’re evaluating a new module for their team of 50.” Under a standard automation, that context stays in the meeting notes object. The AE receives a notification that says “New meeting completed with John Doe,” but has no automated way to see that this meeting is an expansion opportunity versus a support escalation or a referral request. The AE then wastes the first 10 minutes of the call rediscovering context the BDR already captured.
The fix: Build a custom “Handoff Summary” property on the deal object that concatenates three key fields from the meeting: “Expansion Signal Detected” (yes/no), “Product Interest” (multi-select picklist), and “Decision Maker Level” (individual contributor, manager, director, executive). Use a HubSpot workflow triggered by meeting completion that checks if the associated company is a customer. If yes, create a new deal with deal type = “Expansion” and auto-populate the Handoff Summary property. This gives the AE a structured expansion brief, not just a meeting notification.
The Timing Mismatch
Standard BDR-to-AE handoffs assume the AE is ready to take the meeting immediately. In expansion white space, the AE might be in the middle of a renewal negotiation with the same account’s procurement team, making the timing of the BDR’s meeting counterproductive. Most vendors don’t check for conflicting account activity before routing the handoff.
The fix: Add a “Conflict Check” step to your handoff workflow. Before routing the meeting to the AE, run a workflow that checks: does the associated company have an open renewal deal with a close date within 30 days? Does the AE have more than 3 active tasks for this account? If either condition is true, route the meeting to a “Expansion Queue” instead of the AE’s calendar, with an automated note: “Hold for account conflict resolution — review within 48 hours.” This prevents the AE from accidentally undermining their own renewal while trying to pursue expansion.
The Reporting Blindness
Most vendors report on handoff volume (how many meetings BDRs passed to AEs) but not handoff quality (how many of those meetings led to expansion pipeline). In HubSpot, this means the BDR is measured on meetings booked, and the AE is measured on deals closed, but nobody owns the gap between them for expansion accounts.
The fix: Create a custom “Handoff Conversion Rate” report that shows, for customer accounts only, the percentage of BDR-booked meetings that result in an expansion deal created within 14 days. Set a target of 40% or higher — if the rate drops below 30%, trigger a review of the handoff summary fields to identify where context is being lost. This single metric forces both teams to optimize for expansion outcomes, not just meeting volume.
The One Report That Changes Everything: Account-Level Expansion Velocity
Most RevOps teams build reports that show pipeline by deal stage or activity by contact. For expansion white space, these reports are useless because they don’t show the rate of change across an entire account. The one report that changes everything is a simple velocity chart that answers: “How fast is this account moving from ‘engaged’ to ‘expansion opportunity’?”
Building the Velocity Chart
In HubSpot’s custom report builder, create a report with the following parameters:
- X-axis: Date (weekly buckets, rolling 90 days)
- Y-axis: Count of unique contacts at customer accounts with engagement score above 50 (calculated from your custom engagement property)
- Series breakdown: By account tier (Enterprise, Mid-Market, SMB) or by product line
This single chart shows you, at a glance, whether your expansion efforts are gaining or losing momentum. When the line trends upward, your BDR and AE are successfully identifying expansion signals. When it flattens or drops, you have a process problem — either BDRs aren’t finding the right contacts, or AEs aren’t converting them.
The Pulse Metric: Expansion Velocity Score
From this chart, derive a single Pulse metric: the Expansion Velocity Score (EVS) . Calculate it as:
EVS = (Number of customer contacts with engagement score > 50 this week) / (Number of customer contacts with engagement score > 50 last week) * 100
An EVS above 100 means your expansion pipeline is growing. Below 100 means it’s shrinking. Report this number weekly to both the BDR and AE managers, along with the top 5 accounts where EVS increased the most and the top 5 where it decreased the most.
Why This Report Fixes the Vendor Blind Spot
Vendors get expansion white space wrong because they focus on static data — how many contacts, how many deals, how much revenue. This report focuses on velocity — how fast the expansion opportunity is developing. When you track velocity instead of volume, you catch problems early: a dropping EVS for a key account means the AE needs to intervene before the BDR’s work goes cold. A rising EVS for an account with no open expansion deal means the BDR found a signal the AE missed.
Implementation note: This report requires 4-6 weeks of historical data to establish a baseline. Don’t try to set targets in week one. Instead, run the report for 30 days, calculate the average EVS, then set a target of 10% above that average for the next 30 days. Adjust based on what the data tells you about your actual expansion velocity, not what you think it should be.
Sources
- HubSpot Knowledge Base — official documentation on CRM setup, deal stages, and automation features for RevOps teams.
- Harvard Business Review — articles on sales team structure, role specialization, and revenue operations strategy.
- Gartner — research reports on sales process optimization, territory design, and BDR-to-AE handoff best practices.
- Forrester — industry analysis on revenue operations frameworks, pipeline management, and sales productivity metrics.
- Revenue Operations Alliance — practitioner guides and case studies on scaling RevOps teams and split roles.
- Salesforce Blog — insights on sales tech stack configuration, data hygiene, and workflow automation for BDR/AE alignment.
FAQ
What is "expansion white space" in a BDR-to-AE split? Expansion white space refers to upsell or cross-sell opportunities within existing accounts that are not actively pursued. In a split model, BDRs typically focus on net-new leads while AEs manage relationships, but expansion often falls into a gap where neither role owns it explicitly.
Why do most vendors fail to track expansion white space in HubSpot? They rely on generic deal stages or pipeline views that don't separate expansion from new business. Without custom properties like "Expansion Opportunity Type" or "Account Health Score," the CRM can't distinguish cross-sell signals from routine renewals, leading to missed revenue.
How should a RevOps team design the audit phase for expansion? Start by exporting closed-won deals from the past 12–18 months and tagging any that involved upsells or cross-sells. Then map those to existing HubSpot fields—if you find fewer than 80% of expansion deals are labeled correctly, you need 3–5 new custom properties before moving to pilot.
What is the single most important metric to measure expansion success? Net Revenue Retention (NRR) at the account level, calculated monthly. A healthy BDR-to-AE split should see NRR above 100% from expansion alone, with at least 15–25% of accounts showing a logged expansion activity in the prior quarter.
Who should own the expansion process in a split RevOps team? The BDR team should own initial expansion qualification (e.g., identifying usage spikes or contract expirations), while AEs own closing. RevOps sets the handoff rules—typically a BDR creates a "Expansion Qualified Lead" in HubSpot, then an AE takes over within 48 hours.
How long does it take to implement a working expansion white space process? A realistic timeline is 6–10 weeks from audit to live pilot: 2 weeks for data audit, 2 weeks for field design and HubSpot configuration, 2 weeks for a pilot with one segment (e.g., accounts with 50+ users), then 2–4 weeks to automate reporting and refine handoffs.
Bottom line
Treat as RevOps product work: prove value on one slice, then scale. Polish can deepen this entry later.