Territory changes that don't zero out a rep's book
ZIP-based territory rules in Salesforce with a live map, and cutovers that dry-run, report what would change, and only commit when a human approves.
- Salesforce
The problem
Lead routing was hardcoded by state. Adding a rep or redrawing a region meant editing rules by hand and finding out a week later which accounts had quietly moved or dropped off everyone's list.
What we built
A territory engine of ZIP-based rules inside Salesforce with a live map. A dry run lists every account and lead that would change owner, a human approves it, and the commit runs once. Running it twice gives the same result, and every cutover writes a before-and-after snapshot.
No AI in this build. Here's why that was right: a territory is a rule. Reps and the commissions engine both need to look at a ZIP and know whose it is.
Rule evaluation, owner reassignment, the dry-run diff, approval gating, idempotency checks, and rollback snapshots. One dry run caught rules that would have emptied a new rep's book before commit.
Outcome
None published yet. The dry-run report from each cutover is available to any prospect who asks.
Who this fits
- Territory sales teams that redraw regions more than once a year
- RevOps leads whose assignment rules are older than the current org chart
- Companies where commissions depend on territory being right