HubSpot plans nearly 660 job cuts—and says AI efficiencies aren’t the driver

HubSpot, a software company, plans to eliminate about 7% of its workforce—nearly 660 people, according to its chief executive’s October 6, 2026 employee update. Alongside that job-cut announcement, she explicitly says the decision is not driven by AI-related efficiencies. [3] [2]

The immediate economics are job losses and a transition bill, rather than a measured productivity dividend. For customers, the question is whether fewer layers make the business better at delivering results without weakening the service. For employees, a future efficiency gain would not erase the disruption from losing a role.

The chief executive describes a shift toward delivering customer outcomes with AI. She says product teams will organize around those outcomes, and management layers will be reduced. This is management’s proposed redesign of how the company works, not a completed productivity result. [3]

In a hypothetical sales-workflow team, clearer ownership could mean fewer handoffs before a customer problem gets fixed. The observable benefit would be shorter delivery times or better customer retention, not merely a smaller payroll. Cutting staff without removing the same work could instead leave the remaining employees stretched.

HubSpot estimates $65 million to $75 million of restructuring charges, primarily future cash expenditures. Role eliminations are subject to local law and consultation requirements, and the company expects substantially all related cash payments by June 30, 2027. These are estimated costs and an expected payment milestone, rather than reported completion. [2]

HubSpot reaffirmed its revenue and adjusted operating-income guidance, while excluding restructuring charges from its non-GAAP financial measures. [2]

Non-GAAP, or adjusted, results remove specified items from the standard accounting presentation. Removing a charge from that measure does not cancel the underlying payments. An unchanged adjusted outlook is not a statement that the reorganization costs nothing. The transition bill and any later operating improvement need to be assessed separately, rather than letting the adjusted-profit presentation stand in for cash economics.

The strongest alternative to an AI-efficiency explanation is the one management gives: reorganizing teams to work better. A smaller, flatter structure could speed up delivery even without automation replacing jobs. But the opposite is also possible: lost capabilities and overloaded teams could harm customers. Improved delivery times and customer retention would support management’s account; deterioration would weaken it.

The next financial reports should be checked for actual restructuring charges and cash payments, alongside the announced completion milestones. Keep expense recognition separate from cash paid out: the two can land in different periods. Pair that accounting check with customer retention and product-delivery times. A leaner organization that meets its timetable but loses customers would not validate the proposed improvement.