What to Do When a Buying Signal Fires
A signal is only useful if something happens next. A short routine for the first hour: who owns it, what to check, what to say, and what to write down afterwards.
5 min read
A signal that nobody acts on is a notification. What turns it into pipeline is a routine that is short enough to follow every time.
Decide Who Owns It Before It Fires
Every signal type needs one owner. If the account has an open deal, the signal goes to the person running the deal. If it is a customer, it goes to whoever manages the account. If it is new, it goes to whoever does outbound. Signals sent to a shared channel with no owner get a thumbs-up and nothing else.
Check Four Things First
Before writing to anyone, spend five minutes on context:
- Do you already know them? An open deal, a past conversation, a support ticket. The right move for a prospect is the wrong move for a customer.
- Is it a fit? Industry, size, and whether they could use what you sell.
- What exactly did they do? Which pages, how many people, over how many days.
- Who is the right person? The visitor may not be the buyer. If you only know the company, find the role that owns the problem.
This research is the part that is easiest to hand to an agent. It is the same four questions every time.
Match the Response to the Signal
This table is our suggestion, not a tested standard. Adjust it to what your own results show.
| Signal | A reasonable first move |
|---|---|
| Demo request or direct question | Reply the same day, with an answer and not a calendar link alone |
| Repeat pricing visits from a target account | A short, relevant note to the likely owner of the problem |
| Several new users in a trial | Help them succeed: a setup tip, an offer to answer questions |
| Usage spike in an existing customer | A check-in from the account owner about what they are building |
| Funding or a new executive | Wait a little, then write about the problem and not the news |
| One visit, no return | Nothing yet. Add them to a list and watch |
What to Say
Lead with something useful to them, not with what you saw. "I noticed you were on our pricing page three times this week" is accurate and it makes most people uncomfortable. The signal tells you when to write and what is probably on their mind. It should not be the opening line.
A good first note is three or four sentences: what you think they are trying to do, one specific way you help with it, and an easy next step. If the signal was documentation pages, write about the technical question. If it was pricing, be ready to talk about cost plainly.
Keep a person on the send. A draft written by an agent is a starting point. The person who knows the account decides whether the moment is right, and edits or drops the draft.
Check Permission Before Outreach
Knowing that a company visited is one thing. Emailing a named person there is another, and it has its own rules, which vary by country. Make sure the contact data you use was collected in a way that permits the message you are about to send.
Write Down What Happened
After each signal, record one of four outcomes: conversation, no reply, not a fit, or false alarm. It takes ten seconds and it is the only way to learn which signals are worth keeping. After a month you will have your own evidence, which is better than any published list. See How to Cut Noise From Buying Signals.
How Leapio Fits
In Leapio a signal can start an action. A notification goes to Slack, Discord, Telegram, email, or a webhook. Prospect Research writes a brief on the company and its contacts, Lead Qualification scores it against your ICP, and Outreach Draft writes a cold email and a LinkedIn sequence. Drafts are only drafts. Nothing is sent on your behalf, and each action checks the person's recorded consent before it runs. See Signals and Agents.