When Enrichment Broke Trust: What HubSpot’s Reversal Teaches Us About Pricing and Value Alignment

On July 1, 2026, HubSpot notified customers of an upcoming change to its enrichment features: starting August 4, business contact details, employer information, and email deliverability signals collected from customer accounts would be shared across other customers by default, to power a new set of data discovery and intelligence tools. Turning that off required each customer to actively find the setting and disable it before the deadline.

The backlash was immediate and loud. On LinkedIn, one post about the change picked up nearly 200 reactions and more than 140 comments within hours, as a sales leader reacted with blunt, public frustration at the news. Multiply that reaction across thousands of HubSpot admins who suddenly discovered they’d need to actively defend data they assumed was already protected, and you have a genuine trust crisis.

Six days later, HubSpot’s Chief Product Officer published a public apology, titled We Got This Wrong. And We Are Fixing It. The company reversed course entirely, declining to move forward with the terms it had announced. Most people who watched this unfold agree on one thing: HubSpot got it wrong, and the swift reversal underscores as much. But the more interesting question is why it went wrong in the first place. This wasn’t a data policy failure. It was VALUE DRIFT — and it’s a sharp reminder of how central licensing is to the customer experience.

What Actually Broke
HubSpot’s own explanation is instructive. The company said its intent was to work with narrowly scoped, professional-level contact details in a shared enrichment dataset — something it framed as a natural extension of existing enrichment features. But it acknowledged that the rollout made customers feel their CRM relationship “was changing underneath you” (HubSpot, We Got This Wrong).

That admission is the real story. Nothing about the underlying data changed the day the email went out. What changed was the customer’s understanding of what they had licensed. Every HubSpot customer made their original purchase decision — a pricing decision — based on an implicit contract that their CRM data would stay theirs. The enrichment announcement didn’t just change a feature; it quietly renegotiated that contract by making participation the default rather than the choice.

This is value drift: the gap that opens up when Product ships a change that alters what a customer is actually getting, or giving up, without any accompanying renegotiation of price, licensing, or consent. The team likely saw an opt-out toggle as a reasonable technical control. Customers experienced it as their vendor unilaterally deciding to monetize something they never agreed to license away.  It got heated quickly.

Why This Is a Pricing Problem, Not Just a Privacy Problem
It’s tempting to file this under “data privacy misstep” and move on. But the sharper lesson is about how organizations govern the boundary between Product and Pricing.

Every meaningful expansion of what a vendor extracts from a customer relationship — more data, more attention, more lock-in, more downstream use of the customer’s own assets — is, functionally, a price increase. It simply isn’t denominated in dollars. When that expansion ships through a feature announcement instead of a commercial conversation, the organization is making a pricing decision without anyone in the room who is actually accountable for pricing strategy, licensing terms, or customer trust.

To its credit, HubSpot’s fix gets this right in principle: the company committed that future enrichment capabilities will be fully opt-in, with customers given clear, upfront control over participation. That isn’t a product tweak. It’s a licensing commitment — a statement about what the customer relationship actually includes, made explicit instead of buried in a terms and conditions page.

The Question Worth Asking Before You Ship
For any product leader watching this unfold, there’s a simple test worth applying before shipping a change that touches customer data, defaults, or usage terms: if you are fully transparent with the customer about what this change actually asks of them, will you need to renegotiate price? If yes, it’s a pricing conversation — not a settings toggle.

Trust, in a subscription business, is the actual currency changing hands every renewal cycle. Customers aren’t just buying features; they’re buying a stable definition of what they’ve agreed to and a sustainable relationship. When that definition drifts without consent, no apology — however well written — fully closes the gap.  HubSpot got the apology right. The more useful question for the rest of us is how to manage pricing and product alignment so that publishing one is never necessary in the first place.

_______
Sources: HubSpot customer email, “Updates to enrichment features and choices” (Hub ID 5911074); LinkedIn post and comment thread reacting to the announcement; HubSpot Community post, “We Got This Wrong. And We Are Fixing It,” published by a HubSpot employee.