Every business we meet has one. The Spreadsheet. Seventeen tabs, colour-coding that only Karen understands, formulas nobody dares touch, and a filename like FINAL_v7_USE_THIS_ONE.xlsx. It runs quoting, or scheduling, or stock, or all three. And everyone quietly knows that if it broke — or if Karen left — the business would have a very bad month.
A spreadsheet is the most successful end-user programming tool ever made, and starting your process in one is genuinely smart: cheap, flexible, instant. The problem is that spreadsheets don’t announce when you’ve outgrown them. There’s no warning light. The workbook just accumulates tabs, links, macros and workarounds until one day it isn’t a spreadsheet any more — it’s an unfunded, undocumented, single-maintainer software project that happens to live in Excel.
Three or more of those, and the spreadsheet is costing more than software would — the cost is just hidden in salaries, errors and risk instead of appearing on an invoice.
Not a huge IT project. The pattern that works: map the process the spreadsheet actually runs (usually two days of asking questions), build the smallest system that runs it properly — one database, one screen per job, accounts for the people who need them — and migrate the data once, cleanly. Modern web apps make this far cheaper than the word “bespoke” suggests, because you’re not paying for the 90% of an off-the-shelf product you’d never use.
What you get back: everyone sees the same live data, nothing depends on one person, the fragile formulas become tested code, and the copy-paste hours come back as actual work. The spreadsheet earned its retirement. Give it a good send-off — then stop running your business on it.