For private equity — hitting plan without strengthening

the deck

Hitting plan, and paying more to convert it.

Working capital several million heavier than the plan cleanly explains; EBITDA still at plan.

Two and a half years into the hold, the company is delivering. Revenue is up, the value-creation plan is on track, the pricing program is through into phase two, the system implementation is on schedule, the new CRO is in role and the commercial team is performing. Service metrics are within range and customer escalations are down quarter over quarter. The CEO has reasons for everything in the deck and the reasons are reasonable.

Working capital is several million dollars heavier than the plan cleanly explains, and the deck still shows EBITDA at plan. The exception queue at customer service has grown for three quarters running. The driver mix in each recent margin reconstruction keeps shifting: freight one quarter, substitution cost the next, rebate realization the third, and the controller cannot put the same explanation against two consecutive periods. The add-backs in the bridge are each individually defensible and each tied to something the company is already fixing.

Every one of those signals has its own explanation, and each explanation holds on its own. None explains why the same burden keeps returning somewhere else.

the masks

Four initiatives, the same burden underneath.

Pricing, systems, leadership, and integration can each move real work while the operating burden remains.

This is not one company. Across operationally complex portfolio companies, the same rising cost keeps surfacing, and each time it surfaces it wears the name of whatever initiative is already in view.

In one company it presents as a pricing problem. The pricing program has been running six months, the dashboards report progress, and margin variance against the deal book has stabilized without narrowing. In another it presents as a system problem: the implementation is mid-flight, on its second consultancy, and the explanation is that the condition resolves once the system stabilizes. In a third it presents as a leadership problem. The new CRO is eight months in and highly competent, pipeline discipline has tightened and forecasting is cleaner, and the condition is unchanged. In a fourth it presents as integration runway. The add-on closed twelve months ago and the corporate consolidation is done, but the combined business still runs the acquired company’s pre-close commercial logic alongside the platform’s.

Different industries, different stages of hold, different management teams, and each remediation makes sense on its own. The cost keeps reappearing because it is being named by its nearest initiative, not by what is actually producing it. Every quarter spent waiting for that initiative to resolve the burden underneath is a quarter of a finite hold spent. The shape recurs.

the burden

Paid where the books are kept.

Carried through memory, exception, defensive inventory, and senior arbitration.

Under the four names is one operating fact. At the front of the order the company commits to a price, a lead time, a freight rate, and a set of customer and service rules, and those commitments have drifted out of fit with what the rest of the chain can carry cleanly to cash. The team absorbs the difference through memory, exception, defensive inventory, and senior arbitration. That difference is the burden underneath, and it rises as volume, account variation, channels, and exceptions add combinations the rules were never rebuilt to hold.

None of it is hidden. It shows up everywhere: as freight on one order, as a rebate that does not realize against the final mix, as an add-back in the bridge. What it never shows up as is the one condition producing all of them, which is why the books read as met while the conversion gets more expensive. Revenue converts, but too much of the conversion into clean EBITDA and cash is paid after the fact, where the books are actually kept: in margin, working capital, and senior bandwidth.

Tightening the sales process, replacing the system, replacing the CRO, extending the integration runway: none of those touches what has drifted. The full case is on The Premise.

the field

Nothing is waiting for a clean restart.

The CRO defended in two board cycles; the system on its second consultancy.

The condition shows up mid-hold, inside a field where everything is already in motion. The pricing program is running, the system implementation is six months in, the new CRO has been defended in two board cycles, the add-on integration has been called operational, and the annual plan already assumes the initiatives will produce what the investment case needs. Nothing is waiting for a clean restart.

The governance calendar is already built around those initiatives. The CEO has a value-creation plan they are accountable to, the board has seen the same initiatives for several quarters, and the GP holds expectations on a rhythm the company does not control. The operating partner is reading this company alongside others at different stages of hold, each with its own board cycle and management team and version of the same pressure. Engagement has to begin inside that field, not by clearing it.

