Re-enrich stale CRM records

Built by: Lusha
Time to build: 1 min
Difficulty: Easy
Tools: Claude ▪ Lusha
Type: Prompt

A Claude prompt that takes CRM records 12+ months untouched and re-validates them with verified data — but more importantly, surfaces what changed since the last update. Promotions, company moves, expanded scope. A stale row isn’t just a refresh problem. It’s a signal-discovery moment.

Once Lusha is connected in Claude, the connector runs in the background — no special syntax needed. Just paste the stale list and run.

Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.

The prompt

Open in Claude Open in ChatGPT 
<context>
CRM records 12+ months untouched. Re-enrich and surface what changed:
not just refresh the fields, but flag contacts whose buying context has shifted.
</context>

<task>
1. Stale CRM list (paste with name, company, last-update date):
   [PASTE LIST]
2. For each contact, compare via Lusha:
   company on file vs Lusha's current employer,
   title on file (if any) vs Lusha's current title,
   job start date (when did they start the current role?),
   previous job (where did they come from?).
3. Output a re-enrichment table:
   Name | Was (company / title) | Now (company / title) |
   Job start date | Change type | Action.
4. Assign one change type per row:
   SAME: same company, same role, refresh the updateDate.
   PROMOTED: same company, new title or expanded scope (re-engage with first-90-days framing).
   MOVED: new company since the CRM record was created (update the row, re-engage at the new employer).
   DEPARTED: no current record (likely retired or off-grid, archive).
5. Summary at the top: total same, promoted, moved, departed.
</task>

<constraints>
- DEPARTED returns no credit charge.
- PROMOTED and MOVED are both signal events. Surface the job start date so the rep can time the re-engagement.
- Do not invent fields. If Lusha returns no match, the row goes to DEPARTED.
- Show the previous job inline when available. It confirms the trajectory and helps frame the re-engagement.
</constraints>

What you'll get back

Input: 4-row stale CRM list — records last touched between 12 and 18 months ago, mix of personas.

Output: 1 SAME, 1 PROMOTED, 1 MOVED, 1 DEPARTED. Below is the real result from running the prompt against the live Lusha connector.

ContactWas (CRM record)Now (Lusha verified)Job start dateChange type
Brian R.(unknown — older record)CFO at [cloud data platform]Sep 2025SAME — refresh row
Sean K.Other role at [cloud observability SaaS]VP of Enterprise Sales at [cloud observability SaaS]Jan 2026PROMOTED — re-engage
Namrata R.Head of Revenue Strategy and Operations at [productivity SaaS]VP of Revenue Strategy and Operations at [AI infrastructure SaaS]Jan 2025MOVED — update row, new employer
Tyler W.[customer messaging SaaS] (on file)No match—DEPARTED — archive

Names and company identifiers abbreviated for privacy. Full records (including company names, emails, and direct dials) are returned inside your Claude session.

The MOVED row is the most actionable. The CRM has the contact at her old employer. Lusha shows she moved to a new company 16 months ago, where she’s been a VP for over a year. The page surfaces both the old and the new record so the rep can update the row and re-engage at the right employer.

Three credits consumed for three matched rows. The DEPARTED row charged nothing.

Why use Lusha

B2B contact data decays at roughly 30% per year. After 12 months untouched, a CRM list isn’t a list anymore — it’s a snapshot of a workforce that has already moved. Three patterns emerge in every re-enrichment pass.

A PROMOTED row is a re-engagement signal, not just a field update. A contact who got promoted inside the same company unlocked a new mandate. The first 90 days of a new mandate is when budget gets scoped, vendors get reviewed, and stacks get rebuilt. The prompt flags the job start date so the rep can time the re-engagement against the mandate window.

A MOVED row is two rows. The contact left the company on file — that record in the CRM is dead. But the contact is alive at a new employer, often more senior, often in a different vertical. The prompt surfaces both sides: the old record to update, and the new record to re-engage. The CRM gets cleaner. The pipeline gets a fresh thread.

A DEPARTED row protects sender reputation. Lusha returned nothing because the contact is no longer in the verified workforce — retired, moved off the grid, or with no current employment record. The page routes the row to archive instead of pretending it can be revived. Lusha data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • How old does a CRM record have to be before this prompt is worth running?

    Twelve months is a useful floor — beyond that, the 30% annual decay rate guarantees at least one in three records has shifted in some way. Records older than 24 months almost always surface a PROMOTED or MOVED change. Records under 12 months are usually handled better by the CRM hygiene prompt.

  • Why does PROMOTED matter as a signal?

    A promotion unlocks the buyer’s mandate window. The first 90 days of a new title is when stack reviews happen, budgets get scoped, and adjacent vendors get evaluated. Catching a promoted contact in that window converts at multiples of generic outbound.

  • Can the prompt distinguish a real MOVE from a contact whose title changed because of a reorg?

    Yes. The prompt uses Lusha’s previousJob field — when the previous company differs from the current company, it’s a real move. When the company stays the same and only the title changes, it’s a promotion or lateral, and gets surfaced as PROMOTED instead.

  • What about a contact who changed companies multiple times?

    Lusha returns the most recent verified employment as the current record. The previousJob field shows the prior employer. The prompt surfaces both — older moves get flagged in the audit trail but the action focuses on the current employer.

  • Can I run this on contacts from a specific date range?

    Yes. Sort your CRM export by lastModifiedDate and paste only the rows older than your chosen threshold. The prompt processes whatever you paste.

  • How is this different from the CRM hygiene prompt?

    The CRM hygiene prompt is general — it checks current title, email confidence, DNC flags across any list. This prompt is specifically tuned for old records and surfaces the change events that matter for re-engagement. Use both: run hygiene quarterly, run this on the 12+ month segment yearly.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Get free access Read the Docs