Enrollment

Auto-enroll job changers

The SDR does not pull a list. The job-change row is already in the sequence when they look.

The loop

  1. 01Watch a named list, not a weekly CSVCustomers, closed-lost, engaged. Recheck title and company on a schedule.
  2. 02Re-fit the new company before you spendIf the new logo is not ICP, stop. Do not enroll every mover.
  3. 03Enrich the new work email on the same rowNew domain, new title. Old address is a bounce waiting to happen.
  4. 04Auto-enroll into a job-change sequenceInstantly or the CRM cadence. Never “congrats on the new role.”
  5. 05Slack the owner after they’re already inThe SDR does not pull a list. The lead is already in the sequence when they look.
linkedin.com ↗The lead is already on the desk.GTME / SDR sync: the job-changer workflow puts a lead in front of the team. The SDR’s line — “an agent just does it” — is the enrollment loop. No campaign number published.

Florin’s Common Room play is context: former champions, job listings at the new company, a reason to meet. Benyamin Holley’s job-changer workflow is the opposite job — make the lead appear in front of the SDR without anyone exporting a CSV. In the GTME / SDR sync he walked, the punchline was the point: “an agent just does it.” The system that puts the row on their desk is the playbook.

Watch a named list. When title or company flips, re-fit the new logo, waterfall the new work email on the same row, and enroll into a job-change sequence — never “congrats on the new role.” Slack the owner after they are already in the cadence. If the new company is not ICP, the row dies there. No published reply rate. The product is the enrollment, not a congrats email.