The Scenario
You run sales at a UK B2B business with eight to fifteen field salespeople covering distinct territories — by postcode region, by industry vertical, by company size band, or by some combination of the three. The rules of who owns what were originally written on a whiteboard. Today they live in a spreadsheet maintained by the sales operations manager, with footnotes capturing the exceptions: shared accounts, named accounts that override geography, accounts inherited at acquisition, and accounts that have been “temporarily” reassigned for the last fourteen months.
The CRM does not enforce any of this. When a new lead comes in, somebody — sales ops, the sales director, sometimes the first salesperson to see it — manually decides who it belongs to and assigns it accordingly.
The Problem
The specific frustration is the territory dispute that lands on the sales director’s desk at the end of every quarter. Two salespeople both think they should have got credit for the deal that closed in Yorkshire. The account was in a vertical owned by one of them but in a postcode owned by the other. The footnotes in the spreadsheet are ambiguous. The matter consumes an hour of sales leadership time, generates a ruling that one party feels was wrong, and leaves residual irritation that lingers into the next quarter.
The cost is two layered problems. The obvious one is the disputes themselves — five or six a quarter, each consuming hours of management time and creating internal friction. The less obvious one is the lead leakage. Leads that should clearly belong to one salesperson based on the rules end up assigned to another because the sales ops manager applies the rules from memory and gets them wrong occasionally. Over a year the cumulative effect is meaningful — the strongest salesperson in a vertical may be losing leads to other reps simply because the assignment is being made by a person rather than by a system.
The Approach
A proper territory management layer replaces the spreadsheet with a system that holds the rules and applies them automatically. Territories are defined in structured terms: postcode regions, industry codes, company size bands, named account lists, and the priority order between them when rules collide. The rules are written down once, agreed by the sales leadership, and then enforced consistently by the system rather than interpreted on a case-by-case basis.
The system is integrated with the CRM through an API integration and with Companies House so each new account is automatically classified by registered address, SIC codes, and size, then assigned to the territory owner based on the rules. Exceptions — shared accounts, override assignments, temporary reassignments with an end date — are captured as first-class objects rather than as footnotes. The layer is built on a workflow automation system so the rule changes flow through to assignment changes when leadership updates them.
The Outcome
The quarterly dispute meeting effectively stops. When two salespeople disagree about who should have got an account, the system shows the rule that was applied and the inputs that drove it. Disagreement is now with the rule — which is the right place to have that conversation — not with whether the rule was applied correctly. Sales leadership reclaims the hours per quarter that used to go into adjudication.
Lead leakage tightens because every account is classified consistently against the same rules. The strongest salesperson in a vertical stops losing leads to other reps because of inconsistent manual assignment. The spreadsheet stops being a source of truth that nobody fully trusts. New territories — opening up a new region, launching into a new vertical — get defined in the system rather than added as footnotes, and the rollout happens cleanly. Acquisitions can be absorbed properly because the inherited accounts get classified into the new framework rather than being held as a special case that nobody quite remembers the rules for.
Who This Applies To
Sales leaders, sales operations managers, and commercial directors at UK B2B businesses with five or more field or named-account salespeople operating across distinct territories. Particularly relevant for manufacturing, equipment supply, distribution, business services, and specialist B2B SaaS — sectors where territory rules are real, not nominal. Also applies to channel and partnership teams managing geographic or sectoral patch allocation.
Sound Familiar?
If your quarterly meetings include a territory dispute as a recurring agenda item, the spreadsheet is the source of the problem, not the team. We build territory management replacements that hold the rules and apply them automatically against your CRM. Let us walk through what yours would look like.