Energy & Utilities
Field-first software for infrastructure that has to stay up.
Utility work happens where the connectivity isn’t. Crews work in substations, trenches, wellheads and rural service territories, and software that assumes a signal gets routed around by lunchtime. Everything we build for this sector is offline-first by default, and everything that touches operational technology is designed with the security boundary as the starting point.
What we hear
The problems that actually show up.
Not a market overview. These are the specific failures that bring people to us in this sector.
Paper that still runs the field
Job packets are printed, marked up, and re-keyed by an admin days later. Asset records drift from reality and nobody trusts the system of record.
Outage communication that lags reality
The outage map, the IVR and the crew’s status disagree, and the call center absorbs the difference.
AMI data nobody uses
Interval meter data arrives at enormous volume and is used for billing and nothing else, while load, theft and reliability questions go unanswered.
Compliance evidence assembled manually
NERC CIP and inspection regimes demand evidence on demand. Producing it currently takes a person a week.
An OT network nobody has an accurate drawing of
The substation and generation networks were built for availability, at a time when the only way to reach them was to be standing there. The historian link changed that, and the architecture diagram has not been updated since.
What we build here
Systems we’ve shipped in this sector.
Some of these are whole products; some are one screen that removed a week of manual work. Both count.
- Offline-first field service and inspection applications
- Work and asset management extensions
- Outage management interfaces and customer communications
- AMI/meter data pipelines and load analytics
- GIS-integrated mapping and routing tools
- DER, storage and demand-response coordination platforms
- Vegetation management and inspection imagery workflows
- Regulatory and reliability reporting automation
Integrates with
The estate you already have.
We work through supported interfaces, not screen-scraping that breaks at the next upgrade.
Built to
The standards this sector answers to.
Engineered in from the start. Retrofitting conformance costs several times as much and produces a worse result.
Case studies
Work in this sector.
Further reading
Written up at length.
- Security6 min read
Catching anomalies on OT networks with fuzzy hashing
Enterprise intrusion detection does not transfer to industrial control networks. The traffic is a different shape, and that turns out to be an advantage.
- Engineering5 min read
From RTL to user space, and why the order matters
Five layers of stack on a single board. The engineering lesson was not about hardware; it was about the discipline of bringing up one layer at a time.
- Engineering3 min read
Offline-first is a product decision, not a technical one
Field software fails for a reason that has nothing to do with engineering skill: someone assumed the network.
Next step
Working in energy & utilities?
Bring the specific failure, not a requirements document. Forty-five minutes and we’ll tell you what we’d do about it.