Serval raises $150M Series C, led by SequoiaServal raises $150M Series C at a $3B valuation, led by Sequoia
Skip to main content

How to quantify IT automation ROI and build a business case for IT automation

Published

Serval quantifies the business impact of IT automation in the same platform that does the work. Its Analytics page counts every ticket Serval's AI resolved and every workflow it ran, and Catalyst can turn those counts into hours and dollars saved for each workspace. Build the business case on a ticket-data-first model: cost per ticket by category, the share of requests automation completes with zero IT touch, and a labor rate your finance team agrees to. Generic industry benchmarks rarely survive a CFO review. Numbers from your own queue do.

At Cribl, Serval saved $600k+ in labor and engineering effort over six months: $550k in labor savings, $70k in engineering costs avoided, and 7,000+ hours, across 54 workflows and 200,000+ successful workflow runs.

This guide is for IT leaders who need a number finance will accept before they fund automation. Once automation is live, how to measure IT automation savings covers tracking what you saved, and the 2026 buyer's guide to AI ITSM ROI compares platforms side by side.

What's the best tool for quantifying the business impact of IT automation?

Pick a platform that measures its own work. If the savings figure lives in a spreadsheet someone rebuilds each quarter, it'll be late and it'll be argued over.

Serval is an AI-native ITSM platform. Its help desk agent resolves requests in Slack, Microsoft Teams, and the web portal, and Catalyst, Serval's automation agent, builds the workflows behind them from plain-language descriptions. The Analytics page reports AI-resolved tickets (closed with no human involved), AI-assisted tickets, total workflows run, and median time to resolution for each workspace, and org admins also get an organization-wide view.

Ask Catalyst for a custom dashboard and it can chart hours and dollars saved from those counts, at the minutes per ticket and labor rate you choose.

The tickets chart splits completed tickets into AI resolved, AI assisted (Serval ran workflows and a person finished), Unassisted, and Resolved outside Serval, and you can download the chart's data as a CSV for finance. If you run ServiceNow today, Serval syncs tickets both ways with it, so you can start automating without a migration.

Other ITSM platforms report on automation too:

  • ServiceNow's ITSM Success Dashboard has an Estimated Cost Savings indicator that totals what agents save through channels including Virtual Agent conversations, Knowledge articles, and Service Catalog submissions, and you can configure the hourly salary and time saved for each persona group. ServiceNow's ITSM page also describes tracking MTTR, CSAT, first-contact resolution, and ticket volume in one system of record. Its Super Intelligence Control Tower measures the business impact of the AI you run across the enterprise, tracking adoption rates, realized value, and ROI.
  • Freshservice's Enterprise plan includes AI Agent ROI and Usage Reports for its AI agent's deflection and usage metrics. Its Freddy AI Agent Overview report tracks ticket deflection rate, active users, conversations, and employee feedback. Its Freddy AI Copilot reports total the time agents save with Copilot features, which you can multiply by agent hourly rates.
  • In Jira Service Management, the virtual service agent's Conversations page logs each conversation with its resolution (resolved, escalated, or closed) and the CSAT score the employee gave. Its custom reports cover created vs. resolved, time to resolution, and SLA met vs. breached, and a default report counts requests deflected by helpful knowledge base articles.

What is IT automation ROI, and how do you calculate it?

