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 expect 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 typically build 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.
- Systems5 min read
The badge nobody turned off
Collecting the card at the exit interview feels like the end of the offboarding. The card was never the thing that opened the door, and the record that did is usually held in more places than one team can name.
- Security5 min read
You cannot practice on somebody else's network
A range full of well-built generic scenarios teaches tool proficiency, which is real and which transfers. The decisions that go wrong during an actual incident are specific to one estate, and those are the ones a generic environment cannot rehearse.
- Systems6 min read
Designed on a desk, operated in a glove
An operator terminal is drawn on a good monitor, indoors, by somebody with bare hands and unhurried attention. Every one of those conditions is false at the machine, and the screen is judged by whichever one broke hardest.
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.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.