Company enrichment

The mechanics are simple. You hand a data API a domain and it hands back a record. CompanyEnrich's getting-started docs say the call returns industry, size, revenue, location, technologies and employee count, 15+ fields in all, for 1 credit per call. Most guides on the subject stop right there. A form fill arrives, the domain gets looked up, the CRM record fills itself in.

That's useful, and I'm not arguing against it. Here are some examples of customer data doing real work: you route a new lead by company size, you split accounts by tech stack, and you let a change fire a workflow. CompanyEnrich's CRM page says headcount shifts, job changes and tech stack changes can trigger one. A company that suddenly grows its team, or swaps a tool you compete with, can start a play without anyone opening a browser tab.

But look at what those facts have in common. They describe the shape of a company, and shape changes slowly. A large software firm and a small agency each come back as a tidy row. The row is identical whether that company read your pricing page yesterday or has never heard of you. A lookup answers "does this company fit us?" It never answers "is this company looking at us right now?"

That second question is the one that moves a deal. A company that fits and sits quiet is a name on a list. A company that fits and has just read your comparison page is a reason to pick up the phone today.

Where does this not apply? If you sell purely outbound, working down a fixed list with no inbound traffic to read, the lookup really is the whole job, and timing has to come from somewhere else. The same goes if nearly every lead already arrives through a form with a work email. Then fit is the only question left open.

Your next step is small. Write down which of the 15+ fields your routing uses today. If it's only size and industry, you don't need the rest, and the gap you're feeling isn't in the lookup.

Most company enrichment guides treat the data as something you buy: a bigger database, more fields, fresher records. But enrichment tells you who a company is. It doesn't tell you whether that company is ready to buy. That signal sits in your own records of what the company did on your site.

Take an illustration, not a customer story. A company reads a comparison page first. Then it opens your docs. A few days later it returns and goes straight to pricing. A third-party list can't show that sequence, because it never saw it. You need the company, the pages and the order.

Order matters because pages carry different meanings. A comparison page is a company weighing you against another option. Docs are a company checking whether the thing works for its stack. Pricing is a company asking what it costs. To be honest, that reading is a judgement. None of the sources here puts a conversion figure on the sequence, so use it to sort follow-up, not to forecast.

The two halves work together. The trail tells you timing. Enrichment tells you fit. A small company on your pricing page and a large one deserve different treatment, and you can only tell them apart once you've asked a data API for size.

Company Enrichment costs 1 credit per call and returns 15+ fields, including industry, size, revenue, location, technologies and employee count. That's enough to score fit from just the email domain of a signup, without manual research. Mark the company that fits and is reading pricing as Priority, and route it first.

Enrichment also has limits. Not every domain resolves to a full record, and you shouldn't guess at the gaps. The sources here don't say how often the data is refreshed or whether it covers every geography equally, so check that before you rely on it.

This doesn't help much if only a handful of companies reach you. There's nothing to sort, and paying for enrichment won't fix that. Bring more companies in first, then enrich the ones that show up.

The mechanics of a data API are cheap on paper. CompanyEnrich lists its company lookup at 1 credit per call. Its Workforce endpoint, which returns headcount trends, costs 5 credits per company. The rate limit is 500 requests per minute per IP. For bigger batches there's a bulk call that takes up to 10K domains asynchronously.

The search side is wider than the lookup. The vendor says it covers 33M verified companies, distilled from 900M raw records. Company Search spans 30M+ companies with 15+ filters, and Similar Companies finds lookalikes of an account you already like. There's also an MCP server, which lets an AI agent call the data directly. If you're wiring a lead API into your own product or CRM, that's the surface you'd be connecting.

Now the uncomfortable part. The vendor's pages I've cited don't publish a price per credit, and they don't state free-tier limits. So I can't give you a USD figure, or a rupee one beside it, and I won't guess. A vendor that hides the price per credit is asking you to commit before you can do the sum. Ask for it in writing, then multiply it by your own volume: how many domains you'd look up, times the credits each call uses. A 5-credit call costs five times the plain lookup, and that adds up if you run it on every account.

