Your Revenue Is Growing. So Why Does It Feel Like You're Losing Ground?
I once spent a Christmas break at Toronto Realty Group pulling client data that nobody had asked me to pull.
I’m a party animal, I know.
The brokerage was healthy by every measure leadership looked at regularly: agent success was on the rise, transaction volume was up, and the marketing I was running was producing some of the strongest performance metrics in the industry. But something about the shape of the business had been nagging at me for weeks, and I could not put words to it until I started looking at numbers that were not in any of the reports we reviewed as a team. What I found was that the company was quietly replacing clients faster than it was keeping them. There were a variety of reasons from the agents having gone cold, to leads who had shown early interest and then vanished without explanation, or relationships that had drifted off without generating a single complaint or escalation. None of that had a formal home in the reporting structure. It existed in fragments, usually as a name cursorily mentioned in a Monday morning meeting, so the information was there, distributed across people and systems, but it had never been assembled into anything a decision-maker could look at and use.
The information that would fundamentally change the meaning of that upward line is living somewhere else, and nobody has built the infrastructure to connect it all.
That experience clarified a pattern I have seen repeated across nearly every founder-led company I have met with.
There are two important meetings that happen in most growing companies throughout any given month, and they almost never talk to each other. The first is the Monday morning (or weekly) team check-in, where, among a list of wins and project updates, someone mentions that a long-standing client did not renew, or went quiet, or finally confirmed they were moving on. The information is noted, maybe briefly discussed, and the meeting moves forward. The second is the monthly revenue review with leadership, where the line on the chart is still going up and the mood in the room reflects it. Nobody in either meeting is hiding anything or acting negligently, but the information that would fundamentally change the meaning of that upward line is living somewhere else, and nobody has built the infrastructure to connect it all.
In 1996, the sociologist Diane Vaughan published an analysis of the Challenger space shuttle disaster that introduced a concept she called the “normalization of deviance.” Her research demonstrated that the O-ring erosion which ultimately caused the explosion had been observed on multiple previous shuttle flights, but because each instance occurred without catastrophic failure, the anomaly was gradually reclassified. Initially it was a concern, then as a known risk, then, eventually, an acceptable condition of flight. The technical deviation became, through repetition and the absence of immediate consequences, part of the expected baseline. Vaughan's central insight was not that NASA was negligent or that individuals had failed to do their jobs, but that the organization's structure made it rational for intelligent, well-intentioned people to accept gradually worsening conditions as normal, because the information systems that would have forced a reckoning were not connected to the rooms where decisions were being made.
The organization's structure made it rational for intelligent, well-intentioned people to accept gradually worsening conditions as normal.
The parallel to client retention in a growing company is nearly identical. A company loses a client in Q1 and there is a reasonable explanation of budget constraints, shifting needs, or an imperfect fit. The next quarter, two more leave, each with a plausible story attached. The revenue review still shows growth, because new clients are arriving faster than old ones are departing, and each individual departure is explicable on its own terms. The churn rate rises quarter by quarter, and by the time it becomes visible in the revenue figures, it has been normalizing inside the organization for a year or more. Revenue growth, after all, is a net figure. A company adding thirty new clients per quarter while losing twenty is spending its acquisition budget to run in place, because every departed client requires re-spending on someone who might have stayed if the conditions had been right. Frederick Reichheld's research for the Harvard Business Review demonstrated that a five percent increase in customer retention produces profit increases ranging from twenty-five to ninety-five percent depending on the industry, and subsequent work by Bain and Company found that acquiring a new client costs five to twenty-five times more than retaining an existing one. These findings have been cited for over three decades. Vaughan's framework, however, helps explain why they so rarely change anything: the economics only become actionable when the organizational structure forces the relevant information into the rooms where resource decisions are being made.
The version of this I encounter most often in founder-led companies is smaller in scale but identical in mechanics. Very little is written down, so the client relationship lives in the memory of whoever handled the onboarding call. The early warning signs of a client at risk, such as declining login frequency, fewer support tickets, or a change in their primary contact, all exist somewhere in the organization but have never been formalized into something a system can flag. In the early years, the founder knew every client by name, understood their business, and could sense when something was off. That personal proximity was itself a retention system, and it worked so well that it left no trace of how it worked or what would replace it. By the time the company has grown past the point where the founder can maintain that proximity with every account, the habit of operating without retention infrastructure is already years old, and the revenue line has made the argument for building it feel academic.
That personal proximity was itself a retention system, and it worked so well that it left no trace of how it worked or what would replace it.
The work is in building what should have been there earlier: a definition of what a healthy client relationship looks like in measurable terms, a system that flags deviation from that baseline before the client has mentally moved on, and a reporting structure that connects retention data to revenue data so that the two meetings are finally reading from the same page. The goal is never to replace the founder's instinct for their clients, which in most cases remains genuinely valuable, but to rebuild the information environment around that instinct so that it remains reliable as the company scales past the conditions it was originally built for, and so that the pattern Vaughan identified (the slow, rational, invisible normalization of loss) has somewhere to become visible before it becomes expensive.
The number going up is the most persuasive argument in any room but what it is not telling you is usually worth more.
