Lana Korzhuk — Founder & CEO of SIMARA AI

Lana Korzhuk

Founder & CEO · LinkedIn

With 20+ years progressing from senior developer to Chief Operating Officer, Lana brings deep expertise in IT systems, ERP implementation, and operational strategy.

Published · 14 min read
Service delivery, scheduling & field operations

When to Ditch Spreadsheets and WhatsApp for Job Tracking: A Simple Cost Threshold for UK SMEs

When to Ditch Spreadsheets and WhatsApp for Job Tracking: A Simple Cost Threshold for UK SMEs

(Time required, difficulty, expected outcome)

  • Time required: 60–90 minutes to run the numbers and see if you are past the job tracking spreadsheet threshold.
  • Difficulty: Moderate — you need basic spreadsheet skills and rough salary figures, not a finance degree.
  • Expected outcome: A clear, pound‑based decision: stay on spreadsheets/WhatsApp for now, buy standard job management software, or invest in AI‑assisted job tracking.

Most UK service and field operations cling to job tracking spreadsheets and WhatsApp groups far too long. The issue is not that they “look messy”. The issue is that, past a certain volume, they quietly cost more in rework, missed jobs and management time than proper job management software — even before you add any AI.

This article answers one narrow question: at what point does sticking with spreadsheets and WhatsApp for job tracking become more expensive than switching to a proper system, for a 10–100 person UK SME? We give you one cost threshold you can calculate in under an hour.

Once you have that, you can make a straight decision: keep the current setup a bit longer, buy off‑the‑shelf job management, or layer AI on top later. If you want help ranking which processes to tackle first once you’ve made that move, our free Automation Priority Scorer will do that in a few minutes.


Required Tools / Prerequisites

To work out whether you’ve crossed the job tracking spreadsheet threshold, you only need a few inputs and an honest look at where time goes.

Definition: Job tracking spreadsheet — a manually maintained Excel or Google Sheet used to log, assign and update work orders, call‑outs or projects.

You’ll need:

  1. Basic time and error estimates

    • Average jobs per week (or per month if that’s how you think).
    • How many people touch the job sheet or WhatsApp group.
    • Rough hours per week spent:
      • Updating the sheet / posting updates in WhatsApp.
      • Chasing status (“where is this job up to?”).
      • Fixing mistakes (missed jobs, wrong address, duplicate visits, rework).
  2. Loaded hourly costs

    • Use realistic, fully loaded London/South East salaries (salary × ~1.3 for NI, pension, overheads):
      • Field engineer/technician: often £40k–£55k → roughly £25–£35/hour fully loaded.
      • Admin/dispatcher: often £28k–£38k → roughly £18–£25/hour fully loaded.
      • Ops/service manager: often £45k–£70k → roughly £30–£45/hour fully loaded.
  3. A simple calculator (or spreadsheet)

    • Excel or Google Sheets is enough. You just need to multiply hours by hourly cost and compare to realistic software/automation costs.

Definition: Service delivery cost of rework — the total cost of sending someone back to redo a job, including labour, travel, materials and any discounts or refunds.

If you already have time‑and‑motion data from an existing audit, even better. If not, rough estimates are fine as long as they’re anchored in actual behaviour (“we spend every Monday morning cleaning the sheet” is more useful than “not that much time”).


Step 1: Quantify What Spreadsheets and WhatsApp Are Really Costing You

First, put a monthly pound value on your current “free” job tracking setup: the spreadsheet plus the WhatsApp groups (or Teams chats) your team actually runs jobs through.

You’re looking at three cost buckets:

  1. Admin & coordination time

    • Time spent keeping the job tracking spreadsheet up to date.
    • Time spent in WhatsApp/Teams clarifying address, scope, photos, “are you done yet?”.
  2. Service delivery cost of rework

    • Extra visits caused by mis‑keyed data, lost messages or outdated job lists.
    • Examples: engineer goes to wrong site, job done on wrong day, missed parts because notes were buried in chat.
  3. Management overhead

    • Time your ops or service manager spends firefighting because the data is fragmented.
    • Time spent building manual status reports from the spreadsheet and screenshots.

