Most JVs fail before the development ever starts.
The term sheet looks good. Both parties are aligned on returns. The site is real, the planning is progressing, and the grid connection is in hand. Then the deal stalls at heads of terms, takes six months in legal, loses a key individual on one side, and either collapses or closes on terms that neither party considers satisfactory.
This sequence is not unusual. It is, in the experience of active participants in European data centre JV markets, the most common outcome. The reasons are predictable. They are also largely preventable.
Where alignment breaks down
JV misalignment in data centre transactions is rarely about headline economics. Parties that agree on a target return, a development strategy, and a broad split of economics can still produce agreements that do not function — because the assumptions embedded in the headline deal are not made explicit until legal drafting forces them to the surface.
Development timeline assumptions are rarely tested at heads of terms. An investor and a developer may agree that a JV will develop a 50MW first phase in 24 months from financial close. That agreement conceals substantial assumptions about what “development” means — specifically, whether planning is assumed or certain, whether the grid connection is contracted or in process, and whether the timeline reflects best-case or base-case scenarios. When legal drafting asks for representations on these points, the gap between what was assumed and what can be warranted becomes apparent.
Decision-making rights are the most common structural failure. The question of who controls day-to-day development decisions, who approves cost overruns, and what happens when the development goes off-plan is the source of more JV failures than returns misalignment. Investors who expect board-level approval rights over material decisions are not operating at development pace. Developers who expect full operational autonomy are not managing investor risk. The tension is real and does not resolve itself through goodwill — it requires explicit structural resolution before signing.
Exit assumptions are made implicitly and tested explicitly. A developer seeking a development JV with an eventual asset sale is operating on different assumptions than an investor seeking a long-term income return. Both may be willing to work together through the development phase. The point at which those assumptions collide — when the developer wants to sell and the investor does not, or vice versa — can unwind a JV that has produced a genuinely good asset.
Structures that move at development pace
The JV structures that close fastest and perform best over the development period share several characteristics that are not complex but are consistently underweighted in standard templates.
The development budget process needs to be fast. A capital call mechanism that requires full board approval for cost items above a defined threshold sounds sensible. In practice, it creates a monthly governance burden that slows decision-making, frustrates development teams, and introduces risk into relationships that were designed to be partnership-based. The structures that work give development teams genuine operational authority within agreed parameters, with board oversight reserved for material deviations rather than routine cost management.
Milestone-based equity release aligns incentives without constraining operations. Rather than full equity commitment at close, structures that release equity tranches against defined development milestones — planning consent, grid connection, practical completion — protect investor capital while giving the developer the certainty needed to manage contractor and supplier relationships. The milestones need to be genuinely negotiated, not developer-drafted with investor sign-off, to reflect realistic development risk allocation.
Pre-agreed dispute resolution avoids the failure mode. JV agreements that go to litigation have already failed. The structures that survive disagreement are those with pre-agreed escalation processes — technical expert determination for construction disputes, independent valuation for exit pricing disagreements, and defined paths to buy-out rather than wind-up when the partnership has run its course.
The practical discipline
The JVs that close quickly are those where both parties have done the structural work before the term sheet rather than after it. That work is not primarily a legal exercise. It is a commercial exercise that requires both parties to model what the JV looks like when things go wrong — budget overruns, planning delays, key person departures, market changes — and to agree in advance how those scenarios are handled.
That conversation is uncomfortable to have at the outset of a partnership where both parties are motivated to close. It is substantially less uncomfortable than having it at the point of a contested cost overrun or an unexpected exit demand.
The developers and investors who approach JV structuring this way are not being pessimistic about their partnerships. They are building the governance infrastructure that allows partnerships to survive the conditions that every real development transaction eventually faces. The JVs that actually close — and that deliver on the development plan — are invariably those where that work was done upfront.