How to move your trades business off spreadsheets and WhatsApp

The signs you've outgrown spreadsheets and WhatsApp

Spreadsheets and a WhatsApp group are how almost every trades business starts, and there's nothing wrong with that. When it's you, a mate and a couple of subbies, a shared spreadsheet and a phone in your pocket is the system. The trouble starts when the business grows and the system doesn't.

• Version chaos. Three copies of the pricing spreadsheet on three laptops, "Quote v2 FINAL final.xlsx" doing the rounds, and nobody sure which one the client signed off.
• Photos and instructions vanish into WhatsApp. The site photo that proves the snagging was fixed, the voice note with the variation instruction, the "yes go ahead" from the client - all buried in a scrolling group chat nobody can search six weeks later.
• No single source of truth. Ask three people what stage a job is at and you get three different answers, because everyone's working off their own note, memory, or bit of paper.
• Things fall through the cracks. A follow-up call never happens, a variation never gets priced, a snag never gets closed out - not laziness, just nothing chasing it.
• No visibility of job costs while the job is live. You find out a job's gone over budget when the final invoice lands, not while there's still time to fix it.
• Onboarding a new person is painful. There's no single place to show them "this is how we do it" - just a folder structure only you understand and a WhatsApp history they weren't part of.

None of these on their own is a crisis. Together, they're a sign the business has outgrown the tools it's running on.

Why it quietly costs you money

This doesn't show up as one dramatic loss - it bleeds out in small amounts, job after job, until you total it up at year end and can't explain where the margin went.

• Unbilled variations. The client asks for an extra socket, a wall moved, a different tile - agreed verbally on site, mentioned in passing, never turned into a priced instruction. By completion, nobody remembers to invoice it.
• Missed materials. Without a live record of what's been ordered against what was quoted, it's easy to double-order, under-order, or lose track of what a job actually cost versus what was priced.
• Disputes with no paper trail. When a client says "you never told us that would cost extra," a WhatsApp thread with 400 messages isn't a paper trail - it's a haystack. Without a dated, attributable record, you're arguing memory against memory, and that rarely goes your way.

Individually these might be a few hundred pounds here and there. Across a year, across every job, they're very often the difference between a healthy margin and a break-even one.

The principle of one source of truth

Whatever you do about this, hold onto one idea: every job should have one place where its current status, its costs, its instructions and its documents live - not scattered across a spreadsheet, an inbox, a WhatsApp group and someone's memory. It doesn't have to be software. It could be a well-run shared folder with strict naming rules and a single running job sheet. But it has to be one place, and everyone involved has to know it's the one place.

Most of the problems above are really the same problem wearing different clothes: information exists, but it's not somewhere everyone can find it, trust it, and update it. Fix that, and half your other problems shrink on their own.

What to move first - and what to leave until later

Don't try to fix everything in one go. Move things across in the order they'll actually pay you back.

1. Quotes and jobs first. Get every live enquiry and job into one place with a clear status, so anyone can see what's quoted, what's won, and what's actually running. This is the highest-value move because it's causing the most day-to-day confusion.
2. Then costs. Once jobs are in one place, start tracking what each is actually costing - labour, materials, subcontractors - against what was quoted. This turns "I think that job did alright" into "that job made 18% margin and here's why."
3. Then site information and photos. Last, because it's the highest volume and easiest to let slide - but once quotes and costs are sorted, moving photos, snagging and site notes out of WhatsApp stops them disappearing and gives you something to point to if a dispute comes up.

Trying to do all three at once is usually how these switches fail - everyone gets overwhelmed in month one and drifts back to what they know.

Make the switch in phases, not a big bang

The biggest mistake businesses make here is trying to move everything, for every job, on day one. It never sticks - people revert to the old habit the moment the new one gets awkward, and you end up running two systems badly instead of one well.

A better approach: pick one live job - ideally a straightforward one, not your trickiest current headache - and run it entirely through the new way of working, start to finish, while everything else carries on as normal. You'll hit the rough edges on something small enough that they don't matter, and your team gets a real example to point to rather than a hypothetical.

Once that job's done and the lessons folded in, add the next few, then make it the default for every new job. Jobs already nearly finished can just run out the old way - there's rarely value in migrating one that's two weeks from completion.

Getting the crew to actually use it

This is where most switches actually live or die, and it's got nothing to do with the tool itself. Office staff will adapt to almost anything with a bit of training and a reason. Field staff won't - and shouldn't have to.

• Keep it dead simple on site. If updating a job takes more than a couple of taps, or means opening a spreadsheet on a phone in the rain, it won't happen. Whatever field staff use needs to be quicker than sending a WhatsApp message, or people will just send the WhatsApp message.
• Don't force field staff into office tools. Nobody who's spent the day on the tools wants to fill in a spreadsheet at 5pm - a photo, a quick note, marking a task done is the ceiling of what you should expect from site.
• Show them why, not just how. "This is so the office stops chasing you for photos" lands better than "head office says we're using this now."
• Get an informal champion on side early. If the most respected foreman on the job uses it properly, everyone else follows within a fortnight.

Worth checking what different job management tools actually expect from field staff day to day, not just what the office dashboard looks like in the demo.

What to keep - accounting stays where it is

None of this is an argument for ripping out your accounting software. Xero or QuickBooks should stay exactly where they are - trying to replace proper accounting software with a job spreadsheet (or the reverse) is how businesses end up with a mess in both places.

The right move is to connect the two: job and cost data flows out of wherever you're running jobs, invoices flow into your accounts, and your accountant keeps working as before. You're not replacing your bookkeeping - you're stopping the job side of the business running on tools never built for it.

Deciding when it's time

There's no single trigger - it's usually a combination of the signs above, plus a gut feeling the business has got harder to run than the workload justifies. As a rough rule: if you're running more than a handful of jobs at once, if more than two or three people need to know what's going on with any given job, or if you've ever lost money on a variation because nobody wrote it down, you're past the point where a spreadsheet and a group chat are doing you any favours.

Spend an afternoon comparing how different tools handle this before committing to one, and check the pricing against what the current mess is quietly costing you in unbilled variations and disputed hours. Whatever you choose, do it in phases, keep it simple for the crew, and leave your accounts exactly where they are.