Looply

Signal × ICP × role playbook

Job change signals in HR technology: a Sales Development playbook

job change playbook for HR technology and Sales Development: evidence, qualification, messaging, compliance, and measurement.

Written by Benjamin GouleauVisible methodology and sources

Direct answer

A job change signal becomes actionable in HR technology only when it is current, attributable, and connected to prioritizing the right accounts, earning replies, booking qualified meetings, and protecting sender reputation. First verify a verified public role transition with the person, company, title, and effective date aligned, then confirm workforce size, hiring or retention pressure, HRIS environment, process owner, and a measurable employee or recruiter outcome.

Why HR technology context matters

people systems are evaluated through employee lifecycle impact, sensitive-data handling, adoption, integrations, and change management.

What the signal does not prove

a job change is not purchase intent by itself; avoid congratulatory pitches and exclude ambiguous or historical employment updates.

more activity is harmful when data, relevance, pacing, suppression, or handoff quality is weak.

Quality before volume

Five checks before any outreach

01

Evidence

Signal proof: a verified public role transition with the person, company, title, and effective date aligned.

02

Fit

Industry fit: confirm workforce size, hiring or retention pressure, HRIS environment, process owner, and a measurable employee or recruiter outcome.

03

Ownership

Role ownership: verify that Sales Development owns prioritizing the right accounts, earning replies, booking qualified meetings, and protecting sender reputation.

04

Exclusion

Exclusion: exclude accounts with no relevant workforce process, unsupported employee geography, or no plausible implementation owner.

05

Caution

Signal-specific caution: a job change is not purchase intent by itself; avoid congratulatory pitches and exclude ambiguous or historical employment updates.

Controlled execution

From signal to attributable outcome

01

Capture

Capture the source, date, entity, and evidence that proves the job change.

02

Qualify

Apply the HR technology ICP and remove accounts that fail the fit or exclusion test.

03

Assign

Select Sales Development only when public remit evidence aligns with prioritizing the right accounts, earning replies, booking qualified meetings, and protecting sender reputation.

04

Frame

Frame a hypothesis, not a conclusion: confirm the new remit and wait until the role is active before testing whether the buyer owns the relevant problem.

05

Test

Run a small cohort with suppression, controlled pacing, and an immediate stop for opt-outs.

06

Measure

Attribute qualified replies, held meetings, trials, and paid customers to the cohort and original signal.

Contextual template

A message that separates evidence from hypothesis

Customize this

Hi [First name] — I noticed [verified job change evidence]. In HR technology organizations, that can make [specific workflow connected to prioritizing the right accounts, earning replies, booking qualified meetings, and protecting sender reputation] worth reviewing. Is that currently in your remit? If so, I can share a short way to test [measurable outcome] without replacing the entire workflow.

Decision standard

Measure value, not activity

  • Share of accounts retained after signal proof, ICP, role, and exclusion checks.
  • Valid contacts, bounces, opt-outs, and negative replies by cohort.
  • Qualified replies and held meetings rather than opens or sends alone.
  • Activated trials, accepted opportunities, paid customers, and attributable revenue.
  • Operator time and total cost per qualified outcome.

Compliance and deliverability

A signal removes none of the obligations

Document the source and purpose, minimize personal data, keep the message professionally relevant, provide a clear opt-out, and maintain suppression. Authenticate domains, control pacing, and follow the mailbox provider’s current sender requirements.

FAQ

Questions before launching the cohort

Is a job change proof that Sales Development is ready to buy?

No. It is a reason to verify timing and relevance, not proof of purchase intent. Confirm current evidence, HR technology fit, role ownership, and an actual problem before outreach.

What evidence should be stored for a job change?

Store the source URL, publisher, observation date, entity, extracted fact, confidence, and any corroborating source. Keep the original wording separate from your commercial hypothesis.

How should this playbook be tested in HR technology?

Use a small, representative cohort, document exclusions, keep the offer and follow-up window stable, and compare qualified replies, held meetings, trials, paid customers, cost, and operator time.

What should disqualify the account?

exclude accounts with no relevant workforce process, unsupported employee geography, or no plausible implementation owner. Also stop when the signal is stale, ambiguous, incorrectly attributed, or unrelated to prioritizing the right accounts, earning replies, booking qualified meetings, and protecting sender reputation.

Official sources

Verified standards used by this playbook

Explore the corpus

Test before scaling

Turn one verified signal into a measurable cohort.

Looply connects source, ICP, contact, campaign, reply, and attribution without turning a hypothesis into fabricated intent.