The Account Whitespace Map: One Logo to Every Buying Center

You already sell to one team inside a customer. This guide turns that single logo into a ranked list of every other department, business unit, and subsidiary that could buy, with a named decision-maker in each. It is written for founders selling their own product, account executives, SDR leads, and partnerships teams who want to build the expansion map by hand rather than wait for a tool to surface it.

Most sales guides map the committee for one deal or build net-new lists from scratch. Neither turns an existing account into a full internal expansion map. This is a search-first procedure: reconstruct the customer's org from public and account evidence, score the untapped cells, and resolve a real person in every unit you do not yet touch.

Why a search-first map beats the CRM view

The CRM shows you where you already are. Account whitespace is about where you are not, and the CRM is silent there by definition. A search-first map reconstructs the whole customer from outside evidence, then subtracts what you own, so the untapped units appear as gaps rather than staying invisible.

The reason this matters is structural. Legal filings systematically under-count buying centers. SEC Form 10-K Exhibit 21 is required and lists a registrant's subsidiaries, their jurisdictions, and their trading names, but names can be omitted where, considered in aggregate as a single subsidiary, they would not constitute a significant subsidiary. Disclosure rules optimize for materiality to investors, not for sales coverage, so the exact units that disappear are often the small, fast-growing ones that hire in clusters and hold their own budgets.

That is the whole argument for building the map from profiles rather than documents alone. Filings give you the legal skeleton. Public professional profiles reveal the operating departments and geographies the skeleton hides.

Unit choice, not just contact count, drives the size of the prize. A single purchase already spans a whole committee. A full customer spans many committees, one per untapped unit, and some units are simply larger targets than others.

What each public source proves, and where it lies

Two source layers matter: the legal-entity layer and the operating-org layer. The legal layer tells you who owns whom; the operating layer tells you who actually buys. Confusing the two is the first mistake in this job.

For a US public company, Exhibit 21 is the fastest legal skeleton available: it lists subsidiaries, jurisdictions, and trading names in one filing. For private and non-US entities, OpenCorporates plus GLEIF LEI data answers who owns whom, including verified parent and subsidiary relationships, alongside foundational company data like current status, named directors, and industry codes. The OpenCorporates Relationships File encodes control statements showing declared ownership or voting rights, subsidiaries as parent-child links, branches as local presences tied to a head office, and share parcels for partial ownership. GLEIF publishes the OpenCorporates-to-LEI relationship files free, updated bi-weekly in CSV.

Here is what each layer proves and how it misleads.

None of these proves a buying center on its own. A subsidiary may buy through the parent's central procurement, or independently, and the filing cannot tell you which. Legal ownership is not the same as operational budget authority. That distinction becomes a scoring rule later: before ranking a unit, confirm a real budget owner exists in it.

The map, start to finish

The procedure runs in eight stages, from legal skeleton to standing re-check. It front-loads reconstruction so that by the time you talk to the customer, you already know which units exist and which are untapped. The total analyst and owner effort is roughly one to two working days per account, most of it in steps two, four, and six.

There is one legitimate order disagreement worth naming. Some teams run the QBR before the signal work, surfacing new units live from the customer in the room. That works, but it makes you dependent on what your one contact happens to know. The search-first method here front-loads reconstruction so you walk into the QBR already holding the map, and use the meeting to confirm and prioritize rather than discover.

Scoring the untapped cells

Score each untapped cell on three inputs, computed separately: whitespace, relationship depth, and share of wallet. Whitespace shows what to sell, relationship depth shows where you are exposed or can multi-thread, and share of wallet shows where the real budget room is. The three answer different questions, and collapsing them into one gut-feel score is how good units get skipped.

Whitespace is a product-by-unit grid: for each cell, mark it owned, adjacent, or untapped. Relationship depth counts how many engaged contacts you already have inside that unit, which doubles as your exposure read. Share of wallet is the one that must be sized, not guessed. Compute it against a sized TAM using a per-head or per-seat basis. One worked example puts a unit's TAM at 300,000 dollars from 500 dollars per each of 600 employees, against a current 250,000 dollar contract, giving 83 percent wallet share. A high wallet share means little room left; a low share on a large unit is the real prize.

Buying-group size feeds the sizing, because each untapped unit carries its own committee. Use published ranges rather than a single number.

Read this table as a planning input, not a target. If a typical committee for your deal size is around 10 people across up to four functions, then a unit you enter with a single contact is understaffed against the reality of how the decision gets made.

A whitespace dollar figure with no per-head or per-seat basis is not an estimate, it is a wish.

