A few years back I worked with a founder running a small import and distribution business. When he started out, it was just him, a sales rep, and a driver. They used WhatsApp for coordination, a shared Google Sheet for tracking orders, and a basic accounting app for invoices.
It worked. It was lean. Cost almost nothing.
Then business grew. He hired five more people, then five more. By the time I met him, fifteen people were sharing that same Google Sheet. Everyone editing the same tab. Color codes that made sense six months ago but nobody remembered anymore. A filter someone had left on two weeks prior. Orders going through WhatsApp threads so long that finding the original message required scrolling for three minutes.
The sheet didn't break. The team did.
Not because they were bad at their jobs. Because they were trying to run a fifteen-person business with tools built for three.
When the tool was the right call
This is the part nobody talks about: the original choices were correct.
At three people, a spreadsheet is the right tool. You don't need Salesforce for a team of three. You don't need a dedicated inventory system when one person can hold the entire stock in their head. WhatsApp is completely appropriate when coordination means two quick messages. The tools matched the scale.
That's important to say because the problem isn't that the founders made bad decisions early on. They made smart decisions for where they were. The problem is that they kept making the same decisions after the business changed shape.
The tools didn't grow. The business did.
The moment it turns
The frustrating thing about outgrowing a tool is that it doesn't announce itself. There's no error message. No moment where the spreadsheet opens and says "you have too many people for this." It just gets slower. Messier. More error-prone.
The first sign is usually workarounds. The team starts working around the tool rather than through it. Someone keeps a personal note because the shared sheet is too chaotic. Someone screenshots a WhatsApp message and sends it by email so it doesn't get buried. Someone builds a second spreadsheet to track the first one.
Workarounds become habits. Habits become process. And suddenly the workaround is the system — an informal, undocumented, invisible system that lives in people's heads and collapses the moment someone leaves the company.
By the time founders notice this happening, they've usually been living inside it for months.
What this actually looks like
I've seen this pattern repeat across different industries, different team sizes, different tools. The specifics change. The shape doesn't.
Excel for inventory works at a hundred SKUs. At two thousand SKUs across three warehouses with four people updating it simultaneously, it's a liability. Cells overwrite each other. Formulas break silently. The last accurate count was three weeks ago and nobody is certain which version of the file is current.
WhatsApp for team coordination works for three people. At fifteen, decisions get lost in scroll. A supplier confirms a delivery. Two hours later, the message is buried under fifty unrelated threads. The driver shows up at the wrong time. Nobody is at fault — the tool just wasn't designed to carry that weight.
A basic invoicing app works for ten clients. At eighty clients across four salespeople, you need something that knows who owns which account, what each client's payment terms are, and which invoices are thirty days overdue. A basic app knows none of that. So the salespeople build their own tracking. In a spreadsheet. Which loops back to the same problem.
The cost of staying
Most businesses already know when a tool has stopped working. The founders feel it. The team complains about it. There's a general awareness that "we should fix this eventually."
But migration feels expensive. Training feels disruptive. There's always a reason to wait: a busy quarter, a new hire who hasn't settled in, a client project that takes priority. "We'll sort it out after the summer." Summer becomes December. December becomes next year.
And in the meantime, the cost accumulates — not as a line item on an invoice, but as time lost to manual work and decisions made on stale data.
Think about it this way. If two people each spend forty-five minutes a day on manual reconciliation that a proper system would eliminate, that's ninety minutes a day, seven and a half hours a week, thirty hours a month. What are those thirty hours worth? What would your team do with those thirty hours instead?
That's the real cost of staying. It's invisible because it's denominated in time rather than money — but it's real, and it compounds.
Outdated tools don't usually cause one big, visible failure. They cause a hundred small, invisible ones — every day, quietly, until the business hits a ceiling it can't explain.
There's another cost too: the people you hire to manage the tool instead of doing the actual work. When a system can't handle volume, businesses often respond by adding headcount. Another person to update the sheet. Another person to chase approvals through WhatsApp. Another person to reconcile the numbers that don't match. You're paying salaries to compensate for software that should cost a fraction of that to fix.
When to ask the question
The question isn't "Is this tool broken?" Broken things are obvious. The question is: Can this tool grow with us?
Ask it now. Not after the next hire. Not after the next product line. Not after the client base doubles and the team is already in pain. Ask it before the growth happens, because the time to change a tool is when things are working — not when they're failing.
If the answer is no — or even "I'm not sure" — that's already your answer. Uncertainty about whether a tool can handle your next stage of growth is a flag. It means the evaluation hasn't happened, which means you're running a business on infrastructure you haven't assessed.
That's not reckless. It's common. Almost every founder I've worked with has done it. But it's also fixable — usually faster and cheaper than people assume, once someone actually sits down and maps what's needed against what exists.
The man sitting on the chair in an empty plaza isn't wrong to be sitting. He just hasn't noticed yet that everyone else already moved on.
