The Hidden Cost of Running a Construction Business Through Email, WhatsApp and Spreadsheets

Almost every UK contracting business under about fifty people runs on the same three tools: email for anything official, WhatsApp for anything urgent, and a spreadsheet for anything with a number in it.

It is easy to be sniffy about this. Do not be. That stack is free, it is instant, every single person already knows how to use it, and it flexes around whatever the job throws at you in a way no software product ever quite manages. Firms turning over several million pounds run on it perfectly happily.

It also leaks money, and the leaks are hard to see because none of them shows up as a line on the P&L. This is an attempt to name them properly.

Cost one: the same number typed three times

Follow a single labour hour through a typical week. An engineer works it on site. It goes into a WhatsApp message on Friday, or onto a paper sheet in the van. Someone in the office types it into a spreadsheet to work out the week's hours. Then it gets typed again into the payroll run. Then, if it is a contract job, it gets typed a third time into the valuation build-up for the application for payment.

One number, three keystrokes, three chances to fat-finger it. And critically, no single one of those is the version of truth — if the payroll figure and the valuation figure disagree, there is no authority to appeal to. You go back to WhatsApp and scroll.

This is one of the most commonly raised problems in the threads we reviewed. Contractors describing their software frustrations keep landing on the same point: the gap between what happens in the field and what the office has, and the manual re-entry that bridges it. It is not that anyone is doing it wrong. It is that three separate systems that do not know about each other require a human to be the integration layer.

Cost two: you cannot prove what happened

This is the expensive one, and it is invisible until the day it is not.

A main contractor's QS knocks £6,000 off your application because, in their view, that work was not done in that period. You know it was. Can you evidence it? The proof exists — it is a photo somebody sent to a group chat on a Tuesday in March, and a message where the site manager said "yeah crack on with that". Both are technically still there. Neither is findable in the twenty minutes you have before the response is due.

The same pattern shows up on variations. Extra work gets instructed verbally or by message, gets done, and then gets disputed at valuation because there is no instruction anyone can produce. It is not that the evidence never existed. It is that WhatsApp is a river, not a filing system, and evidence you cannot retrieve on demand is evidence you do not have.

Put a number on it if you like: one disputed variation a quarter at a few thousand pounds each is a five-figure annual cost, and it will never appear as anything other than "margin was down a bit this year".

Cost three: the compliance stuff you find out about at the gate

Certificates, cards and RAMS have expiry dates, and expiry dates in a spreadsheet only work if somebody opens the spreadsheet.

The failure mode is well known to anyone who has run site work: someone turns up at the gate, the card has expired, and you are down a man for the day. Contractors discussing this describe exactly that scenario — a faded card, a date nobody checked, and the worse version where it is not caught at all and the risk sits on site until an inspection finds it.

The RAMS version is subtler. Chasing method statements out of subcontractors is a job in itself, and what comes back is frequently last job's document with the site name changed. A spreadsheet register tracks whether a document was received. It cannot tell you whether the document is any good, and it certainly cannot chase for a better one.

Cost four: you find out what a job made far too late

In a spreadsheet-run business, job profitability is a retrospective exercise. Costs land at different times — labour weekly, materials whenever the supplier invoices, subcontractors whenever they get round to applying — and the picture only assembles itself once the job is finished and someone sits down to add it up.

Which means you learn the job lost money at the point where the only remaining lever is "price the next one better". Everything that could have saved it — pulling a man off, challenging a variation, chasing an instruction in writing, going back on rates — needed to happen weeks earlier, at a moment when nobody had the numbers.

This is the cost that compounds. A firm that finds out at week four can fix the job. A firm that finds out at month four can only fix the estimate.

Cost five: it all lands on one person, at night

The last cost is the one people are least willing to write down. In most firms this size, the person who prices the work is also the person who runs the jobs, answers the phone, and does the applications for payment. The admin does not fit in the working day because the working day is spent on site, so it happens in the evening.

Contractors are blunt about this ratio when asked directly. Answers range from an hour a day to more than half the week, depending on the role — and the people carrying the most of it are usually the ones with the least slack. That is a real business risk, not just a lifestyle complaint: a business where one person holds the whole picture in their head is a business with a single point of failure who is also tired.

What to actually do about it

The bad advice here is "buy software". Plenty of firms have bought software and ended up running email, WhatsApp, spreadsheets and a system nobody logs into, which is worse.

What actually helps, in rough order of return:

• Pick one system of record for hours. Not three. Whatever you choose, the rule is that payroll and the valuation both read from it. This kills the re-keying cost and the reconciliation arguments in one move.
• Make instructions leave a trail by default. Verbal instruction is fine; verbal instruction with no follow-up message referencing the job is what costs you at valuation. A one-line "confirming the extra riser containment on job 214, as discussed" is worth thousands.
• Put expiry dates somewhere that chases you. A register that has to be opened is not a control. A calendar with real alerts is a poor system that beats an excellent spreadsheet.
• Cost jobs weekly, not at the end. Even roughly. A crude weekly number that is available beats a precise one that arrives in month four.
• Only then look at tooling, and evaluate it against those specific problems rather than a feature list. We wrote about what the main UK options actually cost, with prices from the vendors' own pages.

Where GUVNR sits on this

GUVNR is being built against exactly this list, so it is worth being precise about which parts are real today rather than implying we have solved all five.

Running in production today, inside the contracting business that builds it: one place for projects and jobs, scheduling and shifts, mobile shift reports off site, timesheets, purchase-order capture, and invoicing where the invoice you raise carries its CIS position and the VAT treatment you set on it. That directly addresses cost one and a good part of cost two, because the record is made where the work happens rather than reconstructed afterwards.

Currently being tested: applications for payment and valuations with retention, and RAMS.

Under active development: the automation that chases expiring certificates and outstanding records rather than displaying them, and project-profitability reporting is planned, not built.

So costs three and four are not solved yet, and we are not going to say they are. What we can say is that they are the reason the product exists.