Intelligence
Development19 Oct 20269 min read

What a Six-Month Data Center Delay Costs

A 10 MW worked example separates a €4.50m cash gap from a €2.57m timing loss, then shows how delivery evidence should change a site-selection decision.

Matthieu Gallego· Powerland Map
What a Six-Month Data Center Delay Costs

A developer has two otherwise comparable options for a 10 MW IT phase. One costs €4 million more and can start billing six months earlier. Is the premium worth paying?

Under the illustrative assumptions below, the slower option creates a €4.50 million cash gap during those six months. Yet the estimated present-value disadvantage is approximately €2.57 million. Paying the €4 million premium would therefore require another benefit beyond the timing effect measured here.

That difference matters. A liquidity problem can stop a project even when its long-term economics remain attractive. Equally, treating every euro of deferred revenue as permanently lost can make an expensive site look cheaper than it is. My starting point would be to price the delivery difference only after defining which capacity can actually earn revenue, on which date, and under which conditions.

This is a worked decision model for developers and investment teams. Its commercial and financial inputs are assumptions, not PowerlandMap market benchmarks or estimates of any named operator's returns.

Start with the revenue-bearing phase

A campus completion date is rarely enough to populate a cash-flow model. The relevant milestone is the handover of the particular phase the customer can accept and pay for.

Consider PAR15 in Dugny, France. In its project announcement, Equans Data Centers describes up to 66 MW of IT power, delivered in four phases, with 12 MW in the first phase. It also identifies the high-voltage substation, internal fit-out and commissioning within its scope. The 66 MW headline therefore cannot stand in for the first billable block.

ENKA's Tuzla project page describes an 11 MW IT project in Istanbul, a May 2025–May 2027 project duration and data-hall fit-out in two phases. That information describes the project and its phasing. It does not establish a customer acceptance date for every megawatt.

Neither example is presented as a delayed project. They illustrate why a financial comparison needs a phase-specific milestone. A six-month change in final campus completion has a different effect from a six-month change in the first occupied hall.

Before assigning a cost to delay, connect the development milestones to the actual commencement of billing. Ask which hall, which IT capacity, which acceptance tests and which remaining external dependency sit behind the proposed date.

What our own records can and cannot tell us

PowerlandMap refreshed its public, non-demo supply records tagged under construction on 19 October 2026 at 06:00 UTC. The snapshot contained 185 distinct record IDs across 39 country codes. A populated calendar target field existed for 154 records. The other 31 records, or 16.8%, had no value in that date field.

Crucially, 29 of those 31 still contained a nonblank textual target field. Those entries require interpretation. A text field might contain a year, a window, several milestones or a statement that timing is unspecified. Its presence alone does not establish a usable delivery commitment.

The practical result is narrow but useful: filtering only on a populated calendar date would exclude 31 records from this snapshot before their narrative timing evidence was reviewed. Calling all 31 “projects without a delivery schedule” would overstate what the extraction proves.

The unit is a database record, which may represent a facility or a phase. This is not a deduplicated count of campuses, a representative market census, a measured delay rate or an independent verification of every stated date. The filter used published, verified-public, public-visibility records with demo records excluded. The under-construction label follows the database's normalized pipeline classification.

For site selection, keep the original wording alongside any normalized date, then resolve the milestone relevant to the customer's deployment. Precision in a spreadsheet should come from stronger evidence, rather than replacing a delivery window with an arbitrary day.

A reproducible 10 MW example

The model begins at the original planned service date, called month zero. The on-time case earns its first monthly contribution at the end of month one. A six-month delay moves that first payment to the end of month seven.

Assume a 10,000 kW IT phase, 75% billable occupancy and €90 of monthly cash contribution per billable kW. Here, billable occupancy means capacity under revenue-producing contracts. It is not electrical load utilization. The €90 contribution is after ordinary operating cash costs and before financing and tax. It is an assumed model input, not an advertised colocation tariff.

Monthly contribution is therefore 10,000 × 75% × €90 = €675,000. Assume that the same 120 monthly payments remain collectible after the delay. There is no tenant cancellation, no shortening of the earning period, no inflation and no terminal value.

During the delay, assume a further €75,000 a month of incremental site security, project management and other prolongation costs. These costs arise only because of the delay and are not included in the normal operating contribution.

For the value comparison, use an illustrative 8% effective annual discount rate. Capital expenditure timing and amounts, working capital, taxes, maintenance investment and residual value are held identical between options and cancel from this incremental comparison. Real projects require those schedules to be rebuilt wherever they differ.

