Case I
The 1.2 GW platform was not twelve hundred independent megawatts of choice
In 2023 we reviewed a proposed US$620 million platform acquisition carrying 1.2 GW of development pipeline. Eight hundred megawatts depended on the same planned connection reinforcement. The projects had different names and locations, but an important part of their progress relied on one common condition. I wanted that dependence visible before the total pipeline was described as a broad set of development choices. None of the pipeline figure represented an assertion that the capacity had been built or was producing power.
Ellis Brackenmere, our fictional development director, wanted to continue negotiations. The shared reinforcement could be an advantage if it progressed, and the platform offered a route to projects the company could not quickly reproduce. He was concerned that hesitation would lose the seller’s attention and the chance to shape the opportunity. I agreed that concentration did not automatically make the platform unattractive. My objection was that the strategic account presented project count and capacity as diversification without sufficiently explaining the shared condition.
We deferred acquisition negotiation after US$3.4 million in review. The proposed US$620 million purchase did not occur in this case. Engineering, connection, permitting, legal, finance and capital owners retained their specialist assessments. My team’s contribution was to reorganise the proposition around its dependencies, so the institution could judge whether it wanted this particular concentration rather than an implied collection of independent opportunities.
Deferral gave up momentum and risked losing access to the platform. The reinforcement might still progress, and another buyer might reasonably accept the concentration. I did not describe the decision as a quantified loss avoided or assume the review expense was recovered. It was a choice about the next commitment on the evidence available, not a prediction that the platform would fail.
The case changed the way I wanted capacity discussed. A total can describe scale while concealing how much of that scale moves together when one assumption changes. The leadership account should retain both views. This invented example reaches no conclusion about a live connection process, project approval or investment. A real public version would need authorised information and professional review of the project status before any capacity or dependency was described.