The blog · Pipeline Strategy · From The Demand Compass · 6 min

How do you write outreach based on a buying signal without sounding creepy?

The signal decides which problem to open with; it never appears in the message itself, the difference between an opener that lands and one that feels like surveillance.

A ship easing through a night channel lit by a hidden lantern, only the light itself visible on the water ahead. Artwork from The Demand Compass.

The signal tells you which problem to open with, and it never appears in the message itself: not "we saw your job post," not "I noticed you visited our pricing page," none of it. A buying signal is evidence, and outreach that works reads the evidence, then leads with the problem it implies, without naming the thing that surfaced it. Openers built this way have pulled replies near thirty percent, against roughly [seventeen percent for a cold but otherwise qualified touch](/post/how-many-emails-should-a-cold-sequence-have), and the gap is not better copywriting. It is that the message arrived at the exact window the signal opened, without telling the reader you were watching for it.

Why does naming the signal backfire?

Naming the signal backfires because it tells a stranger you have been watching them, and the instant someone notices that, they pull back. "I saw your job post for a Head of Security" reads as surveillance, not insight, even though the sender meant it as proof of relevance. The problem is not that watching happened; every buying trigger worth acting on came from reading a signal closely. The problem is showing your work. A magician who narrates the trick while performing it ruins it; one who plainly knows something the audience does not, and never shows how, keeps the room. Signal-based outreach that works reads like someone who understands the reader's world, never like someone describing their own research process.

What should the message lead with instead?

The message should lead with the problem the signal implies, not the signal that revealed it, because the problem is the part the reader actually feels. A funding round sitting in a database is a company-level fact; the same round, caught fresh on an account that fits your profile, becomes a trigger, and the trigger's only job is to point you at a pain, a new budget with no plan yet for spending it, a board asking why the roadmap has not moved. Write the opener as if you already knew this person had that problem, because in a sense you did, not from watching them personally, but from reading what a role, a hire or an event usually means for whoever is now living inside it.

How did this play out on a real deployment?

The clearest version in our own case work is an In-Market account, high readiness, low awareness, meaning something was moving inside it before it had ever heard of us. A new security leader had just started at a fintech company, in a stretch when the sector had publicly learned what a breach costs, and the account's compliance and pricing pages were getting fresh visits. A stack-named job post pointed at the same story: a new In-Market leader, in a regulated industry, right after competitors nearby had been breached, almost certainly under pressure to prove control fast. The opener went to that leader and led with exactly that pressure. It never mentioned the job post, the page visits, or the fact that anyone had been watching at all.

The opener led with the pressure a new security leader inherits. It never named the job post that revealed it.

Sales still needed the whole chain of evidence, the new hire, the sector pressure, the page visits, the role that named the gap, and that trail traveled with the account to the rep so the follow-up could be specific too. The discipline was never to hide the reasoning from your own team. It was to keep it out of the first message a stranger reads.

30%reply rate on a signal-led opener that never names the signal
17%reply rate on a cold but otherwise qualified touch
3separate signal facts that shaped one opener without appearing in it

How should the message change for a VP versus a manager?

The message should change on altitude, not on the signal, because the same account often has two readers who need two different pitches. A VP or C-level buyer gets a short message pitched at outcomes and business consequences: what the board conversation looks like if this gap stays open. A manager or individual contributor gets the practical version: the specific task that gets harder every week it stays unfixed. Same account, same signal, same quadrant, still two emails, because a message written for the title above lands as noise on the one below, and the other way round.

ReaderMessage pitched atRegister
VP or C-levelOutcomes and business consequencesShort, senior
Manager or individual contributorThe practical problem they own day to daySlightly more detail

What happens if you skip this discipline?

Skip this discipline and the same signal that should have opened a door closes it, because a reader who feels monitored answers colder, later, or not at all, and a spooked account is often harder to re-approach next quarter than one you never touched. The failure is rarely the offer. It is the frame: naming the signal turns a relevant message into an alarming one, on an account that was, until that line, genuinely ready to hear from someone. Speed does not excuse it either. In-Market accounts move fast and the window is short, but a fast message that spooks the reader loses more time than a careful one that lands, because you do not get a second opener on an account that already flinched at the first.

Does this discipline change once the account replies?

It changes completely once the account replies, because the reader has now volunteered the conversation instead of having it opened for them. From that point the why-now can be named plainly if it helps the discussion, the timing, the pressure, the reason this matters this quarter, since a reader who wrote back is not the reader who pulls back. The discipline lives entirely in the first message, where the reader has not yet chosen to talk to you and every line either earns the reply or spends it.

Is it ever okay to name the signal directly?

Rarely, and mostly when the signal is public and mutual, a shared conference, a shared connection, something the reader already knows you both saw. Naming private behavior, a page visit, a scraped job post, works against you even when it is accurate.

Does this rule apply to LinkedIn as much as cold email?

Yes, and the shape of the gap is the same on both channels: an opener built on a signal but not naming it runs well ahead of one that announces the research behind it.

What if the reader asks how you knew to reach out?

Answer honestly once asked. The rule protects the opener, not a permanent secret. A reader who is curious enough to ask is not the reader who pulls back from feeling watched.

How do you train a team to write openers this way?

Hand writers the signal and the persona, never let the signal read as a fact to cite. Ask whether a stranger reading only the first two sentences cold could guess what triggered the message; if they can, rewrite it.

Does a signal-led opener still need to be personalized beyond the signal?

Yes. The signal earns the right topic; it does not write the sentence. The account, the role and the industry still decide the specific words.