How to enrich HubSpot lead data automatically (2026 guide)

TL;DR: HubSpot enriches firmographic and form-fill data through Breeze Intelligence (credit-based). Its Spring 2026 Breeze AI release also added call capture and Smart Deal Progression, which suggests CRM updates after recorded calls. But those suggestions need a rep to accept or reject each one, stay scoped to a single call and to standard deal properties, and do not map conversation content to custom MEDDIC or BANT fields or fire downstream workflows. HubSpot also has weaker coverage for SMBs and non-US contacts. Building a complete, automated CRM requires a hybrid "waterfall enrichment" stack: configure Breeze first, then add a CRM automation layer like AskElephant that captures what gets said on calls and writes it directly to HubSpot deal fields.

RevOps teams spend up to 32 percent of their week cleaning CRM data that reps should have captured accurately at the source. The problem isn't that reps are ignoring HubSpot. Your enrichment stack stops at the form fill, leaving every qualifying conversation, objection, and next step locked inside someone's memory rather than the system of record.

Most HubSpot enrichment guides fall into one of two traps: they overstate what HubSpot handles natively, or they treat native tools as useless and jump straight to expensive third-party databases. Both framings miss the operational reality. Breeze Intelligence handles firmographics reliably and cost-effectively for the accounts it covers. Its Spring 2026 call tools can suggest deal updates after recorded calls, but they stop short of writing conversation data to your custom deal fields automatically, and that conversational layer is where deal records go dark and forecasts go wrong.

This guide covers exactly how to configure HubSpot's native enrichment tools, where they hit their operational ceiling, and how to build a hybrid stack that automates data capture from first form fill through closed-won, including the conversational data that native tools can't reach.

What HubSpot can enrich natively (and how to turn it on)

HubSpot Insights and the transition to Breeze Intelligence

HubSpot Insights, the legacy free auto-enrichment feature that automatically populated company records with publicly available firmographic data, ended on March 17, 2025. As About Inbound's analysis of the transition explains, HubSpot deprecated Insights to address its core limitations: outdated data, incomplete records, and inconsistent coverage. Breeze Intelligence is now the native enrichment layer for all HubSpot accounts.

The Intelligence tab in HubSpot still exists and surfaces firmographic data, including employee count, company type (public or private), annual revenue, industry, address, and company description. The difference is that accessing enriched data now routes through Breeze rather than the legacy Insights engine. To enrich a record manually, navigate to the contact or company record, click the Intelligence tab, and if new data is available, click "Enrich record."

Breeze Intelligence credit-based enrichment

Breeze Intelligence is HubSpot's native enrichment layer, drawing from over 200 million profiles to fill contact and company records with firmographics, technographics, and buyer intent signals. Key data categories include industry, employee count, revenue range, tech stack, and anonymous website visitor identification through Buyer Intent.

The billing model transitioned in June 2025. Basic contact and company enrichment is now included with many HubSpot subscriptions, and standard firmographic data typically no longer consumes HubSpot Credits for most users. If you exceed your included allocation, HubSpot automatically adds credit packs in 1,000-credit increments at $10 each. The credit burn conversation now centers primarily on high-volume enrichment of unqualified contacts and Buyer Intent monitoring, not routine record updates.

The practical implication for RevOps: Breeze is efficient for enriching qualified contacts and accounts in active pipeline, but you need workflow guardrails to prevent burning credits on unqualified leads that haven't passed ICP criteria.

Form-fill enrichment setup

Form-fill enrichment appends firmographic data to contact and company records the moment a form is submitted, before the lead reaches a rep's queue. The setup process using HubSpot Workflows follows a clear sequence:

1. Create the workflow trigger: Set enrollment to trigger on form submission.
2. Add the Enrich data action: Available under workflow actions within your HubSpot account.
3. Set conditional logic: Only enrich if specific fields (such as Job Title or Company Size) are empty, so you avoid overwriting existing data or burning credits unnecessarily.
4. Define target properties: Specify which HubSpot properties should receive enriched data on submission.

This setup ensures that by the time a rep receives a lead notification, the contact record already carries company context, reducing the pre-call research time before first outreach.

Workflow-triggered bulk enrichment

Bulk enrichment applies Breeze data to existing records already in your CRM. Build a list of contacts or companies that meet enrichment criteria (for example, contacts with empty Industry or Employee Count fields), then create a workflow that targets list members and applies the Enrich data action.

