Weekly Lusha champion job change sweep for HubSpot customers

PromptCreate

Build me an agent workflow that runs every Monday at 7am and sweeps our HubSpot customer base for champion job changes, splitting the follow-ups between churn defense and expansion opportunities.

Step 1. Pull the champion list from HubSpot. Use HubSpot Search Contacts to fetch every contact flagged as a champion or primary customer stakeholder on an existing customer account. Filter on our champion property (or a specific lifecycle stage, whichever the user configures). For each contact, keep the current company, current title, contact id, associated company id, and the CSM/AE owner.

Step 2. Enrich in batches. Batch the contacts in groups of 100 and call Lusha Enrich People (Bulk) using LinkedIn URL when we have one, otherwise email. For each returned person, capture the current employer, current job title, and (if available) start date at the new role.

Step 3. Diff. Compare the company and title Lusha returned against what HubSpot has stored. If neither changed, drop the contact. If either changed, treat this contact as a job change and route into one of two branches.

Churn-risk branch. Fires when the champion has left a customer account (their new company is not the account they were tied to). For that contact: call HubSpot Update Contact with the new company, new title, and a job change date. Call HubSpot Create Task on the account's CSM asking them to identify a replacement champion inside the customer, with a due date a few days out. Call Slack Send a Message to post a churn-risk alert in the customer success channel that names the customer, the champion who left, where they went, and tags the CSM.

Expansion branch. Fires when the champion has landed at a new organization that is not already a customer. For that contact: call HubSpot Update Contact with the new company and title. Call HubSpot Create Task on the AE who owns that territory to run a reconnect play at the new account. Call Slack Send a Message to post an expansion alert in the sales channel that names the champion, their new company, and includes two or three warm-intro talking points based on their history with us. Finally, call Gmail Create a Draft to stage a personalized "congrats on the new role" reconnect email from that AE, referencing the champion's prior work with us and offering to catch up. The draft is not sent, only staged for the AE to review.

Step 4. Wrap-up post. After all branches are done, call Slack Send a Message one more time to post a leadership summary in an executive channel: total champions scanned, total job changes detected, split between churn-risk and expansion, and a short list of the highest-value moves. Leadership should be able to scan this in ten seconds and see the play is working.

Make the champion filter, the CS channel id, the sales channel id, the leadership channel id, and the email tone all easy to edit at the top of the workflow. Assume the user will want to tune these without touching the rest of the logic.

What does this prompt do?

Sweeps every champion and primary stakeholder on your customer accounts every Monday and re-verifies their current employer and title with Lusha.
Splits the follow-ups two ways: churn-risk plays when a champion has left a customer account, and expansion plays when a champion has landed somewhere new.
Updates the HubSpot contact with the new company and title, opens a task for the right CSM or AE, and posts an alert in the matching Slack channel.
For expansion opportunities, drafts a personalized "congrats on the new role" reconnect email in Gmail for the AE to review and send.
Closes with a Monday morning leadership digest in Slack that shows total job changes, split by churn risk and expansion opportunity.

What do I need to use this?

A HubSpot login with access to your customer contacts, and a champion flag or lifecycle stage you can filter on.
A Lusha account with credits available for people enrichment.
A Slack workspace with the customer success and sales channels you want alerts posted to.
A Gmail account for AEs so the reconnect drafts land in the right outbox.

How can I customize it?

Change the day and time of the sweep, for example run it every other Monday, or run a smaller Friday afternoon check.
Swap the filter that defines a champion, whether that is a custom HubSpot property, a lifecycle stage, or membership in a specific list.
Pick different Slack channels for churn-risk alerts, expansion alerts, and the leadership summary, and choose who gets tagged in each.
Adjust the follow-up owners, for example route churn tasks to the account CSM and expansion tasks to the AE who owns that territory.
Change the tone and length of the "congrats on the new role" Gmail draft so it matches how your team writes.

FAQs

How does the workflow know a champion changed jobs?

It compares the current company and title Lusha returns against what HubSpot has on file. If either one differs, the contact is flagged as a job change and routed into the right follow-up path.

What is the difference between a churn-risk alert and an expansion alert?

A churn-risk alert fires when your champion leaves a customer account, since the relationship inside the current account now needs a new sponsor. An expansion alert fires when that same champion shows up at a company that is not yet a customer, since it is a warm door into a new account.

Do I have to send the reconnect email automatically?

No. The workflow only drafts the message in the AE's Gmail. A human reviews and sends it, so the tone stays personal and no email goes out without a person signing off.

Will this update HubSpot records I did not want it to touch?

It only updates contacts that match your champion filter and only when Lusha finds a real change. You choose the filter, so contacts that are not champions are never rewritten.

Can I run this on Salesforce instead of HubSpot?

This starter is wired for HubSpot. If you use another CRM, start from a sibling prompt in the library or ask Geni to rebuild it against your system of record.

Related templates

Call overdue Xero customers with an AI collections agent

Every weekday at 10am, an AI voice agent phones your most overdue Xero accounts, logs what each customer promised, and reports back to finance in Slack.