Signal-Based Messages: Name the Consequence, Not the Signal
"Saw you're hiring 3 SDRs, congrats on scaling. We help teams like yours..."
That message has a signal in it. It is still spam.
This is the most common failure we see now that signal data is easy to buy. The targeting got better. The timing got better. The message stayed a template with a fresh fact glued to the front. Buyers read the fact, recognize the shape of the sentence that follows, and close the tab.
The fix is one line of thinking, and it moves reply rates more than any subject line test. Do not name the signal. Name what the signal costs them.
Why repeating the signal back fails
Three reasons, and they compound.
→ They already know. The prospect posted the job. They signed the funding announcement. Telling them a fact about their own week is not insight, it is a read receipt.
→ It proves surveillance, not understanding. "I saw you opened 3 SDR roles" tells the buyer you have a tool. It does not tell them you understand what happens next in their quarter.
→ It leaves you nothing to say next. Once the fact is spent, the only place a templated message can go is the pitch. The prospect feels the pivot coming from the second line.
Across more than 1500 campaigns, the pattern holds: an opener that recites a detail performs like no opener at all. The signal earned you the right moment to arrive. It did not earn you the reply. Those are two different jobs, and most teams have only done the first one.
The fix: name the consequence, not the signal
Every real buying signal implies a near-future problem. That problem is the message.
A signal is an event. A consequence is what that event does to the buyer's next 90 days. Write the second one.
Three steps:
- Name the event to yourself, not to them. Three SDR roles opened this month.
- Ask what breaks next. New reps arrive with no list, no signal source, and a ramp clock already running.
- Write that, then attach something that removes the problem today.
The prospect reads a sentence about their own next quarter, written by someone who has clearly watched this happen before. That is what personalization was always supposed to feel like.
Before and after, line by line
Before:
"Saw you opened 3 SDR roles. We help you scale outbound."
After:
"3 SDR roles open in a month usually means the tooling gap bites before the new hires ramp. I pulled a list of 200 companies in your space showing buying signals right now. Want it?"
Same signal. What actually changed:
→ The fact moved from claim to premise. "3 SDR roles open in a month" is no longer the point of the sentence, it is the setup for the point.
→ "Usually means" earns the voice. It says: I have seen this pattern more than once, here is where it goes.
→ The problem is specific and time bound. Not "scaling is hard." The tooling gap bites before the new hires ramp. A sales leader hiring three reps has already had that exact thought at 11pm.
→ There is no pitch. There is a thing they can have. The ask is "want it," which costs one word to answer.
On one of our own LinkedIn inboxes, this single shift took reply rates from under 1% to 42%. The list stayed the same. The signals stayed the same. The second sentence changed.
A consequence for every signal type
The mechanic only works if you know what each signal implies. This is the part teams skip, so here is the mapping we run across the five signal types.
Hiring signal. The company posted the job that means budget was approved. In our data, 73% of those roles go live within 30 days of approval, while formal vendor research usually does not start for another 60 to 90 days. The consequence: the buyer is committed and unequipped, inside a window that closes before procurement opens. Write to the gap between the hire and the ramp.
Competitor post likers. Someone reacted to a competitor talking about the exact problem you solve. The consequence: they are in evaluation mode and they are hearing one vendor's framing of the problem. Write to the part of the problem that framing leaves out.
Competitor post commenters. Stronger than a like, because they typed. The comment usually contains the objection or the use case outright. The consequence: they have one specific unresolved question. Answer that question and nothing else.
Competitor company followers. A quieter, longer lived signal. Following is research, not a moment. The consequence: they are building a shortlist and you are not on it. Write to the criterion they have not thought to compare on yet.
Influencer engagers. They engage with the voices your buyers read, which tells you the vocabulary they trust and the priority they have adopted. The consequence: they are trying to run a play they read about and have no data source for it. Offer the data source.
None of those five consequences mention your product. That is the test. If your consequence sentence only makes sense to someone who already knows what you sell, it is a pitch wearing a signal.
The four parts of a signal message that earns a reply
Structure it, and the message stops depending on how you feel that morning.
- Premise, one clause. The signal, stated flatly, as the reason you are here today. No congratulations.
- Consequence, one sentence. What this usually costs, in their language, on their timeline. This is the whole message.
- Useful object. A list, a teardown, a number, a source. Something with standalone value that you hand over whether or not they ever buy.
- One word answer ask. "Want it?" beats "Would you be open to a quick 15 minutes to explore synergies."
Four lines, under 60 words. Written this way against ICP filtered lists, we see roughly 55% acceptance and 30% replies on LinkedIn, against 20 to 30% acceptance and 5 to 8% replies on cold unfiltered lists.
Five ways teams put the signal back into spam
→ Congratulating. "Congrats on the raise" is the tell that the rest is a template. Cut it entirely.
→ Stacking signals to show off. Naming three signals in one message reads like a dossier. Pick the freshest one and write its consequence.
→ Making the consequence generic. "Scaling brings challenges" is not a consequence. If the sentence would fit any company on the list, it is a merge field.
→ Using your calendar as the useful object. Your calendar is not a gift. A list of 200 accounts showing signals right now is.
→ Sending late. A consequence named three weeks after the event is a problem they have already handled. Fresh signals or none.
That last one is the quiet killer. Most teams lose reply rate to latency, not to copy.
Making it repeatable without writing every line by hand
One good message is a craft exercise. Two hundred a week is a systems problem, and this is where signal based outreach usually dies. The consequence has to be written per lead, and nobody has time to read 200 accounts properly.
Two things make it survivable.
First, filter before you write. A strong signal from a company you cannot serve still costs you a message. In one recent run, 4,774 raw signal records came down to 341 worth a human sentence, which is 6.7%. Writing consequences for the other 4,433 would have been the entire week.
Second, let the per-lead reading happen automatically. B2B Signals ships every signal record with the context needed to write the consequence, and exposes the whole feed through MCP, so Claude Code or any MCP aware agent can pull today's ICP filtered signals and draft the four part message per lead, with a human approving what goes out. The reading gets automated. The judgment does not.
The signal gets you the timing. The consequence gets you the reply. Most teams have bought the first half and are still writing the second half like it is 2019.
Frequently asked questions
Is naming the consequence the same as personalization? No, and the difference is the whole point. Personalization usually means referencing a detail about the prospect. Naming the consequence means referencing a pattern you have watched play out after that detail. One proves you looked. The other proves you know. Only the second is worth a reply.
What if I get the consequence wrong? You will sometimes, and it costs less than you think. A specific, wrong consequence still starts a conversation, because the prospect corrects you, and "actually the bigger issue is X" is a reply that hands you the real problem. A generic opener gets silence, which teaches you nothing.
Does this work in cold email as well as LinkedIn DMs? Yes, with one change. Email needs the consequence in the first line, because the preview pane is the whole message. On LinkedIn you have a connection request and a first message, so the premise can sit in the request and the consequence can open the DM.
How fresh does a signal have to be? Inside two weeks for engagement signals, inside 30 days for hiring and funding. Past that, the consequence you are naming has usually been handled already, and you arrive as the person describing yesterday's problem.
Do I still need a strong offer if the consequence is good? Yes. The consequence earns attention, the offer earns the reply. A perfectly written consequence attached to "open to a chat?" still loses to a plain message attached to something the prospect actually wants.