Validate every contact in a territory before a QBR
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 checks every contact in your CRM territory before a QBR cycle starts — who’s still there, who’s changed roles, and who’s left. Lusha validates each one and finds replacements for any that have departed. The output is a structured contact health report your reps can act on before they walk into the room.
The prompt
<context>
I want to validate the contacts in my CRM before a QBR cycle starts. I need to know which contacts are still current, which have changed roles, and which have left — so my reps aren't walking into QBRs with stale data.
My territory:
- Account list: [PASTE COMPANY NAMES — one per line]
- Contact list (optional): [PASTE NAME, TITLE, COMPANY — one per line, OR "find key contacts from Lusha"]
- Focus: [ALL CONTACTS / DECISION MAKERS ONLY / ECONOMIC BUYERS ONLY]
- What matters most: [TITLE CHANGES / DEPARTURES / EMAIL ACCURACY / ALL]
</context>
<task>
1. For each contact in the list, use Lusha to validate:
- Are they still at the company?
- Is their title current — or has it changed since it was logged?
- Is their work email still valid?
- How long have they been in the current role?
2. For any contact who has left or changed roles significantly, use Lusha to find their replacement:
- Who now holds the equivalent role at the account?
- Return their verified title, email, and direct phone
- Flag if no clear replacement is found — structural gap at the account
3. Flag contacts by status:
- CURRENT: title and email confirmed, still at the company
- TITLE CHANGED: still at the company but role has shifted — update needed in CRM
- DEPARTED: no longer at the company — replacement found or flagged as gap
- UNVERIFIED: Lusha can't confirm — needs manual check before the QBR
4. Return a territory contact health report:
- Summary: X contacts checked, X CURRENT, X TITLE CHANGED, X DEPARTED, X UNVERIFIED
- DEPARTED and TITLE CHANGED contacts listed with what changed and the replacement or new title
- UNVERIFIED contacts flagged for manual follow-up
- CURRENT contacts listed only — no detail needed
5. For each account where a key contact has departed or changed roles significantly, flag it as a QBR prep risk — the rep needs to re-establish the relationship before walking into the meeting.
</task>
<constraints>
- Only return what Lusha verifies. If a contact can't be confirmed, flag as UNVERIFIED — don't assume they're still current.
- Title changes matter when they affect seniority or function. "Senior Manager" to "Director" at the same account is worth flagging. "Manager" to "Senior Manager" in the same function is not.
- The report is for the manager, not the rep — keep it structured and scannable. Reps get the relevant rows for their accounts, not the full report.
- If Lusha returns no replacement for a departed contact, flag the account as having a structural gap — don't leave it blank.
</constraints>What you'll get back
The situation: A RevOps lead runs the prompt one week before a QBR cycle for a mid-market territory — 10 accounts, 18 CRM contacts, decision makers only. Last contact audit was done 6 months ago.
Output: 10 CURRENT, 4 TITLE CHANGED, 3 DEPARTED, 1 UNVERIFIED. Two accounts flagged as QBR prep risks.
Territory contact health report
18 contacts checked · 10 CURRENT · 4 TITLE CHANGED · 3 DEPARTED · 1 UNVERIFIED
Run: May 19, 2025. Decision makers only. Validated via Lusha.
DEPARTED — replacement found or gap flagged
Marcus T. — formerly VP of Revenue Operations, Meridian Logistics
- Status: departed — no longer appears in Lusha’s verified records
- Replacement found: Jordan P., Head of Revenue Operations — joined 8 months ago
- Jordan P.: j.p@[meridian].com ✓ · direct mobile available
- ⚠ QBR prep risk — rep’s primary relationship has left. Jordan needs to be contacted and briefed before the QBR.
Sandra V. — formerly Head of Procurement, Cartway Technologies
- Status: departed — Cartway was acquired; procurement function restructured
- Replacement: unclear — acquisition integration ongoing, no equivalent role confirmed in Lusha yet
- ⚠ Structural gap — no verified procurement contact at this account. Rep needs to ask their main contact who now owns vendor approvals before the QBR.
Daniel F. — formerly VP of Sales, Pallet Systems
- Status: departed 11 weeks ago
- Replacement found: Keiko R., VP of Sales — joined 6 weeks ago
- Keiko R.: k.r@[pallet].com ✓ · direct mobile available
- ⚠ QBR prep risk — new VP of Sales hasn’t been introduced to the rep yet. Should be looped in before the QBR, not introduced in the room.
TITLE CHANGED — CRM update needed
| Contact | Account | CRM title | Current verified title | Change type |
|---|---|---|---|---|
| Brian R. | Finova Group | Director of RevOps | VP of Revenue Operations | Promotion — seniority change, update CRM |
| Amy S. | Waverly Digital | Sales Ops Manager | Head of Sales Operations | Promotion — now owns broader scope |
| Tom K. | Dune Analytics | CFO | Chief Financial and Operating Officer | Expanded scope — now also owns operations |
| Priya N. | Brightfield Co | Senior Manager, Procurement | Director of Procurement | Promotion — now likely has higher approval authority |
UNVERIFIED — manual check needed
Chris L. — VP of Engineering, Novela Group Lusha cannot confirm current status at this account. Two people with similar titles returned — unable to verify which is the active contact. Rep to confirm directly before QBR.
CURRENT — no action needed
10 contacts confirmed current across Bright Arc Systems, Corelink SaaS, Kestrel Labs, Thornwick Media, and Aster Platforms. Titles and emails verified. No CRM updates required.
All contact data validated via Lusha connector, May 19. Details abbreviated for privacy.
Why use Lusha in Claude
CRM contact data decays at roughly 30% per year — titles change, people leave, org structures shift. A QBR cycle built on 6-month-old contact data means reps walking into rooms expecting one person and finding another, or emailing an address that bounced two months ago. Lusha in Claude validates the full territory in one pass and flags exactly what needs to change before the cycle starts — not after a rep discovers it live in the meeting.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
How often should I run this?
Before every QBR cycle as a minimum. Quarterly is the right cadence for most territories — often enough to catch meaningful changes, not so often it becomes overhead. For high-velocity accounts or strategic territories, monthly works better.
What if I don't have a clean contact list to paste in?
Put “find key contacts from Lusha” in the contact list field and list only the account names. Lusha will return the most senior verified contacts in the relevant function for each account. You won’t get a CRM comparison, but you’ll get a current-state map of who’s actually there — which is often more useful than validating a stale list.
What counts as a significant title change?
A change in seniority level (Manager to Director, Director to VP) or a change in function (Sales Ops to Revenue Operations, Finance to CFO). A lateral move within the same function at the same level isn’t worth flagging in a QBR prep context — it doesn’t change who owns the relationship or the decision.
What do I do with the UNVERIFIED contacts?
Manual check — LinkedIn, a direct email, or asking the rep to confirm on their next call. UNVERIFIED means Lusha returned ambiguous or no data for that contact. It’s honest information: don’t assume they’re still current, but don’t assume they’ve left either.
Can I run this for my full CRM, not just one territory?
Run it territory by territory for clean, actionable output. A full CRM validation across hundreds of accounts produces an output that’s too large to act on in a QBR prep context. For a full-database enrichment run, Lusha’s API and bulk enrichment tools are the right approach — this play is for targeted pre-QBR validation.
Should reps see the full report or just their accounts?
The full report is for the manager or RevOps lead — it shows patterns across the territory. Reps get the rows relevant to their accounts only. Showing a rep that three other reps have departed contacts doesn’t help them prep; showing them that their key contact at Meridian left does.
Ready to build this?
Get started with Lusha and set up this play in minutes.
