Build your territory plan for next quarter from Lusha signals

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own territory and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Every quarter starts with the same conversation: which accounts should this rep focus on? The answer usually comes from a CRM sort, a manager’s intuition, and a spreadsheet that was last meaningfully updated before the previous quarter ended. By the time the rep opens their territory on day one, the plan is already based on data that’s weeks or months out of date.

This Claude prompt builds the territory plan from the data up. It takes every account in a rep’s territory, runs them through Lusha to score ICP fit and surface live buying signals, and returns a three-tier prioritized plan — accounts to work immediately, accounts to develop, accounts to monitor — with the specific data behind every decision. Sales leaders walk into Q planning with a ranked territory map. Reps start day one knowing exactly where to spend their time.

The prompt

<context>
I want to build a data-backed territory plan for next quarter.
Every account in my territory scored, ranked, and tiered —
so my rep starts the quarter knowing exactly where to focus.

My territory accounts:
[Paste company names or domains — or say "use my full
territory" if your CRM is connected]

My ICP: [describe your ideal customer — industry, company
size, geography, funding stage]

My best closed-won customers for pattern matching:
[optional — list 2–3 company names or domains]

My target buyer: [e.g. VP of Sales, Head of RevOps, CFO]

Quarter starting: [e.g. Q3 2026 — July 1]
</context>

<task>
1. ICP SCORING — For every account in the territory,
   score against my ICP via Lusha:
   - Firmographic fit: industry, size, funding stage,
     geography
   - Lookalike fit against my best closed-won customers
     if provided
   - Score each account: Strong fit / Moderate fit /
     Weak fit / Disqualify

2. SIGNAL SCAN — For every ICP-fit account, check for
   live buying signals:
   - Hiring surges in the target function
   - Executive moves in the buying role
   - Funding events in the last 90 days
   - Intent signals on relevant topics
   - Tech stack signals relevant to your product
   - Rank signals by strength and recency

3. CONTACT VERIFICATION — For each account, verify
   the primary target contact via Lusha:
   - Current title and tenure confirmed
   - Verified email and direct dial
   - Flag departures and recent hires
   - Flag accounts with no verified contact — these
     need prospecting before outreach

4. PIPELINE CHECK — Flag accounts already in pipeline:
   - Active opportunity: note stage and last activity
   - Closed-lost in last 12 months: note reason if
     available and check for new signals since close
   - Never contacted: highest priority for net-new
     outreach

5. TERRITORY TIERING — Return the full territory in
   three tiers:

   TIER ONE — Work immediately:
   Strong ICP fit + active signal + verified contact
   + not currently in pipeline. These are the accounts
   most likely to convert this quarter.

   TIER TWO — Develop this quarter:
   Strong or moderate ICP fit + some signal activity
   + contact identified. Need outreach and qualification
   to determine pipeline readiness.

   TIER THREE — Monitor:
   Moderate fit, no current signals, or contact not
   yet verified. Check again mid-quarter for signal
   changes before investing time.

   DISQUALIFIED — Remove from active territory:
   Weak ICP fit with no compensating signals. Flag
   for reassignment or removal from territory.

6. SUMMARY — Return a territory overview:
   - Total accounts by tier
   - Total verified contacts ready to contact
   - Top 5 accounts to prioritize on day one
   - Biggest data gaps to address in week one
</task>

What you'll get back

A fully tiered territory plan built from verified data and live signals. Every account scored, ranked, and ready to work — so day one of the quarter starts with a prioritized list, not a blank spreadsheet.

Accounts scored: 42  ·  Tier one: 8  ·  Tier two: 14  ·  Tier three: 12  ·  Disqualified: 8  ·  Contacts verified: 31  ·  Data gaps flagged: 6

Territory overview

TierAccountsVerified contactsAction
Tier one — work immediately88 of 8Outreach week one
Tier two — develop this quarter1411 of 14Qualify by end of month one
Tier three — monitor127 of 12Check signals mid-quarter
Disqualified — remove8Flag for reassignment

Top 5 accounts for day one: [Company A], [Company B], [Company C], [Company D], [Company E] — all Tier one, all with stacked signals, all with verified contacts ready to contact.


Tier one — work immediately

Strong ICP fit, active signal, verified contact, not currently in pipeline. These 8 accounts are the highest-probability opportunities in the territory this quarter.

AccountICP fitTop signalContactPipeline status
[Company A]StrongSeries B closed — $22M✓ VP Sales verifiedNever contacted
[Company B]StrongNew VP Sales — 4 weeks in seat✓ VP Sales verifiedNever contacted
[Company C]Strong12 SDR roles posted✓ Head of RevOps verifiedNever contacted
[Company D]StrongIntent score 81 — your category✓ VP Sales verifiedClosed-lost 14 months ago
[Company E]StrongEMEA expansion — new office✓ VP Sales verifiedNever contacted
[Company F]StrongHeadcount up 22% in sales✓ CRO verifiedNever contacted
[Company G]StrongFunding + hiring surge stacked✓ VP Sales verifiedNever contacted
[Company H]StrongNew CRO hired 6 weeks ago✓ CRO verifiedClosed-lost 9 months ago — new signals since

[Company A] — full detail

FieldValue
IndustryRevenue Intelligence / SaaS
Employees280–320
FundingSeries B — $22M raised [date]
HQAustin, TX
ICP fitStrong — matches 5 of 5 criteria
SignalTypeDate
Series B closed — $22MFunding event[date]
14 SDR roles postedHiring surge[date]
Sales prospecting data — intent score 74Intent[date]
ContactTitleTenureEmailDirect dial
R.M.VP of Sales8 monthsr.m@[company].com+1 512 555 ••••

Contact confirmed live via Lusha connector, [date]


Tier two — develop this quarter

Strong or moderate ICP fit with some signal activity. 14 accounts — 11 with verified contacts, 3 with coverage gaps to address. Qualify by end of month one.

AccountICP fitSignalContactGap
[Company I]StrongHeadcount up 14%✓ Verified
[Company J]ModerateNew VP hired✓ Verified
[Company K]StrongNo signals yet✓ VerifiedNo active signal
[Company L]ModerateIntent score 62⚠ Not found in LushaContact needed
[Company M]StrongFunding — bridge round✓ VerifiedBudget pressure

Biggest data gaps — address in week one

  • [Company L], [Company N], [Company O] — No verified contact found in Lusha. Strong ICP fit but can’t contact until a VP+ is identified. Run the Buying Group play on these three accounts in week one.
  • [Company P], [Company Q] — CRM records not updated in 90+ days. Verify contacts before outreach to avoid bounced emails and stale titles.
  • [Company R] — Closed-lost 8 months ago. New signals present. Check what changed before re-engaging — use the Closed-lost reengagement play.

Example outputs in this play are illustrative — they reflect the structure, fields, and format of real Lusha connector output, but were not pulled from a live session. Run the prompt with your own territory and connectors to see live results.

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude, HubSpot, Lusha

Why use Lusha in Claude

Territory planning fails for the same reason pipeline reviews fail: the data behind every account is either stale, incomplete, or disconnected from what’s actually happening at those companies right now. A rep inherits a territory with 40 accounts, sorts by ACV, and starts at the top — never knowing that account number three just raised a Series B, account number twelve has a new VP of Sales who’s never heard of them, and account number twenty-two was closed-lost nine months ago by a different rep but now has three fresh signals that make it worth reopening.

Lusha’s Deep Intelligence layer changes what a territory plan can be. Every account gets scored against your actual ICP — the specific firmographic and signal patterns from your closed-won data, not a generic filter set someone configured two years ago. That scoring happens live, against verified company profiles and current signal data, so the tier one list reflects what’s true at the start of the quarter rather than what was true when someone last updated the CRM.

The signal scan adds the timing dimension that static territory plans completely miss. An account that’s strong ICP fit with no signals is worth developing. An account that’s strong ICP fit with a funding event, a new VP of Sales, and an intent surge on your category is worth calling on day one. Lusha processes 1.2B+ data points daily and surfaces 7M new signals every week — which means the territory plan built from this play captures timing windows that a spreadsheet-based plan will never see.

The contact verification step closes the gap between a prioritized account list and an actionable call list. Every tier one account comes with a verified contact — current title, direct dial, business email — so the rep doesn’t spend the first two weeks of the quarter hunting for the right person to call. The accounts flagged with no verified contact in Lusha get surfaced as data gaps in week one, so the rep knows where to focus prospecting effort before it becomes a mid-quarter problem.

For sales leaders, this play changes the Q planning conversation entirely. Instead of debating which accounts feel promising, the discussion is grounded in data: here are the eight accounts with the strongest signal and ICP fit combination, here are the fourteen that need qualifying, here are the eight that don’t belong in this territory. That’s a 20-minute planning conversation instead of a two-hour one.

Lusha data is sourced and used in accordance with Lusha’s Privacy Policy and Terms of Use.

FAQ

  • How is this different from the Territory Coverage Gaps play?

    The Territory Coverage Gaps play audits an existing territory for accounts that are misrouted, uncovered, or missing verified contacts — it’s a data quality and coverage check. This play is a forward-looking prioritization engine: it takes the full territory, scores every account by ICP fit and signal strength, and returns a tiered plan the rep can act on from day one of the quarter. Use the coverage gaps play to fix the territory data. Use this play to build the plan on top of it.

  • Can a sales manager run this for multiple reps at once?

    Yes — run it once per rep, with each rep’s account list as the input. The output is territory-specific so mixing accounts from multiple reps in one pass produces a combined list that’s harder to act on. For a full team review, run it rep by rep and compare the tier one counts and data gap flags across the team — it’s a fast way to identify which reps are starting the quarter with strong data coverage and which ones need support before the first pipeline review.

  • What should I do with the disqualified accounts?

    Flag them for reassignment or removal from the territory before the quarter starts. Disqualified accounts — weak ICP fit with no compensating signals — are the hidden cost of every territory plan. A rep who spends time working accounts that will never convert is a rep not working the eight accounts that could. Getting disqualified accounts out of the territory in week one means the rep’s attention is focused on the right work from the start, not discovered missing at the mid-quarter review.

  • How do I handle closed-lost accounts that appear in the territory?

    The play flags them separately with a note on how long ago they were closed and whether new signals have appeared since. An account closed-lost nine months ago with three fresh signals — a new VP, a funding round, a hiring surge — is a different conversation than an account closed-lost three months ago with no new signals. For the former, use the Closed-lost reengagement play to check what changed before re-engaging. For the latter, leave it in tier three until the signals shift.

  • How often should I rebuild the territory plan?

    Once per quarter as the primary planning input, and once mid-quarter as a signal refresh. The tier one list changes as signals come and go — an account that had no signal at the start of the quarter might have a funding event and a new VP by week six. Running a lighter version of the play at mid-quarter — just the tier two and tier three accounts, checking for signal changes — keeps the plan current without rebuilding it from scratch. Save the prompt in a Claude Project with your territory accounts as a custom instruction and the mid-quarter refresh takes under five minutes.

Ready to run this?

Connect once, run anywhere. Works in Claude, ChatGPT, n8n, Clay, or any agent connected to Lusha.