One Operator — Advise & Build
Product work that sits between teams.
Modus One works with energy and industrial companies — one operator, quietly embedded. Advisory when that's what's needed, building when that's what's needed.
What the work looks like
01
Internal
How the business runs
Operations, commercial strategy, data, customer success, internal tooling.
02
External
What customers see
Customer apps, portals, dashboards, onboarding — the product itself.
A note — on the work
A few patterns that keep recurring.
The interesting product work in energy and industry rarely sits inside a single team. It sits at the boundaries — where commercial, technical, regulatory, and customer-facing functions interface, and where no one person has the mandate to resolve what happens in between.
The patterns below are a few shapes this takes. What they share is that the missing piece was rarely a tool, a team, or a budget — it was usually a person who could hold the whole picture at once.
-
The customer product that nobody specified.
An approved, funded product — an app, a tariff, a portal, a service — that crosses commercial, technical, and regulatory functions and that no internal owner has authority across all three. Six months later, it's still a slide deck. The work is usually shorter than the organisation fears; the reading that comes first takes the longest.
-
The operational system nobody owns.
A tool or workflow that several teams rely on but none of them owns. The reporting pipeline that everyone trusts until it breaks. The forecasting model maintained by one person who's leaving. Too important to stay broken, not important enough to warrant a team.
-
The platform trying to become a product.
A technical platform that works, with customers operating at a fraction of its capability. The gap is almost always between what the platform can do and what the customer has been set up to absorb — organisationally, operationally, and in the workflows a real operator has time for.
-
Customer success that needs to become a product function.
A team doing heroic work to keep accounts alive one email and one workshop at a time. The insights captured in each interaction disappear into inboxes, and the product never feels the pressure of what its users actually struggle with. The shift is treating customer success as a product surface, not a support function.
-
The services business trying to become a software business.
An organisation delivering high-touch outcomes through people, now trying to convert those engagements into recurring revenue. The conversion rarely fails on commercials. It fails on packaging, product maturity, and the muscle to sell and support two revenue models at once.
-
The AI programme looking for a product.
A data science capability, often well-funded, that has produced interesting outputs without being translated into value. The model works. The product around the model is the gap — and it's almost always a question of what decisions the model is meant to support, not what an interface should look like.
-
Growth as a system, not a function.
A senior team carrying commercial ownership out of necessity — the CEO in every deal, forecasting by feel. Not a sales problem. A structural one. The work is industrialising the commercial system so the next ten million in revenue doesn't require the first five people who built it.
Seven patterns among many. A conversation usually reveals which one the current situation most resembles — and often, a version not yet written down.
A short email is a good start
Start with the real problem.
Most conversations begin with a problem someone has been carrying for a while. Describe it as it is, not as a neat brief.
Useful to include
The situation
As it actually is right now — not the tidied-up version.
Who's involved
Which teams touch it, and where ownership goes quiet.
What's been tried
Earlier attempts, and roughly where they stalled.