Headquarters Is Not the Job Site: Route B2B Intent Across Branches

October 30, 2026•11 min read

For a B2B company that serves specific locations, an account-level intent signal is only the beginning of the routing decision. A large organization may have a headquarters, several operating sites, a shared procurement team, and local managers with different needs. Before assigning the signal to a salesperson, determine which organizational level the evidence actually describes and which location your company can serve. Otherwise, relevant demand can reach the wrong territory or become an apparent targeting failure.

This article proposes a practical account-and-location framework for custom buyer intent. It contains hypothetical examples rather than measured Cortex customer findings. The framework is especially useful for regional service providers, industrial suppliers, commercial contractors, and companies selling into organizations with multiple branches. The objective is not to claim perfect visibility into a buying committee. It is to preserve the distinction between what the evidence identifies and what your team still needs to learn before acting.

Start with the entity the source actually resolves

Ask whether the signal is associated with a legal company, a brand, a domain, a physical site, a household, or another unit. These are different entities. A domain can represent many branches. A brand can span multiple legal businesses. A billing address can differ from the location where a service is needed. If the provider can resolve only the parent organization, keep that limitation visible. Do not create branch-level certainty by attaching the nearest address from a separate directory.

The distinction affects the next action. Parent-level evidence might justify researching the organization or identifying an appropriate business contact through an authorized process. Site-level evidence may support a more geographically specific review if its basis is reliable. Neither automatically establishes the identity of the person who performed the research. A clear entity label helps a salesperson describe the opportunity honestly and avoid making claims that the source cannot support. It also improves the quality of feedback returned later.

Model the commercial relationship you actually serve

Draw a simple map of the customer structure: parent organization, operating company, site, and opportunity. Include only levels relevant to your sales process. A small business may need only account and service location. A distributor serving a national customer may need a more detailed hierarchy. The map should answer who buys, who uses the product, who approves payment, and where delivery occurs. Those roles can belong to different parts of the same organization.

For a hypothetical maintenance supplier, headquarters might negotiate an approved-vendor agreement while each plant places orders. Research associated with headquarters could concern the agreement, while a local plant’s activity could concern an immediate replacement. The supplier should not collapse those needs into one sales task. A parent relationship can be valuable context without replacing the local purchase details. Design the intent workflow around this actual commercial structure rather than assuming that every account has one address and one decision maker.

Keep geography in two separate fields

Separate the location associated with the observed signal from the location where your company would deliver the service. They may be identical, but that should be established rather than assumed. A purchasing manager can research from home or a central office on behalf of another site. A company can also operate in several regions under one domain. Routing only by the signal’s apparent location may send a legitimate opportunity to the wrong team or exclude it prematurely.

The service-location field should be confirmed through an appropriate business record or conversation when the source does not establish it. Until then, label it unresolved. A regional provider can use a preliminary research route for unresolved accounts rather than assigning them directly to a local salesperson. This approach preserves useful demand without pretending the location is known. It also gives operations a clear point at which to confirm capacity, travel boundaries, and delivery requirements before a proposal is prepared.

Define ownership before the first duplicated contact

Organizations with multiple branches can enter several territory queues at once. Decide how ownership works when the same parent appears in different lists. The rule might depend on confirmed service location, an existing account owner, a national agreement, or a coordinating representative. Document the rule and the exception process. Without one, separate teams may contact related people with conflicting offers and then argue over which channel deserves credit for the eventual sale.

Ownership should not erase the evidence contributed by other teams. Keep a shared account history where permitted, with distinct site and opportunity records. A representative who discovers a relevant branch can pass it to the correct owner without losing the context of the original signal. This is an operational design question, not a guarantee about any specific integration. During a Cortex consultation, ask how the proposed workflow would fit the CRM and territory system you actually use.

Resolve duplicates without merging different opportunities

Duplicate management should distinguish repeated records of the same entity from legitimate records of related entities. Two spellings of one company name may be duplicates. Two plants owned by the same parent may not be. A merger, rebrand, or domain change can also create ambiguity. Keep stable identifiers where available and retain the evidence used for a merge. Name similarity alone is rarely enough to establish that two records should share every outcome and activity history.

Before merging, ask what information would be lost. If one site has an open quote and another has declined service, combining them into a single account status can make the feedback misleading. The solution may be to link both sites to a parent while preserving their separate opportunities. A useful account model supports both aggregation and distinction. It lets a manager see the overall relationship without forcing every local event to become a statement about the entire organization.

Avoid spreading one site’s outcome across the whole parent

A successful sale at one location does not prove that every branch is equally suitable. A loss at one location does not prove that the parent is a poor fit. The reason may be local: capacity, equipment, timing, budget, or a site-specific competitor. Return the outcome at the level where it occurred, with the relevant offer and date. If the outcome concerns a national agreement, label that broader scope explicitly rather than inferring it from the customer’s name.

This matters for customer-specific learning. A model trained on loosely aggregated outcomes may learn that a parent is universally positive or negative when the real pattern is more conditional. You do not need to assume a particular modeling architecture to recognize the data issue. Preserve the hierarchy and ask the provider which levels the implementation can use. If the current system supports only account-level labels, narrow the use case and document what nuance the model cannot yet represent.

Build a location-confirmation conversation

