Follow champions who change jobs
Each week, champions at won accounts are checked for a new employer, the new company is scored on your ICP, and a warm deal opens with a note for the right rep.
- Starts
- Weekly schedule
- Steps
- 7
- Checks and gates
- 0
- A person decides
- Never, runs alone
Trigger · Schedule
Weekly schedule
Once a week the run reads every champion at your won accounts, so a move is a deal within days of the new badge photo.
Claude runs the rest autonomously
- 1
AI spots champions who changed company.
HubSpotHubSpot
Every contact marked a champion or an active user at a won account is checked against their current profile, and the ones with a new employer come back with the date of the move.
LinkedInLinkedIn
- 2
AI checks the new company in the CRM.
HubSpotHubSpot
A new employer that is already a customer, an open deal or a recent loss goes to that account's owner with the news, and leaves the list.
- 3
AI pulls what they achieved with you.
PostHogPostHog
What the champion's old account did with the product and what they said on calls come back as the material for the note.
GranolaGranola
- 4
AI judges the new company against your ICP.
The new company is scored on your own profile, and one that is not a fit is noted on the contact and not contacted.
- 5
AI chooses the owner from your territory rules.
Your own rules decide who takes the deal, the rep for the territory and segment or the old account's owner when a relationship travels with the person, and the rule is named.
- 6
AI finds the new email, drafts the note.
FullEnrichFullEnrich
The champion's new work email comes back from a waterfall, and a short note waits as a draft that names what they did with you last time and asks for twenty minutes.
GmailGmail
- 7
AI opens the deal, notifies both owners.
HubSpotHubSpot
A deal opens on the new company with the champion as its contact and the move as its source, and the new owner and the old account's owner each get a line.
SlackSlack
The person who championed your product at their last company just started at a new one. They know what it did for them, they have a budget to prove themselves with, and for about ninety days they are deciding which tools to bring in. Somebody on your team will notice the LinkedIn post a month from now, after the new company has signed with whoever was paying attention. Tracking job changes is the highest-converting source most sales teams have, and the one they run least, because it means re-checking three hundred profiles every week.
The profiles are on LinkedIn. The champions are in the CRM, marked as such on the deals they helped win. What they did with the product is in analytics, and what they said about it is in their calls. Your profile of a good customer and your rules for who owns which account are written down. The run reads them together once a week, and a move is a deal before the welcome lunch.
What you get
A champion who moves is a warm deal at the new company within the week, with the company scored on your ICP, the right rep on it under your own rules, the contact's new email found, and a note drafted from what they achieved with you last time.
What a champion's move is read against
The run opens once a week on every contact that HubSpot marks as a champion, a decision-maker or an active user at a won account. It reads:
- Their current profile, on LinkedIn: a current company that is not the account's company, started after the deal closed, is a move, with the new title and the date.
- The new company's history, in the CRM: a customer, an open deal or a recent loss on the same domain means the move goes to that account's owner instead of becoming a new deal.
- What they achieved, from PostHog and Granola: the old account's usage during the champion's time, and anything they said about the product in their own words on calls.
The new email comes back from the FullEnrich waterfall, the note is drafted in Gmail, and both owners hear about it in Slack.
What makes champion tracking hold up
The new company is scored before the person is contacted. A champion at a company outside your profile is noted on the contact with the new company and the reason, and left alone: the relationship is kept for their next move, and nothing is sold to a company you would not sell to. The score and the reason go on the deal for the ones that pass, so the rep knows why the company is worth their week.
The CRM is read first. A new employer that is already a customer, has an open deal or lost one in the last six months is not a new deal, and the only thing that happens is a line to that account's owner saying who just joined and from where. An owner who learns that a known champion has landed inside their stalled deal has the best news they will get that week, and a second deal on the same company would have hidden it.
The owner comes from your rules. Whether a relationship travels with the person or stays with the territory is a decision sales teams argue about, and the run does not take a side: it reads the rule you wrote, names it on the deal, and where none exists opens the deal with no owner and says so.
A note only you could write
The draft congratulates them in one line and names one specific thing they did with the product last time: a number from analytics, or their own words from a call. "You were running 1,400 reports a month on it by the end" is a sentence no competitor can send, and nothing about features follows it, only a request for twenty minutes. It is created as a draft from the rep the rules chose and never sent, and where no work email can be found it is drafted for LinkedIn instead.
The deal exists on the new company before the rep opens Slack, with the champion as its contact, the move as its source and the rule that chose the owner. The new owner gets the champion, where they came from, what they did and where the draft is. The old account's owner gets one line: their champion has left, and the account may need a new one.
The prompt
The real prompt behind the steps above, detailed enough that an agent with the same tools can run it as written. The Run buttons copy the full version, which also carries the steps for connecting those tools.
# Follow champions who change jobs
You have access to a CRM, LinkedIn search, product analytics, a
call-recording tool, an email enrichment waterfall, an email account,
and a messaging tool. Run this every week for **[every champion and
active user at your won accounts]**.
## 1. Spot champions who changed company
From the CRM, list every contact at a won account who is marked a
champion, a decision-maker or an active user: **[the contact roles or
properties your team uses for this]**. Keep their name, their account,
the account's owner and the deal they were on.
For each, read their current LinkedIn profile. A current company that
is not the account's company, with a start date after the deal
closed, is a move. Keep the new company, the new title and the start
date. A contact whose profile cannot be found is reported, not
guessed.
Only moves since the last run are new. Everything else was handled
the week it happened.
## 2. Check the new company in the CRM
Match each new employer against the CRM on its domain. If it is a
current customer, has an open deal, or lost a deal in the last
**[six months]**, the move is not a new deal: post one line to that
account's owner saying who just joined and from where, note it on
the contact, and take the move off the list.
## 3. Pull what they achieved with you
For each move that is left, read the old account's usage in product
analytics for the champion's time there: the features used most, the
volume, and any number that grew. Search the call recorder for the
champion's calls and keep anything they said in their own words about
what the product did for them.
This is the material for the note. A note that says "we worked
together" is a note anyone could send; one that says "you ran 1,400
reports a month on it" is one only you can.
## 4. Judge the new company against your ICP
Score the new company on **[your ideal customer profile: segment,
size, geography, and what disqualifies]**. A champion at a company
that is not a fit is noted on the contact with the new company and
the reason, and not contacted: the relationship is kept for when they
move again, and nothing is sold to a company you would not sell to.
Keep the score and the reason for the ones that pass.
## 5. Choose the owner from your territory rules
Read each move against **[your routing rules: territories by
geography and segment, named accounts, and whether a relationship
travels with the person or stays with the territory]**. Name the rep
and the rule. Where your rules say the old account's owner keeps the
relationship, the deal is theirs.
If no routing rules are written down, open the deal in step 7 with no
owner and say so in the message.
## 6. Find the new email, draft the note
Submit the champion's name and new company to the enrichment
waterfall and keep a verified work email. If none comes back, the
deal is still opened in step 7 and the note is drafted to be sent
through LinkedIn instead; say which.
Draft a note from the rep chosen in step 5: congratulations on the
move in one line, one specific thing they did with the product last
time, in a number or in their own words from step 3, and a request
for twenty minutes. Nothing about the product's features. **Create
it as a draft. Never send it.**
## 7. Open the deal, notify both owners
Create the deal on the new company, with the champion as its contact,
the move as its source, the ICP score and reason, and the rule that
chose the owner. If the company does not exist in the CRM, create it
with what step 4 found.
Post one message to the new owner: the champion, where they came
from, what they did with the product, and where the draft is. Post
one line to the old account's owner: their champion has left, and the
account may need a new one.
## Output
Report: contacts checked, moves found and since when, moves set aside
as already in play and the owners told, what was found for each
champion in analytics and on calls, the ICP score and reason per new
company, the owner chosen and the rule, emails found and missing,
the deals created, and the drafts waiting.
Why run it with Tulina
A prompt helps one person. A process moves a team.
Pasted into a chat, the prompt above works once, for whoever pasted it. In Tulina, "Follow champions who change jobs" becomes a process the team shares, that keeps its history, runs on its own, and stays inside the same security perimeter as the tools it calls.
The whole team works on the same one
PersonalTeamOrganisation
A process lives where it belongs: yours, your team's or the whole organisation's. Whoever runs it can improve it, and everyone starts from the best version instead of explaining the job again.
Every edit is a version
v1v2v3
Each change is a new version with the previous one kept, so a bad edit is undone by restoring an earlier one. Every run records the version it followed, and what a run teaches goes back into the process.
It runs without you
schedulewebhookon demand
A hosted agent runs the process on Tulina's own infrastructure, on a schedule or when an event arrives, and keeps going when you close the chat. Nothing to host. Every run is tracked to its outcome.
Inside the same security perimeter
vaultrolesrun log
Credentials stay in the vault, never in the prompt. Roles decide who may run what, every call is logged, and a step a person has to approve waits for that person.
Questions about tracking champion job changes
Also on HubSpot
Other processes that run mainly on HubSpot. The tools they share with this one are lit.
Expand accounts from usage
Each morning, accounts near a plan limit or on a feature their plan lacks get an offer priced on your packaging rules, an expansion deal and a drafted proposal.
- Shares
- PostHog, HubSpot, Granola, Gmail
Daily schedule7 steps →
Social listening to qualified leads
Every morning, competitor-post engagers and companies reading your site are matched to the CRM, qualified on your ICP, ranked by intent and handed to their rep.
- Shares
- LinkedIn, HubSpot, FullEnrich, Slack
Daily schedule7 steps →
CRM hygiene and prospect job changes
Weekly CRM data cleansing: duplicates merged with their history kept, prospects who changed jobs moved to their new company, and a recap posted to the team.
- Shares
- HubSpot, LinkedIn, Slack
Weekly schedule4 steps →