It’s July, the phones haven’t stopped, and the office is behind. Callbacks are going out late, invoices are a week behind, and someone spends the afternoon answering “where’s my tech?” It’s natural to ask whether the office needs more help.
That’s your decision, and this post won’t make it for you. What it will do is give you a number your usual reports don’t show: what each job costs your office in time and money, and where that time actually goes. Whatever you decide, you’ll decide it knowing which parts of the work grow with every job, and which parts shouldn’t exist at all.
Why measure cost per job at all?
You probably know your numbers on the field side: revenue per job, materials, maybe technician hours. The office side is harder to see, because it’s spread across a dozen small moments. A call, a lookup, a text to the tech, a callback, an invoice fix. None of them feels big, and nobody adds them up.
Adding them up gives you three things:
- Where the time goes. Which steps take the most minutes across a month.
- What grows with volume. Some steps happen once per job no matter what. Others, like status calls and chasing missing details, multiply as you get busier.
- A baseline. If you change a tool or add an automation, you can measure again and see what actually changed.
This is about capacity: how much work the process can handle, and where it strains. You’re measuring the process, not anyone’s performance. That matters for a practical reason too. If people think they’re being timed and compared, steps get padded or left out, and the number stops meaning anything.
What counts as one unit of work?
The thing your office handles over and over. For an HVAC or plumbing company, it’s usually a service call. For a property manager, a maintenance work order. For a roofer, an inspection or a quote. For a professional services firm, a client file or a support ticket.
Pick one type and measure it on its own. A no-heat call and a full system replacement run through different steps. Mix them and the average describes neither. Start with the one you handle most often, and measure the others later.
How do you list every step from request to invoice?
Follow one typical job from the moment the request arrives to the moment it’s billed. Write down every step, including the ones that feel too small to count:
- Answering the call and checking whether they’re an existing customer
- Entering the address, equipment and problem into the job system
- Checking the board and offering an arrival window
- Texting or calling the tech with the details
- Taking the “when will they be here?” call
- Re-entering the tech’s notes and parts into the invoice
- Chasing a missing photo, part number or signature
- Fixing an invoice that went out wrong
Map the process as it actually runs, not as it’s written in a manual. The quickest way is to sit with the people who do the work and ask them to talk you through a real job. They know the workarounds: the second system that has to be checked, the spreadsheet that fills a gap, the sticky note on the monitor. Those steps rarely make it into a process document, and they’re often where the time goes.
How do you put a cost on each step?
Two numbers per step.
Minutes. How long the step takes on a typical job. Estimate it with the people who do it, or time a handful of ordinary jobs. Use the typical case, not the best day or the worst.
Loaded hourly cost of the role. That’s the wage plus payroll taxes, benefits and overhead. Your bookkeeper can give you the real figure for each role: customer service, dispatch, billing, office manager. Use the role’s cost, not a named person’s pay. You’re costing a step in a process, and keeping it at the role level stops the exercise from turning into a conversation about individuals.
Then, for each step: minutes × loaded hourly cost ÷ 60. Add the steps together and you have the office labor cost of one job. Multiply by your monthly volume for the monthly cost.
What does a cost-per-job calculation look like?
These are made-up numbers, not a client result. Say an HVAC company handles 400 service calls a month, and the office side of each one looks like this:
- Take the call and enter the job: 8 minutes, customer service role at $30 an hour, $4.00
- Schedule and confirm: 6 minutes at $30, $3.00
- Customer calls for a status update: 5 minutes at $30, $2.50
- Retype job notes into the invoice: 7 minutes, billing role at $32 an hour, $3.73
- Chase a missing detail: 4 minutes at $32, $2.13
That’s 30 minutes and about $15.36 of office time per job. At 400 jobs a month, it’s 200 hours and roughly $6,100 a month.
Now go back and mark every step that is retyping, chasing a status or fixing something. Here that’s three of the five: the status call, the retyping and the chasing. Together they take 16 minutes a job, more than half the total, and over 100 hours a month. None of them moves the job forward. They exist because information didn’t get where it needed to go the first time.
The cost-per-job worksheet has this example, the method step by step, and a blank sheet you can print and fill in.
If volume went up 30% next month, what breaks first?
This is the question the number is for. Take the hours on the marked steps and add 30%. Then ask two things: who absorbs that time, and what slips?
In the example, 30% more volume is 520 jobs a month. Total office time on these steps goes from 200 hours to 260. The marked steps alone go from about 107 hours to about 139. That’s roughly 32 more hours a month of status calls, retyping and chasing, before anyone has done more of the actual work.
Then look at what slips. It’s usually the work without a fixed deadline. Callbacks get slower. Invoices go out late, so cash comes in late. The phone goes to voicemail at the busiest hour of the day. Whatever doesn’t get done lands on whoever stays late to catch up.
Write the answer down, even if it’s rough. The step that breaks first is usually where to start. If you want a quick first read before you sit down with the worksheet, the capacity check asks seven questions about where work piles up and gives you an answer in about two minutes.
What does the number let you decide?
It turns “we’re swamped” into a list you can act on.
- Where tools or automation would remove work. A status call can disappear when customers get an automatic text with their arrival window and a heads-up when the tech is on the way. Retyping shrinks when job notes flow from the field app into the invoice, either because your field service software already does it and nobody turned it on, or through a small connection between two systems that don’t talk. Chasing shrinks when a job can’t be closed without the photo or part number.
- What to fix first. Rank the marked steps by minutes per month and by how hard they are to change. The best first fix is usually big and simple, not the most interesting one.
- Whether a tool is worth paying for. Compare what it costs with the minutes it removes, at the loaded rate. The ROI calculator does the arithmetic.
- Whether a change worked. Measure the same unit of work again after the change, against your baseline.
This is the kind of work automation handles well: routing new requests, sending reminders and status updates, and moving data between the tools you already use. If you run a field service business, the dispatch and billing handoffs are usually the first place to look.
What doesn’t this number tell you?
Plainly: staffing decisions stay with you, and they’re outside what this measures. The number doesn’t tell you whether to hire, how many people the office needs, or how anyone is doing their job. It measures a process. A process can be slow for reasons that have nothing to do with the people running it: two systems that don’t share data, a form missing a field, customers who never get told when the tech is coming.
It also leaves things out. Some of the most important office work isn’t a step at all: a judgment call, calming an upset customer, noticing that two jobs on the board can’t both happen at nine. Don’t try to squeeze that into minutes. The point of the exercise is to find the repetitive steps that crowd that kind of work out.
And don’t use it to compare people. The moment it becomes a scorecard, you lose the honest answers that make it useful.
Where do you start?
Pick one unit of work this week and walk it end to end with the people who handle it. The cost-per-job worksheet gives you the method and a blank sheet. If you’d rather start with a quick read, take the capacity check.
If you want it measured properly, our AI consulting work starts with a two-week throughput audit in one department. We measure what each job, ticket or file costs in labor, map the process as it really runs, rank the opportunities by impact and effort, and build one working automation in your own systems before we leave. Everything we build lives in your accounts. We don’t give staffing advice or evaluate people. Decisions about your team stay yours.