Definition: Field operations WhatsApp risk — the operational and compliance risk created when critical job instructions live in unstructured, personal messaging apps instead of controlled systems.

A simple cost formula you can reuse

Use this rough monthly cost model:

  • Admin & coordination
    Admin monthly cost = weekly admin hours × admin hourly cost × 4.33

  • Rework
    Rework monthly cost = rework jobs per month × average rework cost per job

  • Management overhead
    Management monthly cost = weekly manager hours × manager hourly cost × 4.33

Total spreadsheet/WhatsApp cost per month
= Admin cost + Rework cost + Management cost

You don’t need perfect numbers. You just want to be in the right ballpark, say within ±20%. The crucial part is that you count rework explicitly; that’s where margins quietly leak.

Definition: Job tracking spreadsheet threshold — the point where the monthly cost of running jobs on spreadsheets/WhatsApp is higher than the monthly cost of running them on structured job management software (with or without AI support).

Calculate this for your business: Once you’ve estimated these numbers for job tracking, use our free Automation Priority Scorer to compare it with other candidate processes so you tackle the highest‑return one first.


Step 2: Work Out a Realistic Cost for Job Management Software (and Optional AI)

Next, you need a realistic monthly cost for moving off spreadsheets and WhatsApp. That usually means some combination of:

  • A job management or field service tool licence (per user, per month).
  • One‑off implementation/configuration.
  • Optional AI‑assisted workflows (e.g. automatic job summaries, routing suggestions) if you are ready for them.

Definition: AI job tracking for UK SMEs — using AI components (e.g. language models, classification, routing suggestions) on top of a job management system to automate admin tasks like notes, scheduling hints, and status updates.

Typical SME job management cost profile

We see UK SMEs in the 10–100 person range often end up in one of three patterns:

  • Standard SaaS job management

    • £20–£40/user/month.
    • 10–25 users in field + office → roughly £300–£800/month.
    • Light setup in‑house or with a small partner.
  • Standard SaaS + modest AI layer

    • Above licence cost plus AI API usage or an AI add‑on.
    • Commonly an extra £150–£500/month depending on volume.
  • Heavier custom AI job tracking

    • One‑off project £7k–£25k to integrate AI tightly with your stack.
    • Ongoing cloud/maintenance £200–£600/month.

If you want fuller automation‑project cost maths, we break that down in our AI ROI analysis guide and our AI consultancy cost overview.

For this article, keep it simple: turn everything into a monthly equivalent so you can compare directly:

  • Spread one‑off implementation over 12 months.
  • Add monthly licences + AI costs.

Monthly structured job tracking cost
= (Implementation cost ÷ 12) + Software licences + AI usage


Step 3: Apply the Simple Cost Threshold

Once you’ve priced both sides, the decision is blunt:

  • If your spreadsheet/WhatsApp cost per month is lower than structured job tracking, stay manual for now.
  • If it’s higher, you’ve crossed the job tracking spreadsheet threshold and should plan a switch.

We use a simple rule with clients:

If your spreadsheet/WhatsApp job tracking is costing more than ~1.5× the monthly cost of a structured tool, you are leaving money on the table.

That 1.5× factor gives you room for:

  • Disruption during rollout.
  • Adoption drag (not everyone uses the system perfectly from day one).
  • The fact that some rework will still happen even with a better tool.

Comparison table: when each option makes sense

Option Monthly cost band (illustrative) Time to value Best when
Stay on spreadsheets & WhatsApp £0 direct, £500–£3,000 hidden labour/rework Immediate Jobs/week < 40 and rework cost is genuinely low
Buy basic job management software £300–£900 (licence + 12‑month amortised setup) 2–8 weeks Jobs/week > 40 and hidden cost > 1.5× software cost
Add AI‑assisted job tracking on top Software above + £150–£600 4–12 weeks You already run a structured tool and admin firefighting is still > 1 day/week

These numbers are broad, but the decision logic is not. If your hidden cost is:

  • Under £500/month → spreadsheets/WhatsApp are usually fine.
  • £500–£1,500/month → you’re on the fence; only switch if your volume is clearly growing.
  • Over £1,500/month → you are almost certainly past the job tracking spreadsheet threshold.