| Model input | Assumption | | --- | --- | | Phase capacity | 10 MW IT, or 10,000 kW IT | | Billable occupancy | 75%, constant from service commencement | | Monthly operating contribution | €90 per billable kW, before financing and tax | | Contribution per operating month | €675,000 | | Extra cost per delayed month | €75,000 | | Earning period | 120 monthly payments, shifted intact | | Discount rate | 8% effective annually | | Earlier-delivery premium | €4m, paid at month zero |

No PUE conversion is needed because the model uses IT capacity throughout. Energy costs are already reflected in the assumed operating contribution. Adding another electricity bill without changing that definition would count the expense twice.

Cash required and value lost answer different questions

The six-month cash gap against the on-time case is €4.05 million of contribution not received during that window, plus €450,000 of additional delay costs. That is €4.50 million before any change in capital spending, working capital or financing terms.

The €4.05 million is deferred under this model. It is not automatically lost forever. The delayed case receives its final six payments after the on-time case has finished earning.

To measure that timing effect, convert the annual discount rate to a monthly rate: r = 1.08^(1/12) − 1, approximately 0.6434%. The value at month zero of the on-time contribution stream is €675,000 × [1 − (1 + r)^−120] / r, approximately €56.32 million.

Moving every payment six months later reduces that value by approximately €2.126 million. The present value of six month-end prolongation payments is approximately €0.440 million. Together, they produce a €2.566 million disadvantage, rounded to €2.57 million.

| Delay | Contribution deferred during delay | Extra delay costs, undiscounted | Cash gap during delay | Present-value disadvantage | | --- | --- | --- | --- | --- | | 3 months | €2.025m | €0.225m | €2.250m | €1.295m | | 6 months | €4.050m | €0.450m | €4.500m | €2.566m | | 12 months | €8.100m | €0.900m | €9.000m | €5.035m |

Calculations: PowerlandMap illustrative model. Present-value disadvantage equals the reduction in the 120-payment contribution stream plus discounted incremental delay costs. It is not a valuation of the whole project.

Financing needs a separate bridge. For example, €40 million of unchanged drawn debt at 8% simple annual interest requires €1.60 million of interest payments over six months. That payment matters for liquidity, but it is not automatically an additional €1.60 million disadvantage against an on-time project that would also service the same debt. Only the difference between the financing schedules is incremental.

Keep operating cash flows and financing cash flows consistent with the valuation approach. Aswath Damodaran's NYU valuation framework makes the distinction between operating cash flows and cash flows after debt payments explicit. The simplified comparison here remains before financing and tax. It does not add the €1.60 million interest illustration to the €2.57 million timing estimate.

When the more expensive site becomes the better choice

Under the six-month scenario, the €4 million premium exceeds the modeled timing benefit by about €1.43 million. On these assumptions, the premium does not pay for itself through earlier cash flows alone.

At twelve months, the modeled disadvantage reaches approximately €5.04 million. Avoiding that delay would exceed the same premium by about €1.04 million. The decision changes because the delay changes, while the remaining assumptions stay fixed.

The result can also change without a longer delay. A tenant might cancel if a long-stop date is missed. A fixed contract expiry might remove the final payments instead of shifting them. An earlier phase could protect a wider customer relationship. Those effects need their own evidence and cash flows. They should not be hidden inside an inflated monthly revenue number.

The opposite case matters too. If customers are not ready to occupy the earlier building, the apparent six-month advantage may produce little additional cash. A gradual occupancy ramp, deferred equipment procurement or a cheaper second phase can favor the slower option.

I would therefore use the premium as a question for the delivery team: what specific evidence supports enough earlier, collectible cash to justify it? A binding milestone, accepted commissioning plan or documented customer requirement can change the answer. A more confident adjective in a sales presentation cannot populate the model.

Turn delivery evidence into a decision

Compare each shortlisted phase using the same customer configuration and billing trigger. Check the grid connection evidence, the remaining construction dependencies and the commissioning acceptance sequence. Record who controls each unresolved milestone and what document would close it.

Then run at least three schedules using the actual occupancy ramp and commercial terms. Keep the cash funding requirement visible beside the discounted value difference. A project can pass the value test and still need a liquidity solution that the sponsor cannot supply.

For this example, €2.57 million is the six-month timing value under the stated assumptions. It is a starting threshold to challenge with better project evidence. The investment case changes when the delay, occupancy, contract survival or incremental costs change.

PowerlandMap can support the first part of that work by organizing public project and delivery evidence for comparison. If the decision concerns competing European locations, request a scoped time-to-power and grid-readiness comparison. Scope and delivery are agreed before the study is commissioned.

Sources and calculations were checked on 19 October 2026. The image is an AI-generated conceptual illustration, not a photograph of PAR15, Tuzla or another named site.

View the discussion on LinkedIn

The data behind the analysis

Follow Development with sourced, dated evidence

Qualified supply, anonymised demand and evidence-based matching sit behind each read — with the source, confidence level and verification date on every record