The category’s favourite product is a score that says an account is “showing intent.” When the reader is a CEO, a CFO, or an investor, that guess isn’t just weak — it’s a liability. This is the case for verified signals in C-level lead generation, and a working definition you can hold any vendor to. Including us.
The promise is to know what a company wants before the company says so. The mechanics are less mysterious: aggregated page visits on publisher networks, topic “surges” scored against a baseline, lookalike models trained on someone else’s customers. Each step is a reasonable statistical operation. Stack them, and what lands on your desk is an average of averages — wearing a percentage.
None of this is fraud. It’s inference, and inference has legitimate uses: sizing a market, prioritising a territory, deciding where to look first. The trouble begins at the exact moment a guess is asserted as a fact — when “this account scored 78 on data infrastructure” becomes the opening line of a message to its chief executive. The model never promised that. The vendor’s dashboard just made it easy to forget.
B2B outbound built on that forgetting has a distinctive smell, and senior people have learned it. They can’t see your data pipeline — but they can see that your first sentence is about something that never happened.
A verified signal is a structural event at an account — a leadership change, an acquisition, new funding, a regulatory shift, a product launch — confirmed against a primary source and carrying the date it was confirmed. Three parts: the event, the source, the date. Remove any one and it isn’t verified. It’s inferred.
The distinction is not a matter of degree, and it can’t be fixed with a higher confidence threshold. A 95% guess is still a guess; the recipient experiences the remaining 5% as a lie. A verified signal, by contrast, can be checked — by you, before you approve the send, and in principle by the person who receives it.
What the score is actually made of.
What a checkable claim is made of.
A primary source is published by someone accountable for the fact. Everything else is an echo.
The acquirer announcing the acquisition; the board announcing the appointment.
Ownership changes, funding events, and structural moves leave paper. Paper has dates.
A letter to shareholders, a keynote, a signed announcement — statements the person stands behind.
Useful for finding the trail — never the end of it. The test is simple: can you click through to the artifact, read it, and see its date? If the trail ends at a database, you are holding an inference.
Here is the uncomfortable arithmetic of guessing. When an inferred hook happens to be right, the reader can’t distinguish it from luck — you collect, at best, a reply you would also have earned with a verified claim. When it’s wrong, the cost is not one deleted email. It’s the account.
This asymmetry sharpens with seniority, which is why it decides C-level lead generation in particular. An operator who reads thirty pitches a week pattern-matches errors in a single line — the congratulations on a role she left, the “initiative” his company never had, the funding round that closed two years ago. Executives don’t file a bad cold email under “try again later.” They file the sender.
So the volume logic collapses at altitude. At the top of an enterprise account there are a handful of people who can say yes, and each of them can only be approached for the first time once. Guessing spends an unrepeatable moment on an unverified claim.
A first impression at C-level is a non-renewable resource. Spend it on something that happened.
Verification has a second job, quieter than the first: it makes quality enforceable. If every claim in a sequence carries its source and its date, an approval gate means something — the person giving the final yes can check the work instead of trusting the vibe. If claims arrive as scores, approval degenerates into theatre. You’re signing off on a feeling.
The same evidence trail works in reverse. When a sequence performs — or embarrasses — you can read back exactly what was claimed, on what basis, and when. That read-back is what turns outbound from a black box into an operating discipline. It’s also, not coincidentally, a bar you can publish.
One caveat, so the definition doesn’t oversell itself: a verified signal aimed at the wrong person is still wasted. The acquisition is real, the source is primary, the date is fresh — and the message lands with a manager who feels the pain but can’t commission the work. Verification answers whether the claim is true. It doesn’t answer who can act on it.
That second question is a separate check — altitude: routing to the person senior enough to say yes and make it stick. The two checks compound; either alone underperforms. How they fit together is on Why Verified.
Hold any outbound vendor — including us — to the three-part test. For every claim that will reach a prospect under your name: What is the event? Where is the primary source? What is the date? A vendor who can answer, line by line, is selling verification. A vendor who answers with a score is selling a guess with good production values.
Fewer messages, each one earned by a fact. That’s the whole position — and at C-level, it’s the only one that compounds instead of burning the list.
The three-part test — event, source, date — runs before anything sends under your name. The next step is a conversation.