Industries

Energy & Utilities

Systems that have to be correct against market rules, not merely correct in principle.

Energy is a sector where generic software competence is not enough. A system that is internally consistent but wrong against market rules is still wrong, and the cost of discovering that at settlement is considerably higher than the cost of getting the domain right during design.

Our work here combines local market knowledge with the supply chain and delivery partnerships that make the build practical. It spans trading and market-facing systems, the operational and metering data that feeds reporting, and the reconciliation work that determines whether the numbers survive regulatory scrutiny.

Most engagements in this sector are integration rather than replacement. Trading systems that work are rarely worth replacing wholesale, so the value is usually in connecting them properly, extending them where the market has moved, and building reporting that can be defended.

Where we focus

Areas of work

Trading and market systems

Systems that operate against National Electricity Market rules, where correctness is defined by market obligations and settlement timing rather than by internal specification alone.

Operational data and reporting

Consolidation of operational and metering data into reporting that stands up to regulatory scrutiny, including the reconciliation work that makes the figures defensible.

Retail and customer platforms

Customer-facing and billing-adjacent systems, and the integration between them and the operational data that feeds them.

FAQ

Common questions

Do you understand the NEM specifically?

Yes — market-facing work in the Australian energy sector is one of our longer-standing areas, and it is a domain where general software capability is not sufficient on its own. Settlement timing and market obligations shape the design.

Can you work alongside our existing trading systems?

Usually that is the requirement. Wholesale replacement of a working trading system is rarely justified, so most of this work is integration, extension and reporting around what already operates.

How do you handle the compliance dimension?

Regulatory and market obligations are treated as design constraints established during discovery, not as a review gate at the end. Reconciliation and auditability are built into the data flow.

Tell us what you are trying to build.

A short conversation is usually enough to tell whether we are the right fit. If we are not, we will say so.

Start a conversation