Field notes on BESS diligence, NEM markets, and the methodology as we build it.
We write about the technical, commercial, and institutional gaps we see in front of us. Short notes, rarely, rather than long thought-leadership on a schedule.
NEM connection-queue reality check: what the AEMO register actually tells you
Treating the AEMO connection register as a proxy for project reality is a common mistake. A guide to reading it the way our red-flag engine does.
Reading a system impact study in an afternoon, not a week
The structure of an ISO system impact study is the same every time. The parts an investor actually needs are small and predictable. A field guide for analysts on the investor side.
P10, P50, P90 and the quiet violence of point estimates
A battery revenue number presented as a single figure hides more than it reveals. A practitioner argument for distribution-first underwriting, with a worked example from a merchant NEM site.
Interconnection is a pricing problem, not an engineering one
Connection queues clear on economics, not merit. The engineers solve the study. The investors price the risk. A note on what that means for how investors should screen their pipelines.
The 72-hour IC memo: what the tooling stack has to get right
Cutting a six-week workflow into a three-day one is not a productivity story. It is an architecture story. What the ingestion, orchestration and review layers have to look like for a memo to clear on a compressed clock.
BESS DD Methodology v1, public white paper
The first full release of our red-flag and revenue methodology, in preparation for Product v1 launch.