The WhatsApp-to-spreadsheet problem
Why so many businesses run on chat plus a sheet, what it quietly costs, and the smallest change that ends the retyping.
Walk into most small businesses in India and you will find the same operating system: enquiries arrive on WhatsApp, someone copies the important ones into a spreadsheet, quotes get written in a third place, and the follow-ups live in one person's head. It is not a failure of discipline. It is the most sensible thing available — right up to the point where it quietly becomes the most expensive.
Why this setup wins in the first place
It costs nothing. It works on the phone everyone already has. Customers prefer it, because they do not want to fill in a form and wait for an email. Staff learn it in zero minutes. No procurement, no training, no login. Any replacement that ignores those advantages deserves to fail, and most do.
What it costs once you are past about five people
The costs are real but hard to see, because none of them arrives as a bill.
- Re-entry. The same customer detail gets typed into the chat, the sheet, the quote and the invoice. Every retype is a chance to introduce a different phone number. Industry surveys on automation have put the share of workers spending at least a quarter of their week on manual, repetitive tasks above 40% (Smartsheet's automation survey); in a business running on chat and a sheet, you can usually see where that quarter goes.
- Enquiries that fall through. A message arrives at 9pm, gets read, does not get replied to, and slides up the thread. There is no list of open items, so nothing marks it as missed. Most businesses discover these only by accident, when the customer calls to say they went elsewhere.
- No history you can search. "What did we quote them last year?" means scrolling a chat. If that chat is on a departed employee's phone, the answer is gone.
- Single points of knowledge. Only one person knows which jobs are live, which payments are pending and what was promised. Their leave becomes an outage.
- No reporting worth the name. You can feel that enquiries are up. You cannot show it, split it by source, or decide where to spend.
For context on how widespread this is: estimates of digital maturity among India's roughly 64 million MSMEs have sat near 12% (RedSeer estimate, widely reported). The chat-plus-sheet pattern is not an edge case; it is the default.
The smallest change that works
The instinct is to replace WhatsApp. That is the wrong move — it is the channel your customers actually answer. The fix is to stop making the chat do a job it was never built for: being the record.
Keep WhatsApp as the front door, and put one shared record behind it. In practice that is three stages, and most businesses should stop after the first two for a while.
- Capture. Every enquiry lands in one place automatically, with who, when, what they asked, and which channel it came from. Nobody retypes anything. This alone ends most of the "we never saw that message" losses.
- Record. That item has a status, an owner and a history: quoted, waiting, won, lost. Anyone can open it. Nothing important lives only in a thread.
- Automate. Only now, and only on the steps you have watched for a month: an acknowledgement sent within a minute, follow-ups scheduled, a reply drafted from your own templates for the question you answer twenty times a week.
Three ways this goes wrong
- Ripping out WhatsApp. Customers do not migrate to your portal. They just stop replying.
- Buying a large CRM first. You end up paying per seat for ninety features to get the three you needed, and staff keep using the chat anyway because it is faster.
- Automating a broken process. If the follow-up rule is wrong by hand, automation makes it wrong faster and to more people. Watch the manual version for a month before you encode it.
How to tell whether it worked
Before you change anything, spend a week counting four things: enquiries received, enquiries replied to within an hour, how many times the same detail got typed twice, and how long it takes to answer "what is the status of this job?" out loud. Those four numbers are your baseline. A month after the change, count them again. If they have not moved, the tool did not help, whatever it cost.
What we would do
We walk one real job end to end with you — the exercise is written up in Before you build an internal tool, map one job end to end — and count the handoffs. Usually two of them account for most of the pain, and a small shared record fixes both. Internal tools of that size sit in the ₹20,000–₹1,00,000 band, and starting from a foundation we already run, like Navis or QuickFMS, brings that down rather than up.
If the honest answer is that a spreadsheet and a clearer habit would fix your problem, we will say so. It happens more often than you would expect from people who sell software.
More from the build
- Websites What a business website should do in its first 90 days Traffic is not the first goal. Enquiries are. What to put on the page, what to leave off, and how to tell whether it is working.
- AI search Google is no longer the only place people search Customers now ask ChatGPT and other assistants for recommendations. What makes a site readable to them, and why it overlaps with good SEO.
- Software Before you build an internal tool, map one job end to end Most failed internal software was scoped from an org chart instead of a job. One afternoon with a pen fixes that.
- AI What an AI pilot should cost, and how to tell if it worked Pick one repeated task, put a number against it before you start, and run it for a month. Everything else is a demo.