How to Research Multi-Location Companies for Sales

A company with ten locations can represent one buying relationship, ten local relationships, or a combination of central and branch decisions. Your research structure needs room for that uncertainty.

Separate the parent account, branches, contacts, and purchasing relationships. Keep evidence for each location and mark unknown authority explicitly. Coordinate parent and territory ownership before contacting several branches.

The account-map example keeps uncertain ownership and category-specific purchasing questions visible.

Separate the relationships before collecting details

Distinguish the brand, parent organization, operating location, and person. They are related but not interchangeable. A franchise location may share branding while having different ownership; a branch may be centrally owned but handle some local decisions.

Record what the sources establish. If ownership is unclear, use an explicit Unknown value in a relationship field rather than forcing the location under a parent because the logo matches.

For a simple account, a parent table and a location table may be enough. Add contacts and activities when the work requires them.

Create stable IDs for the account structure

Use one parent ID for the confirmed account relationship and a distinct location ID for each site. Link contacts to the relevant parent or location according to their actual role.

IDs should not change when a name, address, or title changes. Keep the original source links so the relationship can be reviewed when the business reorganizes.

Do not use spreadsheet row position as an identifier. Sorting and filtering should not alter which location an activity belongs to.

Research the parent and the locations separately

At the parent level, review the company's public description, locations, relevant service lines, and any published supplier or contact information. At the location level, confirm address, function, service scope, and public contact route.

A corporate contact page may provide headquarters information without answering a branch-specific question. A local location page may explain operations without revealing purchasing authority.

Save the source that supports each important relationship. A generic homepage link alone may not explain why a location was assigned to a parent account or why a contact was linked to a branch.

Classify the role of each location

Determine whether the site is a headquarters, sales office, service branch, warehouse, showroom, or another type of operation when the source makes that clear. The role affects whether the location matters to your offer.

Do not infer function from the address or map image alone. If the business does not explain it, record the question and choose a suitable research or contact step.

For a fictional supplier, a service depot may be relevant while a corporate mailing address is not an operational target. Both can belong in the account structure, but they should not be treated as equivalent prospects.

Establish purchasing responsibility through evidence

Use a field such as Purchasing responsibility with values Confirmed central, Confirmed local, Mixed, and Unknown. Add a source or conversation note supporting any confirmed value.

A person's title does not necessarily answer who approves a supplier or controls a budget. Ask about the process and scope: which categories are decided locally, who approves new suppliers, and whether a central agreement applies.

Keep answers tied to the relevant category. A branch may buy routine supplies locally while major service contracts are handled centrally. One answer should not be generalized to every purchase.

Preserve shared domains without collapsing branches

A shared website is useful evidence of a relationship, but it is not a sufficient duplicate rule for location records. Keep the branch address, location URL, and Maps source where available.

Prospect describes support for separate Maps location records even when websites match. Review the exported rows and add your own parent relationships and purchasing notes in the working system.

Use the location-record structure and duplicate review before combining records. If a business has moved, distinguish relocation from the addition of a second active site.

Coordinate territory and account ownership

A parent account can span several territories. Decide who owns the parent relationship and who handles local research or service activity.

Record those roles explicitly. A branch rep may own the next operational action while an account lead coordinates commercial discussions. Unclear ownership can create duplicate contact and contradictory messages even when the underlying data is accurate.

Carry account-level restrictions and relevant history into branch work. A new location import should not bypass a decision already recorded for the wider account.

Map an account without assuming one buying process

Imagine Example Supply has two confirmed company-owned branches and a third similarly branded location whose ownership is unresolved. Keep those relationships separate:

Do not assign the central location to C001 merely because the branding matches. Also do not copy the north branch's service fit onto the south branch.

If a later conversation confirms central purchasing for the relevant category, record the source and category scope at the parent level. Link the branches to that process while preserving their operational differences. A central decision for parts does not automatically establish central authority for every service contract.

The completed map should show confirmed relationships, unresolved questions, and who will resolve each one. It does not need to look complete to be useful.

Hand off the account with its unresolved questions

A useful handoff includes the parent relationship, relevant locations, verified sources, known contacts, purchasing-process evidence, ownership, and next actions. Keep the unresolved questions visible rather than presenting the account map as complete.

For a large account, prioritize the locations that affect the immediate objective. You do not need to document every site in equal depth before asking a well-scoped question, but you should state which part of the account has been reviewed.

Use pre-call research to turn the structure into a focused conversation plan.

Maintain the relationships as the account changes

Update moves, closures, acquisitions, and role changes when they become relevant to active work. Preserve retired IDs and their replacement relationships so historical activities remain understandable.

If you move the structure into a CRM, confirm that the destination can represent the company and location relationships you need. A domain-based matching rule may behave differently from your branch-level spreadsheet. Use the CRM import guide before importing the full account set.

Related Questions

Does a shared logo prove locations have the same owner?

No. Shared branding can occur under different operating arrangements. Record the relationship supported by the source and leave ownership unknown when it is not established. Do not substitute brand similarity for a confirmed company relationship.

Should every location receive the same qualification score?

No. Service scope, territory relevance, and operational function may differ. Apply the relevant criteria to each location and keep parent-level facts separate from branch-specific evidence and open questions.

For geographic assignment, continue with territory planning. For the working data structure, see Excel list management.