Connect
You walk into the budget meeting ready to pitch automation. You know it will save time, and free your team for real work. Then the CFO asks one simple question:
How much are we spending on this problem right now?
If you don’t have a number, the conversation stalls.
Before you can prove automation saves money, you have to show what manual work actually costs today. That number is your Manual Cost Baseline, and it turns a hopeful pitch into a hard business case.
This blog will teach you how to build that baseline using three simple inputs. We’ll walk through the exact math and real data your leadership team wants to see. For the full framework, including scoring tools, grab The Automation Mindset eBook. But keep reading first, because the core formula takes just a few minutes to understand.
The Formula That Frames Your Entire Pitch
Everything starts with a single equation. Your Manual Cost Baseline (Cm) is the monthly cost of handling repeatable tickets by hand.
| Cm = Tres × Rh × Vt |
Three variables drive it. Mean Time to Resolve (Tres), your Fully Burdened Hourly Rate (Rh), and Monthly Ticket Volume (Vt). Get these right and you have a number no executive can argue with. Let’s break down each one.
Measure Real Technician Time, Not Calendar Time
The first mistake teams make is measuring the wrong kind of time. A ticket might sit open for three days, but your technician only touched it for twelve minutes. Calendar time is how long a ticket lives. Touch-time is how long your people actually work on it. Only touch-time belongs in your baseline.
This distinction matters because manual work drags on. Reports by Fixify show that tickets handled with automated workflows hit a median resolution time of 4.4 hours. The same work done manually takes 71 hours. That gap is where your money leaks out.
So track the active handling time for your common Level 1 and Level 2 tickets.
Use the True Cost of a Technician, Not the Salary
When people estimate labor cost, they use the base salary. That number is far too low. Your real cost includes payroll taxes, benefits, and overhead like software and desk space. This is the Fully Burdened Hourly Rate.
| True Employee Cost = Base Salary + Payroll Tax + Superannuation/Retirement |
| Cost Per Hour = Allocated Share of Indirect Expenses/ Total Annual Billable Hours across the Team |
| Rh = (True Employee Cost / Annual Productive Hours) + Overhead Cost Per Hour |
Here’s how it works. A technician with a $60,000 base salary actually costs your company over $90,000 once you add everything up. Now divide that by their real productive hours. A full-time employee gives you roughly 1,700 productive hours a year after meetings, breaks, and time off. That math produces a true rate of about $53 per hour.
Whatever your organization’s number is, use the fully burdened figure. That’s your Rh, and it makes your case honest and defensible.
Count Your Repeatable Tickets Over 12 Months
The third variable is volume. You want the total monthly count of repeatable, rule-based tickets that automation could handle. Password resets, access requests, and onboarding tasks are some examples.
One tip here. Don’t use last month’s numbers alone. Ticket volume swings with seasonal spikes that can reach 30%. Instead, pull a trailing 12-month average to smooth things out. This gives you a stable, believable number that holds up under questions.
Putting the Baseline Together
Let’s put it all together with an example of a mid-sized IT team drowning in repeatable tickets. You’ve measured your three inputs, and here’s what they look like side by side. Your Mean Time to Resolve (Tres) is 0.2 hours per ticket, which is the 12 minutes of touch-time your technicians spend on each request. Your Fully Burdened Hourly Rate (Rh) is $40, the true cost of a technician’s time once you fold in taxes, benefits, and overhead. And your Monthly Ticket Volume (Vt) is 20,000, the trailing 12-month average of repeatable tickets your team handles by hand each month.
Cm = 0.2 x $40 x 20,000 = $160,000
That’s $160,000 every month spent handling tickets by hand. Suddenly your automation pitch has a clear target. You’re not asking for a budget on a hunch. You’re showing a real, recurring cost your team can shrink.
The Hidden Costs Your Baseline Reveals
The baseline is only the start. Manual work also creates costs that hide in plain sight. Escalation defects are a big one. These happen when a simple ticket gets passed up to a more expensive support tier.
Then there’s downtime. Gartner puts the average cost of IT downtime at $5,600 per minute. When your team is buried in manual tickets, they can’t respond fast, and those minutes get expensive quickly.
Build Your Case with Data
You now have the formula, the variables, and the proof points to build a business case leadership will respect. Start by measuring your own Manual Cost Baseline this week. Even a rough baseline beats walking in empty-handed.
To go further, The Automation Mindset gives you the full toolkit. Inside, you’ll find a Priority Scoring Matrix to rank which tasks to automate first, ROI formulas to prove financial value to leadership, and much more.
Download The Automation Mindset today and build a case your CFO can’t ignore.
