Four Days: How Fast HubSpot Reversed Its Enrichment Terms
HubSpot's changed its CRM data governance amid backlash. Governed b2b data enrichment keeps your pipeline under your control.
By Ronan Leonard, Founder, Intelligent Resourcing
HubSpot announced Contact Discovery on 1 July 2026 and reversed the supporting terms changes four days later, after customer backlash.The controversy was about b2b data enrichment running without clear governance, not about the feature itself. CRM data is commercial intelligence where when a team cannot account for where it comes from or how it is governed, a platform term change is all it takes to expose the gap.
HubSpot planned to let enrichment data from customer CRMs feed a shared dataset. Customers pushed back. HubSpot reversed the terms on 5 July.
The specific mistake is fixed. The wider gap remains. Most B2B teams do not govern their enrichment data, signal sources or CRM data flows.
Platform enrichment is convenient, but the logic running underneath it is not visible to the team depending on it. When terms change, a team without a governed signal layer has no fallback.
The answer is a revenue system where the data logic is owned, not borrowed from a platform. Intelligent Resourcing's GTM Engineering practice builds governed signal-led systems to make that possible before the next platform update arrives.
Factor | Platform Enrichment Default | Governed Signal-Led Enrichment |
Data source visibility | Platform-managed, not visible | Documented per field |
Signal logic | Platform-defined, shifts with terms | Client-owned, auditable |
Opt-in control | Opt-out required, settings scattered | Explicit opt-in per source |
Risk when terms change | Outreach logic shifts without warning | System continues unaffected |
CRM data trust | Varies by platform update cycle | Verified, timestamped, sourced |
Platform enrichment is a useful starting point, not a revenue strategy. A Verified Buying Window™ only holds if the signal underneath it is clean and governed. A team that delegates that logic entirely to a platform finds out it was borrowed the moment the terms change. B2B teams need governed signal-led growth systems that keep data, intent and pipeline creation accountable. Better enrichment alone does not get there.
What Was HubSpot's Contact Discovery Change?
On 1 July 2026, HubSpot updated its Product Specific Terms. Customers using enrichment features would allow HubSpot to add enrichment data to its commercial dataset, which could then be used to enrich other customers' records. Contact Discovery, planned to launch 4 August, was built on top of that shared pool.
In scope: names, job titles, company affiliations, work email addresses, company data and tracking-code signals.
Out of scope: notes, deals, call recordings, custom fields and internal CRM records.
Most B2B teams treat the in-scope fields as standard prospecting data, which is exactly why the change was commercially significant. Customers pushed back for three reasons:
Business contact data powers prospecting and outreach decisions directly.
Customers had not explicitly agreed to their contacts contributing to a shared dataset.
The opt-out lived inside Settings under Data Management and Data Enrichment, a location most customers had never visited.
A detailed breakdown from CMSWire notes that the backlash centred on customers being opted in by default rather than asked, with critics arguing the plan treated customer-built CRM data as HubSpot's to redistribute.
HubSpot's Reversal and the Trust Gap It Exposed
On 5 July, HubSpot's chief product and technology officer posted a public reversal titled "We Got This Wrong. And We Are Fixing It." The terms changes were scrapped. Future enrichment features using customer data would be transparent and fully opt-in, and CRM data would not be used without explicit permission.
The reversal was the right call. What the backlash confirmed is that most customers had not read the updated terms, did not know the opt-out existed, and could not explain how their contact data was being used inside the platform running their pipeline. That is the common state for most B2B teams using any CRM with enrichment enabled, not just HubSpot customers.
Commercial intelligence is the raw material of revenue. Contact records, engagement signals and buying behaviour tell a team who to contact and when. When a team cannot account for where that data comes from, how it updates or what governs it, the pipeline built on top of it is fragile. A term change makes that fragility visible. So does a data audit, a compliance review, or a sales rep questioning a stale contact record.
Regional exposure varies too. Analysis from Mi3 Australia points out that Australian brands can face separate privacy compliance questions if business contact data collected for sales or marketing is later used for AI training or enrichment without disclosures that align with the Privacy Act.
The Problem That Outlasts the Rollback
B2B data enrichment done well is one of the highest-leverage actions a revenue team can take. Fresh contact data, accurate job titles and verified company signals improve outreach precision directly. The problem is enrichment running without governance.
A few numbers show why this matters beyond one vendor's terms page:
Issue | Reported figure | Source |
Average annual cost of poor data quality | USD 12.9 million per organisation | |
Organisations losing more than USD 5 million a year to data quality issues | Over a quarter of organisations | |
Annual decay rate of B2B contact data | Roughly 22.5% per year |
A team most exposed when a platform changes its terms treats enrichment as infrastructure it inherited rather than a system it owns. The settings were configured during onboarding, the data has been refreshing in the background ever since, and nobody on the revenue team can say with confidence which fields are platform-enriched, which are first-party, and which have never been touched.
The HubSpot incident spread because the terms change surfaced in a community post. Most platform updates land in a legal notice or changelog nobody reads. By the time a team realises its signal logic shifted, the pipeline has already been running on bad inputs.
How Does a Governed Signal Layer Work?
Intelligent Resourcing's GTM Engineering practice builds the governed enrichment layer before any outbound motion starts:
Documents sources per field, so every value in the CRM can be traced back to where it came from.
Defines refresh logic, so the team controls how and when a field updates.
Sets overwrite rules the client controls, replacing a platform toggle with a structure the client owns.
Platform-provided buyer intent signals are generated on your data but processed through a platform's infrastructure. When a platform changes its terms or its signal methodology, outreach logic shifts with it. Owned signals such as technographic triggers, hiring events, funding rounds and leadership changes fire against logic the client builds and controls, so a platform update does not move the goalposts on active campaigns. Intelligent Resourcing's CRM Enrichment approach runs this kind of signal detection inside a client's existing CRM, rather than waiting on a platform's own roadmap.
The same principle applies at the AI search layer. Before any content is produced or outreach initiated, a business needs to confirm its brand entity, category signals and data consistency across every touchpoint. Intelligent Resourcing's Answer Engine Optimisation service applies this at the level of AI answer engines rather than CRM records. In both cases, the platform serves the strategy only when the team controls the data behind it.
Checks Worth Running Before the Next Platform Update
# | Check | What to confirm |
1 | Enrichment settings | In HubSpot: Settings → Data Management → Data Enrichment. Which automatic and continuous enrichment features are active, which fields they update, and what the overwrite behaviour is. |
2 | Source separation | Which contact fields came from platform enrichment, first-party form fills, manual entry, or third-party data tools. If every record looks identical regardless of source, data quality cannot be audited. |
3 | Opt-out settings reviewed independently | HubSpot's updated DPA applies controller-to-controller terms across enrichment features, AI model training, and tracking-code intent data sharing, as three separate settings. Turning off one does not affect the others. |
4 | Signal logic documented | Can outreach sequences, account prioritisation rules and lead scoring logic be explained without referencing a platform's enrichment output? If not, the signal system is borrowed, not governed. |
Fit Check
Best for:
B2B teams using HubSpot enrichment who have not reviewed their settings since 1 July 2026
Revenue leaders relying on platform-provided enrichment without a documented first-party signal layer
Companies building outbound systems that need to compound over time rather than shift with platform terms
Not for:
Early-stage teams where manual outreach covers the full addressable market and enrichment is not yet in use
The trade-off: a governed b2b data enrichment system takes longer to build than enabling a platform enrichment toggle. The toggle is faster to turn on. The governed system is harder to have turned off on you.
Your CRM data is already generating commercial intelligence. The HubSpot backlash proved that governing your enrichment layer is a revenue decision.
Run a governed enrichment review →
FAQs
What did HubSpot announce on 1 July 2026?
HubSpot updated its Product Specific Terms to allow enrichment data from customer instances to feed its commercial dataset and enrich other customers' records. Business contact information, company data, website visitor signals and email engagement data were in scope. Notes, deals and call recordings were not.
Why did HubSpot reverse the decision?
Customers objected to their business contact data contributing to a shared dataset without explicit opt-in. HubSpot acknowledged it did not communicate the changes clearly and confirmed on 5 July the terms would not go forward.
What separates platform enrichment from governed enrichment?
Platform enrichment runs on the platform's schedule and logic, invisible to the team depending on it. Governed enrichment documents sources, refresh rules and confidence scoring per field, so the team controls data quality rather than inheriting platform defaults.
Does turning off HubSpot enrichment cover the other settings?
No. HubSpot applies controller-to-controller terms across three separate settings covering enrichment features, AI model training and tracking-code intent data sharing. Each needs to be reviewed and configured independently.
