Twenty five years of running field networks has left me with a set of opinions about what works, and a longer list of things I got wrong the first time and had to fix while the network was still growing. Both end up here.
I write about uptime and unit economics, plus the operating decisions that quietly determine whether a network compounds or bleeds. No framework I have not personally used, and nothing I would not say out loud in a review meeting.
If something here is useful to you, take it. If you think I have it wrong, I would rather hear that than not.
Latest · Operations
Every other number you report is downstream of this one. Utilisation, revenue per site, customer retention, cost per swap. All of them assume the asset was running, and none of them survive a network that is quietly down eight percent of the time.
Placeholder post — replace with the first real piece
FEATURED IMAGE
4:3 crop
optional
Newest first. Six placeholders below, ready to be swapped out as the real pieces go live.
If you want to know whether this is worth your time, here is roughly what you will find.
What it actually takes to keep thousands of unmanned assets alive at once, and why the number is a leadership decision rather than a maintenance statistic.
The cost curves that decide whether a network gets healthier or sicker as it grows, and how to bend them in the right direction during expansion.
Standard procedures, escalation paths, and vendor governance. The unglamorous machinery that separates a managed network from a collection of sites.
Condition-based maintenance, remote intelligence, and why operating models built in India are becoming the ones worth exporting.