Automation & tools
The spreadsheet is the prototype
Short answer
Almost every small business runs on a spreadsheet that grew a tab for every new need. It is not a failure: it is a working prototype written by the people who know the process best. The right replacement follows it closely, fixes what breaks, and arrives in small steps.
Almost every small business has one. It might be called Bookings 2024 FINAL, or Quotes, or simply Stock. It has twelve tabs, three colours that mean something, a column nobody remembers adding, and a formula in cell F2 that everybody is afraid of.
It is easy to treat that file as an embarrassment. It is better to treat it as the most valuable document in the project.
Why the spreadsheet is right
The spreadsheet was built by the people who do the work, one need at a time. Every column exists because someone needed to know something. Every colour code is a status that matters. Every awkward workaround marks a place where the real process is more complicated than it looks from outside.
That is a specification, written in the most honest way possible: by use.
Why it eventually breaks
Spreadsheets are excellent for one person and a few hundred rows. They start to fail when:
- several people edit the same file at once,
- the same data has to be typed into two places,
- nothing stops an impossible value being entered,
- there is no history of who changed what,
- and the only way to get a number out is to ask the one person who understands the formulas.
None of those are reasons to feel bad about the spreadsheet. They are signs the business has grown past it.
How to replace it without losing what it knows
- Sit with the people who use it. Ask what each column is for, and what happens when something goes wrong. The workarounds are the requirements.
- Replace one process first. Bookings, or quotes, or leads. Not all of them.
- Build a small first version quickly, and use it on real work while the spreadsheet still exists as a fallback.
- Import the history, so nobody loses the past.
- Retire the spreadsheet only when the team stops opening it.
Software is not always the answer
Sometimes the right fix is a better spreadsheet: validation, protected ranges, one owner. Sometimes it is an off-the-shelf tool. The point of starting from the spreadsheet is that it tells you which, before anyone writes any code. That is how we approach workflow automation.