When to run this play
Run this when a person has publicly started a role that owns a problem you help with, or when a known champion has moved and you are sure about the new company. Leadership changes use the same steps plus a required second fact.
Qualify before anyone writes
- Two sources agree, or one source is the company or the person and it is recent.
- The company fits. A big title at the wrong company is not a lead.
- You are not implying a relationship that belongs to a previous employer.
- For executive roles, a second public fact about the programme is on the record.
Sample sequence
Example TWL Reach sequence for planning. It is not a customer result, a script to paste, or permission to contact someone you have no business contacting.
- Day 0 · LinkedIn. Name the role and one part of the job from the source. Ask if it is a this-quarter priority. Skip “congrats” as the whole message.
- Day 3 · Email. The same point in slightly more detail, with the source named so they can see you did not guess.
- Day 9 · Email or LinkedIn. Only if you have a new public fact. Otherwise stop. A bump with no new fact is how these sequences feel automated in the worst way.
Keep the agent controllable
Wrong-company errors are obvious. The workflow refuses to send when the company on the person and the company on the signal differ.
The agent prepares the brief. A human approves executive notes. Practitioner notes can move to sampled review after the team has seen the pattern.
Keep reading
Questions people ask
How is a champion move different?
You may refer to a real past conversation. You may not tell the new company they are already a customer, and you may not pressure the person to introduce you on day one.
What if the headline is stale?
Do not send. Stale headlines are common. The qualify list is there to catch them.
Which signal pages apply?
New hires and job changes, and leadership changes for the executive case.
Does this replace a job-change data provider?
No. It is the operating play once you have a source. It does not promise a feed.
Put the next workflow on the stack.
Start with the tool you need. Connect signals, TWL Reach and the rest of the system when the job is real.
Get TWL