- Faten Bazzi & Jacqueline N. Hernandez
The most expensive operating failures inside portfolio companies do not announce themselves.
They accumulate.
By the time a sponsor sees the cost in the financial reporting, the operating leakage that produced it has been compounding for two to four quarters, sometimes longer.
The bridge is broken before the bridge analysis flags it.
- § 01 THE OPERATING REALITY
Value does not erode in dramatic events.
This is the central operating reality of every hold period. Value does not erode in dramatic, identifiable events.
It erodes through execution drag, the slow, structural friction that prevents the operating thesis from converting into earned outcomes inside the business. Execution drag is what happens when the strategy is right, the team is competent, the market is real, and the value creation plan still misses by twelve to fifteen percent. The work was done. The work did not compound the way the model said it would.
The institutional misreading of this pattern is what produces most of the value destruction Fulcrum encounters in mid-market portfolio companies. Sponsors look at the financial trajectory and diagnose a financial problem. They reach for financial instruments. The financial instruments do not work, because the problem was never financial. It was operational, three quarters earlier, when no one was looking at the operating layer because the financials still read green.
This is the operating layer the value creation thesis sits on. When it drags, everything above it drags too.
- § 02 THE Pattern
What execution drag actually looks like.
Execution drag is not a single condition. It is a pattern of operating friction that develops below the visibility threshold of conventional sponsor reporting. The patterns are recognizable to any operator who has spent meaningful time inside a sponsor-backed company. They show up at the same operating level whether the business is industrial, software, healthcare services, or consumer.
Decisions slow. A question that should resolve inside one meeting consumes three. A capital allocation conversation that should close in a week stretches across the month. The decision velocity of the executive team collapses, and the team does not notice because the calendar still fills up.
Work duplicates. Two functional leads each interpret the same operating priority differently, run separate workstreams against it, and arrive at conflicting recommendations. The CEO arbitrates. The arbitration takes time the CEO does not have. The next initiative starts the same way.
Meetings replace decisions. The operating cadence drifts from accountability rhythm into status theater. The same questions get asked across three weeks of standing meetings. Nothing closes. The executive team is exhausted and the operating partner cannot point to a single resolved decision inside the quarter.
Accountability blurs. Two executives believe they own the same outcome. Both report on it. Neither delivers on it. When the outcome misses, both can defensibly explain why the miss was not theirs. The CEO has no clean way to drive accountability without restructuring the decision rights, which the CEO does not have time to do, because the operating cadence is already broken.
Implementation stalls. An initiative gets approved in the operating review, assigned to a functional owner, and never quite installs. The functional owner is waiting on three inputs from three other functions. None of those inputs are scheduled. None of them are tracked. The initiative is reported as in progress for nine consecutive months.
Escalation becomes the only working mechanism. Every meaningful operating question routes to the CEO because no one else has the authority to close it. The CEO becomes the operating bottleneck for the entire business. The CEO knows this and cannot fix it without slowing down further.
Communication fragments. Internal messages cross between leadership, operations, the commercial team, and external partners through inconsistent channels. The same information arrives in different forms at different times. Vendors and customers experience the company as inconsistent, different answers from different people in the same week.
None of these conditions are individually catastrophic. They are individually annoying. Together, across two or three quarters, they compound into the financial pattern sponsors recognize too late.
◆ The strategy was right. The team was competent. The market was real. The value creation plan still missed by twelve to fifteen percent. The work was done. The work did not compound the way the model said it would.
FULCRUM · OPERATING PARTNERS
- § 03 THE Diagnostic Failure
Why most companies misdiagnose the problem.
The diagnostic failure is structural. When the financial pattern surfaces, the most available explanation is always functional. Revenue softens, the diagnosis is a sales problem. Pipeline slows, the diagnosis is a marketing problem. Margins compress, the diagnosis is a pricing problem. Top performers leave, the diagnosis is a hiring problem.
Each of these functional explanations is locally credible. Each of them is also wrong, or at least incomplete. The functional symptom is real. The functional layer is not where the cause lives.
Execution drag is an architectural failure. The operating architecture of the company, its decision rights, its accountability structure, its communication cadence, its installed systems, is no longer capable of converting effort into outcome at the rate the value creation plan assumes. The functional teams are working as hard as they have ever worked. The architecture above them is dropping output on the floor.
This is the reason traditional consulting interventions often produce decks but not durable change. The deck addresses the functional symptom. The architecture remains unchanged. Six months later, the symptom returns in a different functional area, because the architecture is still leaking the same way it was leaking before the consultants arrived.
Fulcrum’s diagnostic posture inverts the standard sequence. We do not begin with the functional symptom. We begin with the operating architecture and ask whether it can plausibly produce the outcomes the plan requires. In nearly every diagnostic engagement we run, the answer is no, and the reason the answer is no is structural, not functional. The architecture has not been deliberately built. It has been inherited from a smaller version of the company that no longer exists.
When sponsors and operating partners arrive at this diagnosis on their own, they tend to arrive late. The architecture problem becomes visible only when the functional fixes have already been tried and have not worked. By that point, two to four quarters of hold time have already been spent on the wrong intervention.
- § 04 THE Financial Geometry
How execution drag becomes EBITDA leakage.
The translation from operating drag to financial impact is direct, even when sponsors do not see it that way in the moment. Every category of execution drag produces a corresponding financial signature. The signatures are diffuse enough that no single one explains the whole picture. Together, they explain almost all of it.
- ◆ THE FIVE FINANCIAL SIGNATURES
01 Margin compresses quietly. Pricing decisions get deferred. Procurement consolidation stalls. Working capital initiatives lose their sponsor inside the company. The cumulative compression is one to four hundred basis points of annual margin, a number that shows up in the QofE as a multi-year trend the seller cannot defend.
02 Management attention erodes. The executive team spends sixty to seventy percent of its time on operational rework, escalation, and rearbitration of decisions that should have been closed weeks earlier. That time is not being spent on the growth initiatives the thesis depends on.
03 Customer experience drifts. The inconsistency between functions reaches the customer through inconsistent communication, variable response times, and uneven service quality. Churn ticks up. Net revenue retention softens.
04 Reporting becomes unreliable. The operating cadence has decayed enough that the monthly board pack reflects what the team can assemble, not what the business actually did. Variances between reported numbers and audited numbers grow. Trust between sponsor and management deteriorates.
05 Transaction readiness collapses. The exit window arrives with operating posture that cannot defend itself through diligence. The QofE surfaces normalization issues that should have been cleaned up two years earlier. The buyer adjusts the multiple. The exit closes at eighty to ninety cents on the modeled dollar.
This is the financial geometry of operating drag inside a hold period. Margin compression, attention erosion, customer drift, reporting decay, and transaction readiness collapse, five financial signatures, all produced by the same architectural condition, all manifesting late.
- § 05 THE Growth Paradox
Why growth makes the problem worse.
Growth is the variable sponsors most reliably want to install on a portfolio company. Growth is also the variable that most reliably exposes operating drag.
Growth installed on unstable operating infrastructure compounds dysfunction faster than revenue. This is the operating principle most often misunderstood at the sponsor level. The investment thesis treats growth as the engine of value creation. Inside the company, growth is also the stress test that surfaces every weakness in the operating architecture beneath it.
A company at thirty million in revenue can operate on personal involvement, informal communication, and shared context between the founders or executives who built it. The systems are weak but the volume is low enough that they work. Decisions happen in hallways. Accountability is interpersonal. Information moves through the people who happen to be in the same room.
A company at one hundred million in revenue cannot operate that way and continue to function. The volume of decisions, the breadth of geography, the number of people who need information, and the speed of execution required to compete all exceed the personal-involvement model that worked at thirty million. The systems that did not need to be formal at the lower volume have to be formal at the higher one. They almost never are. They have not been built deliberately because they did not need to be built when the company was smaller.
THE GROWTH PARADOX
The result is a paradox sponsors encounter constantly. The company that grew through founder energy and informal coordination cannot continue to grow through the same mechanism. The mechanism that produced the success is also the mechanism that prevents the next stage of it. Growth amplifies the operating fragility instead of overwhelming it.
Founder dependency is a particular instance of this pattern. The founder is the operating glue holding the company together. The founder is also the operating ceiling on what the company can become.
When the sponsor underwrites growth, the underwriting implicitly assumes the founder can scale the way the company can scale. That assumption is almost never tested in diligence. By year two of the hold, it begins to fail. By year three, the founder is the constraint the sponsor cannot resolve without restructuring the leadership architecture, which usually requires conversations the sponsor postponed in year one because the founder was producing results.
Operating fragility scales the same way revenue scales. Faster, in many cases, because the operating architecture compounds friction multiplicatively while revenue compounds additively. By the time the sponsor recognizes the fragility, the growth has already installed three or four quarters of operational debt that has to be paid down before the next stage of growth can proceed.
This is the structural reason sophisticated operators sequence operating discipline ahead of growth, not in parallel with it. The discipline has to be installed at the operating level the company is heading toward, not the level it currently occupies. Otherwise, growth produces decay.
- § 06 THE Discipline
What sophisticated operators do differently.
The operators who consistently produce durable hold-period outcomes do four things differently from operators who do not. None of these are exotic. All of them are difficult.
First, they diagnose for architectural risk before they diagnose for functional risk. When they enter a portfolio company, they look at the decision-rights structure, the operating cadence, the accountability architecture, and the installed systems before they look at the sales pipeline, the pricing model, or the marketing funnel. The functional layer cannot produce outcomes the architectural layer cannot support. They establish the architectural baseline first.
Second, they install operating cadence as infrastructure, not as a meeting calendar. Operating cadence is not a weekly leadership meeting. It is a documented sequence of decision events, with named owners, defined inputs, and explicit close-out criteria. The cadence is what allows the executive team to convert intention into outcome on a predictable timeline. Without it, every initiative waits on someone’s calendar instead of someone’s accountability.
Third, they protect management attention as a scarce resource. The executive team has a fixed amount of cognitive bandwidth available for value creation work. Every operational rework, every escalation, every rearbitrated decision draws against that bandwidth. The sophisticated operator’s first job is to reduce the draw, by clarifying decision rights, by installing accountability discipline, by removing the structural friction that consumes executive attention without producing outcome. The reclaimed attention is what makes the value creation plan executable.
Fourth, they sequence the operating work to the hold period. The interventions installed in year one are different from the interventions installed in year three. Year one is for the operating floor, stabilizing the architecture, installing the cadence, resolving the decision-rights structure that the value creation plan needs to sit on. Year three is for the value-creation levers themselves, the two or three moves that move the multiple, executed by a team operating against the installed discipline. Year four is for transaction readiness, defending the EBITDA quality the operating discipline produced. The sequence matters. The sequence is the difference between durable compounding and operational debt.
Fulcrum’s operating methodology, Portfolio Value Architecture™, is built around this sequence. The framework runs in three phases: Frame, Floor, Focus. Frame diagnoses the architectural condition. Floor installs the operating infrastructure the architecture requires. Focus directs the resulting capacity to the value-creation levers the hold period rewards. The sequence is not a deliverable. It is an operating discipline installed inside the company for the duration of the engagement.
The firms that produce consistent results inside the hold period have something like this discipline running, whether they call it that or not. The firms that do not produce consistent results are the firms still treating operating intervention as a series of functional fixes, a sales restructuring here, a marketing recalibration there, an HR refresh somewhere else. Each functional fix solves a local symptom. None of them addresses the architecture that produced the symptom. The architecture continues to leak.
- § 07 THE Closing Position
Operating discipline is the load-bearing structure of EBITDA.
Most value destruction inside portfolio companies is operational before it is financial. By the time it appears in the financial reporting, the leakage has already compounded for two to four quarters, and the remediation window is narrower than the sponsor model assumes.
The discipline that prevents this is not exotic. It is the discipline of treating the operating layer as the infrastructure the value creation thesis sits on, rather than as the background condition the thesis happens against. Operating architecture is not a soft variable. It is the load-bearing structure of every dollar of EBITDA the company produces.
Sponsors who diagnose for architectural risk early, and who install operating discipline before they install growth, produce durable hold-period outcomes. Sponsors who diagnose for functional risk first and architectural risk later produce the pattern Fulcrum sees most often in our diagnostic engagements: a hold period spent on the wrong intervention, an exit that closes below thesis, and a value creation gap no one can quite explain because the explanation requires reading the operating layer that no one was watching.
Execution drag is the silent killer of enterprise value because the operating layer where it lives is invisible to the reporting layer where it surfaces. The work of sophisticated operators is to make that layer visible, and to install the discipline that closes the gap between intention and outcome before the gap reaches the bridge.
This is the operating work Fulcrum was built to do.
§ ENGAGE
If execution drag is compounding inside one of your holdings, the cost of waiting is measured in basis points on the multiple.
◆ The Authors
Jacqueline N. Hernandez & Faten Bazzi
CO-FOUNDERS · FULCRUM OPERATING PARTNERS
Jacqueline N. Hernandez directs Fulcrum’s strategy, positioning, and sponsor relationships. With two decades of operating leadership across revenue, executive alignment, and performance recalibration inside mid-market companies, she leads the firm’s Performance Recalibration and Leadership Alignment practices and authored the Frame phase of Portfolio Value Architecture™.
Faten Bazzi leads Fulcrum’s embedded operating practice. With 14 years of institutional embedded operator experience inside sponsor-backed and growth-stage companies, she runs the firm’s Portfolio Value Architecture and Pre-Exit Readiness engagements and co-authored the Floor and Focus phases of the methodology.