How to Set Up Territory Management in DenchClaw

Territory management is how you prevent salespeople from stepping on each other's toes, ensure all market segments get covered, and hold reps accountable for defined slices of your addressable market. Most CRMs bury territory management in expensive enterprise tiers. In DenchClaw, it's a combination of fields, views, and automation you build yourself—tuned to exactly how your business divides up the market.

Common Territory Models#

Before building anything, decide how you want to divide territories. The most common approaches:

Geographic: West Coast, East Coast, EMEA, APAC. Simple and intuitive, but requires reps to specialize by time zone and sometimes language.

Industry vertical: FinTech, HealthTech, EdTech, Retail. Reps develop deep domain expertise. Better for complex enterprise sales where industry knowledge matters.

Account size: Enterprise (1000+ employees), Mid-market (100-999), SMB (10-99). Aligns rep skill level with deal complexity and sales cycle length.

Hybrid: Geographic + vertical (e.g., EMEA FinTech, US Enterprise, Asia-Pacific SMB). More complex to manage but allows precise specialization.

Step 1: Define Your Territory Structure#

Create a territories object:

"Create a territories object with fields: 
Territory Name (text), 
Type (enum: Geographic, Vertical, Account Size, Hybrid), 
Owner (text or relation to team members), 
Definition (richtext, describe the rules), 
Target Accounts (number, how many accounts in this territory), 
Open Pipeline Value (number, auto-calculated), 
Quota (number)."

Add entries for each territory:

"Create these territories: 
1. US West - Geographic, owner: sarah, quota: $500,000/quarter
2. US East - Geographic, owner: marcus, quota: $400,000/quarter
3. EMEA - Geographic, owner: james, quota: $350,000/quarter
4. Enterprise (1000+ employees) - Account Size, owner: lisa, quota: $600,000/quarter"

Step 2: Add Territory Fields to Contacts and Companies#

"Add a Territory field to my companies object: 
type: relation to territories. 
Also add Territory field to my leads object."

Then run the initial assignment:

"Assign territories to all existing companies in my CRM based on these rules:
- US West: State is California, Oregon, Washington, Nevada, Arizona, Colorado
- US East: All other US states
- EMEA: Country is in Europe, Middle East, or Africa
- Enterprise: Company size > 1000 employees (takes precedence over geographic)"

The agent writes a SQL UPDATE query against your DuckDB to apply these rules in bulk.

Step 3: Automate Territory Assignment for New Records#

New leads and companies should be auto-assigned when they're created:

"When a new company is added to my CRM, automatically assign it to a territory 
based on these rules (same as above). If the assignment is ambiguous, 
assign to 'Unassigned' and send me a Telegram notification."

"When a new lead is added, check their company's territory assignment 
and copy it to the lead. If the company doesn't have a territory yet, 
run the territory assignment logic."

Step 4: Create Territory-Filtered Views#

Each rep should have their own view showing only their territory:

"Create a view called 'Sarah - US West Leads' in my leads object: 
Territory = US West, sorted by Lead Score descending."

"Create a view called 'Marcus - US East Pipeline' in my deals object: 
Territory = US East, Stage not Closed, sorted by Deal Value descending."

These views are your rep-specific working views. Each person logs into DenchClaw and immediately sees their territory.

Step 5: Track Territory Coverage#

Coverage analysis tells you whether you're actually reaching all the accounts in each territory:

"For each territory, show me: 
total accounts assigned, 
accounts with at least one open deal, 
accounts with no activity in 90+ days, 
total pipeline value, 
and percentage of accounts ever contacted."

Whitespace (uncovered accounts with no activity) represents untapped pipeline. Surface it monthly and prioritize it in territory planning.

Step 6: Handle Territory Conflicts#

When two reps both prospect the same account:

"Check my leads and deals objects for accounts that appear in more than one 
territory, or where the territory assignment doesn't match the rep who created 
the record. Show me any conflicts."

Establish a conflict resolution rule: first-touch wins, or the rep with the existing relationship wins. Whatever your rule is, encode it:

"If a company already has an open deal with an owner, 
any new lead at that company should be assigned to the same owner 
regardless of territory, and the territory-owning rep should be notified."

Step 7: Territory Performance Reporting#

Monitor how each territory is performing:

"Show me territory performance this quarter: 
for each territory, show quota, pipeline value, closed revenue, 
coverage percentage, and projected attainment."

"Which territory has the highest win rate? 
Which has the longest average sales cycle?"

Territory-level analytics help you make better decisions about headcount, quota assignment, and where to invest in demand generation.

Step 8: Quarterly Territory Planning#

At the end of each quarter, review and adjust territories:

"Run a territory health check: 
are any territories undersized (reps closing deals too fast, 
need more accounts)? Oversized (too many accounts for one rep to cover)? 
Show me the distribution of accounts and pipeline value per territory."

Rebalancing territories based on data—rather than gut feel—is one of the highest-leverage activities in sales operations. DenchClaw makes the data readily available.

Step 9: Named Account Lists#

For enterprise territory management, you often assign specific named accounts (not just rules):

"Create a named_accounts object with fields: 
Company (relation to companies), 
Territory (relation to territories), 
Account Tier (enum: Tier 1, Tier 2, Tier 3), 
Target Stakeholder (text), 
Strategic Notes (richtext)."

Tier 1 accounts get the most attention; Tier 3 accounts are in your addressable market but aren't a current priority. This structure is standard in enterprise sales operations.

Frequently Asked Questions#

How do I handle accounts that qualify for multiple territories?#

Define a hierarchy of rules. Usually: named account tier takes priority, then account size, then geography. When a company has 5,000 employees but is in your "US West" rep's geographic territory, the Enterprise rep should probably own it—define that precedence explicitly.

Can reps see other territories' pipelines?#

Yes, by creating views without territory filters. You might want managers to see all territories while reps see only their own. DenchClaw doesn't have role-based access control in the single-user model—implement this by convention (each rep only uses their filtered view).

What if we reorganize territories mid-year?#

Run a bulk reassignment: "Reassign all accounts currently in 'US East' with company size > 500 employees to the new 'Enterprise East' territory." Update the territories object with the new structure and adjust rep quotas accordingly.

Should I use geographic territory management if my team is fully remote?#

Geographic territories work even for remote teams because prospects are still physically located somewhere—time zones, in-person meetings, and local events still matter. The alternative is to go purely vertical (industry-based) or use a rotating/round-robin model.

How do I track territory ownership over time?#

Add a Territory History field (richtext) or create a territory_changes log object. When a company's territory changes, log the old territory, new territory, date, and reason. This gives you clean attribution data even when territories are reorganized.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →