How to Tell If a B2B Contact Was Verified or Guessed

“Verified” is one of the most overused words in B2B data. It sits on every list seller’s landing page next to a checkmark, implying that the contact is real and safe to spend a message on. In practice it usually means something narrower: the email address was checked and didn’t come back invalid. That’s a real check and it matters, but it’s a different claim from “a person confirmed that this individual currently holds this role at this company.” Most buyers assume they’re getting the second when they’re only getting the first.

The difference matters most at the moment you decide whether to trust a list before spending time, or a message, on it.

Two different meanings of “verified”

Deliverability-verified means an email-validation check confirmed that the address is correctly formatted and the receiving mail server accepts it. It tells you the message probably won’t bounce. It doesn’t tell you whether the person named still works there, still holds that title, or exists at all. Those checks confirm that an address can receive mail, not who reads it or what role they hold.

Identity-verified means a specific, checkable, dated public source confirms that a named person currently holds a role at a company. That could be a company staff page, a recent press release or a direct quote in an interview, something you could go and check yourself rather than taking the vendor’s word for it.

A list can be entirely deliverability-verified and mostly guesswork on identity, and both can be true of the same list at once. The label “verified” alone doesn’t tell you which one you’re getting.

What public information can and can’t verify

Public sources can reasonably confirm a person’s name, a stated current or recent role, a company affiliation and sometimes a published contact channel. They generally can’t confirm that a specific generated email address is monitored, that a person wants to be contacted this way, or that a role listed six months ago is still accurate today. Anyone who guarantees that a contact is current and reachable is promising something public information can’t support.

Published contact details versus inferred ones

There’s a meaningful difference between a published contact channel and an inferred one. A published channel is one the company or the person put in front of the public themselves. An inferred channel is most often a pattern-generated email such as firstname.lastname@company.com, built from a known or guessed formatting convention, with no confirmation that the address exists or is monitored.

Pattern generation isn’t inherently dishonest. It’s a guess, and the honest version says so. The trouble starts when the guess is delivered looking exactly like a confirmed, published address, with the same “verified” label on both.

Freshness: why the date matters as much as the source

A contact record with an excellent source can still be wrong if the source is old. Roles and employers change faster than a single dated source can track, and a source that was accurate a year ago carries real but shrinking weight. As a working standard, treat anything older than 12 months as stale until it’s re-checked.

When sources disagree

It isn’t rare to find two public sources naming different titles, or different companies, for what looks like the same person. Self-maintained professional profiles reflect whatever the person last updated, which doesn’t always happen when they change jobs, and directories can inherit each other’s errors when one copies from another without checking the original. When sources disagree, flag the conflict, prefer the more recent and more primary source, and say that’s what you did. Don’t quietly pick whichever version is more convenient and present it as settled.

Common red flags

• No source cited at all, just a database’s internal confidence score.
• A source that is itself another directory with no original source behind it.
• An email address that follows a common company-name pattern with nothing confirming it’s real or monitored.
• A title or company listing more than a year old, with no sign it was re-confirmed.
• The same contact showing different titles in two sources, with no note of which is more current.
• A batch in which every record carries an identically formatted, generic source citation.

A practical verification sequence

1. Identify exactly what’s being claimed.
2. Find the source cited for that specific claim.
3. Confirm the source is public and independently checkable.
4. Check the source’s date.
5. Look for a second source on the same fact, and note whether the two agree.
6. Classify what you have: verified, inferred and labeled, stale, incomplete, contradictory or guessed.
7. Decide from that classification whether the record is usable as it is, usable with a caveat, or should be set aside.

This is the same sequence behind the No-Guessed-Contacts Review Framework, a free, standalone walkthrough of each step with a scoring system and a worked example, for when you want to apply it systematically rather than case by case. For a broader checklist that covers an entire delivered list instead of a single record, see What Makes a Prospect List Trustworthy?

What this doesn’t promise

None of this guarantees that a contact will respond, that a message will reach a monitored inbox, or that the public information was accurate at its source. It also isn’t a substitute for whatever data-privacy or compliance review applies to how you handle contact data in your own jurisdiction. What it does give you is a way to tell a claim that’s been checked from one that has only been asserted, which is the gap most “verified” labels don’t actually close.

How Be My Tech applies this

Every prospect record Be My Tech delivers goes through this sequence before it reaches you. Each has a public source, a checked date and a stated fit reason, and published contact details are kept separate from anything inferred. Nothing is pattern-generated and presented as confirmed. See how prospect research works, and confirm current fit, scope and pricing before ordering.

Methodology reference: The No-Guessed-Contacts Review Framework, Be My Tech, v1.0.