We use the same threshold mindset in our wider workflow work — our workflow automation guide applies similar logic across other processes.


Step 4: Run a Worked Example Using Realistic UK Numbers

To check that your reasoning hangs together, it helps to walk through a concrete example with UK salary levels.

An illustrative scenario: 20‑person London maintenance firm

Imagine a 20‑person building maintenance firm in North London:

  • 12 engineers, 3 office admins, 1 ops manager, 4 others.
  • Roughly 120 jobs per week (reactive and planned).
  • Jobs tracked in a shared Google Sheet; updates and photos live in two WhatsApp groups.

You estimate:

  • Admin & coordination

    • 3 admins spend ~5 hours/week each updating the sheet and chasing engineers on WhatsApp → 15 hours/week.
    • Fully loaded admin cost ~£20/hour.
    • Admin monthly cost ≈ 15 × £20 × 4.33 ≈ £1,299.
  • Rework

    • Around 8 jobs/month need a revisit purely due to tracking failures (wrong address, missed note, lost photo).
    • Average rework cost per job (engineer time + travel + goodwill discount) ≈ £180.
    • Rework monthly cost ≈ 8 × £180 = £1,440.
  • Management overhead

    • Ops manager spends ~4 hours/week on “where is this job?”, updating a status report from the sheet and WhatsApp screenshots.
    • Fully loaded cost ~£35/hour.
    • Management monthly cost ≈ 4 × £35 × 4.33 ≈ £606.

Total spreadsheet/WhatsApp cost per month
≈ £1,299 + £1,440 + £606 ≈ £3,345.

Now compare job management options:

  • Job management SaaS: 16 users at £30/user/month → £480/month.
  • Light implementation help + data migration: £6,000 once‑off.
  • Optional AI‑assisted summaries/routing: start small at ~£200/month.

Monthly equivalent (year one):

  • Implementation amortised over 12 months: £6,000 ÷ 12 = £500.
  • Licences: £480.
  • AI usage: £200.

Total structured job tracking cost (year one)
≈ £1,180/month.

Set that against the £3,345/month hidden cost you’re currently absorbing. You’re almost 3× over the software cost, well above the 1.5× threshold. Even if your estimates are off by half, you’re still past the point where a job system (with or without AI) is commercially obvious.

This is exactly the sort of scenario where, in our three‑phase model, we’d prioritise job tracking as a Phase 1 pilot: the volumes are high, the process runs daily, and the cost of rework is material.


Step 5: Decide Whether You Need AI Now or Later

Once you’ve decided you’re past the spreadsheet threshold, the next question is when to buy job management software with AI features versus starting with a standard tool and layering AI later.

We recommend a simple sequence:

  1. Get out of spreadsheets and WhatsApp first.

    • Move to a structured tool where jobs, notes, photos and signatures live in one place.
    • Use built‑in automation (status triggers, checklists, basic notifications) before you touch AI.
  2. Add AI only when three conditions are met:

    • You generate enough unstructured data (free‑text notes, photos, emails) that humans waste time summarising or searching it.
    • Your team spends at least 1 day/week collective time on admin related to job updates, reporting or communication.
    • You have someone who can own and monitor AI behaviour 4+ hours per week.
  3. Start with low‑risk AI use cases in job tracking:

    • Auto‑drafting job summaries from engineer notes.
    • Suggesting next‑day scheduling options based on SLAs and locations (human‑approved).
    • Classifying incoming job emails into the correct queues.

Definition: Decision repeatability — the proportion of day‑to‑day choices (assigning jobs, prioritising tickets) that follow a consistent rule that an AI or rules engine can learn.

Our AI Readiness Scorecard is built around this idea. If your processes are repeatable and your data is reasonably structured, AI on top of job management software will usually pay back in months, not years.

If you’re not sure whether AI belongs in your first wave, our AI readiness checklist walks through the data and process prerequisites in more detail.


Common Pitfalls / Troubleshooting

Even with clear maths, UK SMEs often trip over the same issues when trying to move away from job tracking spreadsheets and WhatsApp.

Pitfall 1: Underestimating the service delivery cost of rework

