Multi-Location Sales Guide: Running One Sales Operation Across Many Branches

Businesses selling from several locations fail in one of two opposite directions, and both are avoidable.

The first is fragmentation. Each branch develops its own process, its own definition of a qualified lead, its own way of recording things, and eventually its own spreadsheet. Head office cannot compare anything, cannot cover an absence, and cannot move a customer between locations without a phone call. Each branch is individually functional and the business as a whole is not.

The second is over-standardisation. Head office specifies everything, including things that genuinely differ between markets, and the branches quietly stop engaging. They enter the minimum required into the system and keep the real information somewhere else, which produces a database that looks complete and describes nothing.

The way through is a deliberate split: standardise the measurement, localise the method. A small number of things must be identical everywhere. Almost everything else should be local.

Pick a primary basis

Geography is the default and it works where customers expect local presence, where travel time is a real cost, or where regulation and language differ across your footprint. Specialisation works better where the deciding factor is expertise, and where a customer would rather deal with the right person at distance than a generalist nearby. Account size or complexity is a third basis, keeping larger customers with a team set up for them.

Most businesses use a primary basis plus documented exceptions. That is fine. What is not fine is undocumented exceptions, which are how a customer ends up being worked by two branches or by neither.

Write the exceptions down

The customer near the boundary who has always dealt with the other branch. The national account handled centrally. The industry a particular branch has specialist knowledge in. Each of these is legitimate and each becomes a dispute if it lives only in someone memory.

Revisit annually, not continuously

Territories should be stable, because a rep who expects their patch to change will not invest in it. Review once a year at planning, with visible criteria, and avoid moving accounts mid-period unless something has genuinely broken.

List every way a lead can arrive: your website, branch-specific pages, the main phone number, branch phone numbers, messaging apps, email, walk-ins, referrals, events, and any marketplace or partner channel. For each one, write the rule.

The rules that matter are the ambiguous cases, because the obvious ones handle themselves. What happens to a web enquiry that mentions no location? To a call to the main number outside one branch working hours? To a message that arrives on a Sunday? To a referral from a customer in one territory about a prospect in another?

Every answer must end with a named owner and a response timer. The failure this design prevents is the enquiry that two branches each assume the other has, which is not a people problem and cannot be solved by asking people to be more attentive.

Reassignment should be normal

Some leads will be routed wrongly. Make reassignment a one-click action with the history preserved, rather than a request to an administrator. Friction in reassignment produces leads that stay with the wrong owner because moving them is a nuisance.

Four standards. Everything else negotiable. When a branch asks for an exception to one of the four, the answer should almost always be no, and the reason should be explainable in one sentence: we cannot compare or cover without it.

Raw revenue comparison between branches is close to useless, because it mostly measures the market each was given and the leads each received. It is also corrosive, because branches know it is unfair and conclude that the numbers are political.

Compare rates, not totals

Conversion at each stage. Cycle time. Average deal size. Activity per person. Response time to a new enquiry. All of these are comparable across branches of different sizes, and all of them point at something a branch can change.

Compare within source

A branch working mostly inbound enquiries and a branch working mostly self-generated opportunities will show different conversion rates for reasons that have nothing to do with capability. Break comparison down by source, and compare inbound with inbound.

Look at the ratio of created to supplied

How much of each branch pipeline did they create themselves? This is one of the most revealing numbers in a multi-site business, because a branch that generates its own opportunities is doing something the others could learn, and a branch that only works what arrives is more fragile than its revenue suggests.

Show the comparison openly

Concealed comparisons breed more suspicion than open ones ever do. Publish the same view to every branch manager. It also creates the useful dynamic where a branch performing well on one measure is asked to explain how, which is the main way practice spreads.

Customers with sites in more than one of your territories are where multi-site businesses either look impressive or look chaotic, and the difference is a rule made in advance.

Name one relationship owner who holds the commercial relationship and the overall view. Local branches own delivery and day-to-day contact at their sites. Then settle credit before it arises: the local branch doing the work needs to see something for it, and the relationship owner needs to see something for coordinating. A split agreed in advance costs nothing. A split improvised after a large order always looks like a judgement about people.

Practically, this needs one customer record visible to all involved branches, with local site records beneath it, so nobody is calling a colleague to ask what happened last month.

A business runs four branches. Branch A produces the most revenue and is treated internally as the benchmark. Branch D produces the least and has been under pressure for two quarters.

Standardising stage definitions and required fields takes three weeks, mostly because branch C has been using a stage list of its own devising since before the current manager arrived. Once the definitions are common, the comparison becomes possible for the first time.

It shows something different from what everyone assumed. Branch D receives roughly a quarter of the inbound enquiries that branch A receives, because most marketing spend has historically been directed at branch A market. On conversion of inbound enquiries, branch D is the strongest of the four. On self-generated opportunities, branch D produces more than the other three combined, which is how it has been surviving on so few leads.

Branch A, meanwhile, converts inbound at the lowest rate and generates almost nothing itself. Its revenue advantage is entirely a lead supply advantage.

The decisions that follow are the opposite of what was planned. Marketing spend is rebalanced towards branch D territory. Branch D manager runs a session for the others on how they generate their own opportunities. Branch A gets attention on response time to inbound, which turns out to be more than a day on average because enquiries arrive into a shared inbox rather than to a named owner.

Two quarters later branch A converts inbound noticeably better and branch D revenue has grown with the additional supply. Nothing about the people changed.

Comparing revenue between unequal markets

Fix: compare rates within source. Revenue comparison between branches is a comparison of the markets and the lead flow they were given.

Routing gaps for ambiguous enquiries

Fix: a written rule for every arrival path including the awkward ones, always ending in a named owner and a timer.

Standardising things that should be local

Fix: keep the standard list to four items. Every additional central mandate reduces branch engagement with the system.

Cross-branch accounts with no credit rule

Fix: agree the split in advance. Cooperation that costs someone their number will not happen twice.

Regional meetings that are branch reports

Fix: circulate numbers beforehand and spend the meeting on the two or three places branches differ most, with the stronger branch explaining their method.

Territory changes mid-period

Fix: annual review with visible criteria. Frequent reallocation teaches reps not to invest in accounts they may not keep.

Four signals. Response time is consistent across branches rather than varying by a factor of ten. The spread in stage conversion between your best and worst branch is narrowing. Cross-branch accounts stop generating internal queries. And a customer moving between locations experiences a handover rather than a restart.

One early warning worth watching: data quality by branch. A branch drifting away from the shared process shows it in missing next steps and unfilled required fields several weeks before it shows in results, which makes it the cheapest signal you have.

Multi-site sales is the situation where a shared system stops being a convenience and becomes structural. Routing rules, common stage definitions, comparable views, one customer record visible across branches, and handovers that carry history are all difficult to sustain when each location keeps its own records.

HelloGrowthCRM supports per-branch ownership and territory rules, common stage definitions with local pipelines where they differ, routing with response timers, and one customer record visible to every branch that needs it. There is a free plan to trial in one branch first, and paid access is $10/user/month billed annually with no minimum seats.

Related reading: lead management software, sales automation, CRM for small business, CRM versus a spreadsheet, what a CRM is, industries, and pricing.