By Siddharth Gangal TL;DR
- Definition: an SDR territory is the defined set of accounts a Sales Development Representative owns for prospecting — bounded by geography, industry, company size, or a named account list. The territory determines which accounts the rep works and in what order.
- Five models: geographic, industry/vertical, account size, named account list, and round-robin dynamic. Most mid-market SaaS teams run hybrid models combining two dimensions — for example, mid-market fintech accounts in North America.
- Capacity reality: one SDR can actively work 80–150 Tier 1 accounts per quarter with 25–45 minutes of focused effort per account per week. Territories sized above 600 total accounts produce coverage gaps, not more pipeline.
- The signal layer: static territory plans under-perform because they treat all accounts as equally ready. Signal-weighted territories — where accounts move up the work queue when a buying signal fires — produce 2.4× more meetings per rep than static list-based approaches (Gangly rep cohort data, 2026).
What is an SDR territory?
Definition
SDR territory — the defined set of accounts, companies, or geographic regions assigned to a Sales Development Representative for prospecting and pipeline generation. The territory sets the boundaries of the rep's work: which accounts to research, which to outreach, and which to qualify. A well-designed SDR territory gives the rep enough accounts to build pipeline without so many that coverage becomes superficial.
Most sales teams define SDR territories along one or two dimensions: geography (which states or countries the rep owns), industry (which verticals the rep covers), company size (which revenue or headcount bands the rep targets), or a named account list (specific companies pre-selected by RevOps or a sales leader). Each model shapes how the rep prospects, who they talk to, and what subject-matter expertise they develop over time.
Territory design is a capacity problem before it becomes a strategy problem. A rep cannot work 800 accounts with the same quality they can bring to 120. The first question when designing any SDR territory is: how many accounts can one rep meaningfully engage in a quarter? Everything else — scoring, tiering, outreach sequencing — flows from that capacity ceiling.
Territory quality also matters more than territory size. An SDR working 150 high-ICP-fit accounts with active buying signals will consistently out-produce a rep working 600 accounts with poor fit and no signal activity. For context on the broader SDR role, see the SDR role complete guide. For the account-level scoring that feeds into territory work, the B2B buying signals guide covers the full signal taxonomy.
The 5 SDR territory models — and which one fits your team
Five territory models dominate B2B SaaS SDR teams. Each one shapes the rep's day differently. None is universally superior — the right choice depends on your go-to-market motion, deal size, and the expertise you want reps to develop.
| Model | How it works | Best for | Weakness |
|---|---|---|---|
| Geographic | Rep owns all accounts inside a defined region — a state, metro area, or country. | Field sales, travel-heavy enterprise motions, industries where in-person relationships matter. | Territory quality depends on density. A rural region and a metro region produce wildly different pipeline opportunity. |
| Industry / Vertical | Rep owns all accounts in a named vertical — fintech, healthcare, logistics — regardless of location. | SaaS companies where pain differs sharply by sector and reps build genuine domain expertise. | Ramp time increases. SDRs need deep vertical knowledge before outreach resonates. |
| Account Size / Segment | Territory split by company size — SMB (1–200 employees), Mid-Market (201–1,000), Enterprise (1,000+). | Teams running distinct motion types by deal size. Enterprise outreach looks nothing like SMB outreach. | Company size does not always predict buying behavior. A 150-person fintech may buy like an enterprise deal. |
| Named Account List | A curated list of 50–300 specific accounts assigned to the rep regardless of geography or vertical. | Enterprise SDRs, account-based motions, teams running tight ICP filters. | Accounts not on the list never get worked, even when a perfect-fit company lands in the rep's market. |
| Round-Robin / Dynamic | Accounts or inbound leads rotate to reps automatically based on availability or capacity rules. | Early-stage teams that lack enough data to create static territory logic. Inbound-heavy motions. | No rep builds deep account knowledge. Context resets with every new assignment. |
Hybrid territory models — the most common setup in 2026
Most mid-market SaaS SDR teams in 2026 run hybrid models: two dimensions combined into one boundary. "Mid-market healthcare accounts in North America" is a hybrid of company size and vertical. "Enterprise fintech accounts in EMEA" combines size, vertical, and geography. Hybrid models give more targeting precision but require clearer documentation — reps need to know exactly which accounts fall inside and outside the boundary before they build their first prospect list.
For AE-level territory design that SDRs feed into, the AE territory planning frameworks guide covers the full account scoring and tiering methodology that both roles share.
How to build an SDR territory from scratch
Building an SDR territory from scratch takes seven steps. The most common mistake is skipping directly to "pull a list and start outreach" — which produces high-volume, low-quality work that burns through the best accounts in the first six weeks and leaves the rep with nothing to work for the rest of the quarter.
- 01
Define the territory boundary
Start with the dimension that matches your go-to-market motion: geography, vertical, company size, or named accounts. The boundary must be clear enough that two reps never claim the same account. Ambiguous territory lines produce internal conflict, double-touches on prospects, and broken CRM data.
- 02
Size the total addressable account pool
Pull the full list of companies that fit inside the boundary from your prospecting tool (Apollo, ZoomInfo, LinkedIn Sales Navigator). Filter by firmographic ICP: industry, headcount band, revenue range, geography, and tech stack. This is your total serviceable account pool — the universe the rep can work from.
- 03
Score each account for ICP fit and signal activity
Not all accounts in the pool are equal. Apply a three-factor score: ICP fit (40%), active buying signals (40%), and prior engagement or CRM history (20%). Accounts scoring above 65 are Tier 1 — high-value, high-intent, work this quarter. Accounts scoring 35–64 are Tier 2 — monitor for signal fires. Below 35 is Tier 3 — nurture only.
- 04
Set hard account caps per tier
Tier 1: 50–150 accounts maximum. Tier 2: 200–500. Tier 3: unlimited (nurture queue). The caps exist because territory coverage is a time problem before it is a strategy problem. A rep with 600 Tier 1 accounts covers none of them properly. A rep with 80 Tier 1 accounts can run a legitimate multi-channel sequence on all 80 within a quarter.
- 05
Map the persona stack per Tier 1 account
For each Tier 1 account, identify the 2–3 personas the SDR will contact: the economic influencer, the day-to-day user or champion, and the technical gatekeeper where relevant. Name them, find their LinkedIn profiles, add them to the CRM linked to the account. This is the pre-work that separates territory planning from list building.
- 06
Define your signal triggers for tier promotion
Set rules that automatically move a Tier 2 or Tier 3 account to active work: a new VP hire at the account, a funding announcement, a LinkedIn post about the pain your product solves, a competitor renewal window opening. Signals decay in 72 hours. The rep who contacts a newly-funded account on day one competes with two vendors. The rep who contacts on day eight competes with twenty.
- 07
Document and share the territory plan
One page: territory boundary, account pool size, scoring rubric, tier caps, persona stack, signal trigger list, and quota math (accounts needed × conversion rates = pipeline required). Share with the SDR manager before the quarter begins. A territory plan is a contract between the rep and the company about what good looks like.
The output of this process is not a spreadsheet — it is a working system. The Tier 1 accounts get a personalized, multi-channel sequence. The Tier 2 accounts get monitored automatically and join the active queue when a signal fires. The Tier 3 accounts sit in a nurture pool that marketing or automation touches on a long cadence. Territory planning and signal-based selling are the same motion — the territory sets the boundaries, signals set the priority order.
SDR territory capacity: how many accounts can one rep actually work?
Territory capacity is the single most under-discussed variable in SDR management. Most territory assignments are set by what is available, not by what one rep can realistically work. The result: reps with 600-account territories who are effectively running 50-account territories because everything above that threshold never gets touched.
The table below shows the real inputs behind SDR capacity math. Use these numbers to audit your own territory size against what your reps can actually execute:
| Capacity Input | Benchmark Value |
|---|---|
| Total working days per quarter | 65 days |
| Net selling time per day | 4.7 hours (after admin) |
| Time per Tier 1 account per week | 25–45 minutes (research + outreach + follow-up) |
| Time per Tier 2 account per week | 5–10 minutes (signal monitoring + triggered outreach) |
| Discovery calls per day (at quota) | 1–3 calls |
| CRM + admin time per day | 1.5–2.5 hours (manually) / 35–45 min (with workflow tooling) |
The admin line is critical. Salesforce's State of Sales 2026 report documents that sales reps spend 41% of their working day on non-selling tasks. For an SDR, that is roughly 2.3 hours per day on CRM updates, list research, internal meetings, and tool setup. Workflow tooling that auto-logs calls, auto-drafts notes, and auto-updates CRM fields cuts that number to 35–45 minutes per day — which directly expands the time available for Tier 1 account coverage.
Track the right territory-level metrics to prove coverage is working. The SDR metrics guide covers the full measurement stack — from activity metrics to pipeline conversion rates — that tell you whether a territory is sized correctly.
The Territory Capacity Framework: Gangly's signal-weighted approach
Static territory plans treat every account as equally ready to be worked. They do not. A company in your Tier 1 list that just announced a $30M Series B round is more actionable today than an equally strong ICP-fit company that has shown zero signal activity in three months. Working them identically wastes the timing advantage on the funded account and over-invests in the dormant one.
The Territory Capacity Framework — Gangly's approach to SDR territory management — adds a signal layer on top of the traditional tier structure. Instead of a static Tier 1 list that stays fixed for the quarter, accounts move up and down the active work queue as signals fire and decay.
The Territory Capacity Framework — 4 Layers
- 1
Static tier structure
Score every account in the territory on ICP fit (40%), signal history (40%), and engagement (20%). Assign to Tier 1 (score ≥65), Tier 2 (35–64), or Tier 3 (<35). Set hard caps: 80–150 T1, 200–400 T2, remainder T3.
- 2
Signal trigger rules
Define the six signals that auto-promote a T2 account to the top of the T1 active queue: new VP or C-level hire, funding round, expansion hiring in an ICP role, competitor renewal window opening within 60 days, LinkedIn post or content engagement indicating pain alignment, and inbound form fill or pricing-page visit. When any of these fires, the account jumps the queue — regardless of where it sat before the signal.
- 3
Signal decay timer
Every promoted account has a 5-business-day window to receive a first touch before the signal advantage erodes. After day five, the account returns to its standard tier position. This forces prioritization: a rep cannot leave 12 signal-promoted accounts untouched because they were busy working lower-priority accounts from last week's list.
- 4
Weekly capacity review
Each Monday, the rep reviews the current signal queue, confirms the active T1 list for the week, and adjusts if new signals moved accounts up. The review takes 15–20 minutes with Gangly's account routing dashboard. Without tooling, it requires pulling exports from four different sources and reconciling manually — typically 60–90 minutes and frequently skipped.
Gangly rep cohort data from Q1–Q2 2026 shows that SDRs running signal-weighted territory management book 2.4× more meetings per rep per month than SDRs working static account lists with no signal prioritization, controlling for territory size and ICP quality. The difference is not working harder — it is working the right account at the right moment.
Gangly's workflow connects buying signal detection, account prioritization, outreach sequencing, call prep, and CRM update into one continuous motion. When a signal fires on a T2 account, Gangly surfaces it in the rep's morning queue, pre-researches the account, and prepares an outreach draft — all before the rep opens their laptop. The rep reviews, adjusts, and sends. The CRM is updated automatically. The signal-to-first-touch time drops from an industry average of 4.7 days to under 24 hours.
How to work an SDR territory week by week
A territory plan without a weekly execution rhythm is a document that sits in a shared drive and never affects behavior. The structure below converts a territory plan into a repeatable weekly operating mode.
| Day | Focus | Key Action |
|---|---|---|
| Monday | Signal review | Pull the weekend signal queue. Promote any accounts that fired a trigger. Set the week's Tier 1 outreach priority list. Block time on Tuesday and Wednesday for new Tier 1 sequences. |
| Tuesday–Wednesday | Tier 1 outreach | Run the primary outreach block on active Tier 1 accounts. Personalized email first touch, LinkedIn connect or message, phone follow-up where appropriate. Aim for 15–25 Tier 1 accounts worked per day. |
| Thursday | Follow-up and calls | Follow up on Tuesday/Wednesday outreach. Block afternoon for discovery calls and AE handoffs. Update the CRM on every completed touch the same day — not at end of week. |
| Friday | Tier 2 signal sweep + reporting | Review the Tier 2 queue for new signals. Move any newly-promoted accounts to next week's Tier 1 list. Log territory metrics: touches, replies, meetings booked, pipeline created. |
Monthly and quarterly territory reviews
Weekly execution keeps the territory moving. Monthly reviews keep the scoring accurate. Every 30 days, re-run the account scoring model on the full Tier 2 pool. Accounts that crossed a scoring threshold (new signal, new hire, ICP tightening) get promoted. Accounts that dropped below threshold (leadership departed, company downsized, competitor locked in) get demoted to Tier 3. The monthly review takes 30–45 minutes and prevents the territory from going stale.
Quarterly reviews are territory-level recalibrations: did the pipeline math hold? Did the quota coverage model work? If reply rates dropped or conversion rates shifted, the Tier 1 account count may need to expand to compensate. If the rep is over-covered — more meetings than the AE team can absorb — the Tier 1 cap can tighten to allow for deeper account work and higher meeting quality.
Territory fairness and SDR performance — the real conversation
Territory fairness is a real operational problem — not just an SDR complaint. If one rep's territory contains 80 high-ICP-fit accounts in a fast-growing vertical while another rep's territory contains 400 low-fit accounts with no active signals, the second rep will hit quota at half the rate regardless of skill, work ethic, or coaching investment. The company loses revenue. The rep loses confidence and eventually leaves.
Three variables determine territory equity:
- ICP concentration: what percentage of accounts in the territory score above 50 on the standard ICP rubric? Territories with fewer than 15% high-ICP accounts are structurally underloaded — not a performance problem, a territory design problem.
- Signal velocity: how many actionable buying signals fire per week inside the territory? A territory in a fast-growing vertical (fintech, AI, healthcare IT) may produce 8–12 fresh signals per week. A territory in a slow-moving sector may produce one. Signal velocity is rarely measured before territory assignments are made.
- Pipeline conversion history: what conversion rates have similar territories produced in prior quarters? Benchmarks for comparable territories — same model, same segment — provide the baseline for evaluating whether a rep is over or under-performing relative to structural opportunity.
One practical approach from the r/sales community and confirmed by multiple SDR managers: rotate Tier 2 and Tier 3 account assignments quarterly to prevent permanent inequity from compounding. Tier 1 accounts — where reps have built account knowledge and relationship history — can remain stable longer, but even those should be audited every two quarters for ICP drift.
When a rep raises a territory fairness concern, the first response should be data — not dismissal. Pull the ICP concentration score, the signal velocity, and the historical conversion benchmarks. If the data confirms the territory is structurally disadvantaged, fix the territory. If the data shows the territory is comparable to peers and the rep is underperforming, that is a coaching conversation, not a territory redesign.
Common SDR territory mistakes that kill quota attainment
These six mistakes appear repeatedly across SDR teams at companies from 10-person startups to 500-person scale-ups. Each one produces predictable, avoidable quota misses.
-
Treating all accounts in the territory equally
An SDR working a territory of 400 accounts cannot give 400 accounts equal attention. The rep who tries to touch all 400 superficially will be outperformed by the rep who runs a legitimate sequence on the top 80. Tiering is not optional — it is the mechanism that makes coverage possible.
-
Waiting for RevOps to give you a perfect territory before you start working
Territory plans are never perfect on day one. The accounts you thought were Tier 1 in January look different by March. Start working with the best available data, build signal triggers, and refine the score each month. A working imperfect territory beats a perfect territory that never launches.
-
Conflating territory size with territory quality
A territory with 1,000 accounts that share a low ICP fit score produces less pipeline than a territory with 150 accounts that score above 70. Fight for account quality over account count. If a territory rebalance looks unfair but the new territory has higher ICP concentration, the numbers will prove it out within two quarters.
-
Never refreshing the tier assignments
Accounts change. A Tier 3 account that was a poor ICP fit in Q1 may have hired a new VP of Sales in Q2 — the exact signal that makes them a Tier 1 target. Tier assignments should be reviewed monthly. Signal monitoring should be continuous.
-
Ignoring signal decay timing
Every buying signal has a half-life. A new VP hire at an account is most actionable within 5–10 business days of the announcement. A funding round is most actionable within 48–72 hours. An SDR who works a "fresh" signal that is three weeks old will find that seven other vendors already ran their sequences. Speed to signal is a competitive advantage.
-
Building a territory plan and never revisiting the quota math
The territory plan should include a pipeline math section: accounts needed × outbound conversion rate × average ACV = pipeline required. If the conversion rates shift mid-quarter (lower reply rates, shorter cycles), the math needs to recalculate. SDRs who catch the mismatch early can expand their Tier 2 pool. SDRs who notice in week eleven cannot.
Ready to Work Your Territory Smarter?
Stop working static lists. Start working signal-triggered accounts.
Gangly connects buying signal detection, account prioritization, outreach prep, and CRM updates into one workflow — so your SDRs contact the right account at the right moment, every day.
Siddharth Gangal
Founder, Gangly — Sales Workflow System for AEs, BDRs, and founders doing outbound. Writing about signals, workflows, and how reps turn buying intent into booked meetings.