Case Study 06 · Enterprise Client · Salesforce RevOps

No Territory Object. No Regions. No Rep Assignments. I Built the Structure — Then Cleaned Up What Was Under It.

Custom Object Build · Territory Design · Account Ownership Audit · RevOps

Salesforce Custom Objects Territory Management RevOps
6
Regions defined and AE-mapped
4
Custom fields on Territory object
Zero
Duplicate assignments remaining

The Problem

Six AEs. Accounts across the country. No system-level record of who owned what geography.

Applied CAX had no territory structure in Salesforce — no object, no regions, no defined ownership per AE. Six account executives were working accounts, but there was nothing in the CRM that said which rep owned which states. Leadership couldn't run a clean regional pipeline report. Reps had no way to know if they were working an account that belonged to someone else.

Duplicate and overlapping account ownership was invisible. It existed, but nothing surfaced it. The ask: build a territory structure from scratch, assign the AEs to regions, and make the CRM reflect how the team actually operates.

The Build

A custom Territory object. Four fields. Six records. One source of truth.

The foundation was a custom Territory object in Salesforce. Four fields: Territory Name (the label), State (the geographic unit), AE (a Lookup to the User object — the assigned rep), and Homebase (the AE's physical home location, used for context on regional alignment decisions).

Six regions were defined and mapped to the AE roster:

East Coast / Northeast
SoCal / Hawaii
Pacific Northwest & Mountain West
Northern California & Mountain West
Great Lakes & Midwest
South Central

Each region got a Territory record. Each Territory record linked to an AE via the Lookup field. The object now exists as the authoritative reference for who owns what geography.

The Cleanup

Building the structure was step one. Validating what was under it was step two.

A territory object is only useful if account ownership in the CRM actually matches it. That required an audit.

I pulled each rep's account list, cross-referenced it against the territory they'd been assigned, and flagged every mismatch. Prospect-type accounts were excluded from scope — territory ownership applied to active accounts only. After the audit was complete, I did a bulk ownership transfer to realign accounts to their correct AEs.

The goal was a state where you could look at any account record and the owner on that record matched the AE assigned to that geography in the Territory object. No exceptions, no gaps.

The Edge Cases

Two problems the audit surfaced that weren't in the original brief.

The first: a single state appeared in two reps' territory lists simultaneously. The duplicate wasn't visible from looking at either list in isolation — it only appeared when I cross-referenced the full set. A state can only belong to one rep. Caught it, flagged it, resolved the assignment.

The second: one inside-sales rep had no region assigned at all. No Territory record linked to their User. The gap was completely invisible until the audit made it explicit — they existed in the CRM, they owned accounts, but the territory structure had no record of them. Added the assignment.

Neither of these was a scope item. Both would have left the territory structure broken in ways that wouldn't be obvious until someone tried to run a regional report and the numbers didn't add up.

"The object build was an afternoon. The audit was what actually mattered — because a territory structure that doesn't match account ownership isn't governance. It's just documentation."

The Result

Zero territory structure to a fully governed, validated system. User-accepted on every sub-task.

Before: no territory object, invisible duplicate ownership, no clean way to report on regional pipeline. After: every AE has a defined region with a Territory record in Salesforce, every active account has a validated owner that matches that region, every duplicate is resolved, every rep is assigned.

Leadership can now filter pipeline by territory. Reps know which accounts are theirs. The inside-sales gap is filled. The duplicate is gone. The system reflects how the team actually operates.

What Was Built