What “running by ear” actually costs a growing business

“It mostly works, we just have to stay on top of it” is the sound of a business running on memory instead of process. Here’s what that actually costs, and where it shows up first.

Every founder-led business we’ve worked with says some version of the same thing in the first call: “it mostly works, we just have to stay on top of it.” That sentence is doing a lot of quiet work. Translated, it means the business runs on a handful of people who carry the actual process in their heads, and the org chart is a polite fiction.

What it looks like from the inside

Running by ear rarely looks like chaos from the outside. Invoices go out, orders ship, tickets get answered. The tell isn’t visible output — it’s what happens the moment the usual person is unreachable. A few patterns show up almost every time:

  • The same three people get pinged for anything unusual, regardless of whose job it technically is.
  • Onboarding a new hire means shadowing someone for two weeks, not reading a document, because the document doesn’t exist or hasn’t been true since March.
  • Nobody can say with confidence what happens to a lead, an order, or a support request between the moment it arrives and the moment it’s resolved — only that it usually works out.
  • Every tool the business runs on was chosen and configured by one person, for reasons that made sense at the time and were never written down.

None of this is a character flaw. It’s what happens by default. A business under twenty people doesn’t need documented process to function — the founder is the process, present in enough decisions to keep everything coherent. The problem shows up on a lag: the business outgrows that model months before anyone notices, because everything still appears to work.

The costs, specifically

“You should really document things” is true but useless as advice — it doesn’t say what’s actually at stake. The costs of running by ear are concrete, and they compound quietly:

  • Bus factor. If the process lives in one person’s head, that person cannot take a real vacation, get sick, or leave without the business absorbing a shock proportional to how much they were quietly carrying.
  • Hiring drag. Every new hire has to be trained by a person instead of a system, which caps how fast the team can grow and makes each hire’s ramp-up unpredictable.
  • Invisible inconsistency. Without a written process, two people handling the “same” task will handle it differently, and nobody notices until a customer gets two different answers.
  • Decisions made from memory instead of data. If the numbers live in someone’s intuition rather than a system that can be queried, every strategic call is a guess dressed up as judgment.

The moment a business notices it’s running by ear is usually the moment it already has been for a year.

That lag is the dangerous part. Growth hides the problem because more revenue looks like more health, even while the underlying process gets more fragile with every person added on top of it.

What actually fixes it

The fix isn’t a personality change or a mandate to “be more organized.” It’s mapping where the business currently runs on memory, and replacing each of those spots with something that survives the person leaving the room: a written process, a system that enforces the process, or both. That’s the whole job — not adding process for its own sake, but finding the specific places where the business is one absence away from a bad week, and closing them one at a time.

Done well, nobody notices the day it happens. They notice six months later, when the person who used to field every question is on a plane, and the business doesn’t stop.

Ready when you are

Let’s take one thing off your plate.

A 30-minute call. We map one bottleneck and tell you honestly what it’d take to fix.