The No-Guessed-Contacts Review Framework

A free, vendor-neutral way to tell whether a B2B contact record is verified, inferred, stale or guessed. It uses five checks, a simple scoring system and a worked example.

The problem

Most “verified” contact data isn’t what buyers assume it means. A contact that passes an email-deliverability check (the address is validly formatted and the receiving mail server accepts it) is making a different claim from a contact that has been identity-confirmed (a real, current, public source says this person holds this role at this company, as of a specific date). Vendors routinely sell the first as if it were the second. The gap between the two is where stale titles, departed employees and pattern-guessed emails (first.last@company.com generated from a formula, not confirmed) end up in a list you paid for.

This framework gives a business buyer a repeatable way to tell which one they actually have, for any single contact record from any source, whether that’s a purchased list, a database export, internal research or a delivered custom research batch.

Definitions

The framework sorts a contact record’s supporting evidence into one of six categories:

• Verified: a specific, dated, public source confirms that this person currently holds this role at this company. The buyer can check the source, and doesn’t have to take the vendor’s word for it.
• Inferred, clearly labeled: the record states a reasonable inference and says so, rather than presenting it as confirmed fact.
• Stale: the supporting source exists but is old, so the role, company or contact detail may no longer be current.
• Incomplete: some fields are confirmed, and the others are left blank instead of being filled in with a guess.
• Contradictory: two or more public sources disagree on a material fact, and the disagreement hasn’t been resolved or flagged.
• Guessed: no public source supports the specific detail. The most common case is an email address generated from a name-pattern formula, with no confirmation that it’s real or in use.

Review sequence

1. Identify the specific claim being made about this contact.
2. Locate the source cited for that claim.
3. Check whether 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 or contradict each other.
6. Classify the record using the definitions above.
7. Decide whether the record is usable as it is, usable with a caveat, or should be excluded.

Source-quality hierarchy

Source types rank from highest to lowest confidence:

1. The company’s own current website, staff page or press release naming the person in the role.
2. A recent, credible news article or interview naming the person in the role.
3. A professional profile the person appears to control, checked for recent activity.
4. A directory or database listing with no visible original source.
5. An inferred pattern with no source at all.

Levels 1 and 2 support classifying a record as “verified.” Level 3 on its own supports “verified with lower confidence.” Levels 4 and 5 don’t support “verified” on their own.

Freshness and date-check standard

Treat a source older than 12 months as stale until re-checked, however confident it looked when you first found it. Roles and employers change faster than a single snapshot can track, so a two-year-old staff page is a starting point, not current proof.

Handling conflicting public information

• Prefer the more recent source, but note both instead of quietly discarding the older one.
• Prefer a primary source over a secondary one, such as a directory that scrapes other directories.
• If the conflict can’t be resolved, label the record contradictory. Don’t resolve it in whichever direction is more convenient.

Contact-channel verification guidance

• A published contact channel is a materially stronger claim than a pattern-generated one.
• A pattern-generated email isn’t verified just because the format is common. At best it’s a reasonable inference, and it should be labeled as one.
• Neither this framework nor Be My Tech’s own process claims that a verified contact will respond or that a message to it will be delivered. The claim is only that the identity and role are supported by a checkable public source as of the stated date.

Scoring and classification

Score a single contact record on five yes/no items:

1. Is there a dated public source for this person’s current role?
2. Can the buyer check the source independently, rather than just being told it exists?
3. Is the source less than 12 months old, or has an older source been re-confirmed?
4. If more than one source exists, do they agree?
5. Is any listed direct contact detail published rather than pattern-guessed?

The result is classified as follows:

• 5 out of 5 (or 4 out of 5 when item 5 doesn’t apply): source-confirmed.
• 3 or 4 out of 5: partially verified, and usable if you note the specific gap.
• 0 to 2 out of 5: likely guessed or unsupported, and it shouldn’t be treated as verified.

Red-flag checklist

• No source cited at all, only a database name.
• The source is another directory that cites no original source (circular sourcing).
• The email format matches a common pattern with no independent confirmation that it’s real.
• The title or company is more than 12 months old with no re-check.
• The same record appears with different titles across sources, and neither is dated more recently.
• In bulk records, every contact at a company shares an identical, formulaic source citation.

Buyer-side acceptance checklist

Before accepting a delivered batch of contacts from any vendor, including Be My Tech, a buyer can reasonably ask:

• Can I see the source for each record, not just a confidence score?
• Is each source dated?
• Does the vendor distinguish published contact details from inferred ones?
• Is there a stated process for what happens when sources conflict?
• Can I get a replacement or an explanation for a record that fails this framework?

Worked example (fictional, not a real vendor, client or individual)

Claim: “Jordan Ellis, VP of Operations at Northfield Instruments (a fictional company), jordan.ellis@example.com.” The domain example.com is reserved for illustrative use by internet standards (RFC 2606) and doesn’t resolve to a real mailbox.

• Step 1: The claim is a role plus a direct email.
• Step 2: The source cited is a March 2026 press release naming Jordan Ellis as VP of Operations.
• Step 3: The press release is public and independently checkable. ✓
• Step 4: It’s dated 4 months before this review, which is inside the 12-month standard. ✓
• Step 5: No second source turned up, so there’s no contradiction to resolve.
• Step 6 (email): No source confirms this specific email address. It follows a pattern inferred from the company’s known format and isn’t confirmed anywhere.

Classification: the role is source-confirmed (4 out of 5, treating email verification as not applicable but noted). The email is guessed, not verified, and should be labeled that way if it’s delivered.

Limitations and appropriate use

• This framework judges what can be checked from public information. It can’t confirm that a contact will read, respond to or convert on an outreach message.
• It doesn’t guarantee that the public information is itself accurate. It only says that a claim traceable to a public, dated, independently checkable source is stronger evidence than one that isn’t.
• It isn’t a legal, privacy-compliance or data-protection audit. Any handling of contact data should separately follow the regulations that apply to the buyer’s jurisdiction and use case.
• Scores are a classification aid, not a guarantee. A 5 out of 5 record can still be wrong if the underlying public source was inaccurate or has since changed.

This framework focuses on a single contact record. To judge an entire delivered list at once, see What Makes a Prospect List Trustworthy?

Methodology

Version 1.0. Be My Tech’s own internal research process is built on this same framework, and every delivered prospect record is reviewed against it before delivery.

Need research built around your actual target market?

Be My Tech researches source-cited, date-checked prospects against the criteria you provide. Current fit, scope and pricing are confirmed through the prospect research path before you commit. See how prospect research works.