HubSpot told employees on October 6 that it is reducing its team by about 7%, nearly 660 people, and reorganizing product development around customer outcomes instead of its Hubs.
What happened
In a message to all staff that HubSpot published in its newsroom, CEO Yamini Rangan said product teams will be organized around goals such as generating demand, winning deals, delighting customers and scaling growth. Each team will own the full customer journey. HubSpot will also reduce management layers and reduce fragmented ownership. “Customers don’t think in Hubs and features,” Rangan wrote.
The message ties the change to a strategy shift. HubSpot says that over the past year it moved from building software that helps customers grow to delivering outcomes for them with AI, and that the shift is changing product, pricing and how it serves customers. Rangan said the cuts are not driven by AI-related efficiencies and are not simply cost-cutting, and that HubSpot will keep growing headcount more slowly than revenue.
Why it matters
A vendor’s team structure sets who answers a customer’s question and what gets built next. A team organized around a product line maps to a function. An outcome team maps to a result that crosses functions. A sales leader who buys one product line should expect roadmap and support conversations to move toward whole journeys, from demand to closed deal.
Our read
We covered HubSpot’s September release, which pitched a CRM that updates itself. The October 6 message adds the organizational side of the same bet. Salesforce has made a parallel move on the measurement side with its attempt to put a real number on Agentforce ROI.
An outcome has no seat count. RevOps teams renewing a CRM contract this quarter should ask their account team who owns a result when it spans products that used to be sold and supported separately, and how that result will be measured in the order form.
Source: HubSpot, A message from our CEO
