Facing a Revolt, HubSpot Reverses Decision to Use Customer Data For AI Feature
Why I picked this
Boy is Hubspot floundering. Their CEO has to be on the hot seat. And not saying its all her fault either but...
“HubSpot's reversal is another demonstration of the leverage that businesses have with traditional software firms nowadays—some large customers have been able to shorten their contracts with software firms keen not to lose clients given fears of rising competition from AI companies.”
Key takeaways
- Customer data governance is now a critical vendor selection criterion—HubSpot's 4-day reversal shows how quickly enterprise customers will mobilize against perceived data misuse in AI features
- Enterprise software vendors face unprecedented leverage loss: stock down 75%, sales growth slowing, and customers now able to negotiate contract terms as AI competition intensifies
- Default opt-in for data collection is now a liability for SaaS vendors; the shift to opt-out triggered immediate backlash, signaling that customers expect explicit consent for AI training data usage
- This sets precedent for how other vendors (Salesforce, Microsoft, etc.) will need to handle customer data in AI features—transparency and customer control are now table stakes
Why this matters for operators: Enterprise software buyers, GTM leaders evaluating vendor risk, data governance teams; also relevant for vendors navigating AI feature rollouts without alienating customers
I cover AI×GTM intelligence like this every Wednesday.
Get STEEPWORKS WeeklyMore picks
Humans will keep inventing new reasons why we must stay in the loop with agents
- Human resistance to full AI autonomy is not purely technical—it's psychological and organizational; companies will rationalize keeping humans in decision loops even when agents are capable
- The 'human-in-the-loop' requirement may become a self-perpetuating narrative rather than a genuine necessity, driven by organizational risk aversion and change resistance
- Product leaders at scale (Notion) are observing this pattern, suggesting it's a widespread phenomenon across enterprise AI adoption, not isolated to specific use cases
Comp plans for consumption pricing
- Consumption pricing fundamentally breaks traditional SaaS comp models—requires rethinking sales incentive structures around usage vs. contract value
- Four distinct contract structures exist (pay-as-you-go, uncommitted, committed, hybrid), each requiring different compensation mechanics and sales behaviors
- Enterprise consumption-based deals create tension: customers want flexibility, sales teams need predictability for quota attainment—comp design must bridge this gap
3 revenue motions your AI is only half wired into
- Model parity has arrived: OpenAI/Claude now trade evenly on core tasks, making 'better AI' a non-differentiator—the edge shifts to integration depth into existing revenue motions
- Waste is quantified: teams paying $17K-$37K/month for AI seats that never touch pipeline generation; real cost is opportunity cost of unused capacity, not subscription fees
- Lean teams have a structural advantage: cannot out-buy larger competitors on model access, but can out-embed them by wiring AI 1 revenue motion deep (pipeline → content → deals) with proprietary deal context competitors haven't seen
This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.