FindingcurrentGTM data

Duplicate accounts make pipeline answers confident and incomplete

A corporate group spread across records and CRMs hides part of its pipeline.

SymptomA pipeline question about a large corporate group returns one confident total that leaves out deals on its sibling accounts, with no warning.

A large corporate group rarely lives on one account record. Unmerged duplicates and brands with their own domains split it up, and sometimes the group spans two CRMs run by different teams.

Domain matching does not join these records, since a group with many brands has many domains and nothing links them. A large CRM can have many duplicate-name groups. When asked about the group, an agent totals the account it found and reports it. That answer looks complete because it is complete for one record, yet it misses a material share of pipeline without saying so.

Group-level revenue has the opposite trap when revenue is reported once for the whole group. Copying it onto each member and then summing multiplies the total by the number of members, while splitting it invents per-account figures.

In a synthetic test set of 40 corporate groups, answering from the one record found missed 56% of the open pipeline; walking the group found all of it. The set shows the mechanism, not how common it is.

Flags and rollups leave duplicates in place rather than merging them at the source, so every answer is only as complete as those flags are current.

Check your setup read-only

Count the account names that appear on 2 or more account records across your CRMs. Take the 10 names with the most records. List the open opportunities on each record in those groups. Any group with open opportunities on more than 1 record means a single-account answer is incomplete.

Passes ifIn each of your 10 largest same-name groups, open opportunities sit on 1 record. Otherwise, parent links join the records your answers read.

Access needed:crm-read

If it fails: changes to make later (not part of the check)
  1. 01Flag every account that has a duplicate sibling in the same or another CRM. Show the flag to the agent.
  2. 02Let the agent walk parent and child links before answering a pipeline question about any account in a group.
  3. 03Define a group rollup for groups whose brands share no domain or parent link.
  4. 04Attach group-level revenue to each member as "one of N members". Never derive a per-account total from group-level revenue.
Applies ifYou route cards or answer pipeline questions per account, and your CRM holds parent-child accounts or you read 2 or more CRMs.

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