The commitments around those initiatives make a clean restart costly. The pricing program cannot be dismissed without making the last two board cycles harder to explain. The system cannot be restarted without turning a delivery problem into a governance problem. The CRO cannot be second-guessed without adding an issue to the CEO’s calendar, and the add-on cannot stay “still integrating” without weakening the synergy story the company has been telling. None of this is anyone behaving badly. The commitments are rational, and the cost of unwinding them is governance cost, not only project cost. So the company keeps carrying it.

Each quarter the working capital base resets a little higher and more routine decisions reach senior leadership. Each quarter the bridge carries another round of add-backs, individually defensible and collectively recurring, and customer-specific exception handling teaches the customer what the business can be pushed to absorb next time. The company does not break. It takes more capital and senior time to hold its shape, and the unit of time is months.

Years are not available.

So any engagement has to fit inside the motion already there: the value-creation plan, the active initiatives, the CEO’s authority, the operating team’s actual capacity. It has to address the condition without requiring the company to stop being managed.

the rebuild

Proof is a workaround retiring, not an initiative added.

Proof appears when the same burden stops recurring in the data the operating cycle already reads.

Engagement runs alongside what is already in motion. The pricing program, the system implementation, the new CRO, the add-on integration: none of it stops. The work happens beneath them, in the rules behind what the business commits to, so the burden underneath growth can be seen, changed, and reduced without stopping the initiatives already in flight.

In a mid-hold company with a value-creation plan in flight, the engagement reads what the plan needs to run on, rebuilds the rules where they have drifted, and installs the rebuild alongside the active initiatives. The initiatives ship into a layer that can carry them. In a recently acquired add-on still running pre-close commercial logic in parallel with the platform’s, the engagement decides which logic the combined business actually operates on, and installs that decision rather than extending the runway again. Where a company is being readied for closer reading, the engagement retires the compensating work that will not hold under diligence: the senior arbitration doing what workflow should do, the customer rules living in memory, the price file drifted from what the system carries.

Across several companies in the same portfolio, the same shape may be appearing for different local reasons. The first question is not which company has the most severe condition. It is which company has the condition that can actually be changed inside the time available, and where engagement would matter most against the value at stake.

The unit of time is months, and the work produces changes in the data the operating cycle already reads, with no new reporting apparatus to stand up. The engagement is with leadership, not around it: what changes is the operating logic the CEO is asking the company to run on, not the CEO’s role in running it, and the engagement is not the operating partner’s enforcement arm.

Proof is not another initiative added to the plan. Proof is that the same burden stops scaling under new volume, new accounts, new channels, or add-on complexity: margin variance narrows, working-capital drag becomes explainable, chosen, or reduced, and the exception load stops recurring under new names.

The workaround retires.

the read

The most useful first conversation has a company in it.

A portfolio company where the plan is moving and the cost of converting growth is visible enough to test.

An add-on called integrated, while inherited pricing, supplier terms, customer rules, and branch practices still run underneath the combined business. A portfolio company where the value-creation plan is moving and the cost of converting that growth is visible enough to test. A company where working capital, margin, and senior escalation keep being explained through different stories. A group of companies where the same shape appears often enough that the operating partner wants to know which one is actually addressable.

The first conversation is not a diagnostic engagement. It is a read, on whether the condition is one the firm can engage, whether the company is in a moment where engagement would matter, and whether the scope can fit inside the environment already in motion. The firm qualifies itself on the same constraints the field sets. The company does not need a finished scope before that conversation. It needs a specific situation.

Some conversations are NDA-ready from the start, which is usually right when the substance depends on a named company, a current initiative, a management team, or an add-on still being integrated. What does not open the conversation well is a generic introduction without a company in view, an RFP against a predefined scope, or a procurement process looking for comparable bids. The work is too specific for that.

When the situation fits, the next scope is small and specific: the company, the operating signature, the decisions producing it, and the proof that would show whether the work changed anything. When it does not fit, the conversation closes there.

The threshold is direct. An email to the principal: consult@davelloandco.com.

The rest of the site is there for the operating partner who wants to read further first. The Premise carries the full argument, The Work describes how the firm engages, The Firm describes the shape of the practice, and Field Notes follows specific patterns in more detail.