On May 5, 2026, Freshworks reported Q1 FY26 results — revenue $228.6 million, up 16% year-over-year, an 18% non-GAAP operating margin and 24% adjusted free-cash-flow margin. On the same call the company announced it would cut roughly 500 employees — about 11% of its global workforce — and take an $8 million one-time restructuring charge. CEO Dennis Woodside, in the prepared remarks: “over half of our code originates in AI today.”
The line is the headline. The pattern underneath it is the story.
This is the second 「11% cut」 in 18 months
Freshworks did the same cut in November 2024 — around 660 employees, roughly 13% of the workforce, framed at the time as “operational efficiency and AI-led transformation.” The cycle is now public: every twelve to eighteen months, Freshworks cuts ~10–13% of headcount and attributes the cut to AI-driven productivity gains.
That cadence is not, on its own, a scandal. It is the working business model of a public-software company in 2026. The math: Freshworks grew Q1 revenue 16% YoY but the median software-multiple compression of the last three quarters means the multiple expansion that used to forgive flat margins is gone. Operating leverage has to come from somewhere. The two places it can come from are pricing — which compressed across SaaS in 2025 — and headcount. The CEO is telling the market: it is going to keep coming from headcount, and “AI” is now the framing that makes the recurring cut sound forward-looking instead of defensive.
The Q1 print itself was good. 1,648 customers paying more than $100,000 in ARR, up 29% YoY. The two largest deals in Freshworks history closed in the quarter, including the firm’s first seven-figure ARR contract in the employee-experience segment. This is not a company in distress. It is a company choosing — in the same press cycle that it announces $228M in quarterly revenue and record large-deal velocity — to remove 500 people from the org.
What 「over half our code is AI」 actually says
Strip the line of its hero framing and what is left is a productivity ratio. Freshworks’ engineering org now ships code at a rate where AI-authored commits exceed human-authored ones. The unstated implication: the firm’s previous engineering headcount produced X dollars of ARR per engineer. Its new engineering headcount, augmented by AI coding tools, produces meaningfully more — enough that 500 of the engineers, support staff, and middle managers who supported the old ratio are no longer needed at the new one.
This is the same number Sundar Pichai gave at Cloud Next on April 27 — Google’s internal code is now 75% AI-authored, up from 30% a year ago. It is the same number Anthropic implied in its $50B/$900B coding-agents revenue thesis on May 3. It is the same number TCS and Infosys’ FY26 negative-headcount guidance was built on. Five different companies, on three continents, in two months, all reporting to investors that their engineering output has decoupled from their engineering headcount.
The cohort being cut at Freshworks is the same cohort being cut at the others: the support-engineer / mid-level developer / process-coordinator layer. The job functions where an AI coding tool delivers the most assist per hour are the job functions that lose seats first. There is a name for this in the literature — Goldman called it the 「skills chasm」 on May 5 — and there is a recipe for it in the executive playbook. Freshworks just ran the recipe.
Why this print was the right time
Freshworks gave FY26 revenue guidance of $958–964M, which back-solves to ~14% growth for the full year — a deceleration from Q1’s 16%. The cut, taken now, gives the firm two quarters to absorb the $8M severance charge and let the operating margin lift flow into the back half of the year. By Q4 the revenue line might be slowing into the low-teens but the margin line will be visibly expanding, and the buy-side narrative writes itself as “Freshworks executed AI-driven margin discipline ahead of the multiple compression.”
The same shape Coinbase ran yesterday with its 14% cut two days before its Q1 print. The same shape Accenture ran on May 5 with its $865M reskill-or-exit charge across 85K employees. The same shape Salesforce ran in late April with its 1,000-grad narrative-violation cut. Different companies. Same operating-margin maneuver. AI as the framing layer over what is, mechanically, a SaaS-multiple-defense exercise.
What to watch through Q2
- The August Q2 print. Freshworks has now told investors that AI is doing more than half the engineering work. The Q2 print is the first quarter where that claim is testable against shipped-feature velocity. If feature releases visibly slow in the back half of FY26, the framing falls apart.
- The 1,648-customer cohort. Large enterprise customers paying $100K+ ARR are the part of the book that asks the most demanding implementation questions. The 500 people exiting Freshworks include implementation engineers, customer-success technical resources, and onboarding leads. Watch the >$100K cohort’s net-revenue-retention number on the Q2 call.
- The third 11% cut. The historical pattern says the next cut comes in roughly Q4 2026 or Q1 2027. If that cut lands on schedule, the “AI-led transformation” framing becomes harder to defend as a one-time restructuring and starts to look like steady-state operating policy — which is, mechanically, what it is.
The dry coda
Freshworks’ Q1 was a good quarter. The company grew 16%, signed its largest deal ever, and lifted its non-GAAP operating margin to 18%. In the same release it announced a 500-person cut and a CEO quote that doubles as the entire industry’s 2026 talking-point: more than half our code is now written by AI.
Both things are true. The cut is real. The growth is real. The thing the framing obscures is that this is no longer a one-off. It is the second 11% cut in 18 months at the same company, with the same justification, run on the same Q-print calendar by the same CEO. “AI-led transformation” stopped being a transformation when it became the cycle.
The line for investors is: Freshworks has told you the operating model. Plan around it.
The line for the cut cohort of 500 is harder to write. They were employed at a company that beat its quarter and shipped record deals — and the quarter Freshworks beat was the quarter their job functions stopped being load-bearing in the new ratio.