What Disconnected Field Service Systems Actually Cost

None of this needs a catastrophe. The costs of disconnected field service systems compound through ordinary weeks: a few days of float on every invoice, a part here and an hour there that never reached the bill, a discount nobody approved because the price was in someone's head.

This isn't a vendor ROI claim. There's no percentage in this article for you to believe or dismiss. These are your figures, and the article shows you where to find them.

Why vendor ROI numbers don't persuade anyone

Every field service vendor publishes a percentage. Faster invoicing by so much, more revenue per technician by so much. Nobody inside your business believes those numbers, and they're right not to. The vendor's customers aren't your customers, their jobs aren't your jobs, and the average of a hundred operations tells you nothing about yours.

What does persuade a controller or an owner is a number that came from their own books. So the alternative is six formulas, each needing inputs you already have or can pull in an afternoon. The numbers you produce will be smaller or larger than someone else's, and they'll be yours.

One caution before you start. These six are the costs of information gaps, places where a fact didn't travel between two systems. If you want the explanation of where each one comes from, start with the six information gaps behind every field service problem. This article assumes you've met them and want to size them.

The six line items

Each formula is written the way you'd put it in a spreadsheet cell. Use your own figures.

1. The invoicing gap

Average daily invoiced revenue × days between job completion and invoice issue = cash permanently in transit.

This is a float cost, not a one-time loss, and the difference matters. You don't lose that money. It's tied up, permanently, in the gap between finishing a job and asking to be paid for it. If you issue invoices nine days after completion, then on any given day about nine days of your revenue is sitting there, financed by you. Shorten the gap and you release that cash once, and it stays released.

Where to find the inputs: daily invoiced revenue from your accounting system, and the average gap from the timestamps on completed jobs and issued invoices.

2. The capture gap

Take one month of jobs. Find the share where a part, a materials charge or an hour never reached the invoice, then multiply by the average value of what was missed.

This is the hardest one to measure because what goes missing leaves no trace. The way to find it is to audit a sample: pick a month, take twenty jobs, and compare what the technician wrote down, what the van's stock or the supplier invoices say was used, and what the customer was billed. Even a small sample usually finds something.

Whatever share you find, apply it across the year's job volume and the average value of the missing item.

3. The pricing gap

Find your highest and lowest quote for the same common job last year. Take the difference and multiply it by how often the low one was used.

Pick the job you do most, maybe a standard repair or a maintenance visit, and pull every quote for it. The spread between highest and lowest is the price of not having one price list. Multiply by how often the low quote went out, and you have the margin given away at the curb.

4. The approval gap

Take your close rate on estimates approved on site versus estimates sent later. Multiply the difference by annual estimate volume and average estimate value.

If you don't track both rates, start tracking them; the first month's data will be interesting by itself. The difference is what waiting costs. It won't be the same in every trade, and this is one place where your number can differ a great deal from anyone else's, which is exactly why you should use yours.

5. The status gap

Status calls per week × minutes per call × the loaded hourly cost of whoever answers.

Have the person who answers the phone count calls for a week, and tag the ones asking where the technician is or what the status of a job is. Loaded cost means wages plus the overhead your finance team already uses. There's also a cost the formula doesn't capture, which is the dispatcher's attention: every call is an interruption in the middle of a decision.

6. The compliance gap

The cost of one audit finding or stop-work order in your trade × your honest confidence that every credential is current today.

Think of this one as a probability times a consequence. Ask yourself how sure you are, today, that every technician on the board holds every credential the work they're assigned requires. Not "we have a process," but how sure you are. If you'd put that at 90%, the other 10% times the cost of one bad day is the number.

We don't put a figure on penalties here and you shouldn't take one from us; ask your compliance lead what a finding costs in your trade. What matters is that this is the only one of the six that has no cost until the moment it has an enormous one.

The hidden line: administrative hours

There's a seventh cost that doesn't need a formula, only arithmetic. Re-keying, chasing and reconciling take hours, and they belong to real people.

