The neatest way to read Freshworks’ May 7 earnings call is to stack the three sentences the company put out that day and see whether they fit in the same paragraph: fiscal Q1 2026 revenue was $228.6 million, up 16% year-over-year and ahead of Wall Street estimates; the company signed two of the largest contracts in its history that quarter; and roughly 500 people, or 11% of staff, will be cut in a restructuring tied to the fact that more than half the company’s code is now being written by AI.
They do not, in fact, fit in the same paragraph. The press release put the headline numbers on top and the workforce reduction in a separate document. The CEO’s quoted line — that “over half of our code is written using AI tools” — was carried by Storyboard18 and TechRadar but did not, conspicuously, appear in the financial reporting. That separation is the whole story.
What Freshworks actually said
Five things, in order, on May 7:
- Revenue: $228.6 million for the quarter ended March 31, up 16% year-over-year, ahead of analyst consensus.
- Contracts: Two of the largest deals in the company’s history closed in Q1, both anchored on the Freshservice IT-service-management product line.
- Workforce reduction: approximately 500 roles, or 11% of headcount, with most of the cost incurred in fiscal Q2 2026.
- Restructuring charge: approximately $8 million, modest by SaaS-layoff standards — a hint that the affected roles skew junior and non-US.
- Rationale: consolidate sales teams, reduce management layers, redirect savings toward Freshservice and other “growth businesses,” operate as an “AI-first” company.
CEO Dennis Woodside, in an internal communication summarized by Storyboard18 and Outlook Business, supplied the quotable line. AI-driven automation, he said, had already changed how the company operated, and “more than half of Freshworks’ code was now being written using AI tools.” That is the candor that gives the May 7 announcement its specific texture. Most “AI-led” layoffs in the May 2026 cohort lean on phrases like “AI-first operating model” or “operational efficiency”. Woodside’s version is a number: more than 50%.
The arithmetic of an “AI-first” cut at a profitable company
Freshworks is not in distress. Q1 revenue accelerated to +16% YoY from prior quarters in the high single digits. The company beat consensus. Two of its biggest-ever contracts closed in the same three months. The stock did not crater on the layoff news, in part because the $8 million restructuring charge is, by Bay Area standards, a rounding error — roughly $16,000 per departing employee if applied evenly, which strongly implies the cut is concentrated in lower-cost geographies (most likely India, where Freshworks runs a large engineering footprint).
That is the arithmetic of a “growth-stage AI restructuring”: cut 11% of staff in geographies where severance is cheap, redirect the avoided salary line into Freshservice product investment, hold the top line at +16%, and call the result “AI-first”. The Q1 financial print and the Q2 restructuring headline are pulling in opposite directions on the income statement, but both, in this case, push EPS in the same direction.
This is a different shape of announcement from the rest of the May 7 cohort. Cloudflare cut 20% with a Q1 beat. BILL Holdings cut 30% bundled with a $1B buyback. Upwork cut 24% against a missed Q2 guide. Freshworks is the smallest of the four cuts in absolute headcount, the most modest in restructuring charge, and the only one that explicitly named the share of the code base being written by AI as the reason. The phrasing is not accidental. SaaS investors track gross margin and headcount-per-dollar-of-revenue. Telling the buy-side that more than half of the engineering output is now machine-generated is the cleanest possible signal that the operating leverage is structural, not cyclical.
What “more than half the code” actually means
The Woodside line is a strong claim, but it is also the most precise version of a story that has been told by Salesforce, Microsoft, Google, and Amazon over the past nine months. To translate the executive sentence into engineering vocabulary:
- “More than half our code is written by AI” almost certainly refers to lines or characters of code committed where the initial draft came from a language model (typically Cursor, GitHub Copilot, Claude Code, or an internal equivalent), which a human engineer then reviewed, modified, and merged.
- It does not mean half of engineering decisions are made by AI. The architectural calls, the test design, the production debugging, the on-call rotation — that work is still concentrated in the smaller, more senior workforce that survives the cut.
- It means the code-volume floor that used to require a certain number of mid-level engineers can now be sustained with fewer of them. The composition of the surviving team will skew senior, with a higher ratio of reviewers to authors.
That is the actual restructuring story underneath the press release. Mid-level roles thin out. The “broader and shorter pyramid” — Cognizant CEO Ravi Kumar’s Project Leap framing for a similar cut at IT-services scale — applies at Freshworks too. Fewer layers, more dependency on tooling, savings redirected to product investment.
The 「AI-first」 phrase, decoded for the May 7 cohort
The Freshworks call landed in a week that effectively defined the corporate vocabulary of mid-2026:
- Cloudflare (May 7) — “AI-first operating model”
- DeepL (May 8) — “AI-native”
- BILL Holdings (May 7) — “AI native company”
- Microsoft (May 7) — “Rule of 70” voluntary retirement
- Freshworks (May 7) — “more than half the code is written by AI”
Of those phrases, Freshworks’ is the only one that reduces to a number a competitor’s CFO can model. That alone makes Woodside’s line the most consequential sentence of the cohort, even though Freshworks’ headcount cut is the smallest of the five in absolute terms. Within a few quarters, “what percentage of your code is AI-generated” will be a recurring earnings-call question for every public software company. Freshworks just told the analysts what their own answer should look like.
What to watch
- The Q2 print. $8M of charges in fiscal Q2 against $228.6M in Q1 revenue. If Q2 revenue holds the +16% trajectory, the layoff was an offensive move. If Q2 decelerates, the cut becomes defensive in retrospect, regardless of how it was announced.
- Where the 500 roles came from. A regulatory filing in the next 10-Q will show geographic distribution. If the cut concentrates in India and lower-cost engineering hubs, the “more than half the code” line implies AI tooling has eaten the entry-and-mid-level engineering ladder there first.
- Freshservice growth. The cited rationale was redirecting savings toward Freshservice. If that segment accelerates faster than +16% in coming quarters, the restructuring narrative holds. If it doesn’t, the cut funded margin, not growth.
- Whether other CEOs adopt the percentage framing. Woodside has just made ”% of code written by AI” a public KPI. Watch the next two earnings cycles for which competitors take the bait.
The dryly funny part
The single funniest line in the May 7 Freshworks framing is that the company chose to celebrate two of its largest contracts ever, beat Q1 estimates, and announce 500 layoffs in the same trading day. The AI tools that wrote the code were apparently not yet deployed against the press release. If they had been, all three of those announcements might have arrived in the same paragraph — and the paragraph would have been honest about which one funded the others.