the voice of customer experience technology
Front page
NewsCRM & Data16h · 11:45 BST · 4 min read

HubSpot Cuts 660 Jobs as AI Strategy Reshapes Business

The layoffs are part of HubSpot's strategy to reorganize around AI-powered customer outcomes. The vendor insists the move is not driven by AI efficiencies, but the distinction between AI efficiency and AI-led reorganization may not mean much to employees whose roles have been eliminated.

HubSpot cuts nearly 660 jobs in an AI-led business reorganization

HubSpot is cutting nearly 660 jobs, around seven percent of its workforce, as the CRM vendor reorganizes around AI-powered customer outcomes.

The layoffs come as HubSpot shifts from “building software that helps customers grow to delivering outcomes for them with AI,” according to CEO Yamini Rangan.

The timing of the layoffs is likely to draw criticism, given HubSpot recently reported Q2 revenue of $911.7MN, up 20% year-over-year, while its customer base also rose 14% to 306,446.

Despite the healthy numbers, HubSpot is not content, as Rangan explained:

“We need to move faster, stay closer to our customers and focus our resources on our highest priorities to set ourselves up for success in this next chapter. That requires difficult choices about how we are organized.”

The cuts were announced on October 6, with the company estimating that the restructuring will cost between $65MN and $75MN. Most of that will go toward severance, notice periods, and employee transition costs.

What Is Changing at HubSpot?

HubSpot is not presenting the decision as a standard cost-cutting exercise.

Instead, Rangan says the company is reshaping itself to compete in an AI market where customers increasingly expect practical outcomes, not another list of platform features.

That means moving product teams away from an organizational structure based on individual Hubs and features. In its place, HubSpot will organize around customer outcomes, such as generating demand and winning deals.

The company will also remove management layers and reduce what it calls “fragmented ownership” across teams.

It is not hard to see the logic. AI agents do not fit neatly into the traditional CRM playbook, where sales, service, marketing, and operations technology often sit in separate product and business units.

To make good on promises around autonomous customer service, sales assistance, and marketing execution, vendors need closer links between product development, pricing, go-to-market, and customer success.

HubSpot has already been moving in this direction through Breeze, its AI offering. Earlier this year, the vendor introduced outcome-based pricing for its Breeze Customer Agent, charging customers per resolved conversation rather than per seat.

That shift puts HubSpot’s commercial model closer to the value that customers expect an AI agent to deliver. But it also raises the pressure on the vendor to prove that its technology can consistently deliver those outcomes.

Not an AI Layoff, But an AI-Led Reorganization?

HubSpot has been clear that this is “not driven by AI-related efficiencies.”

Rangan also insisted that the layoffs are “not simply a cost-cutting exercise,” arguing that the business has been disciplined in growing headcount more slowly than revenue.

There is some truth in that. HubSpot reaffirmed its full-year revenue guidance of between $3.678BN and $3.686BN, representing growth of roughly 18%. In addition, its non-GAAP operating margin reached 20.3% in Q2, up from 17% a year earlier.

This is clearly not a business scrambling to stop a revenue slide.

However, the distinction between an AI efficiency cut and an AI-led restructuring may not mean much to employees whose roles have been eliminated.

The technology may not have directly replaced 660 people, but HubSpot’s AI strategy has clearly changed the skills, structures, and investment priorities it wants for the next stage of growth.

That is becoming a familiar story across the enterprise software sector.

Salesforce, for example, made headlines last year after CEO Marc Benioff confirmed the company had reduced its customer support headcount by 4,000, with AI agents taking on more work.

Salesforce’s explanation was more direct, with the vendor claiming that automation had allowed it to “rebalance” its support organization.

HubSpot’s narrative is more nuanced. It is not claiming that Breeze has replaced hundreds of employees. Instead, it is arguing that becoming an AI-first business requires a different operating model.

Still, both cases point to the same uncomfortable reality. As enterprise vendors build AI agents into their own operations and products, workforce change is likely to follow.

The CX Lesson: Outcomes Need Ownership

For CX leaders, the wider lesson is not to treat AI as a standalone automation project.

AI agents touch multiple parts of the organization. They require clean customer data, effective knowledge management, robust governance, clear escalation paths, and teams that can act quickly when something goes wrong.

That is difficult to deliver when responsibility is scattered across product groups, service functions, IT teams, and commercial leaders.

HubSpot is betting that a flatter structure and outcome-focused teams will help it overcome those challenges.

But reorganizations can create their own problems, particularly if they remove customer knowledge or weaken the relationships that help vendors understand where their products are falling short.

The real test will come after the layoffs. Can HubSpot move faster without losing the customer focus that has underpinned much of its growth in the CRM market?

For now, the company has made its position clear: the AI era will not only change the software it sells. It will change the business behind it.

rate this story
helps rank stories across CX Today
The discussion0 takes · attributed & checked

Does this reflect your experience?

opening the room…
Read nextordered by techtelligence · every pick explained
same beat · CRM & Data

AI Agents Trigger a New Battle for Customer Data Control

6 Oct 2026
matches this topicFrom Notifications to Revenue Drivers: Turning Support Channels into Growth Engines24 Sept 2026matches this topicWhy Claudeforce Indicates CRM Complexity Is Breaking Customer Experience23 Sept 2026