.png)
The definition of a well-run operation hasn't changed. The baseline has.
Here's the updated BigChange article with the new headline and subhead, everything else unchanged:
For most field service businesses, running well has always meant the same things: jobs completed on time, engineers showing up where they're supposed to, invoices out before the end of the week. Get those right and you're ahead of most of the market.
Still true. But there's a growing group of businesses operating at a different level — not because they're working harder, but because they have something most of the industry doesn't yet. An intelligent layer that handles the operational work that used to fall through the cracks. Preparation that happens automatically. Documentation that doesn't depend on end-of-day memory. Business questions that get answered in seconds rather than hours.
This is what a well-run field service business looks like today. And what it means for the ones still operating the old way.
The businesses that have implemented BigChange Lightning are operating differently from the ones that haven't — not in ways that are visible on the outside, but in ways that compound quietly on the inside. In margin. In capacity. In the kind of operational control that separates a business running at 6% from one running at 24%.
This is what a field service business driving towards high profit margins looks like.
The day starts with preparation, not catch-up
In most field service businesses, the first thirty minutes of an engineer's day is spent reconstructing context. Pulling up job notes. Checking what happened last time at this site. Figuring out whether the part they need is in the van or needs to be sourced. Working out what to ask the service manager before heading out.
It's not wasted time in the sense that it's idle — they're working. But it's rework. Information that already exists in the system, being manually retrieved and assembled by someone who has other things to do.
A profitable field service business today eliminates that rework before the engineer gets in the van.
Every job comes with a briefing. Not a job card — a briefing. What the site history looks like. What was found last visit and what was left unresolved. What the customer has flagged. What parts are most likely to be needed based on the asset type and fault history. The information the engineer needs to walk in prepared rather than walking in and then getting prepared.
That briefing doesn't require a coordinator. It doesn't require the service manager to spend an hour the night before. It's generated automatically by Cooper — the AI brain of BigChange Lightning — from the data BigChange already holds. Because that's one of the twenty things a profitable field service business needs to do that most couldn't afford to staff for.
Prepared engineers fix more jobs on the first visit. Fewer return trips. Fewer parts delays. Less time on the phone between the depot and the site. The maths on first-time fix rate is direct — every percentage point improvement reduces the cost of a van roll and improves the customer experience at the same time.
Documentation happens during the job, not after it
The job record is one of the most undervalued assets in a field service business. It determines invoice accuracy, dispute resolution, asset history, regulatory compliance, and the quality of the briefing for the next engineer who attends that site. A complete, accurate job record is genuinely valuable.
The problem has always been that creating it requires the engineer to reconstruct what happened from memory, at the end of a long day, on a phone screen, in the van.
The notes that come out of that process are often incomplete. Sometimes wrong. Occasionally missing entirely. Not because engineers are careless — because they're tired, and writing notes is the last thing they do before they finish for the day.
A profitable field service business today captures job documentation as the work happens.
The conversation between the engineer and the customer. The fault description. What was done. What was found. What was recommended. Captured, structured, and written into the job record automatically — so the record reflects what actually happened, not what someone thought they remembered about it two hours later.
The downstream effects are significant. Invoices go out faster because the documentation is already complete. Disputes are easier to resolve because the record is detailed and accurate. The next engineer who attends that site arrives better prepared because the previous job record is actually useful.
The engineer's day ends when the job ends. Not when the paperwork does.
Questions get answered in seconds, not hours
Every field service business owner has a version of this experience. A question comes up — about margin, about an engineer's performance, about which customers haven't paid — and getting the answer means either running a report they half-remember how to configure, asking someone who has to go find out, or setting it aside to deal with later.
Most of those questions get set aside. Not because the answer doesn't matter, but because finding it is too much effort relative to everything else competing for attention.
A profitable field service business today answers those questions immediately.
What's my margin by job type this quarter? Which engineer has the highest first-time fix rate? How many jobs are currently at risk of running over? Who hasn't paid me in 60 days?
Those questions go to JustAsk. Plain English. No report to configure. No BI tool to log into. No analyst to brief. The answer comes back in the time it takes to read it.
The business intelligence that used to require dedicated headcount or dedicated software is now part of BigChange. Because BigChange has a brain now — and the brain knows what the data says.
The decisions that follow — which engineer to invest in developing, which customers to prioritise for collections, which job types to pursue or drop — get made faster, with better information, by people who have the context to act on them.
The operational baseline keeps rising
Here's the part that's most important to understand, and easiest to underestimate.
What's described above — the prepared briefings, the captured documentation, the instant answers — is not where the ceiling is. It's where the floor is now.
BigChange Lightning is a platform, not a feature set. The brain that's learning a business today is learning it continuously. In six months it knows more. In 12 months it knows significantly more. The agents that exist today — FieldReady, JobReady, JobScribe, JobBrief — are the first wave of what becomes an expanding digital workforce. New capabilities ship on the same upgrade. The business that gets on BigChange Lightning now is getting a platform that keeps producing.
And because installing the brain also accelerates BigChange itself — new features shipping faster, the platform improving more rapidly — the operational baseline doesn't stay fixed. It rises. Every month.
This is what separates businesses running at 24% from the ones stuck at 6%. Not a single improvement. Not a one-time investment. A platform that compounds — because the intelligence gets smarter, the operations get tighter, and the gap between prepared and unprepared keeps widening.
A profitable field service business has always been defined by execution. Getting to the job, completing it well, getting paid.
What's changed is the standard for what execution looks like — and what's possible when the business has the intelligence to support it.
That's what BigChange Lightning changes. Not the definition of a well-run business. The baseline.
