Reading Purchase Intent Signals Before You Send a Cold Email

Not every company on an ICP list is equally worth a message this week. Purchase intent signals — trigger events that correlate with a company actively evaluating a solution — are how a small cold outreach operation decides which accounts jump the queue, and just as importantly, what to actually say to them once they're being contacted.

What makes a signal a signal

A purchase intent signal is a publicly observable event that correlates with a company being more likely to evaluate a solution in the near term. The key word is correlates — no single signal proves a buying decision is underway, and treating any one of them as certainty leads to overconfident messaging that reads oddly when the assumption turns out wrong. What signals are genuinely useful for is triage: given a list of qualified accounts, which ones have some evidence of active urgency right now, versus which ones are equally good fits on paper but show no sign of near-term motion.

For B2B cold outreach specifically, the most useful signals are the ones observable without a paid data feed, because they're verifiable, current, and specific enough to reference directly in a message rather than sitting behind an opaque vendor score.

It's also worth distinguishing purchase intent signals from broader interest signals. Someone downloading a generic industry report shows category-level curiosity; a company posting three roles for a function your product directly serves shows something closer to committed resourcing behind a real initiative. Both are technically signals, but they don't deserve the same weight in a prioritization decision.

The signal categories worth tracking

A handful of trigger types show up consistently across B2B categories, though which ones matter most depends on the specific product and problem being solved.

• Hiring patterns: multiple postings for a specific function in a short window, often the clearest available proxy for a team investing in a problem right now
• Funding and financial events: a new funding round, especially one explicitly earmarked for a function relevant to the offer
• Leadership changes: a new hire in a role that owns the buying decision, since new leaders commonly re-evaluate existing vendor relationships in their first months
• Technology and tool changes: evidence a company added, removed, or is evaluating a tool in the relevant category, visible through website technology footprints
• Expansion events: new office openings, entering a new market, or headcount growth crossing a threshold that typically strains existing processes
• Public statements: earnings calls, press releases, or executive interviews naming a specific initiative the product supports

Function-specific beats company-wide

A company-wide hiring spike is weaker evidence than a spike concentrated in the specific function the product serves. A logistics-software vendor should weight three warehouse-operations postings far more heavily than fifteen postings across sales, marketing, and engineering combined — the general spike says the company is growing, which is mildly useful context; the concentrated spike says a specific team is actively under-resourced for the exact problem being pitched, which is a much sharper reason to reach out now.

This is worth building into however signals get scored or filtered: a rule that only counts postings, funding language, or tool changes tied to the relevant function will surface a shorter but far more actionable list than one that treats any growth signal as equally strong.

Corroboration over single-signal confidence

Any single signal has a real false-positive rate. A job posting can be a replacement hire rather than growth. A funding round can be earmarked for something unrelated to the product's category. A tool change on a website can be a redesign artifact rather than a real switch. Requiring two independent, corroborating signals before treating an account as genuinely high-intent — a hiring pattern plus a recent funding round, or a leadership change plus a visible tool-stack shift — cuts false positives substantially without adding much delay, since most of these signals are checkable within minutes.

This corroboration step is also what keeps the exercise honest as a prioritization tool rather than an excuse to contact every account that shows the faintest flicker of activity, which just recreates broad, low-precision targeting under a more sophisticated-sounding label.

A practical way to apply this without overthinking it: treat a single signal as a nudge that moves an account up modestly in a review queue, and reserve top-priority, fastest-cadence treatment for accounts where a second, independent signal shows up within a reasonably tight window — a few weeks, not a few months apart.

Building a simple scoring habit around signals

A workable signal process doesn't need a formal scoring model to be useful. A simple weekly routine — scan the active account list for any new signal since the last check, log it with a date and source, and bump an account's priority when two signals stack up — captures most of the value without building anything elaborate. Teams that try to formalize this too early often end up maintaining a scoring spreadsheet nobody trusts more than their own judgment anyway.

What matters more than the scoring mechanism is consistency: checking the same list on the same cadence, so a signal that appeared three weeks ago and was never acted on doesn't sit invisible until someone happens to notice it. A missed signal is a missed reason to prioritize an account that was already worth contacting — a small, avoidable loss that adds up across a full pipeline.

Turning a signal into the message, not just the queue position

The biggest missed opportunity with intent signals is using them purely to decide send order and leaving them out of the message itself. A signal specific enough to reference directly — 'noticed you've posted three ops roles this month' — does more for reply rates than the same email sent to the same account without that line, because it's concrete evidence the message wasn't sent to a purchased list at random. Vague signal references ('I see you're growing') undercut the credibility the specificity was supposed to buy.

Signals also decay differently — a hiring posting is often stale within a month as roles get filled, while a funding round can stay relevant for a couple of quarters given typical deployment timelines. Tracking a rough shelf life per signal type prevents an opener from referencing something the prospect would recognize as old news.

One more distinction worth holding onto: a signal earns a place in the opener only when it plausibly connects to the actual problem being pitched. A funding round is a weak hook on its own — funding for what, spent on what, is the real question — and works far better when it's paired with a second detail, like a specific new hire or initiative the funding is visibly supporting, that makes the connection to the offer concrete rather than implied.

FAQ