More Resources
Prompt

Flag promoted champions ahead of renewal

Tools: Claude ▪ Lusha

Champion departure gets watched closely, and for good reason — it’s a real renewal risk. Champion promotion gets almost no attention at all, even though it’s arguably the more common event and a genuinely positive one. A champion who’s been promoted since signing usually has more authority, a bigger budget, and a stronger internal case for renewing than they had a year ago. That’s worth walking into the renewal conversation already knowing, not discovering when they mention it. Connect Lusha to Claude and this prompt checks your customer base for champion promotions and flags them ahead of the renewal date.

The prompt

Here are my customer accounts and their champion contacts: [paste
account names and champion names].

Using the Lusha connector, check whether any champion has been
promoted in the last 180 days. Return a table with account name,
champion name, previous title, new title, and promotion date.

Then flag which accounts have a renewal date in the next 90 days,
since a recent promotion is most useful right before that
conversation.

Finish with a one-line renewal talking point for each flagged account
that references the champion's new role.

What you’ll get back

The situation: a CSM pastes 25 customer accounts with their known champion contacts and asks for a promotion check ahead of Q3 renewals.

The output:

Example output

Checked 25 accounts: 5 champions promoted in the last 180 days

[Company Y]: R.D. promoted from Director to VP, 45 days ago. Renewal due in 60 days — flagged.

[Company Z]: M.K. promoted from Manager to Senior Manager, 120 days ago. No renewal in the next 90 days — noted, not urgent.

Three more with the same structure.

Renewal talking points: for [Company Y] — “R.D.’s promotion to VP puts budget authority for this renewal fully in their hands, worth a direct conversation about expansion, not just renewal.”

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 account list to see live results.

Why it works

This is the direct mirror of the existing champion-departure play, built for the opposite event. Departure tracking exists because everyone accepts it’s a real risk; promotion tracking is worth exactly the same discipline, because it’s a real, underused opportunity signal that almost nobody checks for on purpose. Tying it to the 90-day renewal window is what turns “nice to know” into “worth acting on” — a promotion flagged six months before renewal is forgettable, one flagged a month before is a real talking point. Contact and company data is verified across multiple sources and handled under GDPR, CCPA, SOC 2 Type II, and ISO 27701 compliance.

FAQ

  • How is this different from the champion-departure play?

    Same underlying mechanic, opposite trigger. That play watches for a champion leaving, a risk signal. This one watches for a champion being promoted, a positive signal. Run both on the same customer base for the full picture.

     

     

     

  • Why the 180-day promotion window?

    Wide enough to catch a promotion that happened between renewal cycles, not just in the final weeks. The 90-day renewal flag is what narrows it down to what’s actually actionable right now.

  • What if the promoted champion left the account entirely?

    That’s a same-company promotion signal specifically — a move to a new employer is tracked separately under the Job changes signal. If a former champion shows up as having left the company, that’s a different play (find the new champion) entirely.

  • Can I use this for expansion conversations, not just renewal?

    Yes — a promoted champion with new budget authority is often a stronger expansion conversation than a renewal one. The talking point the prompt generates works for either framing.

     

  • Is tracking promotions like this compliant?

    The prompt reads business-profile changes — title and role history — the same public professional information visible on a profile. Lusha’s data is professionally sourced and opt-outs are honored automatically.

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