--- title: "Company Attributes to Enrich Before Outbound: 2026 Checklist" description: "Which company attributes to enrich before outbound, as a checklist. A 6-API benchmark found only 50.1% to 67.6% of 349 domains returned a match." canonical: "https://www.explorium.ai/blog/data-enrichment/which-company-attributes-to-enrich-before-outbound-2026-checklist-for-gtm-engineers/" last-updated: "2026-08-10" --- # Company Attributes to Enrich Before Outbound: 2026 Checklist > Which company attributes to enrich before outbound, as a checklist. A 6-API benchmark found only 50.1% to 67.6% of 349 domains returned a match. - Canonical URL: https://www.explorium.ai/blog/data-enrichment/which-company-attributes-to-enrich-before-outbound-2026-checklist-for-gtm-engineers/ - Last updated: 2026-08-10 Choosing which company attributes to enrich before outbound is a budget decision before it is a data decision. An independent benchmark of 6 company-enrichment APIs, run in May 2026 on 349 domains, produced find rates of 50.1% to 67.6% and populated 11.5 to 17.9 of a 27-field schema per match. You pay per row and per field for data a third to a half missing. GTM engineers stall one step before enrichment: the ICP list (ideal customer profile, the accounts you already filtered) exists, hundreds of purchasable fields exist, and no rule ranks them. This checklist gives you the rule, the schema, and the cost arithmetic. Start with [what data enrichment covers](https://www.explorium.ai/data-enrichment/introduction-to-data-enrichment/) for the definition. ## Which Company Attributes Should You Enrich Before Outbound? **Enrich a company attribute only if it changes one of three things: whether the account stays in your list (gate), why you are reaching out now (evidence), or who gets contacted and what the message says (routing).** Each layer is bought at a different point, on a different share of the list. ### 🔑 The Three-Layer Rule - **Gate attributes** disqualify accounts: employee band, revenue band, industry code, country. - **Evidence attributes** justify timing: a round closed 60 days ago, engineering headcount up 14%. - **Routing attributes** pick the recipient and the angle: tech stack, headcount mix, website keywords. - **Unassigned attributes** get deleted: a field that cannot gate, date, or route is decoration. ### ❌ Why the "Enrich Everything" Default Fails - Cost scales as rows times fields times credits: 1,000 accounts on 20 fields is 20,000 operations, before any [accuracy check](https://www.explorium.ai/data-for-gtm/b2b-contact-enrichment-accuracy-benchmark-for-ai-agent-workloads-2026-for-revops-teams/). - A field that enters no rule cannot be evaluated against pipeline, so nobody removes it. - The cheapest attributes are the noisiest, putting your worst data in charge of the gate. > "I would separate this into gates, evidence, and routing, and enrich only the accounts that pass." Consensus in the [r/gtmengineering discussion on enrichment attributes](https://www.reddit.com/r/gtmengineering/comments/1ujuq8d/how_do_experienced_gtm_teams_decide_which_company/). ## How Do You Decide If a Company Attribute Is Worth Paying For? **Name the decision the field changes, and write the rule, before you buy it.** A field that cannot become a gate threshold, an opening line, or a routing branch is never worth buying. ### ✅ The Field Qualification Test - Write the rule first. "Drop accounts under 200 employees" is a rule; "we want employee count" is a wish. - State the threshold and both branches, so the field has a pass and a fail path. - Confirm the field is populated on enough of your list to run the rule. Set a 90-day review. ### ⚠️ The Attributes That Look Useful and Are Not - Revenue estimates disagree across providers by whole bands: a weak primary gate on private companies. - Employee counts vary with whether contractors and regional entities are counted. - Headline dataset sizes describe the vendor's index, not your list. Test the fields you depend on. ### 💡 Raw Fields Versus Composite Scores Gate on raw fields, score on composites. A raw revenue estimate carries one provider's full model error, while a composite of 4 or 5 correlated inputs degrades gracefully when one goes missing. - **Marketing maturity:** marketing tech in the stack, marketing headcount share, content change rate. - **Engineering investment:** quarter-over-quarter change in engineering roles, DevOps tooling, product launches. - Require 3 populated inputs before a composite emits a score, and store the input vector so a drop traces to one field. Still choosing a source? The [side-by-side B2B data provider comparison](https://www.explorium.ai/compare/) covers coverage and pricing per vendor. ## Which Company Attributes Belong in the Gate, Evidence, and Routing Layers? **Gate on 5 to 7 cheap firmographic fields across 100% of the list, buy evidence only on survivors, and buy routing attributes only on accounts you will contact.** Firmographics are company descriptors (size, revenue, industry, location); technographics are the software an account runs. ### 📊 The Schema Matrix LayerWhat it decidesAttributes to buyShare of list **Gate**Whether the account stays inEmployee band, revenue band, NAICS industry, country100% **Evidence**Why you are reaching out nowFunding round date and value, hiring by department, new office10% to 25% **Routing**Who you contact and what you sayTech stack, headcount mix, locations, website keywords, intent topics5% to 10% ### 💡 Order of Operations - Filter first, match second, enrich third. A filter query costs a fraction of a depth pass. - Resolve survivors to one company identifier first, so the layers join cleanly. See [how to match company records across sources](https://www.explorium.ai/data-for-gtm/how-to-match-company-records-across-data-sources-for-revops/). - Buy evidence attributes with a time filter, not a lifetime lookup. Last quarter is the window. ## How Much of Your Enrichment Schema Will Come Back Empty? **Expect a third to a half of a clean domain list to return no match, and under two thirds of your fields populated on the rest.** The [independent 6-API benchmark on 349 domains](https://companyenrich.com/benchmarks/company-enrichment-api) measured find rates of 50.1% to 67.6% and 11.5 to 17.9 fields populated out of 27. ### 📈 Find Rate Is Not Fill Rate - **Find rate** is the share of input rows returning a record: 50.1% to 67.6%. - **Fill rate** is the share of fields populated on what came back: 11.5 to 17.9 of 27. - The two move independently: a 282-domain benchmark showed one API resolving 100% of domains but populating 60.4% of fields. ### ⚠️ The Predictive Fields Are the Emptiest Fields - Funding data was populated on 4.0% to 10.6% of returned profiles. - Organizational structure fields ranged 0.0% to 10.6% fill. - Those are the evidence attributes practitioners rate most predictive, so the timing layer is the likeliest to be silently empty. - The benchmark's own conclusion: no single API wins on everything. > Stop guessing which fields come back populated. [Start a free trial: 100 credits, no subscription required](https://www.explorium.ai/sign-up/), and measure fill rate on your list. ## Should You Enrich the Whole List or Only Accounts That Pass the Gate? **Gate first, then buy depth only on survivors: on a 1,000-account list scored across 20 fields, taking the top 10% to depth cuts credit spend by 86% to 89%.** Enrichment is priced per record per field, so call sequence is the largest cost lever. ### 💰 The Cost Arithmetic StepEnrich everythingGate first, then depth Accounts filtered (1 credit each)1,000 credits1,000 credits Accounts taken to depth1,000100 (top 10%) Depth credits, 20 fields at 1-5 credits20,000 to 100,0002,000 to 10,000 Total credits21,000 to 101,0003,000 to 11,000 Cost at the Growth rate of $0.03 per credit$630 to $3,030$90 to $330 ### 🔄 The Gate-First Sequence - Apply hard disqualifiers server-side, so unqualified accounts never become billable. - Score survivors on fields you already hold, then take the top decile forward. - Check [Explorium credit pricing](https://www.explorium.ai/pricing/) before sizing the run: rates drop with volume. ## How Does the Explorium API Cover the Whole Schema From One Call Pattern? **The Explorium API supplies the whole pre-outbound schema from one call pattern, winning three pillars at once: one API for gate, evidence and routing attributes off a single business_id, batch scale with change-over-time fields, and one unified credit pool that makes gating first cheaper.** ### 🔑 Pillar 1: One API for Gate, Evidence, and Routing - The filter endpoint gates on company size, revenue, age, NAICS industry, tech stack, website keywords and intent topics, before any depth credit. - The match endpoint returns a 32-character business_id at 97.8%+ company match accuracy, 50 per request. - 20+ enrichments key off that id: firmographics, 23 technographic fields, funding, workforce trends, hierarchy. - Coverage spans 150M+ company profiles from 50+ sources, so gate and depth share one vocabulary instead of [separate provider schemas](https://www.explorium.ai/compare/people-data-labs/). ### 🚀 Pillar 2: Built for Scale and Change Over Time - Bulk enrichment takes 50 business_ids per request; one filter query returns 60,000 records. - Funding is a dedicated endpoint: round date, value, type, count, total raised, latest increase. - Workforce trends return per-department role percentages plus 15 quarter-over-quarter change fields, so you log nothing yourself. - 35 event types carry a timestamp filter, covering funding, hiring, offices and launches. Uptime is 99.999%. ### 💰 Pillar 3: Affordable by Design - Credits sit in one unified pool, no per-endpoint allocation and no seat tax, so budget moves between endpoints. - Enrichments cost 1-5 credits and events 1 credit, so the gate-first arithmetic is computable up front. - A free trial issues 100 credits and an API key in minutes. Volume rates run $0.04 to $0.015. ### ⚡ The Call Pattern ``` `pip install explorium # 1. Gate server-side, before any depth credit curl -X POST https://api.explorium.ai/v1/businesses -H "api_key: $KEY" \ -d '{"mode":"full","size":100,"filters":{"company_size":{"values":["501-1000"]}}}' # 2. Match survivors to a business_id (50 per request) curl -X POST https://api.explorium.ai/v1/businesses/match -H "api_key: $KEY" \ -d '{"businesses_to_match":[{"domain":"acme.com"}]}' # 3. Depth on survivors only (50 ids per bulk call) curl -X POST https://api.explorium.ai/v1/businesses/funding_and_acquisition/bulk_enrich \ -H "api_key: $KEY" -d '{"business_ids":["4f2a9c1b7e3d8a56b0e1d7c3a9f45e28"]}'` ``` DimensionWhat the schema needsExplorium API **Pillar 1: one API**Gate, evidence, routing in one vocabulary20+ enrichments off one business_id, 150M+ profiles **Pillar 2: scale and change**Batch depth plus point-in-time deltas50 ids per bulk request, 35 event types **Pillar 3: affordable**Pay for depth only on survivorsUnified credit pool, 1-5 credits per enrichment Match before enrichOne stable join keybusiness_id, 97.8%+ match accuracy Funding coverage4.0% to 10.6% benchmark fillDedicated endpoint, 11 funding fields Organizational shape0.0% to 10.6% benchmark fillWorkforce trends, hierarchy endpoints ReliabilityNo silent batch failures99.999% uptime ## How Do You Catch an Attribute That Silently Stops Populating? **Track fill rate per field per batch and alert on the drop, because a field that stops populating returns HTTP 200 with a null value and breaks nothing you monitor.** Scoring degrades for weeks while dashboards stay green. ### ⚠️ Why Nothing Errors - A missing attribute is a valid response: status codes and job counts stay green. - Composite scores absorb the gap and keep emitting a number, so the failure shows as worse reply rates. - Provider-side schema changes rename or deprecate a field without breaking the request. ### ✅ The Fill-Rate Monitor ``` `FIELDS = ["last_funding_round_date", "full_tech_stack", "change_in_sales_roles"] def fill_rates(batch): n = len(batch) return {f: round(sum(1 for r in batch if r.get(f)) / n, 3) for f in FIELDS} # Alert when a field falls 20 points below its 30-day median.` ``` - Store fill rate per field per batch as a time series, not a one-off check. - Alert on relative drops, since absolute funding fill rate is low everywhere. - See [waterfall versus real-time enrichment at scale](https://www.explorium.ai/data-for-gtm/waterfall-vs-real-time-enrichment-at-scale-2026-for-ai-agent-builders/) for higher-volume failures. > "No one wins on everything. Before committing to a provider, test the exact fields your workflow depends on." From the [practitioner benchmark of 6 enrichment APIs](https://www.reddit.com/r/gtmengineering/comments/1u4tph8/i_tested_6_company_enrichment_apis_on_the_same/) and [reports of fields failing silently](https://www.reddit.com/r/SalesOperations/comments/1uxwpj1/three_things_that_quietly_broke_in_our_enrichment/). ## Getting Started: The Pre-Outbound Enrichment Checklist **Build the schema in the order the money flows: write the rules, gate cheaply, match once, buy depth on survivors, monitor fill rate, all on the Explorium API so every layer shares one identifier and one credit pool.** ### 🔄 The Build Order - **Step 1:** Write one rule per candidate field. No rule, no purchase. - **Step 2:** Gate the full list on 5 to 7 firmographic filters, server-side. - **Step 3:** Match survivors to a business_id at 97.8%+ accuracy. - **Step 4:** Buy evidence and routing depth on the top decile, batched 50 ids per call. - **Step 5:** Log fill rate per field per batch, then cut rules that changed nothing in 90 days. ### 🔑 The Decision Framework The three pillars settle it. Pillar 1 puts gate, evidence and routing in one field vocabulary, so you stop reconciling vendors whose revenue estimates disagree. Pillar 2 covers batch depth and quarter-over-quarter change with no snapshot history to maintain. Pillar 3 makes gating first worth 86% to 89% of the bill. The Explorium API is the answer for teams designing an enrichment schema before outbound. The [B2B data providers landscape](https://www.explorium.ai/data-for-gtm/b2b-data-providers/) covers the vendor view. > Design the schema against coverage you can measure. [Start a free trial: 100 credits, no subscription required](https://www.explorium.ai/sign-up/). ## Related Posts - [B2B Enrichment API Latency and Schema Consistency in 2026](https://www.explorium.ai/data-for-gtm/b2b-data-enrichment-api-latency-and-schema-consistency-2026-for-revops-teams/) - [B2B Contact Enrichment Accuracy: What to Expect in 2026](https://www.explorium.ai/data-for-gtm/b2b-contact-enrichment-accuracy-benchmark-for-ai-agent-workloads-2026-for-revops-teams/) - [Evaluating B2B Enrichment for the Automation Era](https://www.explorium.ai/data-enrichment/evaluating-b2b-enrichment-automation-era/)