FindingcurrentGTM data

An email domain does not prove which company someone works for

Subsidiaries, agencies and observers break the standard domain-to-account match.

SymptomA meeting lands on the wrong account because one attendee's email domain is another account's domain, and agents then name the wrong company.

Matching a person to a company by email domain is the standard first move. It builds a domain list per account from the CRM website, contacts and meeting attendees.

An email domain is evidence rather than an answer, because some accounts hold a contact whose domain is another account's primary domain.

  • A subsidiary or sister brand filed under the parent.
  • An agency or partner employee logged as a contact.
  • An observer who sits in on meetings across two or three accounts.
  • A contact filed under the wrong account by hand.

A count threshold clears single-contact noise. A bigger threshold will not settle what remains, because those cases ask a question about the company and need adjudication.

In a synthetic test set of 2,000 contacts, 40 carried a domain that is another account's primary domain. A domain join filed all 40 to the wrong account; trusting an explicit account link first left 6, the ones with no link. The set shows the mechanism, not how common it is.

Check your setup read-only

List the contact email domains per account in the CRM. Count the accounts where a contact's domain is another account's primary domain. Any such account can misfile a meeting. 5% of accounts or more means domain matching can't be your only rule.

Passes ifUnder 5% of accounts hold a contact whose email domain is another account's primary domain. Your matching has a rule beyond domain for those accounts.

Access needed:crm-read

If it fails: changes to make later (not part of the check)
  1. 01Keep one domain registry that every consumer reads, instead of each job deriving its own domain list.
  2. 02Drop domains seen on only one contact before judging the rest.
  3. 03Have a person or a model adjudicate each candidate domain against the account. Treat human overrides as final.
  4. 04Re-check an account only when its evidence changes.
  5. 05Compare a new matcher's output with the current one before switching.
Applies ifA job matches people, emails or meetings to accounts by email domain, and the CRM holds more than a few hundred accounts.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.