Definition
What is an operations OS?
Every business has a system of record for money, and usually one for customers. Very few have one for how the work itself is done.
Last updated: July 2026
Definition
An operations OS is a system of record for how an organisation actually operates: every process across every entity, what each one costs, where each one breaks, and the work in progress to change it. It sits above the tools that execute work, and below the finance systems that report on it.
Why the category exists
An operations leader inheriting a group of businesses asks a simple question: how do we actually run, and what does it cost us? Every existing system answers something adjacent. Finance reports by cost centre. Task tools show what people are working on this week. The ERP knows what was transacted. None of them can say that invoice matching costs £33,000 a year in one subsidiary and £11,000 in another.
So the answer gets assembled by hand — a consultant, a few weeks of interviews, a spreadsheet that is accurate on the day it is delivered and stale within a quarter. An operations OS is the argument that this should be a live system rather than a recurring project.
What an operations OS does
A map of how work actually happens
Every process, across every entity, described by the people who run it — not an idealised flowchart drawn once during an ERP project and never opened again.
A cost attached to each one
Hours against a loaded rate, plus leakage, giving an annual figure per process and per entity. Without a number, processes cannot compete for budget.
A diagnosis, not just a picture
Where a process breaks, why, and what a better version looks like. A map that only describes the present is an audit; an operations OS is meant to change something.
A route into execution
The fix becomes owned, dated work, still linked to the process it came from — so improvement is tracked against the thing it was meant to improve.
How it differs from adjacent tools
Each of these answers a real question well. The distinction is which question.
| Tool | Question it answers | Where it stops |
|---|---|---|
| Project management tool | What is everyone working on? | Tracks decided work. Silent on standing processes and what they cost. |
| Process mining | How did this process actually run? | Precise, but only sees what systems recorded, and needs event logs and months. |
| BPM / workflow engine | How should this process run? | Automates a defined process. Assumes you already know which to fix first. |
| ERP | What happened, financially? | Reports by cost centre, not by process. Cannot tell you what invoice matching costs. |
| Operations OS | What does how we operate cost us, and what do we fix first? | Accepts estimates rather than measurements, in exchange for coverage and speed. |
Who it is for
An operations OS matters most where there are several entities — a holding company, a group, a portfolio — each with different systems, different process maturity, and no shared definition of what anything costs. That is where per-entity comparison stops being a nice report and starts being the only way to see anything. It works for one company too: the map and the costs are just as real, and AI agents doing recurring work are as useful to one company as to a group.
When you don't need one
Worth saying plainly, because a category page that claims universal relevance is not worth reading:
- • One entity, one system, and processes that already run cleanly end to end — you probably need better reporting, not another system.
- • A single known problem you have already scoped. Fix it. Do not map an organisation to justify a decision you have made.
- • High-volume transactional flows fully captured in systems, where the question is conformance rather than cost — that is what process mining is for.
Common questions
How do I map how my business actually runs?
Four steps, done process by process rather than department by department: describe each process the way the people who run it actually do it, not as an idealised flowchart drawn once and never reopened; attach a cost to it in hours and a loaded rate; work out where it breaks and why; and turn the fix into owned, dated work that stays linked back to the process it came from. An operations OS repeats this continuously, across every entity, rather than once as a project.
What is an operations OS?
A system of record for how an organisation actually operates: every process across every entity, what each one costs, where each one breaks, and what is being done about it. It sits above the tools that execute work and below the finance systems that report on it.
How is an operations OS different from a project management tool?
A project management tool tracks tasks — work someone has already decided to do. An operations OS is concerned with the standing processes that run whether or not anyone creates a task, what they cost, and whether they should run that way at all.
Is an operations OS the same as process mining?
No. Process mining reconstructs how processes ran by analysing event logs from source systems. An operations OS captures the process from the people who perform it and costs it directly, which covers work that never touches a system but requires accepting estimates rather than measurements.
Who needs an operations OS?
Typically a COO, CFO or managing director responsible for several entities — a holding company, a group, or a portfolio — where processes differ per entity, systems differ per entity, and nobody has a single view of what any of it costs.
Related
- Cost of operations — the method for putting a number on a process.
- Process mining alternative — the closest adjacent category, and where the two differ.
- Espresso for private equity — the same operations OS, applied across a fund's portfolio.
- For holding companies — the category applied to a group with subsidiaries.
Espresso is an operations OS
Map every process across every entity, cost it, diagnose it, and push the fix into delivery — without an integration project in front of it.
See how it works