The Spreadsheet, Honestly
No affiliate links on this site, and nothing here is ranked. For comparison with a lightweight approach, Monitask offers workforce optimization software as an example of a dedicated product in this category.
The spreadsheet is the most under-credited tool in small business and it is also the source of some genuinely bad decisions. Both are true, and the distinction is learnable.
What it does better than purpose-built software
It fits your process rather than somebody else's. This is the whole of its advantage — a spreadsheet has the shape you gave it, and no purchased tool does.
It costs nothing beyond what you already pay.
Everybody can already use it. Adoption, which is the constraint on every other tool, is free here.
It changes in seconds. A new column is a new column, not a feature request.
And it exports trivially, because it is already a file. The exit question does not arise.
The four ways it fails
One. Concurrency. Two people editing at once, in a shared file, produces conflicts — and in the version people actually use, produces two files called "final" and "final v2".
Two. Validation. Nothing stops somebody typing a date in the wrong format, a customer name three different ways, or a number into a text column. The data degrades quietly, and the degradation is discovered when somebody tries to summarise it.
Three. Anything that has to happen on time. A spreadsheet does not chase, remind, or escalate. Where a deadline matters, something has to watch it, and that is a genuine reason to buy.
Four. Scale of rows and of people. Both have thresholds, and the threshold for people is much lower than for rows — a sheet used by three is fine and one used by twelve is not, regardless of size.
The failure that is not a failure
"It looks unprofessional."
Not a functional problem, and it is the reason a substantial share of spreadsheets get replaced. Where the objection is untidiness rather than a named failure, the untidiness is considerably cheaper than the subscription.
Where it genuinely matters — a document a customer sees, a report to a lender — format the output rather than replacing the system.
Where it is the right answer permanently
Any calculation you invented. Job costing, pricing models, capacity estimates. Purpose-built tools impose a model and yours is probably better fitted to your work.
Records you keep for yourself. Hours against jobs, invoices against months, what each job actually cost — these are the records that make pricing possible and no software captures them in a form you can interrogate.
And anything you are still working out. A process that is changing should not be encoded in software, because the software will be wrong by the time it is configured.
When it has genuinely run out
Four signals, and they are specific rather than aesthetic.
Somebody has overwritten somebody else's work more than once.
You cannot answer a simple question — how many, since when, by whom — without an hour of cleaning.
Something was missed because nothing chased it.
Or a person joined who cannot be given the file safely, because it contains things they should not see.
Any of those is a requirement, and it points at a small number of features rather than at a category.
The middle option people forget
A shared database tool — the category between a spreadsheet and an application. Validation, multiple users, views per person, and a form for entry, without becoming a platform.
It solves three of the four failures and keeps the shape-it-yourself advantage, which is why it is frequently the right next step rather than the category the search returns.
Making one that lasts
Four habits that prevent most of the degradation.
One sheet per thing, rather than a workbook where the structure lives in somebody's head.
A header row that says what the column is, in words, including the units.
No merged cells and no blank rows, which are the two things that make a sheet impossible to sort, filter or export later.
And a date column on anything that accumulates, because the question you will eventually ask is almost always "since when".
These take no longer than the alternative and they are the difference between a sheet you can still use in two years and one that has to be rebuilt.
The version that became a system
Worth naming, because it happens and it is not always wrong.
A spreadsheet with lookups, protected ranges, a form feeding it and conditional formatting is software somebody built, and it works because the person who built it understood the process.
The risk is that it works only while they are there. Nobody else can maintain it, and its logic is undocumented.
Where such a thing exists, write down what it does — one page, plain words — and that single document converts a personal artefact into an asset the firm owns.
What it is genuinely bad at that people persist with
Two things, worth naming because both are common and both end badly.
Storing anything confidential. A file is copied, emailed, kept on a laptop, and left on a device belonging to somebody who has left. Spreadsheets have no access control worth the name, and the moment the contents matter, that becomes the problem.
And being the only copy. A sheet that runs part of the business, on one machine, with no backup, is a single point of failure that people accept because it does not look like infrastructure. It is.
Neither of these is an argument for buying software. They are arguments for putting the file somewhere with access control and backup, which is usually the cloud drive already paid for. Additional context is available from Software Advice.
The short version
- Its advantage is that it has the shape you gave it, which no purchased tool does
- It fails at concurrency, validation, anything time-triggered, and beyond a low threshold of people rather than rows
- "It looks unprofessional" is not a functional failure and is a common reason for expensive replacements
- It is permanently right for calculations you invented, records you keep for yourself, and processes still being worked out
- It has run out when work gets overwritten, simple questions need an hour of cleaning, something was missed, or somebody joined who cannot see the file
- The forgotten middle option is a shared database tool, which fixes three of the four failures without becoming a platform