Most teams only count obvious rework: the second visit. They ignore:

  • Time spent on the phone calming an annoyed customer.
  • Discounts or credits offered to “make it right”.
  • Knock‑on delays for the next jobs on that engineer’s route.

If you’re struggling to quantify this, start by tagging a month’s worth of rework incidents and recording why they happened. Anything linked to poor job information or lost messages belongs in the rework column.

Pitfall 2: Over‑buying software because “AI will fix it”

We see SMEs jump from spreadsheets straight to heavy, AI‑branded platforms without fixing the basics:

  • No clear job codes or categories.
  • Vague SLAs.
  • Inconsistent data entry.

AI amplifies whatever data you give it. If your underlying job tracking is chaotic, AI will just give you faster chaos. Fix the structure first, then automate.

Pitfall 3: Ignoring field operations WhatsApp risk

WhatsApp feels convenient, but for job tracking it carries real risk:

  • Key instructions lived on a leaver’s personal phone.
  • No audit trail when something goes wrong.
  • Photos and customer data stored outside your controlled systems.

From a GDPR and operational standpoint, you want job‑critical data flowing through tools you control, log and can export — even before you consider AI.

Pitfall 4: Not assigning an internal owner

Whether you stay on spreadsheets for another year or move to a job tool next month, someone has to own job tracking quality.

  • On spreadsheets: they keep the template clean, defined and version‑controlled.
  • On software: they maintain templates, workflows, roles and basic automation.

Without an owner, both spreadsheets and software degrade quickly and your careful maths stops matching reality.

Pitfall 5: Trying to automate low‑volume, bespoke work

Some job types are highly bespoke or infrequent. For example, a quarterly shutdown project that takes a week of planning but only happens four times a year.

Those are poor candidates for heavy automation. Document them well and keep a simple checklist. Save AI and integration effort for high‑frequency, medium‑complexity work where small efficiencies stack up daily.


It’s good enough if three things are true: you handle fewer than about 40 jobs per week, your team spends under 5 hours/week collectively maintaining and chasing the sheet, and rework linked to tracking errors is rare (say, less than one incident every fortnight). If you’re above those thresholds, run the cost calculation in this article — you may already be overpaying to stay manual.

When should a UK SME buy job management software instead of improving spreadsheets?

You should buy when your total monthly cost of spreadsheets/WhatsApp (admin time + rework + management overhead) is more than about 1.5× the all‑in monthly cost of a job management tool. At that point, even a conservative improvement in rework and admin will pay for the system within a year. If you need a wider view across processes to pick your first target, our free Automation Priority Scorer will rank them by impact and effort.

Do I need AI from day one, or can I add it later?

You can add AI later. In fact, we usually recommend it. Move from spreadsheets/WhatsApp to a solid job management tool first, run it for a couple of months, then look at where admin and decision‑making still eat time. AI delivers the best return when it’s automating clearly defined, repeatable tasks on top of structured data.

What’s the biggest risk of keeping job tracking on WhatsApp?

Operationally, the biggest risk is that critical instructions and evidence (photos, messages, approvals) live on personal devices with no central record. That leads to disputes you can’t evidence, missed jobs when someone is off sick, and significant GDPR exposure because you don’t control where customer data is stored. Even a basic shared system is a step change in control and audit trail.

Which process should I automate first once I buy job management software?

Start with the most frequent, most painful admin loop — often job creation and closing, or daily reporting. Look for steps that happen every day and involve copying data between tools. To make this less guesswork and more maths, use our free Automation Priority Scorer: it ranks your candidate workflows by effort, impact and risk so you start with the highest‑return one.


Ready to move beyond spreadsheets and WhatsApp, or want a second pair of eyes on your numbers? → Contact SIMARA AI and we’ll help you quantify the break‑even point for your specific field or service operation.


Sources & Further Reading


What to explore next:

If you’re ready to talk through your specific job tracking setup and cost threshold, you can reach us directly here → Contact SIMARA AI


See your numbers before you spend a penny

Free, no sign-up: the Automation Priority Scorer ranks your candidate workflows by effort, impact and risk so you start with the highest-return one.

Try the free Automation Priority Scorer

Or talk to us directly: