Nobody chooses Excel deliberately. It simply happens to be nearby the moment something needs counting quickly, and then it stays for years. It starts as one sheet of orders. A year later it is a file with twelve tabs, four competing versions with names like “final_v3_edits”, and one person in the company without whom none of it can be deciphered.<\/p>\n
The problem is not the spreadsheet itself. The problem is that at a certain scale a spreadsheet stops being a record-keeping tool and becomes a source of errors that cost real money.<\/p>\n
The case against Excel is not that it is old-fashioned. It breaks for specific mechanical reasons.<\/p>\n
The moment a file is emailed, there are two versions. Two people edit different copies, both convinced theirs is current. A week later nobody can say which one is right.<\/p>\n
Text can be typed into the amount column. “Tomorrow” can be typed into a date field. A phone number can be entered five different ways, and no filter afterwards will behave as expected.<\/p>\n
Someone deleted a row. When, who, why and what it contained is unknown. During a dispute with a client this turns into one person’s word against another’s.<\/p>\n
Either someone sees the whole file or nothing at all. Giving a sales rep access to their own orders while hiding margins and the supplier list is impossible in a spreadsheet.<\/p>\n
Not everyone needs a custom system. But if at least three of these apply, the spreadsheet is already costing you more than it appears.<\/p>\n
A custom panel is justified not because it is “nicer to use”. It closes specific gaps, each of which can be named.<\/p>\n
| Gap in the spreadsheet<\/th>\n | What the panel does<\/th>\n | What the business gets<\/th>\n<\/tr>\n<\/thead>\n | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Multiple file versions<\/td>\n | One database, browser access<\/td>\n | Everyone sees identical data<\/td>\n<\/tr>\n | |||||||||||||||||||||
| Data entered any which way<\/td>\n | Required fields, formats, reference lists<\/td>\n | Reports reconcile without manual cleanup<\/td>\n<\/tr>\n | |||||||||||||||||||||
| No record of who changed what<\/td>\n | Action log with user and timestamp<\/td>\n | Disputes close in a minute<\/td>\n<\/tr>\n | |||||||||||||||||||||
| All-or-nothing access<\/td>\n | Roles: rep, manager, accountant<\/td>\n | Sensitive data does not leak<\/td>\n<\/tr>\n | |||||||||||||||||||||
| Reports assembled by hand<\/td>\n | Prebuilt views and exports<\/td>\n | Decisions made the same day<\/td>\n<\/tr>\n | |||||||||||||||||||||
| Nothing connected to the website<\/td>\n | Leads land straight from forms<\/td>\n | No enquiry gets lost<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nOff-the-shelf CRM or a custom panel<\/h2>\nThe honest answer: in most cases you should start with something off the shelf. Custom development is justified when your process does not fit somebody else’s logic.<\/p>\n
|