Home  /  Research Videos  /  Freshworks
Freshworks · 4:20 · Buyer-side briefing

Freshworks Renewal, Part 1: The Active Agent Audit and the Zendesk Anchor

Freshworks built its position as the cheaper Zendesk and has spent four years moving toward the tier it undercut. Part one of the VendorBenchmark Freshworks prep: the four shifts, the active agent audit, the Freddy AI usage audit, the bundle audit, the competitive file, and the December quarter.

Share

The presenters in this briefing are AI generated avatars. The research, figures, and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.

Transcript

Full narration of the briefing. Click a section heading to jump the player to that moment.

The cheaper Zendesk, four years on 0:00

Freshworks built its market position as the cost effective alternative to Zendesk and Salesforce Service Cloud, and has spent four years moving its pricing upward toward the enterprise tier it originally undercut. Organizations that benchmarked Freshworks against Zendesk at signing and never refreshed that benchmark are often paying more per agent than a comparable Zendesk tier: the exact reversal of the reason they chose it. I am Tom, Claire is with me, and this is part one of the VendorBenchmark Freshworks prep: the four shifts, the three audits you run before anyone dials, and the competitive file.

The four shifts 0:40

Four shifts change the script. First, the headline per agent rate understates total cost once Freddy AI, analytics, and premium support are added. Second, Freddy AI is the primary upsell and the primary cost growth vector: Freddy Self Service, Freddy Copilot, and Freddy Insights, each either in a higher tier or separately metered per agent or per resolution. Third, Zendesk and Jira Service Management compete at comparable per agent rates, and Freshworks account teams have been trained against Zendesk since founding.

Fourth, the Customer Service Suite bundles Freshdesk with Freshchat and Freshcaller, and you pay bundle rates for channels you may never use.

The active agent audit 1:22

The most consistent source of overpayment is agent count inflation, and it is the least scrutinized. Licensed agents accumulate through team expansion, restructuring, and part time users who resolve a handful of tickets a month. So the first audit is the active agent audit: every licensed agent, last ticket resolved, total resolved in the past ninety days, and team assignment. Agents with fewer than five resolutions in ninety days are occasional users paying full rates.

Agents with zero resolutions are candidates for removal. Pull it from the admin console under agent reports, before the first call, and quote every product at that count.

Freddy AI and the bundle 2:08

The second audit is Freddy AI usage. Self Service: monthly conversations handled by the bot against total conversations. Copilot: daily active agents using suggestions against total agents. Insights: weekly active admins viewing them.

Features with engagement under twenty percent are candidates for removal from the committed scope. Organizations that discover Copilot has five to ten percent adoption are paying AI rates for a feature a small fraction of agents use. The third audit is capability usage: Freshchat conversations per month, Freshcaller call minutes, against what the suite contracts. Dormant channels at bundle rates are the direct reduction argument.

The competitive file 2:52

Then the competitive file, and it is specific, not general. Zendesk Suite priced for your active Freshdesk agent count and channel scope. Jira Service Management priced for your active Freshservice agent count if ITSM is in scope, and Atlassian's volume discounts make it attractive where Jira Software already runs. Intercom if live chat is the primary use case.

Each is a named alternative for a named capability. An actual Zendesk quote for the same agent count requires a desk level response the account team cannot handle with general positioning, because Zendesk is the competitor Freshworks defined itself against.

One voice and their calendar 3:36

Two more things before the first call. One voice: route everything commercial through sourcing, because support and IT teams embedded in Freshworks workflows resist re evaluation, and every side conversation confirming the platform is irreplaceable removes leverage. And their calendar: Freshworks' fiscal year ends December thirty first, quarters close March, June, September, and December, and the deepest close is the fourth quarter. Final asks land six weeks before December thirty first, not six days.

Part two walks the three calls word for word. More briefings at redresscompliance dot com slash research videos.

The research playbook behind this briefing

Freshworks Renewal: Talking Points, Call Scripts, and Negotiation Prep

This briefing is drawn from the full playbook by Vendor Benchmark LLC: the preparation runway, the estate math, the give and get table, the tactics and counters, and the concessions checklist. Read it here, save the PDF, or send it to whoever owns the renewal.

PDF, free, no form. Opens in the page on desktop, or in your browser's own viewer on a phone.

Negotiating a Freshworks renewal this year?

Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.

Talk to a Freshworks negotiator
Browse all 202 research videos