There's a build-versus-buy point too. An API means a developer wires it in, handles errors and keeps to the rate limit. If nobody on your team can do that this quarter, one of the lead data tools with a screen is the honest choice, even at a higher price. An unused API costs more than a tool someone opens. One question stays open in the brief: whether the API allows calls straight from a browser. Until you've checked, plan to call it from your server.

When does the API route not apply? If you handle a small number of accounts a week, a manual lookup does the job and you'll never touch the rate limit.

Coverage is where I'd be most careful. The sources give totals, 33M verified companies and 30M+ in search, but they don't say whether that coverage is even across countries. The open question in the research is plain: does it cover all geographies equally? Nothing here answers it, so I won't claim that a database built for global reach serves an Indian B2B team as well as a US one.

What a US team and an Indian team each face may differ in practice, but the sources don't measure it. None gives a budget, a team size or a fill rate for either market. So the useful move isn't to trust a global number. It's to test. Take a sample of company domains from each market you sell into, run them through the lookup, and count how many come back with size and industry filled in. If your Indian accounts return half-empty rows and your US accounts return full ones, you've learned more than any brochure will say.

Prices are the same story. Vendors that list in USD leave an Indian team converting at the going rate. On 29 Sep 2026 that's 1 USD = ₹96.07, so a dollar price lands at whatever that multiplies to for you. Where a vendor publishes only a rupee price, take it as written and don't back-convert it.

Then there's privacy, which changes with where a company and the professionals in its records sit. Requirements vary by jurisdiction and your consent setup, so use your own legal review. That applies to any tool you evaluate. It's a good reason to ask each vendor how it handles deletion before you connect it to your CRM.

This doesn't apply if you sell into one market only. Then you test one sample and you're done. If you sell into both, keep the two results side by side and let the gaps decide which tool you use for which market. You may need one source for the US and a different one for India.

You can test a company enrichment API without buying anything new. All you need is a list of company domains you already have, from sign-ups, leads or customers. Here's the method, in the order I'd do it.

1. Pull the list of company domains you already hold. Start with a short list, so you can check results by hand.
2. Run each domain through the enrichment API. On CompanyEnrich, Company Enrichment costs 1 credit per call and returns 15+ fields, including industry, size, revenue, location, technologies and employee count.
3. Check the fields against what you know. Pick a few companies you know well and see if the size and industry match. That tells you how far to trust the rest.
4. Decide which fields you'd act on. Size and industry are usually enough to score or route a lead. Leave the rest until you need them.
5. Mark the companies that fit your buyer as Priority. Follow those up first and leave the rest for later.

A few honest edges. Step 4 is my rule, not a measured one, so adjust it after you've watched what happens to the leads you follow up. A short list is cheap to check by hand, so enrichment earns its cost once the list gets long. If you have a longer list, CompanyEnrich's Bulk Enrichment takes up to 10K domains asynchronously.

Now the case where this doesn't work: a tiny list. If you only have a handful of companies, an API adds little. Look them up by hand and save the credits.

Some questions stay open from the sources. CompanyEnrich doesn't disclose its price per credit, or how often its data is refreshed. It also doesn't say whether it covers all regions equally. Check these before you commit, and test with companies from your own market.

The trap is treating the output as proof. A record can be out of date, or a company can be a poor fit despite matching on size and industry. Treat enrichment as a reason to look closer, not as a promise. For the wider picture, see our guide to B2B sales intelligence.

PageFox is the wrong choice for a site with little traffic: it tells you which companies are already visiting, it does not bring new visitors.

Decide whether your gap is missing company facts or missing timing, and if it's timing, stop shopping for bigger lists. This week, pull the companies that came back to your site and read which pages each one opened.