# From WhatsApp and Spreadsheets to an Operating System ## How operations-heavy businesses outgrow the tools they started on > Every operations business runs on a stack nobody designed: WhatsApp for inquiries, paper for the floor, Excel for occupancy, Tally for invoices. What it costs, and what replacing it actually requires. Source: https://mrova.rocks/blog/whatsapp-to-operating-system Published: 2026-06-25 Author: Sunny Luthra · mRova (https://mrova.rocks) Tags: Product, Operations, Vertical SaaS --- Ask the owner of a boarding facility, a clinic, or a small logistics operation what software they run on and you will usually get a shrug. The honest answer is a list: WhatsApp for inquiries, a paper register at the door, an Excel sheet for occupancy, and Tally or QuickBooks for invoices at month end. Nobody chose that stack. It accumulated. And each piece of it, on its own, is a defensible choice — which is exactly why it survives long past the point where it is costing real money. ## The cost does not appear on any invoice This is the part that keeps the stack in place. WhatsApp has no licence fee. Paper registers cost nothing. Excel is already paid for. On a spreadsheet of business expenses, the stack looks free. The cost is hours. When we mapped this for Indian dog boarding facilities before building [Bos.Dog](https://bos.dog), owners were losing **around three hours a day** to WhatsApp replies alone — the same questions about availability, pricing and vaccination requirements, answered by hand, one conversation at a time, with no record afterwards that could be searched or counted. Three hours a day is most of a full-time role. It never appears as one, because it is distributed across every hour of the owner's day in two-minute increments. The second cost is invisibility. A WhatsApp thread is not a record. You cannot ask it how many inquiries converted last month, which weeks run at capacity, or which customer has not been invoiced. The data exists; it is just scattered across a medium that cannot answer questions. ## The market has already moved This is not a contrarian observation any more. [60% of small businesses now run daily operations on vertical SaaS platforms, and 89% of executives and IT leaders describe vertical SaaS as the sector's future](https://qubit.capital/blog/rise-vertical-saas-sector-specific-opportunities). The structural reason is retention: a product that handles scheduling, invoicing, dispatch and payments stops being a tool and becomes infrastructure. Nobody churns off infrastructure casually. The opportunities that remain are, almost by definition, the workflows still running on spreadsheets and chat threads. That is where the pattern below applies. ## What replacement actually requires The naive version of this project is a database with forms over it. That version fails, reliably, for reasons that have nothing to do with engineering quality. ### It has to be faster than WhatsApp on the first day An owner comparing your product to WhatsApp is not comparing feature lists. They are comparing the time to answer one inquiry. If your booking flow takes longer than typing a reply, the stack wins — and you do not get a second evaluation. This is why inquiry handling, not invoicing, is usually the right first surface. Invoicing hurts once a month. Inquiries hurt hourly, so that is where the relief is felt immediately. ### It has to work for the person on the floor, not the person who bought it The buyer is the owner. The user is a caretaker with wet hands, standing in a kennel, holding a phone in one hand. Those are different people with different requirements, and building for the buyer produces software the floor quietly abandons. Concretely, for Bos.Dog that meant tap-based logging rather than typed notes: meals, walks and mood recorded in one thumb press. A text field would have been faster to build and would have gone unused. ### It has to speak the local regulatory dialect Generic tools lose on the last mile. In India that means GST-compliant invoicing and UPI-native billing, rupee pricing and IST timestamps — not as settings, but as defaults. A product that makes an Indian facility convert currencies or hand-adjust tax fields has handed the work back. This is the durable advantage of vertical over horizontal software. A horizontal invoicing tool can add a GST field. It cannot make GST the assumption without breaking everyone else. ### It has to replace the whole stack, not one layer Partial replacement is worse than none. If bookings live in the product but check-ins stay on paper, staff now maintain two systems and reconcile them by hand. The migration only pays off at the point where the last spreadsheet closes. ## The part nobody plans for The output that mattered most for Bos.Dog was not a feature we scoped at the start. It was the checkout report card: an automatically generated, branded summary of the dog's stay — meals, walks, photos — that parents post to Instagram without being asked. That turned a back-office operations tool into a customer acquisition channel. A product built to save the owner three hours a day also produced organic referrals, which was never the pitch. The general lesson: in operations software, the record you create for internal reasons is often worth more pointed outward. You are already capturing what happened. Presenting it to the customer costs almost nothing and changes what the product is for. ## Where to start If you run an operations business on a stack like this, the diagnostic is simple. For one week, count the things you type more than once. Not the tasks you dislike — the ones you repeat. That count is the business case. Everything else is implementation. We build these systems for clients, and we run our own — [Bos.Dog](https://bos.dog) is ours, which means we carry the support burden rather than handing it over at launch. If you are looking at this migration, the next step is a conversation about what your week actually looks like. --- ## Frequently asked questions ### What is vertical SaaS? Software built for one industry's specific workflow rather than a general capability sold to everyone. A scheduling tool anyone can use is horizontal; a boarding management system that understands vaccination records and kennel capacity is vertical. ### Why do operations businesses stay on WhatsApp so long? Because it works, right up until it doesn't. WhatsApp has no adoption cost, no training and no licence fee. The cost is hours of manual re-entry and lost history, which never appears on an invoice and so never gets budgeted against. ### What should replace the stack first? The layer generating the most repeated manual work, which is usually inquiry handling rather than invoicing. Invoicing is painful monthly; inquiries are painful hourly.