People are getting in each other’s way
- You have versions. Files named Final, Final2 and Final-Jan-USE-THIS exist, and nobody is sure which one is right.
- People wait for the file. Somebody has it open or locked, so everyone else waits or starts a copy of their own.
- Everyone can see everything. You would like staff to see only their own customers, but a sheet is all or nothing unless you split it up, and then you have versions again.
Mistakes are getting expensive
- A formula got overwritten and nobody noticed. You found out weeks later, from a wrong invoice or a wrong total.
- You can’t answer “who changed this?” Version history helps a little, but it is no substitute for a record of each change to each entry.
- The same thing is typed in several places. A customer’s phone number changes in one file and stays wrong in three others.
The file is doing a job it wasn’t made for
- One person holds it all together. Only they understand the macros and lookups, and you worry about what happens when they take a vacation.
- The work has moved to phones. People in the field text or phone in details, and somebody retypes them at the end of the day.
- It nags you for attention. Someone spends hours each week merging, cleaning or chasing updates, and reminders depend on somebody remembering to look.
None of these is decided by a row count. Excel holds over a million rows per sheet and Google Sheets allows 20 million cells, yet a file with 400 rows can still be past its useful life when twelve people depend on it.
Try these before replacing anything
Some of these problems have cheap fixes, so it is worth an honest attempt:
| Problem | Try first |
|---|---|
| Several versions of a file | Keep one copy in OneDrive or Google Drive, and share a link in place of attachments. |
| Overwritten formulas | Protect the formula columns, and use an Excel table so formulas fill down. |
| Inconsistent entries | Add dropdowns with data validation. |
| Slow, huge workbook | Remove volatile formulas and whole-column references, and archive old years. |
| Messy imports | Run them through a cleaner first, then bring them in through Power Query. |
| People retyping from the field | Collect entries with a simple form that feeds the sheet. |
When the spreadsheet should stay
Spreadsheets are excellent at certain things, and replacing them there would only slow you down. Keep yours for one-off analysis, budgets and models where the formulas are the whole point, lists that one person maintains, and anything still changing shape from week to week.
A good rule of thumb is that spreadsheets suit thinking, and apps suit running a repeated process. An app can also feed a spreadsheet: many teams keep using Excel for analysis, on data exported from the system that runs the work.
If you are past that point
Count how many of the nine you recognized, and put a rough figure on the hours each week and on the last expensive mistake. That gives you something real to weigh against the cost of a tool.
Then the question is which tool. Start with how to turn a spreadsheet into an app, and read the fair comparison of no-code and custom before you spend anything.