What Developers Risk When They Sign an Embedded Network Agreement

By the time the problems arise, the leverage is gone.

A provider reaches out during the development phase. They’re across their product, they make the process sound simple, and they’re there at exactly the right moment, when the embedded network needs to be resolved and the development team has fifty other decisions competing for attention. A proposal lands. It looks reasonable. Nobody has a strong basis to push back because nobody on the team has seen enough of these agreements to know what the spread actually looks like across the market.

So it gets signed. Ten years. Sometimes twenty. One provider, no competing benchmark, no independent view of whether the terms are anywhere near what the market would actually support.

What gets uncovered later is rarely one thing. It’s the revenue that should have been flowing back to the development and wasn’t. The technology upgrade the provider has no contractual obligation to deliver. The exit clause that makes changing providers so costly it’s effectively not an option. The occupants raising billing complaints that the owners corporation has no visibility into and no contractual leverage to resolve. And eventually, the renewal conversation where the incumbent knows the other side has nowhere to go, because no one thought to build leverage into the original agreement.

This is not an unusual outcome. It is, in fact, the standard one. The embedded network market rewards providers who move quickly and quietly, and disadvantages developers who don’t know what questions to ask before they sign.

In Australia, there is no requirement for an embedded network provider to disclose what they offered the development next door. Without that transparency, and without an independent process to test the market, developers are negotiating in the dark against someone who isn’t.

One proposal tells you almost nothing

When you negotiate directly with a single embedded network provider, you get one data point. One commercial model. One view of what the deal looks like. Without anything to compare it against, there’s no way to know whether the revenue share is strong, whether the technology provisions will hold up in five years, or whether the exit conditions are workable. “Nothing obviously wrong with it” is a very low bar for a ten-year commercial agreement.

The market varies significantly beneath the surface. Revenue structures differ materially between providers. Service models differ. Technology platforms differ. Some providers will genuinely invest in solar and EV infrastructure. Others will make commitments in the proposal that quietly disappear in the contract. Some agreements are structured to look generous upfront while locking in long-term conditions that erode that value over time.

A provider negotiating directly with a developer is not going to point any of that out.

The terms that cause the most trouble

The parts of an embedded network agreement that generate the most grief down the track are rarely the ones that received the most attention at signing. These are the areas where the gap between what was agreed and what was possible tends to be widest.

• Revenue share structureProviders often front-load headline numbers to make the proposal look attractive, while the structure across the full term is where the real value quietly erodes. A strong year-one figure tied to degrading conditions over a ten-year agreement isn’t a good deal. It’s a good opening move.
• Exclusivity provisionsMany agreements include clauses that prevent the owners corporation from switching retailers or introducing new energy services without provider consent. These provisions are often buried in the contract and rarely flagged in the proposal. They become very visible the moment the building wants to do something the provider hasn’t agreed to.
• Metering ownership and depreciationIn many agreements, the provider retains ownership of the metering infrastructure and depreciates it over the term. On a ten-year agreement with no depreciation schedule, the owners corporation can find themselves at renewal with no asset, no leverage, and a provider who knows it. Understanding when, how, and under what conditions ownership transfers is a basic question that is too often left unasked.
• Exit conditionsThe cost of leaving a provider who isn’t performing is one of the most consequential and least scrutinised elements of any embedded network agreement. Penalties, notice periods, and infrastructure retrieval costs can make an exit so expensive it isn’t realistic. This is where agreements that looked acceptable at signing become ones the owners corporation is stuck with regardless of performance.
• Future technology provisionsSolar, battery storage, and EV charging are no longer optional extras in most residential and mixed-use developments. They’re expectations. An embedded network agreement that doesn’t clearly commit to how these technologies will be accommodated, and at whose cost, is one that will create friction the moment residents or the market expect them to be available.
• Occupant outcomesHow residents and tenants actually experience billing, communication, and service under the agreement is rarely a priority in direct negotiations. It tends to become one very quickly once the building is occupied and people start engaging with their energy bills. The provider’s name isn’t on the door. The development’s reputation is.

On a ten-year agreement with no depreciation schedule, an owners corporation can reach renewal with no asset, no leverage, and a provider who knows it.

What the market actually looks like when it’s properly tested

One reason direct negotiations work so well for providers is that their proposals aren’t designed to be compared. Revenue share models are presented differently. Fee structures are packaged differently. Technology commitments are described in language that makes direct comparison difficult. When you can’t compare like with like, you can’t tell what’s competitive, and providers know it.

Utilizer runs a structured process that cuts through that. We go to market with a consistent brief, receive proposals from our panel of qualified providers, and evaluate them on the same basis across financial terms, service model, technology capability, and long-term fit. We model outcomes across three stakeholders: the developer, the owners corporation, and occupants. That’s the full picture of what an embedded network agreement actually delivers, and it’s what most direct negotiations never produce.

When providers know they’re being evaluated against each other on a level playing field, they respond differently. The terms improve. The commitments sharpen. That’s not a coincidence.

This isn’t about adding complexity. It’s about shifting who has the leverage.

A structured embedded network procurement process for new developments runs in parallel with the construction programme. It doesn’t add time. What it does is change the dynamic of the negotiation entirely, because a provider who knows they’re competing against the full market behaves very differently to one who thinks they’re the only name on the table.

The outcomes are consistently and meaningfully better. Better revenue share. Stronger technology commitments. Clearer exit provisions. Agreements that reflect what the market will actually support rather than what a single provider decided to offer a developer who had no basis to push back.

If you’ve already signed without going through a competitive process, that conversation isn’t over. Renewal is where the leverage comes back, and how you approach that moment matters just as much as how the original agreement was struck. Start thinking about it well before the contract end date arrives.

Frequently Asked Questions