Here's a worked example, with the assumptions visible. Suppose four people in your office each spend four hours a week moving information between systems: retyping tickets, matching parts lists, reconciling a schedule against a timesheet. That's 16 hours a week. Over a 50-week year it's 800 hours, or about 40% of a full-time role at 2,000 hours a year.

That example is an illustration, not a benchmark. Your team size and your hours will differ, so substitute them. The point is that a small weekly task, repeated by several people, adds up to something you'd notice if it were a job title.

Systems that don't talk to each other also cost time in a way that doesn't show up as labor: knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey). Every additional tool means another login and another place to look, and a dispatcher who is already the supervisor, the customer service rep and the first line of tech support pays for each one.

Where the costs hide on the P&L

Finance readers should see where each gap lands, because it's rarely a line labeled "information."

The first four are visible once you know where to look. The last is the odd one out: it costs nothing for years and then costs a lot at once, which is why it tends to stay off spreadsheets.

What closing the gaps looks like

The pattern is always the same: one record instead of several. A job is requested, assigned, captured on site, estimated, invoiced and synced to accounting without anyone retyping it. The work order lifecycle lays out the six steps.

MangoApps Field Service Suite runs on one data layer shared with the rest of the platform, so the work order, the price list and the customer's view of both are the same record. That's what lets an invoice be ready when the job closes and a lapsed credential stop an assignment. Whether it's the right answer for you is what the evaluation guide is for.

The worksheet

Copy this into a spreadsheet and fill in your own figures. Every input is something you can pull from your own systems or a week of counting.

Use your own figures. They're the only ones that will persuade anyone in your business.

The trade-specific versions matter, too. A fire and life safety contractor's compliance gap and an electrical contractor's differ, and so do their invoicing patterns; see fire and life safety and electrical contractors for how they see it.

Once the number exists

Once you've added up the six, the conversation inside the business changes. It stops being "should we?" and becomes "which gap first?" That second question has an answer you can defend, because the number is yours.

From here, the evaluation guide gives you twelve questions to put to any platform, and the six information gaps article is the map of where each cost comes from. If the price gap looks largest, start with one price book. If it's the status gap, see the customer portal. And if the compliance gap kept you up, that one has its own article.

The six formulas are also in the Field Service Management guide, alongside the gaps they measure and a scorecard for comparing vendors. It's a free download with no email required. You can also see the Field Service Suite itself.

Frequently asked questions

How do you calculate the cost of late invoicing?

Multiply your average daily invoiced revenue by the number of days between job completion and invoice issue. The result is the cash permanently in transit, which is money you've earned and financed but haven't yet asked for. It's a float cost, so shortening the gap releases the cash once rather than saving the same amount every month.

What is billing leakage and how do you measure it?

Billing leakage is billable work that was done but never reached the invoice: a part fitted but not listed, a materials charge missed, an hour not logged. Measure it by sampling. Take a month of completed jobs, compare what the technician recorded and what the stock or supplier records show was used against what was billed, and note the share of jobs where they differ and the average value of the difference.

What is a reasonable days-to-invoice target for a field service company?

It depends on the trade, and any universal number would be invented. What matters is that the invoice is ready the moment the job closes, so the delay comes from your billing cycle and customer terms rather than from re-keying. Measure your own average gap from completion to issue and watch it fall as hand-offs disappear.

How do you estimate the cost of a compliance gap?

Estimate what one audit finding or stop-work order costs in your trade, then multiply by how uncertain you are that every credential on your board is current today. If you're 90% sure, use 10%. It's a risk figure, not a certainty, and it's worth asking your compliance lead for the cost of a finding rather than guessing.

How do I use these formulas with my own numbers?

Copy the worksheet table above into a spreadsheet and fill in the inputs from your accounting system, your job timestamps, your quote history and a week of counting calls. Each formula is written to use figures you either already have or can gather in an afternoon. Nothing here needs an account or an email address.