Before running bulk enrichment, deduplicate your records. Enriching duplicate records wastes credits and creates conflicting field values that produce reporting errors downstream. Run a deduplication pass through HubSpot's native deduplication tool or a third-party tool like Dedupely before enrolling records in bulk enrichment workflows.

Quick setup walkthrough

The core navigation path to configure enrichment in HubSpot:

1. Go to Settings in your HubSpot account.
2. Navigate to Data Management and select Data Enrichment.
3. Toggle on automatic enrichment for contacts and companies, or configure manual triggers per workflow.

Before layering enrichment on top of existing records, the free HubSpot CRM Health Grader grades completeness and field hygiene across your current records so you know exactly which gaps you're solving for.

Where native HubSpot enrichment hits its ceiling

Call capture stops at suggestions, not automation

HubSpot's Spring 2026 Breeze AI release added real call-to-CRM capability, and an accurate enrichment plan has to account for it. Breeze AI Notetaker joins Zoom, Google Meet, and Teams calls, transcribes them, and generates summaries and action items. Smart Deal Progression goes further: after every recorded call, it suggests CRM updates such as deal stage changes, amount updates, and next steps, and it drafts follow-up emails, all grounded in your pipeline definitions.

That is genuinely useful, and it closes the gap where a rep forgot to update a deal. But it stops at suggestions. A rep still has to accept or reject each one, so it is a nudge rather than automation. The suggestions are single-call, single-deal scoped, with no analysis across a deal's full call history. And they cover HubSpot's standard deal properties, not the custom MEDDIC or BANT qualification fields most revenue teams forecast against. Objections surfaced during discovery, budget ranges confirmed in a follow-up call, and named stakeholders still do not land in your custom methodology fields without third-party automation.

That gap is the reason deal records go dark between the first call and close. For a deeper look at why automated CRM enrichment matters beyond firmographics, the distinction between data that describes a company and data that describes an active deal is the operational fault line where most revenue teams lose ground.

Meeting-derived MEDDIC and BANT fields stay manual

Qualification frameworks like MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) and BANT (Budget, Authority, Need, Timeline) require extracting structured signals from live conversations, then mapping those signals to specific CRM fields.

HubSpot's Data Agent can auto-populate custom properties using AI, so it is not accurate to say HubSpot does no custom-field automation. But Data Agent enriches from web research and a thin slice of CRM context, runs prompt by prompt, and user reports put its reliable ceiling at roughly 75 records before output quality degrades. It was built to answer questions like "what is their tech stack", not to read a discovery call and populate your Economic Buyer, Decision Criteria, and Champion fields. Smart Deal Progression suggests updates to standard deal properties from a single call, not methodology fields across the deal. Whether your prospect confirmed economic buyer access on a call last Tuesday still does not reach your custom MEDDIC properties on its own.

This is the gap that produces the most expensive downstream failures: forecasts built on deals where qualification fields are empty, coaching conversations where managers reconstruct call content from memory, and CS handoffs where post-sale teams inherit blank records. The best AI tools for sales operations address this gap by extracting methodology-mapped data from calls rather than relying on rep-typed summaries.

Thin SMB and non-US coverage

Breeze draws from public web data and commercial databases, but coverage degrades on smaller companies and contacts outside North America. Dedicated intent and regional enrichment tools can address some of this, but it's worth understanding the structural reason: as firmographic data provider research documents, most major databases share the same source architecture (LinkedIn plus corporate web data), which means moving between providers may not solve local or SMB coverage gaps the way teams expect. If your ICP includes SMBs, early-stage companies, or accounts in EMEA, plan to evaluate coverage specifically for those segments before assuming a top-up tool solves the problem.

Credit costs at scale

Even with standard enrichment included for Core seat holders, enrichment at volume adds cost, particularly for Buyer Intent monitoring and high-volume contact enrichment. Enriching every inbound contact regardless of ICP fit or lead score burns credits on records that will never progress past MQL. Workflow logic that gates enrichment behind qualification criteria keeps your credit consumption proportional to pipeline potential rather than raw contact volume.

Buyer Intent covers surface signals only

Breeze's Buyer Intent feature identifies companies visiting your website and monitors enrolled prospects for purchasing signals, which is genuinely useful for prioritizing outreach timing. However, it does not provide the breadth of real-time signals that dedicated intent platforms generate: active research on competitor products across the broader web, topic-specific Surge data, or technographic shifts indicating a vendor evaluation. Teams that need deep purchase-stage intelligence will find Breeze's intent layer a starting point, not a complete solution.

