When a finance, ops, or HR team has a spreadsheet with 14 tabs, conditional formatting that makes the grid eye-watering, and a manual ‘paste from this column to that one’ step on the first of every month — that is not a spreadsheet. It is a job description waiting to be automated. Here’s how to tell, and what to do about it.

The ‘one-person workflow’ tell

The clearest signal that a spreadsheet has outgrown its job is the ‘one-person workflow’ phenomenon: there is exactly one person who knows how to update it, exactly one person whose holiday triggers a small panic, and exactly one person whose laptop has the local copy that’s somehow more current than the shared drive version. If you have that person on your team, you have a spreadsheet that should be a system.

It’s not their fault. They built the spreadsheet because they had a problem and no engineering team to solve it. Over years it accumulated tabs, formulas, hidden columns, and rules they keep in their head. The thing that started as a productivity aid became their job. That’s the goldmine — it’s also a continuity risk.

What you can usually keep (and what you can’t)

When we replace one of these spreadsheets, the goal is not to eliminate Excel from the team’s life. Spreadsheets are excellent for ad-hoc analysis and one-person quick exploration. They are bad for shared, repeated, multi-step processes. The replacement is therefore a small system that handles the structured part — the data, the rules, the workflow — and lets the team continue using spreadsheets for the unstructured part.

What goes into the system: the source-of-truth tables, the rules that run on update, the multi-user inputs, the recurring outputs (reports, exports, dashboards). What stays in spreadsheets: ad-hoc analysis, scenario modelling, things you might do once a quarter and rebuild from scratch.

How we audit a spreadsheet for automation

Three-step audit, usually done in 90 minutes with the spreadsheet’s owner. Step 1: walk the workflow. The owner shows us, screenshare, what they do at the start, middle, and end of a typical month. We watch and don’t interrupt. Step 2: we name every input, every transformation, and every output. Most owners are surprised by how many there are when listed — usually 12–25 distinct steps in spreadsheets that ‘aren’t very complex.’

Step 3: we classify each step as automatable, judgement-required, or system-of-record. Automatable steps go into the new tool. Judgement-required steps stay with humans but in a clearer interface. System-of-record steps get migrated to the proper system (CRM, ERP, accounting software). The ratio is usually 70/20/10.

What replaces it

The replacement is rarely a SaaS product the team didn’t already have. Most off-the-shelf tools are too generic to handle the specific shape of one company’s workflow. The replacement is usually a small custom web app — auth, a few forms, a database, the rules baked in, recurring scheduled jobs that do the monthly grind, exports back to Excel for the parts that genuinely need to live there.

Build time: usually 2–4 weeks for the kind of spreadsheet we’re describing. Cost: typically £8–20k depending on integrations. The continuity benefit alone — the team’s institutional knowledge no longer lives in one person’s head — is worth most of that. The time savings (2–10 hours/week ongoing) are bonus.

Find your goldmine

If your team has a spreadsheet that fits this description — and most teams have at least one — it’s almost certainly worth a 30-minute conversation about whether replacing it makes economic sense. Sometimes the answer is no (the workflow is genuinely simple and the spreadsheet is fine). Sometimes the answer is ‘yes, but smaller than you’d think’ (a single integration plus a small dashboard, not a full rebuild).

We do these audits as a free first step into internal tools and automation. Drop us a line with the spreadsheet’s job and we’ll come back with an honest scope.