Flag accounts that are misrouted or uncovered in your territory
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt scans your territory for accounts with coverage problems — unassigned, assigned to the wrong rep’s segment, or grown past the tier threshold — using verified Lusha firmographic data. Returns a ranked list with the specific problem, the correct assignment, and a priority flag for any account that has both a coverage gap and a live signal.
Tools: Claude, Lusha, territory data (pasted)
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to find accounts in my territory that are misrouted, uncovered, or have grown out of their current tier — before the quarter starts rather than discovering it mid-quarter.
My territory:
- Territory definition: [YOUR CRITERIA — industry, size, geography, or named accounts]
- Account list (if available): [PASTE COMPANY NAMES — or "build from ICP criteria"]
- Rep assignments (if available): [WHICH ACCOUNTS ARE ASSIGNED TO WHICH REP]
- Tier thresholds: [HOW YOU DEFINE SMB / MID-MARKET / ENTERPRISE BY HEADCOUNT]
</context>
<task>
1. For each account, use Lusha to pull current verified firmographic data:
- Current headcount
- Industry
- Geography
- Headcount in the function we sell into
- Any recent signals: funding, exec hire, headcount growth, M&A
2. Flag accounts with coverage problems:
- UNASSIGNED: in the territory but no rep assigned
- MISROUTED: assigned to a rep whose territory criteria don't match the account's current firmographics
- TIER MISMATCH: account has grown or shrunk past the threshold for its current rep's tier
- SIGNAL — READY TO ESCALATE: account has a signal suggesting it should move up a tier or get more senior coverage
3. For each flagged account, return:
- The specific coverage problem
- The correct assignment based on current firmographics
- Any signal that makes this account a priority to fix now vs next quarter
4. Return a territory coverage report:
- Summary: X accounts checked, X UNASSIGNED, X MISROUTED, X TIER MISMATCH, X SIGNAL flags
- Full flagged list with current firmographics and correct assignment
- Total ACV exposure from misrouted or unassigned accounts (if ACV data provided)
- Top 5 accounts to fix before the quarter starts — ranked by ACV and signal strength
5. Flag any account where both a coverage problem AND a live signal exist simultaneously.
</task>
<constraints>
- Base coverage assessment on current verified Lusha firmographics, not CRM data.
- MISROUTED and TIER MISMATCH are process problems, not rep failures — frame as fixes needed.
- If no rep assignments are provided, focus on UNASSIGNED and TIER MISMATCH only.
- Top 5 priority list must rank by ACV and signal, not just by coverage problem type.
</constraints>What you'll get back
The situation: A RevOps lead runs the scan across 20 accounts in a North America mid-market territory before Q3 starts. Three reps. Tier thresholds: SMB = under 150 employees, Mid-market = 150–600, Enterprise = 600+.
Output: 2 UNASSIGNED, 3 MISROUTED, 2 TIER MISMATCH, 2 SIGNAL flags. $312K ACV exposure. Top 5 fixes identified.
Territory coverage report — Q3 pre-scan
20 accounts checked · 2 UNASSIGNED · 3 MISROUTED · 2 TIER MISMATCH · 2 SIGNAL flags
Total ACV exposure: $312K
Run: May 19, 2025. Firmographic data via Lusha.
⚠ Double flag — coverage gap + live signal (fix immediately)
Bright Arc Systems · $110K · TIER MISMATCH + SIGNAL
- Assigned to: SMB rep D.P.
- Lusha current headcount: 420 employees — above SMB ceiling of 150
- Signal: Series B closed 6 weeks ago, sales headcount up 28%
- Correct assignment: Mid-market team (J.R. or S.K.)
- Why urgent: A $110K account growing fast with a live funding signal sitting in an SMB rep’s queue is the highest-cost coverage error on this list. Fix before Q3 starts.
Halcyon Ventures · $72K · UNASSIGNED + SIGNAL
- Assigned to: No rep
- Lusha current headcount: 310 employees · SaaS · Austin
- Signal: New CRO hired 18 days ago
- Correct assignment: Mid-market team
- Why urgent: An unassigned account with a new CRO in the first 60 days is a closing window. Assign today.
MISROUTED — wrong rep’s segment
| Account | ACV | Assigned to | Problem | Correct assignment |
|---|---|---|---|---|
| Finova Group | $180K | SMB rep D.P. | 180 employees — above SMB ceiling | Mid-market: J.R. |
| Pallet Systems | $55K | Enterprise rep | 141 employees — below enterprise floor of 600 | Mid-market: S.K. |
| Novela Group | $48K | Mid-market rep J.R. | 48 employees — below mid-market floor of 150 | SMB: D.P. |
UNASSIGNED — no rep assigned
| Account | Headcount | Industry | Correct tier | Signal |
|---|---|---|---|---|
| Halcyon Ventures | 310 | SaaS | Mid-market | New CRO 18 days ago ⚠ |
| Thornwick Media | $78K est ACV | 220 | SaaS | Mid-market |
TIER MISMATCH — grown or shrunk past current tier
| Account | ACV | Current rep | Current headcount | At assignment | Problem |
|---|---|---|---|---|---|
| Bright Arc Systems | $110K | SMB rep D.P. | 420 employees | 180 at assignment | Grown 2.3× past SMB ceiling ⚠ |
| Dune Analytics | $44K | Enterprise rep | 280 employees | 650 at assignment | Contracted below enterprise floor |
SIGNAL — ready to escalate tier
| Account | ACV | Current rep | Signal | Recommendation |
|---|---|---|---|---|
| Waverly Digital | $72K | Mid-market J.R. | Series B closed, headcount up 34% | Monitor for enterprise threshold crossing — flag for re-tier in 60 days |
Top 5 to fix before Q3
- Bright Arc Systems ($110K) — TIER MISMATCH + Series B signal. Highest ACV + live signal. Move to mid-market immediately.
- Halcyon Ventures ($72K est) — UNASSIGNED + new CRO signal. Closing window. Assign today.
- Finova Group ($180K) — MISROUTED. Highest ACV misroute on the list. Move from SMB to mid-market.
- Pallet Systems ($55K) — MISROUTED. Enterprise rep carrying a mid-market account wastes capacity.
- Thornwick Media ($78K est) — UNASSIGNED. No signal but unassigned at start of quarter — assign before outreach season.
Firmographic data via Lusha connector, May 19. ACV data from pasted territory list.
Why use Lusha in Claude
Territory coverage problems are invisible in most CRMs because the CRM reflects assignments, not current firmographic reality. A company that was SMB when it was assigned is still showing in an SMB rep’s queue even after it hits 420 employees and raises a Series B — the CRM never updated. Lusha in Claude checks the current verified state of every account against the tier thresholds and finds the gaps that have been quietly building since the last territory review. The double-flag output — coverage gap plus live signal — is what makes this urgent rather than administrative: an account with a new CRO sitting unassigned is a different problem than one with no signal.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How often should I run this?
Quarterly at minimum — before each quarter starts. Companies grow and shrink fast enough that a territory review done six months ago may have significant drift by now. Run it at the start of Q1 and Q3 as a minimum, and before any major territory restructure.
What if I don't have rep assignments documented?
The prompt still runs on UNASSIGNED and TIER MISMATCH — it finds every account that doesn’t fit the tier criteria for any rep, and every unassigned account. The MISROUTED flag requires assignment data to know which rep has the wrong account.
What counts as ACV exposure?
The total contracted or estimated ACV of accounts that are misrouted or unassigned. An account being worked by the wrong rep isn’t necessarily lost — but it’s at risk of being handled with the wrong deal motion, wrong pricing authority, and wrong escalation path. ACV exposure quantifies what’s at stake from the coverage gaps.
How is this different from the single account routing check?
The account routing check validates one specific account at the moment it enters the system. This prompt scans the whole territory on a schedule. Use the routing check as a gate, this prompt as the quarterly audit.
What do I do with the SIGNAL — READY TO ESCALATE accounts?
Monitor them. Waverly Digital is growing fast but hasn’t crossed the enterprise threshold yet. Flag it in your CRM for a re-tier review in 60 days. If it crosses 600 employees or raises another round before then, escalate immediately — don’t wait for the next quarterly scan.
Ready to build this?
Get started with Lusha and set up this play in minutes.