Tools that pair with HubSpot to fill the gaps

For conversational and post-meeting data

AskElephant's HubSpot integration captures call data through three methods: a desktop app (botless recording), a mobile app for in-person conversations, and a bot recorder that joins virtual meetings. Botless recording via the desktop app is becoming the preferred capture method as bot reliability issues grow and meeting platforms like Google Meet add friction to bot-based solutions, but all three methods remain available so teams can maximize capture coverage across every conversation type. More complete capture coverage means more conversation data written to HubSpot, which means higher quality output from the downstream workflow automations that depend on it. AskElephant extracts structured signals from those transcripts and writes that data directly to HubSpot company, deal, and contact properties.

The output is not a summary dropped into a notes field. It's field-level data mapped to your specific HubSpot schema, triggering the same downstream workflows that would fire if a rep typed the data manually. The difference is that it fires automatically, at the moment the call ends, without any rep action required.

The operational proof is direct: Vendilli, a marketing agency, started at 15% CRM data completion and reached 90% after deployment of AskElephant's field automation. The downstream improvements in forecasting accuracy and CS handoff quality followed directly from that data quality shift.

"I use AskElephant as a source of truth for what's going on with a specific deal or account. It's better than my CRM because it actually knows all of the transcripts from the calls and I can chat not just about a single call but multiple calls. I also love the workflows that it facilitates for us, things like updating certain fields in our CRM or sending us a slack update about accounts with churn risk." - Verified user on G2

For teams who have evaluated Gong and found it stops at observation rather than execution, the distinction matters practically. Gong tells you what happened in a call. AskElephant writes what happened to your HubSpot fields and fires the downstream triggers. The Gong vs. AskElephant mid-market TCO breakdown covers the cost and capability gap directly.

For broader contact firmographics

When Breeze returns incomplete data on enterprise or mid-market contacts, Apollo and ZoomInfo provide additional coverage. ZoomInfo draws from 174 million email addresses and 135 million+ verified phone numbers for B2B contacts, with multi-source data curation from public records, business websites, annual reports, and verified user contributions. Apollo offers broader accessibility for growth-stage teams at a lower entry price.

One important caveat: both Apollo and ZoomInfo share the same structural source architecture (LinkedIn plus corporate web data), so switching between them won't resolve SMB or regional coverage gaps. Both platforms have similar limitations for smaller companies and non-US contacts. Position these tools as top-up layers applied through waterfall logic for mid-market and enterprise contacts where Breeze returns incomplete data, not as universal fixes for every coverage gap.

For intent and buying signals

6sense and Bombora provide real-time buying signal depth that Breeze's Buyer Intent doesn't match. 6sense's Signalverse ingests first-party, second-party, and third-party intent data and classifies accounts into predictive buying stages based on cross-web research behavior. Bombora offers Surge data that flags when a target account is actively researching your category and comparing competitors. Both integrate with HubSpot to score and prioritize accounts based on purchase-stage signals rather than static firmographic data. Choose 6sense for account-level prioritization or Bombora for topic-specific intent tracking.

For LinkedIn-sourced contact data

Hublead and Surfe extract LinkedIn profile data, recent activity, and professional history directly into HubSpot contact records. This fills gaps where firmographic databases carry incomplete job title or role data.

Building a hybrid HubSpot enrichment stack

Waterfall enrichment is the operational model that makes a multi-tool stack cost-efficient. The waterfall queries providers sequentially, moving to the next source only when the previous one returns no match. Each layer handles what it does best, and no record gets enriched by more providers than necessary.

Here's the recommended build sequence:

1. Turn on Breeze Intelligence. Configure your enrichment settings in HubSpot's Data Management panel and set workflow triggers to enrich company records as soon as a domain is associated. This is your baseline layer, and for many subscription tiers, basic company and contact enrichment runs without consuming additional credits.
2. Decide how to gate credit-consuming enrichment. Evaluate your inbound volume and Ideal Customer Profile (ICP) match rate before enrolling contacts in enrichment workflows that consume HubSpot Credits. Set workflow conditions to trigger enrichment only on contacts at Marketing Qualified Lead (MQL) or above, exclude industries outside your ICP, and set a minimum lead score threshold as a gate. This keeps credit consumption proportional to pipeline potential rather than raw contact volume.
3. Layer in conversational enrichment. This is where AskElephant slots into your HubSpot integration. Once a qualified contact enters active pipeline and a discovery call is scheduled, AskElephant captures the call, extracts structured deal signals, and writes them to the HubSpot deal record automatically. MEDDIC fields populate. Documented objections populate. Confirmed next steps populate. The Customer Success (CS) team inherits a complete deal history at contract close rather than a blank record and an AE debrief. For a detailed look at what this execution layer looks like in practice, the guide on AI tools that update CRM after meetings covers the mechanics directly.
4. Add firmographic top-up tools only where coverage gaps appear. Run your enriched records through a completeness report after steps 1 through 3. If Breeze returns incomplete data on a meaningful percentage of your ICP accounts (particularly enterprise contacts where ZoomInfo or Apollo have stronger coverage), add a waterfall layer that fires only when Breeze returns no match. Set field-level priority rules to handle data conflicts: define which source wins when two providers return different values for the same property.

HubSpot enrichment setup checklist

Before going live with a hybrid stack, run through these steps:

• Breeze Intelligence enabled and confirmed active on contact and company records
• Enrichment workflow built with ICP qualification gating (MQL or above, ICP industry, minimum lead score)
• Deduplication completed before bulk enrichment run
• Contact and company records linked (no orphaned contacts)
• AskElephant configured with your HubSpot field schema and mapped to target deal properties
• Waterfall logic defined (Breeze fires first, top-up tools fire only when Breeze returns no match)
• Data conflict resolution rules set at field level
• CRM health baseline recorded using the free CRM Health Grader before and after

Common mistakes that break HubSpot enrichment automations

Over-enriching every contact

Running Breeze enrichment on every contact in your CRM, regardless of lifecycle stage or ICP fit, burns credits on records you will never move into active pipeline. The fix is waterfall logic with enrollment criteria: only trigger enrichment on contacts at MQL or above, exclude industries outside your ICP, and set a minimum lead score threshold as a gate. Teams where enrichment runs without qualification filters often report that conflicting or irrelevant data creates more cleanup than it prevents.

Not deduping before enriching

Running enrichment on duplicate records creates two versions of the same contact with potentially different field values for the same properties. The result is CRM data that looks enriched but generates conflicting output in reports and workflows. Always run a deduplication pass before executing bulk enrichment.

Enriching contacts but not companies

Account-level reports can show gaps when your company record lacks enriched fields. Enrichment workflows need to target both the contact and the associated company record, not just the contact.

Skipping conversational data

This is the biggest structural gap in most HubSpot enrichment stacks, and it is the root cause of dirty deal data and failed CS handoffs. Firmographic enrichment tells you about the company. It does not tell you about the deal. What a prospect said about their budget on the discovery call, which stakeholders they named as blockers, what objections surfaced in the follow-up: none of that enters HubSpot through Breeze or any firmographic database. It enters HubSpot only through a conversational enrichment layer.

Randy B., reviewing AskElephant on G2, described the integration directly:

"We love AskElephant's integration with HubSpot, which helps us stay aligned and informed. The simple setup process and supportive team made our transition smooth. I appreciate the AI's ability to interact with meeting transcripts, improving visibility and efficiency. Workflow automation in Slack enhances our productivity." - Verified user on G2

For teams building out a complete RevOps stack, the modern RevOps stack for fast-growing startups guide maps out how these enrichment layers connect to the broader tooling architecture.

See field-level automation in your own HubSpot schema

HubSpot's native enrichment gets you firmographics and suggested deal updates. The conversational layer, the budget confirmed on a call and the stakeholders named as blockers, still needs a CRM automation layer to reach your deal fields. Book a demo and we will configure AskElephant against your actual HubSpot deal properties, not a generic sandbox, so you can see the execution layer in your own environment.

Key terms glossary

Waterfall enrichment: A sequential data enrichment method that queries multiple providers in order, moving to the next source only when the previous one returns no match, preventing duplicate credit spend while maximizing data coverage across the full contact and company database.

Technographics: Data describing the technology stack a company uses, including software platforms, cloud providers, and tools, used to identify accounts running complementary or competing products as part of ICP targeting.

Intent data: Behavioral signals indicating that a company is actively researching a product category, comparing vendors, or exhibiting purchase-stage behavior, sourced from content consumption, search activity, and third-party B2B networks.

CRM hygiene: The operational state of a CRM where you populate fields accurately, deduplicate records, and capture data that reflects actual deal status rather than what reps remembered to type, forming the data quality foundation for reliable forecasting and workflow execution.