All signal plays

Signal play / They came to you

A deal that went quiet

A deal you lost reaches the date it was meant to come back, or the person on it replies or books a meeting after the loss.

They already know who you are and once had a reason to talk. A deal lost on timing or budget is often worth a second look once that reason has moved, and the first message does not have to explain who you are.

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

Illustration
  1. Every lost deal carries a reason from a short list and a close date, and the reason sets when it may come back. A deal lost for poor fit never does.

  2. On that date, or sooner if the person replies or books a meeting, the deal joins one follow-up list in your CRM, freshest reason first.

  3. Customers, open deals, unsubscribes and anyone on your do-not-contact list come out before the list is ranked.

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.
When to act
Strongest in the first two weeks after it comes back, and it leaves the list after a month.
The examples
The examples are written for a made-up company that sells scheduling software to manufacturers.

The call, and the first message.

A rep on our payroll picks up the phone. 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
“When we last spoke, the schedule project was waiting on next year's budget, so I said I would come back once it was set.”

The question after it

“Is that budget set now, or has the plan moved?”

What our rep never does

Never makes them explain the project again from the start.

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

The first message, by Email

Illustration

When we last spoke, the timing was wrong because next year's budget was not set. Since then we have added a way to switch one plant at a time, so nothing has to change everywhere at once. Would that one change help now?

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 loss reasons may come back, and how long each one waits.
  • Which lost deals our rep may call, and which stay with the salesperson who owned them.
  • The call script and the first message, before anyone is contacted.
  • Each meeting, accepted or rejected against the written definition.

You keep

  • The loss reasons, the wait for each and the rules the list reads, in your CRM.
  • Every follow-up outcome on the person: a meeting, a reply, a new deal or a date to leave them alone until.
  • Every call note and outcome, written to your CRM with the signal attached.

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

  • Anyone who became a customer, has an open deal or asked to be left alone comes out first, however warm.
  • A lost deal with no person on it, or with an unclear reason, waits for a person to read it.
  • A person drops off the list after a month, so it never grows past what a rep can work.

How far we run it today.

We are setting this up in our own CRM now, from the guide we published. It is new, so there is nothing to report from it yet.

Our services that run it
RevOps, then BDR
What it costs
Each service has its own published price. See pricing
The guide behind it
The warm pipeline, the build written out step by step.

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