Your list includes a clinic network with 40 locations, a freight carrier with branches in six states, or a retailer with distribution centers all over the map. Your SDR asks: do I call the VP of Operations at headquarters or the manager at the Dallas branch? The wrong answer costs you months. Going in through a branch when purchasing is centralized gets you friendly meetings that never turn into contracts. Going in through HQ when the decision is local gets you silence, because nobody at corporate feels the pain you solve.
There's no single rule. There is a way to figure out which door opens fastest for each account.
First, figure out where the decision lives
Before you build the cadence, answer three questions about the account:
- Who signs the contract? Centralized procurement, regional leadership, or a location manager with their own budget.
- Who feels the pain? Often it's local operations: the branch missing deliveries, the clinic with empty appointment slots, the field team without the right tools.
- Who uses it day to day? In distributed companies, the user and the buyer are rarely the same person.
Public signals help. Procurement openings posted only at HQ point to centralization; postings for "location manager with P&L ownership" suggest local budget. News about system standardization, recent mergers, or a new CEO tends to pull decisions up to headquarters.
When to go in through headquarters
HQ is the right door when your product requires integration with corporate systems (ERP, security, data), when the deal size exceeds any single location's spending authority, or when the value lies precisely in standardizing across locations.
How to approach it
At corporate, nobody wants to hear about one location's isolated problem. Talk about variance across locations, consolidated visibility, and the cost of running different processes. A message that tends to work looks like this: "Multi-location companies usually see a big performance gap between their best and worst sites. Can you see that in one place today?"
The risk: HQ is more crowded with vendors, has longer cycles, and may ask for proof before bringing other teams in. Be ready to propose a pilot at two or three locations.
When to go in through the local branch
The branch makes sense when the initial deal fits the local budget, when the pain is operational and immediate, and when the company has a culture of regional autonomy (common in franchises, healthcare networks, and logistics).
How to approach it
Be concrete and local. The location manager wants to fix this week's problem, not debate corporate strategy. Phone and text or WhatsApp work better here than at the executive level, because these people live in operations and barely read email.
The risk: you win one location and expansion stalls because HQ finds out about the tool later and decides to block it. So from the very first meeting, ask: "If this works here, who needs to sign off to roll it out to other locations?"
What works best: both plays, coordinated
In large accounts, the best results usually come from working both levels at once, with different messages and shared context. A practical sequence:
- Map 4 to 8 contacts per account: one or two at HQ (operations, IT, finance) and two to four at the highest-volume locations.
- Start with the branches showing the most visible pain: new locations, expanding ones, or those with poor reviews.
- Use what you hear locally to approach HQ: "I've been talking with some of your location managers and a pattern came up around X." That changes the tone of the executive conversation.
- Never throw the local manager under the bus: talk about patterns, not about who complained.
- Log everything at the account level, not the contact level: the SDR talking to HQ needs to know what the branch said yesterday.
Pro tip: create a CRM field called "decision model" with three options: centralized, regional, and local. Fill it in after the first two conversations and adjust the cadence for the whole account accordingly. Within a few weeks you'll have a pattern by segment and stop guessing.
Mistakes that kill prospecting in distributed accounts
- Two people on your team hitting the same account without knowing it: the prospect notices, and your credibility drops.
- Same message for HQ and branch: the pain is different, and so is the vocabulary.
- Counting a meeting with a manager who has no buying authority as a qualified opportunity: that's discovery, not pipeline.
- Giving up on the account after HQ goes quiet: corporate ignores you until it sees internal traction. The branch is often what creates that traction.
How to tell if the strategy is working
Instead of tracking only meetings per contact, track by account: how many levels are engaged, how many locations have talked to you, and whether you have a sponsor at HQ yet. An account with three local conversations and none at corporate is moving slower than it looks. At Nord, programs in sectors like logistics and healthcare, such as one for a logistics company in Spain booking 32 meetings a month, rely on exactly this account-level view rather than on individual leads.
Next steps
Take the ten largest multi-location accounts on your list, classify each one's likely decision model, and choose your initial point of entry. Build two message versions, one for HQ and one for the location, and review results in 30 days. If you don't have the bandwidth to coordinate multiple plays per account, consider a dedicated sales development team, in-house or outsourced like Nord's, to run that cadence consistently.





