Company enrichment appends firmographic and technographic detail to an account record you already hold, usually starting from nothing more than a domain. It is the account-level counterpart to contact enrichment, and it is what makes routing, scoring and territory assignment possible.
Match on the domain, never the name
This is the single most common implementation mistake. Legal entity names drift, subsidiaries carry different names from their trading brand, and punctuation varies between systems. A domain is stable and unique. Every reliable enrichment pipeline keys on it.
What you can append from a domain alone
- Employee count and headcount trend
- Industry classification and a plain-language description
- Revenue estimate and funding history
- Headquarters and office locations
- Technology stack, covered in technographic data
- Hiring activity, which is often the most actionable timing signal
Where it pays for itself
| Use case | What enrichment unlocks |
|---|---|
| Inbound routing | A signup with only a work email becomes a scored, assigned account |
| Territory assignment | Accurate location and size instead of rep guesswork |
| Scoring | Fit signals that do not depend on the prospect filling in a long form |
| Expansion | Headcount and funding movement inside the existing customer base |
| Form shortening | Ask for an email, infer the rest, and watch conversion rise |
Refresh cadence
Company-level fields move more slowly than contact-level fields. A quarterly sweep on active accounts and an enrichment-on-create trigger for new records covers most needs without burning credits on data that has not changed.
For the contact-level equivalent see the contact enrichment API. For chaining providers to raise coverage see waterfall enrichment, and for the customer-base version see customer data enrichment.
Implementing it without breaking the CRM
- Create dedicated enrichment fields. Never write into fields a human edits. “Employee count (enriched)” sitting beside “Employee count” costs nothing and prevents the argument that ends enrichment projects.
- Store a source and a timestamp on every enriched field. When a rep says the data is wrong, you need to know where it came from and when.
- Decide precedence once, in writing. Human edit beats enrichment, newer enrichment beats older, and a higher-confidence source beats a lower one.
- Enrich on create, then on a schedule. Not on every record update, which burns credits re-confirming unchanged data.
- Log failures visibly. A silent no-match looks identical to a field that is genuinely empty, and the two need different responses.
Field mapping that survives contact with reality
| Enriched field | Map to | Precedence rule |
|---|---|---|
| Employee count | Account size band | Overwrite freely, it is observational |
| Industry | Vertical picker | Never overwrite a human selection |
| Revenue | Reference only | Do not drive routing from a modelled estimate |
| HQ location | Territory | Overwrite only if the field is empty |
| Funding stage and date | Timing trigger | Always take the newest |
| Technology stack | Multi-select | Append, never replace |
Measuring whether enrichment is paying for itself
Enrichment is easy to buy and hard to justify later because nobody defined the measure up front. Three numbers make the case or kill it.
- Fill rate. What share of records got the field you were paying for. Below 50 percent, question the provider or the matching key.
- Routing accuracy. What share of enriched accounts landed with the right rep first time. This is the number executives care about.
- Time to first touch. If enrichment is meant to speed up inbound response, measure that directly. If it has not moved, the enrichment is not the bottleneck.
When company enrichment is the wrong tool
If your problem is that you do not know which accounts to pursue, enrichment will not solve it: it makes existing records richer, it does not find new ones. That is a discovery problem, covered in B2B prospecting tools. If your problem is that emails bounce, that is contact-level verification rather than company enrichment. Buying the wrong layer is the most common and most expensive mistake in this category.
Frequently asked questions
What is company enrichment?
Appending firmographic and technographic detail to an account record, usually starting from just a domain name.
Should I match on company name or domain?
Always domain. Legal names drift, subsidiaries trade under different names, and punctuation varies between systems. Domains are stable and unique.
How often should company records be refreshed?
Quarterly for active accounts, plus an enrichment trigger when a record is created. Company-level fields move more slowly than contact-level ones.
