Revenue growth is the easiest part of scaling a company to celebrate and the hardest part to survive. Founders who hit their number rarely fail because demand dried up; they fail because the machine underneath the number was never designed to carry it. Cliff Carnes, Principal at BCC Group, a board member, and advisor who has led capital markets teams handling billions in annual transactions, frames the problem in terms most founders do not want to hear during a good quarter: the systems, processes, and team structure you built at 12 people determine whether 40 people function or fracture. “In today’s market, plenty of founders can grow revenue,” he says. “What often trips them up is the machine underneath, the systems, the processes, and the team structure that decide whether that growth holds together or starts to strain.” That distinction, between growth that compounds and growth that strains, is where most operating failures live.
Small Inefficiencies Do Not Stay Small
The most expensive assumption in a scaling business is that a process which works badly at current volume will work badly at the same rate later. It will not. Inefficiency is multiplicative, not additive, which is why a manual approval chain or an undocumented handoff that costs a few hours a week at one stage becomes a structural tax at the next. Carnes treats this as the first order of business, and he goes looking for it in the functions founders tend to leave alone. “When you’re expanding, small inefficiencies multiply fast,” he says. “I go into finance, HR, IT, and marketing and find where time and money leak out and put clean systems in place.”
The outcome he describes is worth reading carefully, because it inverts the standard response to strain. Most companies answer operational pressure by hiring, which converts a process problem into a payroll problem and buries the original defect under new salaries. Carnes argues the sequence runs the other way. “The result is lower costs and more capacity without adding headcount you don’t need yet,” he says. Capacity, in other words, is something you can manufacture from the systems you already own before you go to market. Founders who skip that step end up paying twice: once for the inefficiency and again for the people hired to absorb it.
Build The Structure Before The Volume Arrives
There is a timing problem at the center of operational readiness, and it is unforgiving. Infrastructure built in response to demand is always built under duress, with incomplete information and no room to test. Carnes is blunt about what growth does to a company: it does not create weaknesses, it reveals existing flaws. “Growth exposes whatever your infrastructure can’t handle,” he says. “I prepare the process, the roles, the structure ahead of the demand. So when the volume arrives, your team is built to absorb it rather than scramble to catch up.”
The word doing the work in that sentence is roles. Process and systems get most of the attention in scaling conversations because they are visible and easy to buy software for. Role design is harder, less satisfying, and more consequential, because ambiguity about who owns a decision does not surface until the decision is urgent. A company that has not defined ownership in advance discovers the gap at exactly the moment it can least afford a pause. The distinction Carnes draws between absorbing volume and scrambling to catch up is really a distinction between two kinds of organizations: one where growth is a load the structure was engineered for, and one where every increase in volume becomes a crisis requiring the founder’s personal attention.
Senior Operating Experience Without The Full-Time Premium
There is a well-known gap in the middle market where the need for a chief operating officer (COO) arrives long before the budget for one does. Carnes puts a size range on it. “Most companies in the 15 to 75 employee range feel the need for a COO long before they can justify a full-time one,” he says. That gap is usually filled by the founder, who absorbs operations on top of everything else and slowly becomes the bottleneck in their own company. The alternative – hiring a full-time operator early – forces a company to buy a seniority level it cannot yet keep busy, and the cost lands on the payroll before the value lands on the business.
The fractional model exists to solve that equation, and Carnes is direct about what it buys. “A fractional model gives you proven C-suite operating experience exactly when you need it, focused on your real problems,” he says. The operative phrase is real problems. Part-time senior capacity only works when it is aimed at specific structural defects rather than spread thinly across a general management remit. Applied that way, it functions less like a discounted executive and more like targeted intervention at the points where the company is most likely to break. The underlying logic of the whole argument is a claim about where founder attention belongs. “Founders should be spending their energy on revenue and vision,” Carnes says. “The operations should run so smoothly they barely think about them.” Operations that demand executive attention are, by his standard, already failing. The test of good infrastructure is that nobody at the top has to look at it.
Follow Cliff Carnes on LinkedIn for more insights on operational infrastructure, scaling readiness, and fractional executive leadership.
