How we ended up here
We started by taking whatever work came, like most small studios. The energy projects were the ones we kept being asked back for — partly because the problems are genuinely interesting, mostly because so few teams are willing to learn how the sector actually works before writing code.
So we stopped spreading. Today almost everything we build sits close to how energy is measured, traded, billed or monitored, and that focus is the reason a first meeting with us tends to be short.
What we believe about building software
The people doing the work know the requirement
Specifications describe the intention. The person handling the exception at 4pm on Friday describes the system.
Working software beats a longer document
Something you can open and try changes the conversation in a way another round of review never does.
A system nobody can maintain is unfinished
If the next engineer cannot understand it, the delivery was a loan rather than a handover.
Bad news early is part of the job
Every schedule slips somewhere. The difference is whether you hear about it while there is still time to decide.