FindingcurrentGTM data

People who leave a company lose the link to their past work

Employment is a time window, so facts link by when they happened.

SymptomFacts from a former employee's calls and emails link to no one, or attach to the wrong account, once their CRM user is deactivated.

The standard model links a person to their employer with one "currently employed" edge. When the CRM deactivates the user, that edge goes away, and so does the path from their past work back to them.

Deactivated users can be a large share of CRM users, making departed users a normal part of the data. Facts from before someone left are still true and still theirs, yet with only a current edge those facts lose their owner and can get attached across accounts. Modeling employment as a window keeps those facts tied to their owner. The start of the window needs care too, because a CRM user's created date is different from their hire date, so the window should start from the person's first recorded activity.

In a synthetic test set of 2,000 dated facts, linking each to the person's current employer put 286 on the wrong account; linking each to the employment window that covers its date, opened at first activity, linked all 2,000 correctly. The set shows the mechanism, not how common it is.

Check your setup read-only

Count deactivated users against all users on the CRM user object. Take the 5 most recently deactivated users. List 4 facts dated before each user's deactivation. Look at whether each fact still links to that person. More than 1 of 20 from before the departure that no longer links to them is a gap.

Passes if19 or more of 20 sampled facts dated before a former user's deactivation still link to that person.

Access needed:crm-readcontext-read

If it fails: changes to make later (not part of the check)
  1. 01Store employment as an edge with a start and an end. Keep the edge when the person leaves.
  2. 02Link each fact to the employment window that covers the fact's event time, not to whoever is employed today.
  3. 03Start the window from the person's first recorded activity, never from the CRM user's created date.
  4. 04Treat a user deactivation as the end of a window, not as the removal of the person.
Applies ifYour CRM user object holds deactivated users, and their earlier calls and emails sit in your fact store.

← 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.