All signal plays

Signal play / Seen in public

A champion changes jobs

Someone who bought from you, or nearly did, starts a new job at a company on your list.

They already know your product and trusted you once. Someone new in a role is expected to change something in their first months, and a call from a person they worked with is the warmest start there is.

How it is spotted.

In your own tools, not ours. The steps below run where the heading says, and what they find stays there.

From the signal to a call task

In your CRM and your Clay workspace

Illustration
  1. Your past buyers and users, and the people on deals that nearly closed, are taken from your CRM into one list to follow.

  2. Job changes are read from public sources and matched to that list by profile or work email, and a move to a company on your account list is kept.

  3. The person on your team who worked with them gets a call task in the week the move is announced, with the new role and the history attached.

What this shows: where this signal is read and where it lands. Both are in tools in your name.
What this page is
A signal play: one thing that happens at a company on your list, and what we do about it, from spotting it to the call.
The examples
The examples are written for a made-up company that sells scheduling software to manufacturers.

The call, and the first message.

The person on your team who worked with them, not our rep. This is the line the call opens with, the question that follows it, and the written message that goes beside it.

The first line of the call

Illustration
“I heard you moved to a new company, and since we worked on the schedule rollout together, I wanted to call you myself.”

The question after it

“What are you finding in how the new plants schedule their work?”

What they never do

Never pitches before asking how the new job is going.

Your yesWaits for you: the call script and the first message, before anyone is contacted.

The first message, by LinkedIn

Illustration

Heard you moved to a new company, congratulations. When we worked together on the schedule rollout, the hard part was getting the plants to trust the numbers. Is that the same at the new place?

Held to our own message rules: three sentences at most, a question, no link and no pitch.

What waits for your yes, and what you keep.

You approveYour yes

  • Which past buyers and users are followed, and who on your team owns each one.
  • The call script and the first message, before anyone is contacted.
  • Each meeting, accepted or rejected against the written definition.

You keep

  • The list of past buyers followed, in your CRM.
  • Every move, written to both the old account and the new one.
  • Every call note and outcome, written to your CRM with the signal attached.

Where it goes wrong, and the rule that stops it.

  • The call comes from someone they worked with. A past buyer is never called cold by a stranger.
  • A person is matched by profile or work email, never by name.
  • The old account is not dropped. It stays on your list, with whoever replaced them.

How far we run it today.

When one of our own past buyers changes jobs, the person here who worked with them makes the call. For clients, the move is tracked in the signal feed and the call goes to the person who knew them.

Our services that run it
GTM engineering, then RevOps
What it costs
Each service has its own published price. See pricing

The other signal plays.

Have us run this play for you.

We run it with your team, in tools you own. You approve the script before anyone is called.

Or skip the form