For holding companies

Operations across a holding company and its subsidiaries

A group is only as visible as its least-visible subsidiary. Espresso models the actual structure — holding, subsidiary, business unit — and rolls process cost and coverage up that hierarchy, so a group office sees one consistent picture instead of one spreadsheet per entity.

Last updated: August 2026

The short answer

Espresso lets a holding company map its structure — holding, subsidiary, business unit, revenue stream, every level optional — and then costs and tracks processes at whatever level they actually happen. Those numbers roll up automatically: a subsidiary GM sees their own operation, a group office sees the same data aggregated across the whole portfolio, and both are looking at the same underlying figures.

What running several entities actually costs you

None of this is about any one subsidiary being badly run. It is about the group having no single place to see across them.

One spreadsheet per entity

Each subsidiary tracks its own operations its own way. Getting a group-level answer means chasing every entity separately and reconciling formats that never quite match.

Uneven maturity, no visibility into it

Some subsidiaries run tight processes; others run on memory and habit. Without a shared view, a group office has no way to see which is which until something breaks.

Different systems, different vocabularies

A newly acquired subsidiary runs on a different ERP, a different naming convention, sometimes a different language. Comparing its operations to the rest of the group takes manual translation every time.

Built around the real shape of a group

The org structure is a first-class model, not a label on a project. That is what makes a group-level and a subsidiary-level view stay in sync automatically.

The hierarchy is modelled, not assumed

Holding, subsidiary, business unit, revenue stream — every level is optional, so the structure matches your actual group rather than forcing a template on it.

Cost rolls up the tree

Every process is costed at the level it happens, then aggregated automatically — per business unit, per subsidiary, and across the whole group — so a CFO and a subsidiary GM are reading the same underlying numbers.

Coverage shows where the gaps are

A group-level view of how much of each unit's process map has been worked, so an under-mapped subsidiary is visible rather than silently absent from the picture.

People and systems attach to the entity

Each holding company record carries its own people and systems, so the context for "who runs this and on what" travels with the entity rather than living in someone's head.

Who this fits

Group operations or shared services functions that need one view across every subsidiary, not a monthly reconciliation exercise.
Holding companies that have grown by acquisition, where each entity arrived with its own systems and habits.
CFOs and COOs who need a portfolio-level cost figure that they can trust actually adds up from the entities underneath it.

When you don't need this

A single-entity business with no subsidiaries doesn't need a roll-up — the cost-of-operations method on its own already covers that case. The hierarchy is only worth setting up once there is more than one entity to roll up across.

Common questions

How do you manage operations across a holding company and its subsidiaries?

By modelling the actual structure — holding, subsidiary, business unit, revenue stream — and rolling cost and process coverage up that hierarchy, so a group-level view and a single-subsidiary view come from the same data rather than a separate spreadsheet each.

Can I see the cost of operations for one subsidiary and for the whole group?

Yes. Cost is calculated per process, then aggregated up the org tree — per business unit, per subsidiary, and rolled up across the whole portfolio — so both views stay consistent with each other.

Do all subsidiaries need to be at the same level of maturity?

No. Every level of the hierarchy is optional, and each subsidiary or business unit builds out its own process map independently. A coverage view shows which units have been mapped and which have not, so uneven maturity across a group is visible rather than hidden.

Does this replace a shared services function?

No. It gives a shared services or group operations function a single place to see what each entity's processes cost and where they break, instead of chasing that picture entity by entity.

For COOs — the same roll-up, from the perspective of the person who has to report on it.
Cost of operations — the method behind the number each entity rolls up into.
What is an operations OS? — the category, and how it differs from a PM tool or process mining.

See your group, one entity at a time and rolled up

Map your holding structure, cost each entity's processes, and see the same numbers whether you're looking at one subsidiary or the whole portfolio.

See how Espresso works

Handling data across multiple entities? Read how we secure it.