White Space Analysis
The cheapest pipeline is your installed base. White space is the systematic discipline of finding it before someone else sells into it.
is unsold capacity inside accounts you already serve: business units you have not entered, geographies not deployed, products in your portfolio not yet adopted, use cases adjacent to existing deployment. White Space Analysis is the structured process mapping current footprint against potential footprint and prioritizing the gap.
Where white space lives
- Cross-BU — adjacent business units inside the same legal entity
- Geographic — regions or countries not yet deployed
- Product / SKU — additional modules, tiers, or adjacent products in your portfolio
- Use case — extending the current capability to a new problem the same team owns
- Persona — selling to an additional buyer (e.g., from IT into Operations)
- Platform consolidation — replacing point solutions inside the account
Mapping current vs potential footprint
Build a matrix per Tier 1/2 account:
- Rows — customer's business units, geographies, and core processes
- Columns — your portfolio (products, modules, services)
- Cells — current state (deployed / piloting / evaluated-and-rejected / never-discussed)
Every 'never-discussed' cell is potential . Every 'evaluated-and-rejected' cell is intelligence about why a prior attempt failed — re-pursue only if the underlying conditions changed.
Uncovering hidden opportunity
Sources to mine:
- Customer's org chart and 10-K — business units, geographies, segments not yet in your
- conversations — 'Who else has this same problem?'
- Product usage data — heavy users in BU you have not formally engaged signal latent demand
- M&A activity — newly acquired entities are net-new
- Leadership changes — new executives often bring willingness to revisit prior 'no' decisions
- Customer success signals — support tickets, feature requests, and data reveal unmet need
Prioritizing white space plays
Score each candidate play on three dimensions:
- Customer value — how clearly does this solve a problem the customer cares about?
- Internal sellability — how easily can the existing advocate to a peer?
- Revenue potential — realistic 12-month
The winning plays usually combine a warm internal path (-led intro) with a clearly named problem in the target BU. Cold expansion into an unrelated BU rarely closes inside a quarter.
Tactical patterns that compound
- — prove value in one team, then ride internal advocacy to the next
- Adjacent BU intro — warm-introduces a peer with a one-page summary you co-author
- Geographic rollout — succeed at HQ, then regions with a repeatable
- New use case — extend the current capability to an adjacent problem the same team owns (low friction, low risk)
- Platform consolidation — bundle into a that replaces multiple point solutions
Reinforce every play with data from the existing footprint — expansion without proven value erodes reference credibility.
Real-world example
An managing a $1.2M account ran a structured exercise. Mapping revealed three never-discussed BUs (two acquired in the last 18 months), one geography (APAC), and two adjacent products. The warm-introduced the head one acquired BU. That intro produced an $800K within 90 days, which then opened a peer intro to the second acquired BU. Twelve months later the account had grown to $3.4M ARR. The original deal pipeline had not changed — the white space discipline did.