More Resources
Prompt

Reactivate past product users who changed jobs

Tools: ChatGPT ▪ Claude ▪ Google Sheets ▪ Lusha ▪ Snowflake

Free trial and freemium signups that didn’t convert aren’t dead — they’re dormant. Most of those people left for reasons that had nothing to do with the product: wrong time, wrong budget, wrong company. This play checks your own product usage export against Lusha’s job-change signal, finds who moved somewhere new with budget and a mandate, and drafts a reactivation message that references what they already know.

Typical use case: Turn a lapsed free-trial list into a working priority queue, not a graveyard.

What is this play?

Reactivate Past Product Users is a Claude prompt that cross-references a company’s own product usage data against Lusha’s job-change signal. A person who tried your product before isn’t a cold contact — they already cleared the hardest objection outbound has to overcome. The moment one of them lands somewhere new with budget and a mandate, this prompt flags it and drafts the outreach.

What Lusha does

Lusha checks each name in your usage export for a companyChange signal, verifies the new company and role, scores it against your ICP, and returns a verified email and direct dial at the new company — all before a single message gets drafted.

Best for

  • Sales — Work a warm list instead of starting every quarter from zero.
  • Marketing — Feed reactivated names back into nurture with a real reason to reopen contact.
  • RevOps — Turn a static CSV of lapsed users into a recurring, always-on check.

Turn this play into action

1

Export your lapsed users

Pull free trial, freemium, or expired-license users from your product database, Snowflake, or a CSV/Google Sheets export.

2

Connect Lusha to Claude

One-time setup at claude.com/connectors/lusha.

3

Run the prompt

Paste your export and ICP in place of the bracketed fields.

4

Review and send

Check the Priority A and B list, review the drafts, and send.

 

The prompt

Open in Claude Open in ChatGPT 
<context>
I have an export of people who used our product before — free trial, freemium, or an expired license. I want to find the ones who changed jobs since, check if their new company is worth a conversation, and draft a reactivation message for the ones that are.

My product usage export (paste below):
[NAME, EMAIL, LAST KNOWN COMPANY, PRODUCT/PLAN USED, LAST ACTIVE DATE]

What I sell: [PRODUCT / SOLUTION]
My ICP: [INDUSTRY, COMPANY SIZE, GEOGRAPHY]
</context>

<task>
1. For each person in the export, use Lusha to check for a companyChange signal since their last active date.
   - If no job change: leave them in the export, don't chase further

2. For everyone who changed jobs, use Lusha to verify:
   - Current title and company
   - Whether the new company fits the stated ICP (industry, size, geography)
   - A verified email and direct dial at the new company

3. Score each mover:
   - PRIORITY A: new company is a strong ICP fit, verified contact available
   - PRIORITY B: new company is a partial fit, or contact needs a fallback (email only, no direct dial)
   - SKIP: new company is outside ICP entirely

4. For every Priority A and B contact, draft a reactivation message that:
   - References the product or plan they used before, specifically, not generically
   - Names the new company and role naturally
   - Makes one clear ask — a 15-minute look at what's changed since they last used it
   - Stays under 100 words

5. Return a table: Name, Old Company, New Company, New Title, Fit, Verified Contact, Priority — sorted A to B.
</task>

<constraints>
- Don't invent a job change. If Lusha finds nothing, the person stays in the "no signal" bucket, not Priority A or B.
- Don't draft a message for anyone without a verified email.
- The reactivation angle must reference actual prior usage — "since you used [X]" not "following up" or "checking in."
- If the new company can't be matched to a Lusha record, flag it for manual review rather than guessing fit.
</constraints>

What you'll get back

A RevOps lead pastes in 40 names from last year’s free-trial signups. One entry: Karen G., who tried the platform while in sales leadership at Ixxuit. Lusha’s job-change signal shows she moved — this record is real, pulled live on August 1, 2026.

Reactivation match — Karen G.

Old company: Ixxuit — Sales Leadership
New company: Jxxper
New title: Director of Account Management
Start date: March 1, 2026
ICP fit: Priority A
Verified email: k.g••••@jxxper.ai (masked for privacy)

“Karen — noticed you moved to Jxxper as Director of Account Management. Since you tried [product] while at Ixxuit, wanted to flag what’s changed for teams your size since then. Worth 15 minutes to see if it’s a fit for the new team?”

Cost to run: 12 Lusha credits for this demo — 11 to scan for job-change signals across the target companies, 1 to reveal the verified email. A no-match doesn’t charge, so scanning a full lapsed-user list stays cheap even at volume.

Data used

  • Job-change (companyChange) signal
  • Verified current title and company
  • ICP fit check against industry, size, geography
  • Verified email and direct dial

 

Why this works

Reactivation email usually opens with “checking in” because there’s nothing real to reference. A former user isn’t a cold contact — they already know the product works, which is the objection most outbound has to overcome before it can even start. Pairing your own usage data with Lusha’s job-change signal means the outreach can say “since you used this at your old company” instead of guessing at relevance.

FAQ

  • Either works. A CSV or Google Sheets export is enough to run this manually on a lapsed-user list. Snowflake or a warehouse connector makes it a recurring, always-on check instead of a one-time pull.

  • They get flagged SKIP and dropped from the priority list. The prompt doesn’t chase fit that isn’t there — a former user at a company outside your ICP isn’t worth the same outreach, even with the relationship head start.

  • A standard job-change play finds anyone who moved into your target persona, cold. This one starts from people who already have hands-on product experience — the pitch isn’t “let me introduce you to something,” it’s “you already know this works, here’s what’s new.”

  • Lusha resolves by name and last known company. A missing email doesn’t block the job-change check — it comes back as part of the new-company enrichment step instead of being confirmed upfront.

  • Monthly is enough for most lists. Job changes don’t spike on a predictable schedule, but a monthly sweep catches the window — first 90 days in a new role — while it’s still open.

Related Prompts

Ready to run this?

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

Start for free Read the Docs