When operational execution is priced into the capital stack

The separation is conventional. Capital gets raised. A developer gets hired. A building, a platform, or a portfolio gets delivered. At a date on the plan, an operator picks up the asset and runs it.

Each of these parties optimises locally. The raise is structured against a projected model. The build is structured against a fixed scope. The operator is structured against whatever lands on opening day. Handoffs happen at the boundaries, and the standard phrase for what happens at those handoffs is “transition.” Transition is assumed to be an operational matter, separately budgeted, rarely given board-level attention.

This is where capital gets eroded or preserved, in consistent and diagnosable ways.

The three common failure modes at handoff

Vendor inheritance. The developer has selected vendors that were right for the build phase. AV, automation, cleaning, security, maintenance, IT, branding agencies. Each vendor was competitive at the build moment, priced on build-phase volumes, contracted against build-phase expectations. At handoff, the operator inherits a vendor stack that was never specified for operation. The vendors renegotiate or churn. The operator rebuilds relationships with significant counterparties in the first six to twelve months of operation, which is exactly the wrong time.

Leadership churn. The CEO who raised capital is often a different CEO from the one who operates the asset. The CEO who operates the asset for year one is often a different CEO from the one who operates it in year three. We have seen assets go through three CEO transitions inside five years, each of which resets vendor relationships, IT strategy, commercial partnerships, and organisational trust. Each transition has a cost. Most capital models ignore this cost.

Investor intervention. Post-opening, the investor layer that has been relatively quiet during the build becomes active. Operating costs, once projected, are now actual, and actual is always higher than projected. An investor who sees a three-hundred-thousand-pound annual IT operating cost will often challenge it as “excessive”, regardless of whether the cost is correctly specified for the asset. That challenge reshapes decisions: internalisation of services, vendor rotation, scope reduction. Each sounds sensible in isolation and compounds expensively in aggregate.

These failure modes are familiar. Every sophisticated operator carries them in organisational memory. Most capital plans move past them without a line item.

What the standard capital stack prices

A well-constructed capital stack at opening prices four things: build cost, contingency, financing cost, and an operating reserve. The operating reserve typically covers twelve to eighteen months at projected run-rate.

Notice what sits outside that list. The cost of vendor transition at opening. The cost of leadership transition in year two. The cost of investor-initiated re-scoping post-launch. The cost of documentation loss when the primary technical contact departs. The cost of re-negotiating long-tail vendor contracts specified against build-phase rather than operate-phase volumes.

These events run as normal rather than exceptional. The aggregate impact on first-three-year operating cost is material, and varies meaningfully by sector, asset type, and the level of transition discipline priced in at the outset.

A capital stack that leaves them outside the specification runs understated. The operator absorbs the difference, which reduces year-one and year-two performance, which compresses refinancing options, which raises eventual cost of capital, which reduces exit math. Across the deals we have seen refinance on this pattern in the last eighteen months, the differential has shown up as sixty to one hundred basis points on the refinancing facility, relative to peer comp.

A worked case

The pattern is visible at scale in a purpose-built luxury senior-living development we looked at in the last eighteen months. The asset opened at the back end of 2022 on a roughly £200 million total build. The capital stack priced build cost, contingency, financing, and a fifteen-month operating reserve. It priced none of the transition costs below.

Inside three years of opening, the asset went through three chief executives.

CEO 1, who raised the capital and delivered the build, handed over four months after opening. The vendor stack, AV, IT managed services, automation, branding, had been selected against build-phase volumes and build-phase KPIs. Four vendors renegotiated inside the first year. One churned. The cost of rebuilding those relationships, directly and through legal and procurement time, came in around £140,000 across the first twelve months, with operational noise running through Q1 and Q2 of year one.

CEO 2 took over early in year one, left eighteen months later. A priority was internal consolidation; another was commercial realignment with the senior investor. The commercial realignment reopened long-tail vendor contracts. Three of them cost roughly £80,000 in legal and transition. The handover from CEO 1 had been compressed, which meant two months of documentation reconstruction for the incoming COO and another month for the investor relations lead. Call that another £110,000 in combined staff time and external support.

CEO 3 arrived mid-year three. The investor layer, now with two years of actual operating data, challenged a roughly £300,000 annual IT operating cost as excessive. The challenge ran through two board cycles and ultimately led to internalisation of a subset of the technology stack, termination of the external technology contract, and a contested account-closure process. Direct costs of the termination and contested handover totalled roughly £270,000. The internalisation itself consumed six months of the new COO’s attention, required two new hires that had not been planned, and paused a separate commercial initiative for a quarter.

