Build a verified B2B contact database for a new sales territory
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector output, but were not pulled from a live session. Run the prompt with your own territory parameters to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Taking over a new territory with no contact list means spending the first two weeks researching instead of selling. This Claude prompt builds a verified B2B contact database from scratch — Lusha finds companies matching the territory criteria, maps the right contacts at each, validates every email and direct phone, and returns a prioritized first-week outreach plan. One prompt run, ready to dial.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I've just taken over a new sales territory and I need to build a verified contact database from scratch — the right people at the right companies, with verified emails and direct phones, before I start any outreach.
My territory:
- Geography or segment: [REGION / VERTICAL / COMPANY SIZE RANGE]
- Function I sell into: [SALES / REVOPS / FINANCE / IT / MARKETING / OTHER]
- Seniority level I target: [VP AND ABOVE / DIRECTOR AND ABOVE / MANAGER AND ABOVE]
- What I sell: [PRODUCT / SOLUTION]
- Number of accounts to build: [TARGET NUMBER OR "AS MANY AS POSSIBLE"]
- Accounts already assigned to me: [PASTE ACCOUNT NAMES OR "NONE YET"]
</context>
<task>
1. Use Lusha to find companies matching the territory criteria:
- Industry, headcount range, and geography matching my segment
- Prioritize companies with recent signals: funding, exec hire, headcount growth
2. For each company, find the right contacts:
- Most senior verified contact in the target function
- Secondary contact if available (evaluator or champion level)
- Verified work email and direct mobile for each
3. Build the territory contact database:
- Company name, domain, headcount, industry, HQ location
- Contact: verified name, current title, email, direct phone, tenure in role
- Signal: any buying signal detected in the last 30 days
- Priority tier: A (signal + right seniority), B (right seniority, no signal), C (lower seniority or partial data)
4. Return:
- Full territory database sorted by priority tier
- Total accounts found, total verified contacts
- Top 5 accounts to call first — based on signal strength and contact seniority
- Any assigned accounts with no verified contact found
5. Recommended first week outreach plan:
- Day 1–2: all Priority A contacts
- Day 3–4: Priority B contacts
- Day 5: any accounts needing manual research before outreach
</task>
<constraints>
- Only include Lusha-verified contacts. Don't build a list with guessed data.
- Priority A must have both a signal AND a verified decision-maker. Don't inflate the tier.
- The first week plan must be specific — names and companies, not generic advice.
</constraints>What you'll get back
The situation: A new SDR takes over a mid-market SaaS territory — companies 200–1,000 employees, North America, selling into Sales and RevOps functions, VP level and above. No existing accounts assigned. Running the build on day one.
Territory database — 8 accounts (illustrative)
| Company | Size | Contact | Title | Priority | Signal |
|---|---|---|---|---|---|
| Crestline Software | 340 | R.V. | VP Revenue Operations | A | New CRO hired 12 days ago |
| Dunmore Analytics | 580 | T.K. | VP of Sales | A | Series B closed 3 weeks ago |
| Ashford Platforms | 420 | M.L. | Head of Sales Operations | B | No signal — ICP fit |
| Briarwood SaaS | 290 | P.O. | VP of Sales | B | No signal — ICP fit |
| Greenway Cloud | 510 | J.A. | SVP of Sales | B | No signal — ICP fit |
| Halcyon Data | 470 | S.P. | VP Revenue Operations | B | No signal — ICP fit |
| Elmont Systems | 610 | C.N. | Director of RevOps | C | Below VP threshold — flag |
| Falcrest Tech | 380 | — | — | — | No verified contact found — research needed |
Total: 8 accounts · 7 verified contacts · 1 gap (Falcrest Tech)
Top 5 accounts to call first:
- Crestline Software — new CRO is 12 days in, evaluating the full stack. Call R.V. first.
- Dunmore Analytics — post-Series B, new budget and headcount targets. Call T.K. this week.
- Greenway Cloud — SVP Sales, longest tenure of any contact in the list, most likely to have budget authority.
- Ashford Platforms — Head of Sales Ops, day-to-day decision influence on tooling.
- Briarwood SaaS — VP Sales at a company at the growth inflection point. No signal but strong ICP fit.
First week outreach plan:
- Day 1–2: R.V. at Crestline + T.K. at Dunmore — signal accounts first, window is open now
- Day 3–4: J.A. at Greenway + M.L. at Ashford + P.O. at Briarwood
- Day 5: S.P. at Halcyon + C.N. at Elmont (qualify seniority on call) + Falcrest research (find contact before calling)
Illustrative example. Run with your own territory parameters to see live results.
Why use Lusha in Claude
A new rep without a contact database spends the first two weeks researching instead of selling. Lusha in Claude compresses that to one prompt run — companies found, contacts verified, signals checked, priority tiers assigned. The signal layer is what separates this from a cold database: Crestline has a new CRO 12 days in, which is the highest-intent window for a sales tooling conversation — a new CRO evaluates the stack in the first 30 days. Without the signal check, Crestline looks identical to every other mid-market SaaS company in the territory. The Falcrest gap is equally important: knowing before day one that an account needs research means the rep doesn’t build a call plan around it that falls apart on day three.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How many accounts should I build in the first pass?
Start with 20–30. Enough to fill a healthy first month without overwhelming the outreach cadence. Run the prompt again at the start of month two to extend the territory. Building 100 accounts at once tends to produce a long list that never gets fully worked — 30 accounts with a clear priority tier is more actionable.
What if Lusha finds no verified contact at an account?
The prompt flags the account as “research needed” — the account stays in the plan but without a verified contact, no call should be made. Use the find the decision-maker prompt to find the right person before outreach. Don’t skip the account — it may become a Priority A once a contact is found.
Can I use this to refresh an existing territory?
Yes — paste existing assigned accounts in the last field. The prompt checks each one for signal and contact freshness, fills gaps, and flags any accounts where the contact has changed since the last update. Same output structure, different input.
What's the difference between Priority A, B, and C?
Priority A requires both a live signal AND a verified decision-maker — both conditions must be met. A company with a funding signal but only a Director-level contact is Priority B. A company with the right seniority but no signal is also Priority B. Priority C is for accounts that need qualifying before they’re workable: below seniority threshold, partial data, or unverified contacts. Don’t call Priority C accounts as if they’re Priority A.
What if most of the territory is Priority B with no signals?
A Priority B-heavy territory reflects accurate data, not a problem with the prompt. Build the list and work Priority B systematically. Signals emerge — a funding round, an exec hire — and Priority B accounts upgrade to Priority A. Running the weekly signal digest on the territory surfaces those upgrades as they happen.
Ready to build this?
Get started with Lusha and set up this play in minutes.
