Freshworks is telling you plainly: your support software bill is about to stop being predictable
In a June 2026 interview with BusinessLine, Freshworks CEO Dennis Woodside said the industry's default pricing model — charging per named seat — is giving way to consumption and outcome-based billing as AI agents take on more support work alongside humans. He described Freshworks' own AI agent product as priced by number of sessions used, with other products billed by assets managed or incidents managed. Woodside also said AI has spoiled his own product team's pace, with development cycles now running faster than before, and that a growing share of new Employee Experience customers are buying AI capability from day one rather than adding it later. No pricing figures, discount levels or contract sizes were disclosed in the interview.
What's actually changing in how support software gets billed?
Vendors are adding usage meters — sessions, incidents, managed assets — on top of or instead of the old per-agent-seat license fee.
That's a bigger shift than it sounds. A seat fee is a number you can put in a budget spreadadsheet in January and not think about again. A per-session or per-incident fee moves with your ticket volume, your seasonality, and — critically — with how much of the work your AI agent actually handles versus escalates. Woodside frames this as the market "shifting more towards consumption or outcome-based functionality," which is a tidy way of saying the vendor's revenue now scales with your usage rather than your headcount.
Why does this matter for anyone budgeting a support stack?
Consumption pricing turns support software from a fixed line item into a variable one tied to ticket volume and AI hand-off rates.
That's not automatically bad — if your AI agent genuinely resolves more without a human, seat-based pricing was already overcharging you for licenses nobody used. But variable pricing also means a spike in ticket volume, a product launch, or a bad week can move your software bill in ways a finance team can't forecast the way they could under seats. Worth asking whether your renewal includes any usage cap or overage alert before you sign, not after your first surprise invoice.
Who actually defines what counts as a "session" or an "incident"?
The vendor does — and Freshworks, like its peers, hasn't published a standard definition that buyers can audit or compare across suppliers.
This is the part the interview glosses over. "Session," "incident," and "managed asset" sound like objective units, but each vendor sets its own boundaries: does a session reset if the customer replies an hour later? Does a bot escalation to a human still count as one billable incident? Until there's an industry-standard metric, comparing quotes from two AI support vendors on a per-unit basis is close to meaningless — you're comparing two different rulers.
What should you ask your vendor before your next renewal?
Get a written definition of every billable unit, a 12-month usage projection based on your own historical volume, and a cap.
Ask specifically how sessions or incidents are counted when a bot fails and a human takes over — that's the scenario most likely to inflate a bill without you doing anything differently. And ask whether the vendor will commit to holding the definition stable for the contract term, since a metric that changes mid-contract is effectively a repricing you didn't agree to.
Frequently asked questions
Is Freshworks dropping seat-based pricing entirely?
No. Woodside described the current model as mixed, with the balance shifting toward consumption pricing as AI adoption grows — not a wholesale replacement announced for 2026.
Did Freshworks give numbers on cost savings or ROI from this shift?
No specific savings, revenue or pricing figures were given in the interview beyond the CEO's qualitative description of faster internal development cycles and rising early AI adoption among new customers.
Does this affect only Freshworks customers?
No. The pricing shift Woodside describes reflects a broader industry direction; other customer support and live chat vendors are moving toward similar consumption or outcome-based metrics.
Source: "SaaS pricing to evolve from seat-based to consumption based: Freshworks CEO," BusinessLine.