The Problem Is Not Using Excel or WhatsApp
A business does not need to replace a tool simply because it has grown. If Excel continues to provide reliable information, the process has a clear owner, and WhatsApp is used only as a communication channel, there is no technical reason to migrate for the sake of migrating.
The sign that matters shows up when the process starts depending on manual work to keep several sources of information in sync, when nobody knows for certain which data is correct, or when reconstructing what happened means digging through files, emails, and conversations.
At that point it is worth reviewing the process. The solution might be a targeted automation, better configuration of existing tools, an ERP or CRM, or a specific system. Custom software is only one of those possibilities.
Why Excel Stops Being Enough (And It Is Not Because of Row Limits)
Excel has a real technical limit of 1,048,576 rows per sheet (Microsoft Support — Excel specifications and limits). But for most businesses that is not the limit that matters.
It is also not accurate to say that modern Excel does not allow multiple people to work on the same file. When the workbook is stored on OneDrive or SharePoint and compatible versions of Microsoft 365 are used, Excel enables real-time co-authoring, version history, and review of changes made (Microsoft Support — Show changes that were made in a workbook).
The problem emerges elsewhere: when a spreadsheet stops being an analysis tool and starts functioning as the central system where different areas manage orders, inventory, customers, approvals, and operational statuses.
An extreme example occurred in 2020: Public Health England confirmed that 15,841 positive COVID-19 cases were temporarily excluded from daily reports due to a technical issue in the automated process that transferred laboratory results to their reporting systems (official statement, GOV.UK). Later reports attributed the incident to the format of Excel files used and their size limits. The case doesn’t prove Excel is a bad tool. It shows the risk of turning a spreadsheet, or a file used to move data around, into a critical piece of a process it was never designed for.
At that point, the question is no longer how many rows Excel supports or how many people can open it. The question is how much your operation depends on everyone entering information correctly, following the same rules, and understanding the process they need to follow.
Academic research on spreadsheets shows that errors are frequent in complex operational models, although the rates found vary considerably depending on the type of spreadsheet, the audit methodology, and the definition of “error” — there is no reliable universal percentage that allows us to claim that a certain proportion of all business spreadsheets contain errors (review of academic literature on spreadsheets).
Excel is still an excellent tool for analysis, calculations, and reports. A business that needs to centralize a process doesn’t have to abandon Excel entirely.
Operational Signs That Manual Management Has Stopped Working
Here they are, plainly:
Multiple people edit the same spreadsheet for different tasks. If sales, administration, and warehouse staff all edit the same inventory or order file with no clear rule about who updates what and when, you raise the odds of contradictory data, or of different teams working from different versions of it.
Nobody can answer a business question without building a report by hand. If answering “How much did we bill this month, by customer?” or “What’s our actual inventory?” means someone has to cross-reference three spreadsheets, you have already lost visibility. The problem isn’t a missing report; it’s that the information is scattered.
The team spends hours each week reconciling data between systems. Copying and pasting information between Excel, WhatsApp, email, and some isolated system so everything “says the same thing” is work that adds no value and that grows with each new customer or order.
There is no universal number of signs at which a business needs to change systems. What matters is whether these problems appear repeatedly, affect critical information, or increase as the operation grows.
Diagnostic Table
| Sign | What It Indicates | Before Changing Tools |
|---|---|---|
| Multiple versions of the same data exist | There is no clearly defined source of truth | Review where the original data should live |
| Reports require manual cross-referencing | Information is fragmented | Identify which systems should be integrated |
| Information is copied between tools | There is repetitive work and risk of inconsistencies | Evaluate an automation before replacing systems |
| Important decisions remain only in chats | Traceability is missing within the process | Decide which decisions have to be recorded in a structured way |
| The process depends on one person who “knows how it works” | The operational knowledge isn’t written down anywhere | Document the process first |
This table is a guide for diagnosis, not an automated test that determines by itself whether you need a new system.
The Risks of Using WhatsApp as a Management Channel
WhatsApp solves a real problem: it is fast, everyone has it, and it requires no training. The limit shows up when it stops being a communication channel and becomes, in practice, the place where business decisions get made and stored.
Traceability depends on the decision being incorporated into the process, not on the chat “disappearing.” The problem is not that WhatsApp automatically deletes a decision when someone changes phones — the app supports linked devices and backups. The risk appears when the only record of an approval, instruction, or agreement exists within a conversation tied to specific people or devices and the company never brings that record into its own management process.
A chat is not equivalent to a corporate traceability system. Depending on the solution used (WhatsApp Business, WhatsApp Business Platform with integrations), enterprise tools, additional storage, and compliance mechanisms may exist — but that takes deliberate design; it doesn’t come free with using WhatsApp as a channel.
End-to-end encryption protects the content of messages between conversation participants (WhatsApp official documentation on E2E encryption), but it does not eliminate risks at the endpoints: a compromised device, phishing, screenshots, unauthorized access, or information that remains on a personal phone.
The risk of depending on unauthorized channels for communications that should be preserved can be seen in the U.S. financial sector. JPMorgan agreed to penalties of USD 125 million with the SEC and USD 75 million with the CFTC for failures in record retention and supervision related, among other channels, to WhatsApp and messages on personal devices (SEC, CFTC). Goldman Sachs subsequently received equivalent penalties of USD 125 million from the SEC and USD 75 million from the CFTC in similar actions (SEC, CFTC). Together, those actions add up to USD 400 million across the two firms.
These cases involve U.S. financial entities subject to specific record retention obligations. That doesn’t make WhatsApp illegal for any business, and it doesn’t mean the same obligations automatically apply in other countries or sectors. It does show that failing to control where business information lives is not a theoretical risk, even for firms with enormous legal resources.
WhatsApp is still fine for quick coordination. The limit is when it becomes the only record of something you later need to look up, audit, or defend.
What to Do After Detecting These Signs
When these signs accumulate, the most common mistake isn’t moving too slowly. It’s jumping straight to installing a system without first sorting out the process that system is supposed to automate. Replacing a broken process with its digital version only produces a more expensive replica of the same problem.
What works in practice is to pin down exactly what information gets lost, duplicated, or delayed today, and only then decide which tool fixes it. Sometimes that’s a targeted automation between the systems you already use; sometimes it’s a new system. You can see how we approach that first step in automations and integrations.
Once the need is identified, the next decision — build something custom or adopt an existing tool — depends on how much your process resembles market standards. We cover that analysis in when a business needs custom software (and when it does not).