Construction and field businesses discover their margin at the end, when the job is closed and the numbers are added up. By then every decision that determined the outcome has already been made. We build the visibility that moves that discovery forward — to the week the cost is incurred, not the month after the job completes.
A job that will lose money usually signals it early — in labour hours drifting past the estimate, in materials drawn faster than planned, in change work performed before it was priced. The information exists on the site; the office receives it weeks later on a paper ticket. Closing that lag is what technology is for here, and each sub-sector closes it differently.
Project delivery, subcontractor management, change orders, progress billing and the retention and lien administration that dominates cash flow.
Crew scheduling across many small jobs, service and project work mixed together, and material and truck stock management.
Preventive maintenance contracts, emergency dispatch, equipment history at each site, and the contract renewals that make a service book valuable.
Technician scheduling with skills and parts, first-time fix rate, warranty and returns, and the customer communication that determines a review score.
Multi-site work orders, service level agreements, planned and reactive maintenance, and reporting to property owners who want evidence, not assurances.
Multi-year projects, equipment and plant utilisation, certified payroll and prevailing wage, and the funding compliance attached to public work.
Where the return actually comes from: Three sources dominate. Change orders: work performed but never priced or billed is, in most contracting businesses we see, the single largest recoverable leak — and it is a process problem, not a commercial one. Utilisation: an extra job per crew per week compounds enormously across a year, and most scheduling is done from a whiteboard and a memory of who is where. And cash: progress billing raised promptly against actual completion, with retention tracked, shortens a cycle that most contractors finance out of their own working capital.
This sector is the most paper-dependent we work in, and the gap between site and office is where most of the value is trapped.
Job cost accounting, progress billing, retention, certified payroll and equipment costing. Construction accounting is genuinely different from general accounting, and generic systems handle it badly.
Crew and technician scheduling, dispatch, work orders, project sequencing and subcontractor coordination — most often run on a whiteboard, a phone and a great deal of institutional memory.
Time entry, material usage, photographs, signatures, inspection forms and daily reports captured at the point of work — and, crucially, working when the site has no connectivity.
Estimating, bid management, contracts, change order pricing and approval, and the customer communication that stops a variation becoming a dispute six months later.
Four problems, and the outcome the owner or operations director is really asking for.
A customer asks for something on site. The crew does it, because saying no is awkward and the relationship matters. The paperwork follows sometimes, is priced optimistically, and is disputed at the end.
The outcome leaders ask forEvery variation captured on site at the moment it is requested, priced against the contract and approved before the work starts — recovering revenue that is currently written off as goodwill.Labour tickets, material invoices and equipment charges reach accounting on their own timetable. A job is understood in the month-end close, by which point nothing can be changed.
The outcome leaders ask forWeekly job cost against budget, with the projected final position updated as costs land, so a drifting job is addressed while there is still job left to fix.Who is on which job, with what skills, holding which parts, and what happens when someone calls in sick at 6am. It works until that person is on holiday.
The outcome leaders ask forCrew and technician scheduling against real availability, skills and location, with the day's plan visible to everyone and reschedulable in minutes rather than by phone tree.Daily reports, timesheets, delivery notes and photographs are captured on paper, and some proportion never arrives. What is lost is exactly what would have won the dispute.
The outcome leaders ask forEverything captured digitally at the point of work, working offline, synced when the device reaches signal — so the evidence exists when it matters.Every one of these is a lag problem rather than a knowledge problem. The site already knows. The question is only how long the office takes to find out, and whether it is still early enough to act. Every one of these is a lag problem rather than a knowledge problem
We baseline from your last twelve months of completed jobs before agreeing any target.
Improvement where cost is visible weekly rather than at close
More variations priced and billed rather than absorbed
Additional productive hours from better scheduling
Faster progress billing against actual completion
Captured digitally, including with no connectivity
Projected final position updated as costs land
How to read these: How to read these: the figures above are typical ranges we plan and measure against, not guarantees. In your first engagement we agree the baseline, the target and the measurement method in writing, then report against them.
Almost everyone starts with the field capture, because it is the fastest way to make everything else possible.
The site end: time, materials, photographs, forms and signatures captured where the work happens, offline when necessary.
The commercial engine: budget against actual while the job runs, variations priced properly, and billing raised promptly.
The resource engine: the right crew, with the right skills and the right parts, at the right site.
We start on site. Designing field software from an office is the most reliable way to produce something crews refuse to use.
We spend days with crews and technicians, watching what gets captured, what gets lost and why.
We agree outcomes with ownership, operations and accounting together, and define the margin metric precisely.
We prototype the mobile experience first and put it in the hands of a real crew before building anything else.
We roll out field capture first, prove it with one crew, then extend to costing, billing and scheduling.
We measure margin, change order capture and utilisation against the baseline across a full season.
The crew that will be hardest to convince should be in your pilot group, not protected from it. If the app works for them it works for everyone, and if it does not, we would rather know in week three than after a company-wide rollout.
Field software fails for one dominant reason: it was designed for the office and given to the site.
Gloves, sunlight, cracked screens, no signal and someone who wants to be back in the truck. If capturing a timesheet takes more than a minute, it will not happen and none of the reporting above it will be true.
Job costing, work in progress, retention, progress billing and certified payroll behave differently from general accounting. Generic implementations get this wrong and the finance team discovers it at year end.
The value is in the loop: what you estimated, what it actually cost, and what that should change about the next bid. Most systems break that loop at the first hand-off.
Mobile devices, connectivity, applications and the managed service from one accountable team — which matters when a crew cannot log in at six in the morning.
Two illustrative engagements showing the shape of the work.
Crews performed extra work requested on site and the paperwork followed inconsistently. The owner estimated the annual write-off but had never been able to measure it.
One dispatcher held the entire schedule in her head and a whiteboard. Technician utilisation was unknown, emergency work displaced planned maintenance unpredictably, and holidays were genuinely stressful.
Practical pieces on margin, field capture and scheduling.
Why variations get absorbed, what it costs annually, and the process change that recovers most of it without damaging the relationship.
Read moreA short piece on why connectivity assumptions kill field software adoption within a fortnight.
Read moreCapturing institutional scheduling knowledge before it retires, and the constraints that actually matter.
Read morePick a job type and give us a real cost code structure. We will build a working demo of field capture, job costing and change orders for that job type — including the offline behaviour — and put it in front of one of your crews.
Describe the situation in your own words.
