BackApproach
Seven stages. What is in scope and what is not at each one.
Continode works a defined sequence from site identification to operating partnership. Each stage has a clear scope boundary. Where partners are needed — hyperscalers, EPCs, utilities — we name the category and the role. We do not name specific counterparties without their permission.
Risk framework
Four things that kill these deals. How Continode de-risks each one.
Hyperscale data centre projects in Australia fail for four reasons. Not market demand — that is not the constraint. They fail on power, planning, capital, and hyperscaler commitment. Each risk has a specific mechanism and a specific de-risk approach.
Power
- What kills deals
- Grid connection timelines that cannot close a tenant's commissioning window. HV equipment lead times that pre-date the connection offer. BTM capital cost that makes the project economics unworkable.
- How Continode de-risks it
- Power is treated as the first commercial workstream, not a late technical dependency. Connection enquiry begins before site control is confirmed. BTM is assessed in parallel with grid-first pathways from the beginning.
Planning
- What kills deals
- Development applications that take longer than the connection timeline, destroying schedule alignment. Environmental issues discovered in DA that should have been identified in Diligence. Zoning incompatibility that makes data centre use require a rezoning rather than a standard approval.
- How Continode de-risks it
- Planning screening is done in the Identify stage. Sites with material planning risk are flagged before site control is sought. Government engagement on major project pathways is initiated early, not after a standard DA is refused.
Capital
- What kills deals
- Capital partners whose mandate does not match the project stage — a stabilised-asset fund cannot hold a development-stage site. Capital partners with FIRB-triggering nationality who are identified late in the process. UAE capital that is genuinely interested but not structured for Australian infrastructure.
- How Continode de-risks it
- Capital structure is designed in Acquire against the specific project profile. FIRB analysis happens before capital is sought, not after. UAE capital introductions are made only when the project can support institutional diligence.
Hyperscaler commitment
- What kills deals
- A hyperscaler conversation that is qualified enough to justify site origination but not binding enough to support capital raising. Tenant technical requirements that change after the facility design is fixed. A hyperscaler whose procurement process runs 18–24 months, during which connection and planning timelines are also running.
- How Continode de-risks it
- Tenant dialogue is initiated in Originate and structured to produce written technical requirements before the capital raise. Facility design is staged against connection milestones, not tenant commitment milestones, so the project can proceed at its own pace. [VERIFY: Gary to confirm whether any hyperscaler conversations are at a stage that can be referenced in public materials.]