Most field service businesses know their margins are under pressure. Fewer know exactly where the money is going. BigChange Lightning makes that visible — and then closes the gap.
Field service is not a low-margin industry by nature. The work is skilled, the demand is consistent, and the pricing in most markets reflects both. And yet the average field service business earns around 6% net profit. The businesses at the top of the market — doing the same work, serving similar customers, charging comparable rates — earn 24%.
That's not a small difference. It's the difference between a business that's surviving and one that's building something. And for years the explanation has been vague: better management, tighter operations, more experience. True, but not particularly useful.
BigChange Lightning makes the answer specific. Because the margin gap between a 6% business and a 24% business isn't mysterious — it lives in identifiable places. Operational friction that adds cost to every job. Revenue that leaves the business without being captured. Time spent on work that doesn't produce income. Problems that compound quietly because nobody had the visibility to catch them early.
This is where BigChange Lightning actually impacts the bottom line.
The return visit problem
One in four jobs in the field service industry ends in a return visit. The engineer gets to the site, works through the job, and somewhere in the process something gets missed — a part not on the van, a fault that connects to something from a previous visit that wasn't in the briefing, a diagnosis that needs a second look.
The return trip costs between £200 and £500 in wasted labour and vehicle time. For a ten-engineer crew, the annual cost of return visits sits at approximately £1 million.
That number sounds extraordinary. It isn't. It's the result of a modest failure rate — one in four — multiplied across the volume of jobs a field service business runs over a year, with each failure carrying a real labour and logistics cost.
JobReady addresses this directly. Every engineer starts every job with a briefing built from the complete operational history of that site, that asset, and that customer. The fault that connects to a previous visit is in the briefing. The part most likely to be needed is flagged before they leave. The context that prevents the return trip is assembled automatically, every time.
Moving from a 75% first-time fix rate — the industry average — to 90% is the difference between one in four jobs generating a return trip and one in ten. For a ten-engineer crew, that improvement alone recovers hundreds of thousands of pounds annually that was disappearing into the cost of doing the job twice.
The documentation gap and what it costs
Incomplete job documentation has a direct financial consequence that most field service businesses feel but don't measure.
When notes are thin, invoices get delayed — because the office needs to chase the engineer for detail before the invoice can go out accurately. When invoices are inaccurate, disputes follow. Industry data puts the billing dispute rate at 8–12% of invoices when documentation is inconsistent. Each dispute costs the disputed amount, plus the time to resolve it, plus the relationship strain that comes with questioning a customer over work that was done well.
The payment acceleration from clean, proactive post-job communication runs at 15–20 days faster on average. For a business carrying £100,000 in monthly receivables, that's £50,000 in improved cash flow — not additional revenue, but revenue that was earned and then sat waiting because the documentation process wasn't working.
JobScribe captures job records in real time. JobBrief generates a professional customer summary automatically when the job closes. The documentation is complete when the job is complete. The invoice goes out the same day. The customer receives a clear account of what was done before they've had time to wonder.
The disputes from unclear records largely disappear. The payment cycle shortens. The cash tied up in the gap between completing work and receiving payment starts moving faster.
The time that isn't going to billable work
Every hour an engineer spends on work that isn't billable is an hour the business is paying for without recovering it.
Pre-job preparation — pulling history, assembling context, figuring out what they're walking into — takes the average engineer 30 minutes per day. End-of-day documentation takes between 30 minutes and two hours. For a ten-engineer crew, the conservative estimate puts the combined cost of that non-billable administrative time at over £50,000 annually. The longer estimate runs past £150,000.
Those aren't wasted hours in the sense that the work is worthless — preparation and documentation both matter. But when that work gets handled by the intelligence layer rather than the engineer, those hours go back to the business. In a tightly scheduled operation, recovering 30 minutes per engineer per day creates capacity for additional jobs. In an operation with flexibility, it reduces the hours that push into overtime.
Either way, it's margin.
The questions that don't get asked — and what they cost
The less visible profit leak is in the decisions that don't get made because the information to make them isn't easily accessible.
Which job types are generating healthy margins and which aren't? A business that can't answer that quickly is almost certainly running unprofitable work because the pattern isn't visible. Which customers are consistently slow to pay? A business without easy access to that list is carrying receivables it could be actively managing. Which engineers are generating return visits at a rate above the rest of the team? A business without visibility into that pattern is absorbing the cost without addressing the cause.
Businesses with real-time access to operational data run at 5–6% higher margins than their peers. Not because they do different work — because they make better decisions about the work they do. They know where the margin is going. They can act on it before it compounds.
JustAsk makes that information available on demand. The questions that were worth asking but too hard to find quickly become routine. The patterns developing quietly in the data become visible before they're expensive.
What the margin gap actually is
The difference between a 6% field service business and a 24% one isn't a single thing. It's the aggregate of a hundred operational improvements, each one modest in isolation, compounding across every job, every day, every week.
A return trip that doesn't happen. An invoice that goes out the same day rather than three days later. A documentation dispute that doesn't occur. 30 minutes of preparation time that goes back to billable work. A job type that gets repriced because the margin data made the problem visible.
None of those individually closes an 18-point margin gap. Together, sustained over time, they do.
BigChange Lightning doesn't change the nature of the work. It changes the system the work runs through — and when that system works, every job is a little more profitable than it was before. The aggregate of those improvements is what moves the margin from 6% to 24%.
That's what BigChange Lightning changes. Not the work. The economics of how the work gets done.
[Understand BigChange Lightning's impact on your business →]
