The real cost of running your business across 17 browser tabs.

We did a count with a client last year. At any given time, their operations manager had: Tally open in one tab, their bank portal in two tabs (current account and OD), their CRM in a third, a Google Sheet for the dispatch plan, a WhatsApp Web window, two email threads, a supplier's portal, and a shared Excel file for the daily production report. Seventeen tabs. None of them talking to each other.

The costs you can see

The costs you can't see

Context-switching kills deep work. Every time someone moves from the dispatch sheet to WhatsApp to Tally and back, there's a cognitive re-entry cost — about 23 minutes to fully re-engage with the original task, according to research. For an operations manager doing this 10–15 times a day, that's not 10 minutes of lost time. It's the difference between reactive firefighting and proactive management.

Stale data means bad decisions. If your stock position in the shared Google Sheet is updated manually every evening, and someone places a large order at 3 PM, they're committing to delivery on the basis of stock numbers that are 19 hours old. This is how overcommitment, stockouts, and customer complaints happen — not from bad intent, but from data architecture.

The fix isn't 'one system to rule them all'

The instinct is to buy an ERP. One system. Everything in one place. In practice, this rarely works for MSMEs — ERPs are expensive, slow to implement, and designed for processes more standardised than yours. The better fix is a data layer: keep your existing systems, but build a single read surface that pulls from all of them and shows the right data to the right person in the right context.

• Operations manager sees: live stock, today's dispatch plan, pending POs
• Sales manager sees: open quotes, pipeline by stage, overdue follow-ups
• Finance team sees: outstanding invoices, cash position, GST liability
• MD sees: the 6 headline numbers and 3 items that need attention today