Development Premiums and Farm-Down Economics: The Return Is a Portfolio Result
Use an explicit worked schedule instead of a headline multiple pretending to be an IRR:
Year -4 development spend ($2.0m)
Year -3 development spend ($2.0m)
Year -2 development spend ($2.0m)
Year -1 development spend ($2.0m)
Year 0 sale proceeds $40.0m
-----
IRR on the successful project 76.3%
Gross proceeds / development spend 5.00×
The $40m sale price is an illustrative assumption, not a market benchmark. The portfolio point remains: if every attempted project costs $8m and only one in five reaches the same sale, gross proceeds from the winner equal the $40m spent across all five attempts. Before overhead, taxes and the time value of capital, the portfolio has not created value.
Development economics have to be measured across the whole pipeline. A return computed only on successful projects is survivor economics, not the return on all development capital deployed.
This post covers what the premium actually is, the stage-gate value curve, the hit-rate arithmetic that makes sense of it, and the farm-down decision it produces.
ℹ️ Note: Transaction prices and development fees vary by scope, rights transferred, milestone, geography, technology and vintage. Worked values are assumptions unless tied to a cited public agreement.
What Is the Development Premium?
The price a buyer pays above sunk cost for a project that has been de-risked. It compensates the developer for capital spent, time taken, and — most importantly — for the projects that did not make it.
It is not a payment for the asset. The asset does not exist yet. It is a payment for the removal of uncertainty: site control, interconnection position, permits, offtake and an executable construction plan, each of which had a probability of failure when development began and no longer does.
The Stage-Gate Value Curve
Do not use one generic $/MW development-premium table.
Public agreements show that development consideration can be tied to very specific milestones and can vary by order of magnitude across transactions. A 2026 Emergen / Bridgelink project-sale disclosure, for example, provides $5,000/MW after land rights and another $3,000/MW at ready-to-build for specified Greenfield Projects. A separate disclosed development-services agreement uses fees of $0.035/W for Solar Development Projects, subject to financing and RTB milestones. An older solar acquisition agreement used a much larger $1.50/W purchase price with post-closing milestone payments and development funding.
Those examples are not comparable “market prices.” They bundle different assets, rights, services, payment timing and risk.
The reusable model is therefore a stage-gate value curve:
| Stage | What changed | Value question |
|---|---|---|
| Site / land control | legal right to pursue the site | how much option value survives after site risk? |
| Interconnection milestone | queue / study / agreement position improves | what cost, timing and deliverability uncertainty was removed? |
| Permits | development rights become more executable | what binary approval risk disappeared? |
| Offtake / route to market | revenue structure becomes clearer | how much financeability improved? |
| RTB / NTP-ready | major development conditions are satisfied | what remaining construction / funding risk is the buyer taking? |
Price the project from the rights and risks actually transferred, not from a stage label.
What Actually Drives the Uplift?
The gates create value to the extent they remove the uncertainties that are binding for that specific project. The ranking can change by market, technology and transaction.
Interconnection. This can be a major value driver because it can resolve cost, timing and deliverability uncertainty, but its value depends on the actual queue position, studies, agreement and network-upgrade exposure. Do not assume it is the single largest risk for every project.
Offtake. A signed PPA with a creditworthy counterparty converts a merchant asset into a financeable one, and the difference in debt capacity alone — as the merchant tail post quantified — is worth a great deal.
Permits. Binary, slow, and subject to challenge. Their value is in the elimination of a tail risk rather than in anything they produce.
Site control. Necessary but not sufficient. Interconnection rules can require substantial site-control evidence at specified stages, which moves development capital earlier; apply the requirements of the relevant RTO / tariff rather than a universal percentage without checking the current rule.
An executable EPC plan. A contractor, a price and a schedule, which is what turns a permitted project into one somebody can actually finance.
Note that four of those five are things the previous two series treated as risks. The development premium is, quite precisely, the market price of having resolved them.
The Hit Rate Is the Whole Calculation
Here is where per-project returns become misleading.
| Illustrative sale price | Proceeds | Successful-project IRR* | Gross multiple | Equal-cost failed attempts covered |
|---|---|---|---|---|
| $70,000/MW | $14.0m | 23.7% | 1.75× | 0.75 |
| $120,000/MW | $24.0m | 49.2% | 3.00× | 2.00 |
| $200,000/MW | $40.0m | 76.3% | 5.00× | 4.00 |
*Assumes four equal annual $2m development outflows followed by sale at Year 0. Change the spend timing and the IRR changes materially. The right-hand column is the one that matters. At $200,000/MW the premium funds the successful project's costs and four failures of equal size. So:
Hit rate needed to break even at $200,000/MW = 1 in 5 (20%)
Hit rate needed at $120,000/MW = 1 in 3 (33%)
Hit rate needed at $70,000/MW = 1 in 1.8 (57%)
Under the equal-cost simplification, a 20% hit rate with $40m proceeds per success is only a gross break-even on nominal development spend. It is negative after overhead and the cost of capital. A higher hit rate, lower failed-project spend or higher realized proceeds improves the portfolio result.
This is why per-success development returns should be paired with pipeline attrition and total development spend. The number is not wrong; it is computed on a sample selected for success.
The related discipline is the one the interconnection post applied to queue costs: a development budget should carry cost per successful project, which is total spend divided by the hit rate, not spend per project attempted.
What Kills Projects, and When?
The hit rate is not a single number applied uniformly. It is the product of survival probabilities at each gate, and knowing where the attrition happens determines where to spend and when to stop.
Attrition can occur at different gates and at different stages of spend. Interconnection can create a late-stage economic failure if network-upgrade cost or timing moves adversely. Permitting can create a binary approval problem. Offtake can delay financeability rather than kill the project outright. Land / title defects can stop a project before major later-stage spend. The ordering and probability are portfolio-specific and should come from the developer's own historical funnel rather than a generic ranking.
The practical consequence is abandonment discipline. At each gate, compare the expected value of continuing with the incremental spend and time required to reach the next milestone. Sunk development cost should not determine whether the next dollar is rational.
Abandonment discipline can matter as much as origination quality. A developer that abandons at the right gate recycles capital into the next attempt; one that funds a stalled project for three additional years while hoping has converted a cheap failure into an expensive one, and that is where hit rates go.
Sell at Ready-to-Build, or Build and Hold?
The decision every developer faces, and it is a capital efficiency question rather than a returns question.
SELL AT RTB — worked example
Development spend $8,000,000 over four years
Proceeds $40,000,000
Successful-project IRR 76.3%
Capital released at sale $40,000,000
BUILD AND HOLD
Further equity required $67,883,125
Equity IRR from the Project Finance Mechanics worked structure 15.07%
Capital committed for 20 years
Those two cases use different capital amounts, timing and risk. Compare them on scarce capital, NPV and portfolio capacity rather than simply placing their IRRs side by side.
Selling at ready-to-build turns $8m into $40m in four years and returns every dollar for redeployment into the next development. Building and holding requires an additional $67.9m — eight times the development spend — to earn a fifteen percent return over two decades.
That difference explains the structure of the industry almost entirely.
A capital-constrained developer may prefer to farm down if selling recycles scarce capital into a pipeline with attractive risk-adjusted expected value. Holding assets would consume the capital that funds the next twenty projects.
Long-duration owners may prefer to hold where their cost of capital and operating capabilities make ownership more valuable than selling. They are natural buyers of exactly what developers are natural sellers of.
There is a caveat to the capital-efficiency argument. A high successful-project IRR is useful only if the developer can continue to deploy capital into projects with attractive portfolio-level expected value. Interconnection windows, land, permitting bandwidth and experienced personnel can become the scarce resource instead of cash.
That is the real argument for retaining assets, and it is not a returns argument at all. It is about what the capital does between projects. A developer with a deep pipeline and a genuine constraint on capital should sell; one whose constraint is deal flow rather than funding is in a different position, and holding an operating asset earning fifteen percent beats holding cash earning four while waiting for a queue window.
Hybrid strategies can do both selectively — retaining a minority stake to keep exposure to assets they believe are mispriced, or selling a majority while retaining an asset management role. The retained stake is often less about returns than about demonstrating conviction to the buyer.
The framing that resolves most internal arguments is the one from the first post in this sequence: compare returns on the capital that is actually scarce. For a developer that is development capital, and nothing in an operating asset competes with it.
What Does the Buyer Think It Is Buying?
Worth taking seriously, because the premium is revenue to one side and a cost to the other — and the buyer's model has to clear its own hurdle after paying it.
A buyer acquiring ready-to-build adds the premium to project cost. On the worked numbers, $40m on a $250m build takes total investment to $290m, and the project IRR falls accordingly. So the buyer is paying for de-risking and must believe the risk removed was worth more than the price of removing it.
Three things it is actually underwriting.
That the de-risking is real. An "executed interconnection agreement" and "a queue position with a favourable cluster study" are very different things, and the gap between them is most of the premium. Buyers with experience price the difference carefully; buyers without it sometimes pay ready-to-build prices for mid-stage projects.
That the assumptions transfer. The seller's energy yield assessment, basis assumption and capture rate all become the buyer's, and the Market Structure analysis shows those are the numbers most likely to be optimistic. A buyer accepting the seller's revenue case without rebuilding it is buying the premium and the assumptions together.
That nothing resets on change of control. A PPA with a change of control consent, an interconnection agreement requiring assignment approval, a permit conditioned on the original applicant — each is a way for de-risking to partially unwind at the moment of sale.
The buyer's discipline, and it mirrors the seller's, is to price the premium against what it would have cost to develop the same project, adjusted for its own hit rate. A utility with no development capability is buying something it cannot make and should expect to pay for it. One with a development arm is comparing a certain $40m against an uncertain internal cost of roughly the same size — and should be clear about which it is doing.
How Can a Farm-Down Be Structured?
Rarely as a single payment, because the buyer wants the seller's incentives to survive the closing.
Staged consideration ties payments to milestones — a portion at signing, a portion at notice to proceed, a portion at commercial operation. This keeps the developer engaged through the transition and reduces the buyer's exposure to a project that turns out less ready than represented.
Earn-outs link part of the price to outcomes: achieved capacity, a performance test result, or an energy yield in the first operating years. They are the buyer's answer to the assumption-transfer problem above — if the seller's yield assessment is right, it gets paid.
A retained minority stake keeps the developer exposed. Buyers often prefer this to an earn-out because it aligns on everything rather than on one measured variable, and developers accept it because it signals conviction. It also, as the returns posts noted, changes the developer's reported returns considerably by converting a clean exit into a mixed one.
A development services agreement keeps the developer working on the project after the sale, paid as a fee. This is frequently where the real negotiation happens: a lower headline price with a generous services agreement and a lower one with none are very different deals, and only the first number gets reported.
Warranties and indemnities, potentially supported by escrow or insurance, can allocate residual risk around permits, title and contracts. Whether transaction insurance is used is deal-specific.
The general observation is that a farm-down headline price is about as informative as a sponsor IRR. What matters is the payment schedule, what is conditional, what services are attached, and what the developer retains — and those four items routinely move the economics more than the headline does.
How Do You Model Development Economics in Excel?
As a portfolio, not a project, with the hit rate as the central input.
The single project
Development_Spend by stage and year
Exit_Price = $/MW × Capacity
PF_DevelopmentIRR = IRR(−spend, proceeds at exit)
PF_DevelopmentMOIC = Proceeds / Total_Spend
The portfolio, which is the real answer
PF_CostPerSuccess = Total_Spend_All_Projects / Projects_Reaching_RTB
PF_BreakevenHitRate = Total_Spend_Per_Project / Exit_Price
PF_PortfolioReturn = (Successes × Exit_Price − All_Spend) / All_Spend
On the worked numbers, the gross nominal breakeven hit rate is 20% at $200,000/MW and about 57% at $70,000/MW. Publishing the hit rate turns a successful-project return into a testable portfolio proposition.
The stage-gate decision tree
For each gate: Spend_to_Pass, P(Pass), Value_if_Passed, Value_if_Failed
Expected_Value = Σ over paths of P(path) × Value(path) − Spend
Abandon if Expected_Value_of_Continuing < 0
The most valuable output of this is not the expected value. It is the abandonment threshold — the point at which further spend is not justified — because the most expensive mistake in development is not a project that fails, it is a project that fails slowly.
The sell-or-hold comparison
Return on successful-project development spend $2m/year × 4 → $40m sale 76.3%
Return on ownership capital $67.9m at 15.07% over 20 years
PF_CapitalEfficiencyRatio = Development return / Ownership return
ℹ️ Note: Never compare a successful-project development IRR with an ownership IRR without also showing capital required, timing, pipeline attrition and redeployment capacity.
To build the stage-gate tree, the portfolio hit-rate economics and the sell-or-hold comparison, prompt Dezzmond with your development budget and pipeline.
What Do Developers and Buyers Actually Check?
- What is the hit rate, and what breakeven premium does it imply?
- Is the development budget stated per project or per success?
- What has actually been de-risked — interconnection agreement executed, or queue position only?
- Is there a signed PPA, and with whom?
- At which gate should this project be abandoned if the next milestone is missed?
- Does the buyer's price reflect the same de-risking the seller believes it delivered?
- Is the comparison between selling and holding made on capital efficiency, not on IRR?
Frequently Asked Questions
What is a development premium?
The amount a buyer pays above the developer's sunk cost for a de-risked project. It compensates for capital and time spent, and for the projects in the same pipeline that never reached a sale.
How large is it?
There is no single transferable market range. Public contracts show milestone payments and development fees from a few thousand dollars per MW to cents per watt, while acquisition prices can be much larger because they include different rights, assets and future economics. Normalize the exact transaction before comparing.
Why can successful-project development IRRs look so high?
Because the capital is deployed over time, the successful exit can be many times the direct spend on that project, and failed projects are outside the successful-project cash-flow stream. Portfolio economics must add them back.
Should a developer sell or hold?
It depends which capital is scarce. Selling ready-to-build turns $8m into $40m and frees it for redeployment; holding requires a further $67.9m for a fifteen percent return over twenty years. Developers sell, balance sheet owners buy, and both are behaving correctly.
How can a farm-down be structured?
Rarely as one payment. Staged consideration tied to milestones, earn-outs linked to capacity or yield, a retained minority stake, a development services agreement, and warranty cover backed by escrow or insurance. The headline price is often the least informative of those.
Where do projects actually die?
Interconnection is the largest killer and it kills late, after most development spend is committed. Permitting kills earlier and more visibly; offtake failure stalls rather than kills. A portfolio's hit rate depends more on abandoning bad projects quickly than on finding good ones.
What drives the uplift?
Whichever milestones remove the binding uncertainties for that project — often some combination of site, interconnection, permits, offtake and an executable construction plan. The ranking is transaction-specific.
Closing: A Return Computed on the Survivors
The successful-project return is real only when it is computed from the actual development cash-flow timing. In the worked equal-spend schedule it is 76.3%, not 208%.
It is simply computed on one project out of a pipeline, and the ones that did not reach a sale are not in the denominator. That makes it the same class of number as a fund quoting its best deal, or a trader quoting a winning position — accurate, and not a description of the business.
The honest version requires one additional figure, and every developer already knows it: the hit rate. With it, a $200,000/MW premium and a 20% hit rate is a business earning its cost of capital and no more, while the same premium at a 40% hit rate is an exceptional one. Without it, both look identical and both look extraordinary.
That number also reframes the sell-or-hold question, which is otherwise argued endlessly on returns that are not comparable. A developer's scarce resource is the capital that funds the next project, and nothing about owning an operating asset competes with redeploying into development at these multiples — which is why the industry is structured the way it is, with developers selling and balance sheets buying, and why the arrangement is stable rather than a sign that one side is mispricing.
the next post takes the number the buyer relies on when it pays that premium: P50, P90 and P99 energy yield, and what each actually means.
Sources: 2026 Emergen / Bridgelink disclosure — $5,000/MW land-rights milestone plus $3,000/MW RTB milestone · SEC-filed development-services agreement — $0.035/W Solar Development Fees tied to financing / RTB milestones · SEC-filed solar development acquisition agreement — $1.50/W purchase price with post-closing project payments · Dezzmond analysis; the $8m / $40m portfolio example is illustrative.