The problem this solves
Territories drawn by geography alone give one rep the region full of perfect-fit accounts and another the region full of poor fits, and the quota conversation six months later is about the map rather than the selling. Territories drawn by count alone ignore that one account is worth ten. The fair split balances fit and region together, and it needs a fit score on every account to be possible at all.
RevOps usually does this in a spreadsheet with a scoring column someone built once and a lot of manual reshuffling. The mission scores every account fresh, proposes rules that produce balanced territories - so the split can be explained and repeated when new accounts arrive - and delivers the mapping in Sheets where RevOps can review, adjust and sign off before anything changes in the CRM.
How the mission runs
- Score every account on the list. The Lead Verification Agent scores each company on list <name> against your ICP from 0 to 100 with reasons, and attaches region from firmographic HQ data, so both dimensions of the split are on every row.
- Propose the assignment rules. The agent proposes rules that divide the accounts into three territories balanced on total fit score and on count, respecting region where possible - for example two regions per territory with a fit-based overflow rule - and shows the balance each rule set produces.
- Build the mapping. Each account is assigned a territory under the proposed rules, and the mapping shows the account, its score, its region, the territory and the rule that placed it, so any assignment can be traced and challenged.
- Deliver to Sheets for sign-off. Google Sheets receives the mapping with a summary tab showing total fit, account count and score distribution per territory, and a rules tab stating the logic, so RevOps can adjust a rule and see the balance change before approving.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A Google Sheet with every account on list <name> assigned to one of three territories, each row carrying the fit score, reasons, region and the rule that placed it, plus a summary tab comparing the territories on total fit, count and score distribution and a rules tab stating the assignment logic. Nothing is written to the CRM until RevOps signs off.
Make it yours
- Split into any number of territories, or balance on expected deal size where revenue estimates exist.
- Write the territory to a HubSpot or Pipedrive property once the sheet is approved, as a reviewed batch.
- Re-run the rules monthly against new additions to the list so incoming accounts are placed consistently.
- Balance on intent as well as fit so each territory has a similar share of in-market accounts.
- Add a fourth territory for a new hire, seeded with the accounts that best match their background.
Frequently asked questions
How is balance measured?
On total fit score and account count per territory, shown side by side; you can weight one over the other and the rules adjust.
Can existing account ownership be respected?
Yes. Provide current owners and the rules keep existing assignments where they do not break the balance, listing the exceptions.
What if regions are uneven in size?
The overflow rule moves accounts from a crowded region to a neighboring territory by fit, and the mapping shows which accounts moved and why.
Can accounts be weighted by open pipeline?
Yes. Connect the CRM and open deal value is added to the balance so territories carry similar pipeline as well as similar fit.
How often should territories be rebalanced?
Quarterly suits most teams; run the mission against the list's additions monthly to place new accounts, and reserve full rebalancing for the quarter so reps keep continuity.