Enterprise expansion: treat each business unit as an account

A new business unit is a new buying group

A second business unit of a customer is a new sale to a new buying group. It has its own budget owner and its own timing, and only some of its seats carry over from the first deal. Selling more to the unit that already bought is a different job, an upsell. Both count as account-based expansion: the account-based method, applied to customers you already have.

The group you meet there is large, and it spreads across departments. Forrester counts 13 internal stakeholders and 9 external influencers in a typical buying decision.^↗ In Forrester’s 2025 Buyers’ Journey Survey, 73% of purchases involved 3 or more departments.^↗ In 6sense’s research, about 40% of buyers joined their buying group from outside the department that will use the product.^↗

So a new unit’s buying group has 2 kinds of seat. Unit seats sit inside the unit: its head, the budget owner, a champion, the lead user and whoever evaluates the product technically. Shared seats sit in group functions such as procurement, IT security and legal, which may have approved you in the first deal. Procurement professionals are decision-makers in 53% of business buying cycles.^↗ A shared seat that already knows you is worth marking on the map.

The cycle stays long. Buyers in 6sense’s 2025 study reported an average buying cycle of 10.1 months, for a median purchase of $200–300k.^↗ An introduction from the first unit won’t move the new unit’s budget year. It can make you known before that unit starts looking.

Treat each business unit as its own target account

We think the unit is the account to plan, score and report on, while the logo holds the contract and the relationship. Budgets and decisions sit with units, so that is where we want the plan to point. Our reasons:

• Coverage on the logo hides empty units. A customer with many engaged contacts looks multi-threaded, even if all of them work in the unit that already bought. A plan that can’t see an empty unit won’t fill it.
• Fit and signals belong to the unit. A unit may be hiring for the problem you solve while its sister unit has just signed with a competitor. A single score for the whole logo averages them into a number nobody can act on.
• Multi-threading has to be designed in. In our view, waiting for the champion to introduce you around leaves expansion to chance. The plan should name the next empty seat, who introduces you and by when.
• Progress needs a baseline per unit. Count engaged seats per unit before you start, then every month. Without that first count, almost any rise in contacts can be presented as progress.

We don’t say every seat in every unit has to be engaged, only the seats that matter to that unit’s decision. And not every unit deserves a plan: some will score too low on fit to be worth the work.

Map a unit’s seats, then fill the next empty one

Write down the seats that decide for the unit, find a warm path to each, and engage them one at a time, starting with the seat nearest the budget. Keep the first map short: our method starts with 3–5 required roles for each account tier.^↗ A long list of seats nobody fills tells you less than a short one you do.

First score the units that haven’t bought, each on its own fit and signals: its budget, its hiring, its projects and the tools it runs today. Weight them from your won and lost deals, then map the unit that scores highest.

Warm paths are what the first unit gives you. In 6sense’s 2025 study, 94% of buying groups ranked their shortlist in order of preference before engaging with sellers.^↗ A unit that hears about you from a sister unit can put you on that list early. For each empty seat, write down who already knows that person: the champion in the unit that bought, that unit’s head, or an executive on your side. Ask for a single introduction at a time, to a named person, tied to a result the first unit measured. A review of that result, with a guest from the target unit, makes an easy first meeting.

That result is also the signal to start. Until the first unit has one, an introduction has no reason behind it.

Aim the first introduction at the budget owner. Across 655,000 opportunities, win rates were 55% higher when decision-makers were involved early.^↗ On deals over $50k, multi-threading lifts win rates by 130% on average.^↗

Report engaged seats per unit, not contacts per logo

The expansion report should show, for each target unit, how many of its required seats are engaged, against the count before the programme began. We measure coverage as engaged roles ÷ required roles, and count roles rather than contacts.^↗ We define engaged up front, for example as a two-way activity in the last 90 days.^↗

A fictional example shows the difference. An industrial group bought from you through its rail parts unit. The CRM holds the group as a single account with 31 contacts, 12 of them engaged, which reads as well covered.^↗ Split by unit, 9 of those 12 work in the unit that already bought.^↗ The energy systems unit has 1 of its 5 seats engaged, and the service unit none.^↗

In the example, the next move is the energy systems unit’s budget owner, introduced by the head of the rail parts unit. A report on the whole logo would not have shown it.

Each month, report per target unit: seat coverage against the baseline, the next empty seat and its owner, introductions asked for and made, and expansion pipeline. Keep the totals for the whole logo for renewal reviews.

Give each unit an account and each contact a role

Unit-level reporting needs an account for each business unit, linked to the group. Each contact then sits on the account of the unit they work in, with a role. Without that, the CRM can count contacts per logo but not engaged seats per unit. The AI answers to this question mention CRM structure but don’t say how to build it. We opened 6 of the 7 pages they cite: none explains how to set up units as accounts or how to tie a contact to its unit.^↗

Salesforce and HubSpot can both hold the structure:

• Salesforce. Record a Parent Account on each unit’s account and Salesforce builds the hierarchy. Each contact has a single direct account, which should be their unit. Once an administrator enables Contacts to Multiple Accounts, you can relate a person to other units as well, with a Roles field on each relationship.^↗
• HubSpot. Associate each unit’s company with the group as parent and child companies; each child company has a single parent.^↗ Association labels, on Professional or Enterprise subscriptions, can carry roles such as budget owner or champion.^↗ You can create up to 50 labels per object pair and filter segments, workflows and custom reports by them.^↗

Work through the clean-up in that order. Merged duplicates stop contacts landing on the wrong unit. Roles added before the unit accounts exist end up on the logo again. It’s the same rule as for CRM clean-up before lead scoring: fix the fields the report reads first.

RevOps or ABM agency: who builds the expansion programme?

You need both kinds of work, so hire a partner that does both in your own CRM, or give the whole brief to a single owner and split the jobs. The clean-up, the unit accounts, the roles and the coverage report are RevOps work. Scoring the units, mapping their seats, planning the introductions and writing for each unit are ABM work.

Each half falls short without the other. Unit records with no plays behind them don’t open a unit, and plays without unit records can’t be measured per unit.

Inside your company, the account owner for that customer should own the plan, with RevOps keeping the records and marketing supplying the content. Whoever you hire, ask 4 questions before you sign:

• Will you build it in our CRM, in our name, and document it?
• Will you record engaged seats per unit before the work starts?
• Do you count engaged roles or contacts?
• Who keeps the unit records and roles current after you leave?