A former customer champion starts a new job, and your team spots the announcement. You already have something useful: a real relationship with someone who understands your product. The temptation is to congratulate them, assume they want the same software again, and drop them into a sequence. That skips the question that determines whether this opportunity deserves your time: does their new company have the problem your product solves?
Build a small outbound motion around answering that question. Use the job change to choose whom to research, the new company’s operating conditions to shape your message, and the buyer’s response to decide what happens next. For a founder with an existing customer base, this is a manageable way to make cold email, cold calling and LinkedIn work together. The relationship may be familiar, but the buying situation is fresh. Treat it with the same care you would give a new account.
Selection
Start with people whose experience with your product you can verify. A champion advocated for the purchase, helped introduce it internally, or regularly worked with your team to get value from it. An executive whose name appears on an old contract may have had very little involvement. Ask whoever owns the customer relationship to distinguish active advocates, regular users and nominal sponsors. For your first batch, prioritize people who would recognize the founder’s name and remember a substantive conversation. Also check whether their previous experience ended well; an unresolved support issue deserves attention before a sales approach.
Then check the destination company against your current GTM Strategy. Suppose, as an illustrative example, you sell invoice approval software to multi-site distributors. A former finance champion moving to another distributor could be relevant. The same person moving to a small consultancy may have little need for your product. Their new title also matters: someone who previously owned accounts payable might now lead investor relations. Familiarity helps you earn attention, while company fit and current responsibility determine whether you have a useful commercial conversation.
For a first pass, review 20 former champions and select up to five verified moves. These are example batch sizes chosen to keep manual review manageable. Give every candidate a simple decision: contact, investigate or exclude. Exclude poor-fit companies, people who have asked you to stop contacting them, and relationships your customer team considers sensitive. A departure may also leave your existing customer without an internal owner, so assign someone to protect that relationship separately. Your outbound opportunity should have a clear owner without distracting from an account that already depends on you.
Evidence
Keep a short evidence record for each selected person. Capture their previous relationship with your company, current employer, current role, announcement date, source link and the reason their new company might fit. Record when you last checked those facts. A public job announcement can be useful evidence, but an enrichment result alone can be stale or mismatched. Verify the move through a current company page or the person’s own profile before sending a message. Record the actual start date separately when it is available; an announcement published yesterday may describe a move from months ago.
Separate facts from hypotheses in the account note. In the invoice approval example, “Alder Tools operates six distribution sites” might be a verified fact. “Approvals could be spread across site managers” is a hypothesis. “The finance team is struggling to close the books” requires direct evidence. Your outreach should preserve those distinctions. You can ask whether site-level approvals create extra follow-up, but you should avoid asserting that the new finance leader has inherited a broken process. That difference makes the message credible and gives the recipient an easy way to correct your understanding.
Use automation for the clerical work: flag possible job changes, deduplicate records and assemble links for review. If an AI tool drafts the account note, require it to attach a source to every factual claim and mark unknowns explicitly. Keep a human approval step before enrollment. Use approved business contact data, honor existing suppression records, and check the rules that apply to the recipient’s jurisdiction and each channel. A public profile or a previous relationship does not automatically establish permission for every form of outreach. Your team should know which contacts and channels it can use before the sequence starts.
Message
Have the founder send the first message when they genuinely know the person. The value comes from remembered context and the founder’s ability to discuss the problem directly. A founder signature attached to an unfamiliar sales pitch adds little. Reference the relationship briefly, then spend the rest of the message on the new situation. Avoid sharing the previous employer’s pricing, usage, internal challenges or results. Even when those details would make a persuasive story, the recipient should feel confident that you handle customer information carefully.
Here is an illustrative email for a founder who previously worked directly with Maya, a finance leader now at the fictional company Alder Tools. The reference to multiple sites should be verified before sending. Adapt the sender details and required disclosures to your own business and applicable rules.
Subject: Invoice approvals at Alder Tools
Hi Maya, congratulations on your move to Alder Tools. I enjoyed working with you on invoice approvals in your previous role.
I saw that Alder operates across several sites. Are invoice approvals part of your remit there, and have you had a chance to review how they reach finance?
If that review is coming up, I can send a short checklist for finding where approvals wait on an owner.
If you would prefer no further outreach from me, please say so and I will update our records.
[Founder name], [Company], [Business address]
Create the promised checklist before sending the email. Keep it to one page and make it useful without a product demonstration. For this example, ask the buyer to inspect ten invoices awaiting approval, identify the current owner of each, record how long each has waited, and check whether finance can see the next action. Those are illustrative inspection steps, rather than a benchmark or promised result. The offer gives Maya a practical reason to respond while letting her decide whether the problem belongs on her agenda.
Sequence
Use a short sequence with one owner and a shared activity history. The following ten-business-day schedule is an example operating choice, not a claim about optimal timing. Apply it only where each channel is appropriate and permitted. The founder handles replies and any live conversation during the initial batch; an operator can manage research, reminders and CRM updates. Before every scheduled touch, check for a reply, a customer-team conversation or a suppression request. One person responding on LinkedIn should stop an email that would make the founder appear unaware of the exchange.
- On business day one, send the email with one question about the buyer’s current responsibility and one useful offer.
- On business day three, make one manual call to an appropriate business number, if available and permitted, to check whether the topic is relevant.
- On business day six, use LinkedIn for a brief personal message if your connection status and the platform’s rules allow it. Keep the same business context.
- On business day ten, send a final email saying you will leave the topic there and that the checklist remains available if useful.
On the call, make the context explicit: “Hi Maya, this is Sam from [Company]. We worked together on invoice approvals in your previous role. Have I caught you with a minute to check whether that falls within your remit at Alder?” If she has time, ask how approvals work today and whether anything needs attention. On LinkedIn, refer briefly to the email and ask whether she would like the checklist there. Every touch should help establish relevance or offer the promised help. Stop the sequence when she replies, opts out, or indicates the topic is outside her responsibility. Silence at the end means closing this attempt.
Decisions
Define reply handling before the first send. “Send the checklist” means permission to deliver the checklist. It gives you a useful next interaction, but the buyer has yet to confirm a project. Send the resource promptly and ask one relevant question, such as, “Can your finance team currently see who owns each pending approval?” If the buyer describes an active problem, offer a short working conversation to map the current process. If they say they are still settling in, ask whether a specific follow-up date would suit them. Record an agreed date instead of assigning one on their behalf.
Keep the CRM simple enough that the founder will use it. Track the verified move, fit hypothesis, channels permitted, outreach owner, last touch, response category and next action. Useful response categories include wrong owner, no current need, review planned, active problem and do not contact. Keep unanswered outreach separate from qualified opportunities. Create an opportunity when your qualification criteria are met, such as a confirmed problem, a responsible buyer and an agreed next step. This RevOps discipline helps you see which conversations deserve attention without turning every friendly reply into forecasted revenue.
At the weekly review, count accounts contacted, substantive replies, confirmed problems and agreed next steps. Review the actual replies beside those counts. With a small batch, a percentage can swing sharply after a single response. The language buyers use will often be more useful: perhaps new finance leaders delegate approvals, or perhaps your company-size filter admits businesses with very simple processes. Change one part of the motion based on that evidence. You might tighten targeting, revise the diagnostic question or improve the checklist before adding another channel or increasing volume.
Launch
This week, assign one person to prepare the batch and one founder to own the conversations. On Monday, review 20 former champions and identify up to five verified, suitable moves. On Tuesday, confirm current responsibilities, check contact permissions and suppression records, and write a factual account note for each person. On Wednesday, finish the one-page diagnostic and have the founder review every opening message. Send only the messages you can support with verified context. Schedule subsequent touches in business days, with a reply check before each one.
On Friday, review research quality, any early replies and the time required to operate the batch. The sequence will still be running, so reserve conclusions about response quality until it finishes. Afterward, decide whether to repeat the same motion, change one assumption or pause it. The aim is a repeatable decision process: recognize a credible opening, test whether the problem exists, and follow the buyer’s answer. A former champion’s new job gives you a reason to reconnect. Your execution determines whether that reconnection earns a useful next conversation.