B2B SALES RESEARCH / ACCOUNT EXCLUSION
Finding new companies is not useful if they are already customers, active opportunities or on a no-contact list. The exclusion rules must be confirmed before account discovery, and uncertain entity matches must be reviewed instead of silently deleted.
Published & reviewed: 25 October 2026 · D2 GROUP B2B Research
Direct answer
D2 can incorporate client-approved existing-account and exclusion rules into a scoped B2B research brief. Candidate companies are checked against relevant identifiers such as legal entity name, business domain, country, parent/subsidiary relationship and a permitted client-provided reference. Matches are classified as exclude, review or researchable with a reason; ambiguous matches remain unresolved until validated. This is research quality control, not a promise of zero duplicates or direct CRM access.
This page addresses the account-identity and client-exclusion problem. The lead-quality guide explains broader ICP and source acceptance; the buying-signal page addresses event relevance. None implies that D2 operates or synchronizes a client's CRM by default.
STRUCTURAL EXAMPLE ONLY. No real customer CRM, business identity, private suppression list or client result is represented.
Confirm Target, Exclusion, Buyer, Timing and Sales Reality. Define what counts as a duplicate, a group-level exclusion and a customer-owned account before researching new names.
Use only an authorized, fit-for-purpose exclusion reference and an approved transfer/retention arrangement if any client data is needed. A public website form is not an invitation to upload an entire CRM.
Compare available legal names, websites, domains, location, company identifiers and evidence dates; distinguish legal entities from brands, facilities and subsidiaries.
Record excluded matches with a rule; send partial, contradictory or group-level cases for review. Do not fabricate a definitive identity match from incomplete data.
Deliver researchable accounts with identity checks, exclusion disposition, cited evidence and GAP status. Changes to the client's CRM remain with the client unless separately scoped and authorized.
EVIDENCE / INFERENCE / GAP
The same surface resemblance can require different treatment depending on the client's exclusion policy and identifiable legal business.
| Observed overlap | Research interpretation | Required review |
|---|---|---|
| An identical company domain and verified entity identifier | Strong duplicate candidate for the same legal business | Confirm CRM record scope and whether that entity is excluded |
| A shared parent brand but a separate local subsidiary | Potential group relationship, not automatically a duplicate | Check country, legal entity, existing coverage and group-level exclusions |
| Similar names with no matching domain or legal identifier | Ambiguous; name-only fuzzy matching is insufficient | Hold, inspect reliable public sources and document uncertainty |
No. Exclusion quality depends on the permitted client reference, complete business identity and agreed group rules. Ambiguous cases should be held and resolved rather than advertised as certain net-new accounts.
Not by default. First agree whether a minimal approved suppression or entity reference can meet the research requirement, along with authorization, secure transfer and retention controls.
Only when the client's exclusion policy says so. A parent and subsidiary may have separate buying teams and legal entities; the relationship needs verification and explicit treatment.
Review criteria
Describe the seller's ICP, current-account categories, group/subsidiary treatment and required research outcome. D2 can discuss a data-minimized exclusion approach without requesting a CRM upload through this page.
Discuss CRM exclusion scopeThis page explains a research method and illustrative fields; it is not an outcome guarantee, quote or permission to send outreach.
Client-owned records, subsidiaries and legal identities may be represented differently across sources. A company-name-only comparison can both miss real overlap and wrongly eliminate valid accounts.
01
Client-supplied exclusions can cover customers, active opportunities, strategic accounts and assigned territories when the scope and permitted reference fields are defined.
02
A valid suppression or exclusion reason takes precedence over a promising public signal. Research inclusion does not create permission to email anyone.
03
A shared brand may represent several legal businesses. Group-level blocking and subsidiary eligibility must be explicit rather than inferred from a name alone.
04
Translations, abbreviations, websites, renamed companies and merged entities require source-backed reconciliation and a manual review path.