Country changes the resolution difficulty, not just the market size. In Refolk's index, the US procurement pool is roughly 1.94x the UK pool, so a "find the procurement lead" step that is easy at the US parent is materially thinner at a UK subsidiary. Budget the extra research time where the pool is shallower.

Resolving a named person in every unit

No unit stays on the list with a title but no name. The score tells you which cells are worth pursuing; this stage makes them actionable by attaching a real economic buyer and a likely champion to each. Without a name, a whitespace cell is a slide, not a pipeline.

There is no published step-by-step standard for naming the person, but the sequencing is documented and the resolution is a search problem. Build the champion first, then expand to the buying committee around the third touchpoint, because leading with executives too early drops win rates. Aim for functional coverage across the committee, not just contact coverage: covering finance, operations, and the end user beats stacking three names in one function.

This is the stage where reconstruction pays off. You already know the unit exists and roughly how large it is; now you need the people in it. Refolk resolves this by searching public professional profiles for the exact role inside the exact unit and geography, so a UK subsidiary with a thin procurement pool gets the same treatment as the US parent.

When you resolve names, sanity-check against the shape of the pool. US procurement leaders concentrate in the San Francisco Bay Area in Refolk's index, and named employers include Caterpillar Inc., Atkore, and Credit Karma. If a unit you expect to be staffed returns nothing, that is itself a signal: either the function is centralized elsewhere, or the unit is smaller than the filing implied.

Timing the approach with a why-now signal

Every unit at the top of the ranked list needs a dated reason to approach now, or the outreach reads as a cold pitch to someone you technically already do business with. The strongest triggers are hiring clusters, leadership changes, funding, and expansion events, and they only count if they fall inside the buy window.

Read hiring on velocity against baseline, never on raw count. A 30 to 40% jump in a department's hiring over 60 days signals a company about to scale, and multiple roles in the same department posted within 30 days suggest rapid scaling. The strongest version is relative: a company that typically has 20 open roles but suddenly posts 50 is exhibiting a hiring surge, a far stronger signal than steady-state recruiting. Fifty open roles at a 50,000-person firm is noise; the same fifty at a unit that usually posts five is a flare. The buy window between a job posting and a purchase decision is roughly 60 to 120 days, and LinkedIn headcount lags actual hiring by 30 to 60 days, so always pair a headcount read with fresh postings.

The top-right quadrant, large whitespace with a fresh signal inside the window, is where the effort goes first. A large unit with no live trigger is worth a champion-building play now so you are ready when the trigger lands.

How this map goes wrong

The failure modes here are consistent and each has a concrete check. Most of them come from treating a proxy as the real thing: a legal entity as a buying center, a raw count as a signal, or a single name as coverage.

Two of these deserve extra weight. The first is treating a legal entity as a buying center. A filings-only map lists entities that may all buy through one central procurement function, which inflates your unit count and wastes outreach on units with no local budget. Confirm the budget owner before the unit earns a rank.

The second is single-threading the newly opened unit. This is the most common and most expensive mistake in the whole job, because it repeats the exact pattern that keeps roughly 70% of opportunities at one CRM contact and win rates at 5%. Every unit you decide to pursue needs an economic buyer and a champion before you count it as opened.

One more trap sits in sequencing. Leading with the C-suite before you have a champion drops win rates, so enforce champion-first order even when an executive name is the easiest one to find. The easy name is rarely the right first touch.

Keeping the map current

The re-check cadence is the part that compounds. A one-time map is a snapshot; a refreshed one catches new units while their buy windows are still open. Wallet estimates age and plays go stale, and median B2B win rates already fell from 23% to 19% even as buying groups grew, so the teams that refresh on a fixed clock hold an advantage that a single deep map cannot match.

Set a tiered rhythm. Quarterly for strategic accounts, semi-annual or annual for smaller ones, and a monthly check-in on top of the quarterly review for strategic accounts in a high-stakes rollout phase. Refresh whitespace estimates on the same clock, and incorporate seasonality and contract cycles so you are ready before renewals, not after. Because the buy window after a hiring cluster is only 60 to 120 days, a quarterly re-scan is the loosest cadence that still catches most triggers in time.

Treat the finished map as a living document with a next review date on it. The first pass reconstructs the org; every pass after that is cheaper, because you are diffing against what you already built. Re-run the profile searches for your top units each quarter, watch for new VPs and directors who joined a division in the last 90 days, and re-score any cell where the hiring velocity or leadership has changed. The map that stays current is the one that keeps turning a single logo into new pipeline long after the first deal closed.