The first conversation should resolve what the data cannot. A salesperson can ask which site needs support, whether the purchase is local or centrally managed, and who should be involved in defining the requirements. Those are normal commercial questions. There is no need to imply knowledge of an individual’s browsing behavior. The purpose of the intent signal is to help prioritize a relevant conversation, not to replace the buyer’s explanation of the problem.

For a hypothetical facilities contractor, the outreach might focus on whether the organization is evaluating service coverage for one building or several. The answer changes scope, staffing, pricing, and ownership. Record it as volunteered business context. If the contact redirects the conversation to another site, preserve the original route and the correction. That history can later reveal whether your source map is useful at the parent level but needs an additional step before local routing becomes reliable.

Measure routing quality with the right unit

Count accounts, sites, and opportunities separately. If one parent produces several site opportunities, a report should not casually treat each site as an independent new account. If the program’s purpose is to identify serviceable locations, site-level outcomes may be appropriate. If its purpose is to establish national relationships, parent-level outcomes may matter more. State the unit before calculating a rate. Otherwise, an apparent improvement may come from changing the level of counting rather than improving the process.

Useful process measures include the share of routed records with confirmed service locations, the number reassigned between territories, and the time required to resolve ownership. These describe the handoff and should not be mislabeled as sales performance. Later outcome measures can connect the original route to qualified opportunities and completed sales. Include unresolved cases and observation windows. Where several sites belong to one parent, acknowledge their relationship when assessing uncertainty rather than assuming every record supplies wholly independent evidence.

Distinguish coverage gaps from territory weakness

A low volume of observed intent in one territory can mean several things. Demand may be lower, source coverage may be thinner, identity resolution may be less effective, or the territory’s accounts may use different research channels. Do not reduce sales staffing or dismiss a region based on a raw signal count alone. Compare what the provider can actually observe and consider other business evidence. A territory should not appear unattractive merely because the measurement system sees less of it.

Ask for segment-specific coverage information when available, and state when it is not. Compare territories with similar definitions and time periods. If a provider changes its matching process, record the effective date before interpreting a geographic trend. Custom buyer intent should reflect the geography your business serves, but customization does not create observations where none are available. A useful implementation explains those limits and helps the customer choose decisions that the existing evidence can support.

Handle acquisitions and organizational changes

Company hierarchies change. A site may be sold, a parent may acquire a competitor, or a brand may move under another legal entity. Record effective dates for these changes rather than rewriting every historical record as if the new structure always existed. Sales actions taken before an acquisition should remain interpretable under the structure known at that time. A current account view and a historical evaluation can both be valid while using different organizational snapshots.

Design a correction process for uncertain relationships. The responsible owner should be able to mark a link as provisional, confirmed, or withdrawn and explain the basis. Downstream queues should reflect material corrections. If a site moves outside your serviceable customer group, decide how open opportunities are reviewed rather than deleting them automatically. The objective is a controlled handoff between data maintenance and commercial judgment. A model score should not silently settle contractual or ownership questions it was never designed to answer.

Make the Cortex discussion concrete

Cortex’s supplied brief emphasizes a customer-specific model shaped by relevant sources and feedback. For a multi-location business, explain the account hierarchy and ask what the proposed implementation can resolve. Specify whether success means a qualified site opportunity, a parent-level agreement, or another defined outcome. Confirm which websites, topics, and sources are relevant and available. A model can become more specific to your niche only if the feedback preserves the distinctions that make the niche commercially meaningful.

Customers outside the original list can contribute useful learning when included appropriately, but their relationships should be mapped with the same care. A referral sale at one branch should not become credited list acquisition at the parent level. Proprietary learning refers to how your business’s evidence shapes prioritization; it does not imply ownership of an entire corporate network or certainty about every employee’s intentions. Keeping those boundaries clear supports both responsible sales use and credible future research.

Review four difficult records before scaling

Before a broader rollout, inspect one parent with several sites, one unresolved service location, one duplicate candidate, and one opportunity that moved between territories. Walk through the expected route and feedback for each. Ask whether the receiving salesperson can understand the evidence and the remaining uncertainty. Check whether the eventual outcome would be attached to the correct entity. These examples can reveal structural problems that a large volume of straightforward records would hide.

If the workflow fails a case, fix the relevant field or rule before expanding the queue. A manual clarification step may be acceptable for a small pilot. Record its workload so that the business can decide whether it scales. Do not assume that adding more intent sources will solve an ownership problem. Better evidence helps only when the organization can route it to an appropriate action. Clear entity structure often makes that action possible.

Bring the opportunity to the right place

Account-level buyer intent can be valuable even when it does not resolve a specific branch. Its value depends on using it at the right level, preserving uncertainty, and confirming the details that matter for service delivery. A thoughtful account-and-location map helps avoid duplicate outreach, misleading feedback, and territory comparisons built on incompatible units. It gives customer-specific learning a more accurate description of how your business actually wins and serves customers.

To review that structure for your market, book a Cortex consultation. Bring a sanitized example of your parent, site, and opportunity records, along with territory rules and service constraints. A later benchmark would need dated entity mappings, routing histories, and mature outcomes. Until those records are available, the framework here remains a proposed method. Its immediate value is helping the next relevant signal reach the right conversation without claiming more precision than the evidence provides.

Back to Blog