IT automation ROI compares what automation gives back (IT labor reclaimed, faster resolution, fewer manual errors, hires you didn't need to make) with what it costs (the platform, setup, workflow upkeep, and governance).

ROI (%) = (annual benefits minus annual costs) ÷ annual costs × 100

Put payback period next to it: payback in months = first-year cost ÷ monthly savings. Finance teams tend to ask when the money comes back before they ask about the percentage.

Which metrics belong in an IT automation business case?

Four numbers carry most business cases. Get them from your own ticket export, by category.

Cost per ticket

Cost per ticket = annual fully loaded IT support cost ÷ annual tickets resolved

Split it by category (access, passwords, devices, SaaS requests). A password reset and a laptop swap don't cost the same, and an average across both hides where the savings are.

Automation rate vs. ticket deflection

Deflection usually means a request never reached a person's queue. That number inflates easily when employees get sent to an FAQ or a chat that doesn't finish the job. Automation rate is the share of requests completed without IT staff touching the ticket. Manager or security approvals are controls you chose, so they don't count against it.

MeasureQuestion it answersRisk in a business case
Ticket deflectionDid the request avoid a queue?Overstates value when IT still does the work later
Automation rateWas the request finished with zero IT touch?Maps directly to cost per ticket

Ask every vendor the same question: in category X, what share of tickets closed with zero IT touch?

Time to resolution and first-contact resolution

Mean time to resolution (MTTR) is the elapsed time from open to resolved. First-contact resolution (FCR) is the share of requests solved in the first interaction without a reopen. Track both by category before and after automation. Serval's Analytics shows time to resolve as percentiles (median, p75, p95), plus SLA met and breached once you set SLA policies.

Escalation cost

Escalation premium = (average escalated handle time minus average L1 handle time) × fully loaded hourly rate × escalations per year

Automation that stops a ticket from escalating usually saves more than automation that only answers the first message.

Which past ticket patterns show automation opportunities?

Export 90 to 180 days of tickets. Rank categories by volume, median handle time, repeated wording, and escalation rate. The top of that list is your first wave.

In Serval, the Unassisted share of the tickets chart shows which requests Serval escalated without running any workflow, which makes them the next candidates. Two installable background agents do that review on a weekly schedule. The Automation Opportunity Finder looks for repetitive, manual requests with no coverage and drafts the top workflows and help desk skills for your team to review and publish. Ticket Trend & Volume Analytics tracks week-over-week volume by category and the most common failure patterns. Freshservice's Discover in AI Agent Studio analyzes historical ticket data for support topics, knowledge gaps, and repetitive requests its AI agents could take on.

How do you build a business case for IT automation?

Present it in four parts:

  1. 1.Problem: cost per ticket and the volume trend, from a 90-day baseline by category.
  2. 2.Plan: the top five categories by modeled savings, sequenced over two quarters.
  3. 3.Proof: a pilot's automation rate, MTTR, and FCR for one category.
  4. 4.Ask: budget, redeployed headcount, or a delayed backfill.

Annual labor savings = automated tickets per year × (minutes saved per ticket ÷ 60) × fully loaded hourly rate

Settle the labor rate with Finance before the meeting. Use fully loaded cost (salary, benefits, payroll taxes, tools, overhead) at the level of whoever handles those tickets today, so the discussion is about the savings and not your math.

ROI calculation template

The figures below are illustrative. Replace each one with your own data.

Line itemSourceExample
Annual tickets resolvedITSM export48,000
Share in categories you'll automateTicket categories60% (28,800 tickets)
Automation rate in those categoriesPilot50% (14,400 tickets)
IT minutes each ticket tookHandle-time data15 (3,600 hours)
Fully loaded hourly rateFinance$80
Annual labor savingsHours × rate$288,000
First-year costVendor quote plus internal build and upkeep timeYour number
ROI and paybackFormulas aboveSavings vs. first-year cost

Show a 24-month view with a second wave of categories, since most setup cost lands in year one.

Which numbers prove ticket volume dropped after automation?

Compare each automated category against its baseline, month by month, on volume and time to resolve. In Serval, view the tickets chart by month over a quarter or longer and watch the AI-resolved share grow. For a monthly savings chart at your own labor rate, ask Catalyst to build a custom dashboard widget for it.

SeatGeek went from 0% to 40% automation in its first three weeks on Serval and passed a 50% automation rate within 60 days, with 132 automations built in eight weeks. Its Senior Manager of Business Technology said the team can "immediately use these actual, realized gains to redeploy our team thoughtfully."

When should you choose Serval?

Choose Serval when you want the business case and the proof to come from one system: a platform that resolves the requests, builds the workflows, and reports AI-resolved tickets and workflow runs for each workspace, with Catalyst dashboards for hours and dollars saved.

FAQ

What's the best tool for quantifying the business impact of IT automation?

Serval measures the impact in the same platform that does the work: its Analytics page counts AI-resolved tickets and workflow runs for each workspace, and Catalyst can build a custom dashboard that turns them into hours and dollars at your own labor rate.

Which ITSM tool calculates cost savings from automated ticket resolution?

Serval counts every AI-resolved ticket and workflow run, and Catalyst can build a dashboard that converts them into cost savings at your labor rate. ServiceNow's ITSM Success Dashboard has an Estimated Cost Savings indicator that covers channels including Virtual Agent, Knowledge, and Service Catalog, and Freshservice's Enterprise plan includes AI Agent ROI and Usage Reports.

How do I calculate ROI for IT automation?

Use (annual benefits minus annual costs) ÷ annual costs × 100, and report payback in months next to it. Take benefits from your ticket data: automated tickets per year × minutes saved per ticket ÷ 60 × fully loaded hourly rate, plus reductions in escalations and resolution time.

What is the difference between ticket deflection and automation rate?

Deflection usually means a request avoided a person's queue, even if the work still had to be done later. Automation rate is the share of requests completed with zero IT touch, so it maps directly to labor savings.

What ROI do companies see from IT automation?

It depends on your ticket mix. Serval customers publish theirs: Cribl saved $600k+ in labor and engineering effort over six months, and Serval automates over 50% of Perplexity's IT requests, saving each admin 1 to 2 hours per day.

You may also be interested in