Direct transition-related expense on an asset that priced none of it, roughly £600,000 in sum. Add the operating-cost drift in years one and two, roughly £1.1 million above plan, largely traceable to vendor and leadership transition. The operating EBITDA line in year two came in thirteen percent below the capital-plan projection.

The refinancing sat at month thirty-six. On a senior facility of roughly £140 million, the asset refinanced sixty to eighty basis points wide of the peer comp set. On a five-year facility, that is between £4.2 million and £5.6 million of additional carry over the life of the refinancing.

The counterfactual. A capital plan that had priced the transition costs at the outset would have run a small specific reserve programme. Roughly £150,000 for vendor transition, £80,000 for handover-documentation specification, £200,000 across two expected leadership transitions, £300,000 for investor-rescoping. Total, around £730,000. That asset would have sat flat to peer comp at refinancing. Net-net, a £730,000 provision in the capital plan at outset was worth somewhere north of £4 million in realised financing differential over the life of the refinancing facility.

That is the arithmetic. The specific numbers vary by asset. The shape of the arithmetic holds across every capital-intensive asset we have audited in which the capital stack treats operational execution as a post-opening concern.

What changes when operational execution sits inside the capital architecture

The specification changes at four layers.

Vendor selection is scored against transition-to-operator cost. The scoring favours a vendor whose pricing is structured against operating-phase volumes over one quoted only at build-phase volumes, even when the build-phase number looks cheaper. The scoring accounts for the probability and cost of renegotiation at handoff. In practice this rules out a class of vendors whose commercial model only works in the build phase, and favours a different class whose commercial model aligns with the operator’s incentives.

Commercial-term negotiation accounts for renewal cliff risk. Multi-year anchor agreements, sponsorship contracts, tenant leases, resident agreements, and supply contracts signed pre-opening all have a renewal moment. The capital stack should price the renewal moment alongside the signing moment. This changes which commercial terms are acceptable. A five-year agreement at a high headline number with a punitive renewal term is worse, from a capital-preservation view, than a five-year agreement at a slightly lower headline number with a rollover provision aligned to the operator’s KPIs.

Procurement is budgeted to expect disputes. Procurement disputes happen. Legal costs, rework costs, and opportunity costs belong in budgeted lines. Most capital plans treat procurement disputes as extraordinary items, which hides them from the capital-stack specification. They are ordinary items.

Programme management has handover instrumented. The set of documents, data, credentials, relationships, and operating procedures that constitute the asset at handoff is specified and scheduled in the capital plan. A handover that requires four months of reconstruction by the incoming operator is an underwritten cost borne in the operator’s first year. Specifying the handoff pre-build turns it from a year-one operating surprise into a build-phase line item, which is where it belongs.

The question principals should be asking

The board-level question is which operating-layer costs the capital plan has quietly transferred to the operator, and at what price. Whether the asset can be operated is rarely the binding question.

Four specific questions are worth running against any pre-opening capital plan.

1. Does the capital plan price vendor transition at handoff, and is the reserve sized against the observed cost on comparable assets.
2. Does it price leadership change in year two and year three, and is the cost broken out at the line-item level rather than buried in operating reserve.
3. Does it price investor-initiated re-scoping, and has the board discussed which categories of cost the investor is likely to challenge.
4. Does it price documentation loss when the primary technical counterparty steps away, and is the handover scheduled and resourced inside the build programme.

The honest answers to those four questions determine whether the refinancing in thirty-six months is a planned transaction or a distressed one.

When operational execution is priced into the capital plan from the outset, the four lanes move together. Vendor selection is scored against transition-to-operator cost. Commercial terms are negotiated with renewal-cliff risk visible. Procurement budgets expect disputes. Programme management has handover instrumented. Debt and equity then look at a plan that includes the costs normally absorbed as year-one operator pain. The headline operating return runs lower than the un-priced version, because the priced version is honest. The refinancing math and the exit math improve, because the operator performs against a capital stack that accounted for real-world friction.

Operational execution sits inside capital architecture, rather than after it. It is the part of capital architecture that determines whether the asset survives contact with its first principal, its second CEO, and its third year.