Your P&L may be accurate and still tell you surprisingly little about why your business costs what it costs.
Labour is visible.
Rework is not.
Software is visible.
The manual work created by disconnected systems is not.
Management salaries are visible.
The hours executives spend resolving problems that should never have reached them are not.
Supplier costs are visible.
The organisational friction surrounding those suppliers is not.
Most businesses understand their visible cost base reasonably well.
Far fewer understand the shadow cost base sitting underneath it.
And that is often where the more valuable cost reduction opportunity sits.
Cost is an outcome
When the pressure comes on EBITDA, the conventional response is understandable.
Management opens the P&L.
Headcount is reviewed.
Contractors are challenged.
Suppliers are renegotiated.
Discretionary expenditure is reduced.
Projects are deferred.
Travel stops.
Vacancies remain unfilled.
Some of this may be necessary.
But there is a problem.
A P&L tells you where money was spent.
It does not necessarily tell you why the organisation needed to spend it.
That distinction matters.
If a business requires ten people to administer work that should require six, the accounting system will correctly report the cost of ten people.
It will not tell you that four of them exist because the process is poorly designed.
If managers spend hours every week reconciling information across different systems, their salaries will appear in the accounts.
The reconciliation problem will not.
If decisions routinely move three levels higher than they should, the executive salaries are visible.
The cost of decision delay is not.
This is the shadow cost base.
It is the cost created not simply by what a business does, but by how the business has evolved to do it.
Most complexity arrived for a reason
Very few organisations deliberately design themselves to become expensive.
Complexity normally accumulates incrementally.
A customer requires an exception.
A spreadsheet is created.
A control fails, so another approval is added.
A system cannot perform a task, so somebody develops a workaround.
A manager does not trust the information, so a second report is introduced.
A business unit grows and creates its own process.
An acquisition brings another platform.
A senior executive becomes the default decision-maker because making the decision themselves is quicker than fixing the underlying accountability.
At the time, every intervention may make sense.
Years later, nobody remembers why half of them exist.
But people continue doing the work.
This is one of the reasons mature businesses can become more difficult to operate as they grow.
Revenue increases.
Headcount increases.
Systems increase.
Controls increase.
Reporting increases.
But operating leverage does not appear at the rate management expected.
Eventually somebody asks a reasonable question:
Why does it cost us this much to run this business?
The answer is rarely one thing.
It is usually hundreds of small decisions that have accumulated into an operating model.
The dangerous response is to remove people without removing work
There is a particular form of cost reduction I see repeatedly.
A business decides it needs to reduce its cost base.
A headcount target is established.
Roles are removed.
The organisation becomes temporarily cheaper.
But most of the work remains.
The approvals remain.
The reports remain.
The meetings remain.
The reconciliations remain.
The exceptions remain.
The systems remain disconnected.
The decision bottlenecks remain.
The same organisational architecture now has fewer people supporting it.
For a period, everybody works harder.
Management absorbs more.
Service levels begin to move.
Key people become overloaded.
Vacancies are quietly refilled.
Contractors appear.
New roles emerge under different titles.
Eighteen months later, much of the cost is back.
The cost-reduction program may have achieved an accounting outcome.
It did not achieve an operating-model outcome.
That is why sustainable cost reduction requires a different question.
Not:
How many people can we remove?
But:
What work, complexity and dependency can we remove?
They are very different questions.
The most expensive work is often work that should not exist
There is a tendency in operational improvement to focus on whether people are performing tasks efficiently.
That matters.
But there is a more important question.
Should the task exist at all?
I have walked into businesses where capable people were performing unnecessary work extremely efficiently.
Reports were produced on time that almost nobody used.
Data was checked multiple times because nobody trusted the source.
Managers approved transactions because authority had never been properly delegated.
Teams maintained shadow spreadsheets because core systems did not provide enough visibility.
Meetings existed to compensate for weak accountability between meetings.
Executive committees discussed matters that should have been resolved two levels below them.
None of those activities necessarily looked large.
Together, they consumed an enormous amount of capacity.
That is why improving operational efficiency is not simply about asking people to work faster.
It is often about asking the organisation to require less work.
The shadow cost base has some common signatures
You can usually see it before you can calculate it.
Look for a business where:
- managers spend significant time chasing information
- the same data is maintained in several places
- decisions repeatedly escalate upwards
- recurring meetings are used to resolve recurring problems
- customer or operational exceptions have become normal operating practice
- senior people are heavily involved in routine matters
- multiple people check the same work
- reports have proliferated but confidence in the numbers remains weak
- process ownership is unclear
- systems require substantial manual intervention
- roles have grown around workarounds
- the organisation cannot clearly explain why particular controls exist
These are not merely annoyances.
They are economic signals.
Each one consumes labour.
Each one consumes management capacity.
Each one can slow throughput.
Each one can increase the amount of organisational effort required to produce a dollar of revenue.
That eventually becomes an EBITDA problem.
This is why revenue growth does not always create operating leverage
One of the assumptions behind growth is that a larger business should eventually benefit from scale.
Some costs should grow more slowly than revenue.
But that only happens when the operating model scales.
If complexity grows at the same rate—or faster—the business can become larger without becoming economically better.
Another customer creates another exception.
Another site creates another management layer.
Another product creates another process.
Another system creates another interface.
Another acquisition creates another way of doing the same thing.
Revenue increases.
So does organisational friction.
The business becomes bigger.
But not necessarily more scalable.
This is where operational performance and financial performance begin to separate.
The P&L shows the financial effect.
The operating model contains the cause.
Sustainable EBITDA improvement starts below the P&L
There is nothing wrong with looking at the general ledger when costs need to come out.
But I would not stop there.
I would also ask:
Where is work being duplicated?
Where is information being reconstructed manually?
Which decisions are being made too high in the organisation?
Which controls exist because another control is unreliable?
Which processes create exceptions as part of normal operation?
Where have roles accumulated around broken workflows?
Which reports exist because managers cannot see what they need from the systems?
Which activities would we choose not to recreate if we were designing this business today?
That last question is particularly useful.
Because organisations are very good at defending work simply because the work already exists.
History becomes justification.
It should not.
Cost reduction and cost redesign are not the same thing
Traditional cost reduction asks:
What can we spend less on?
Cost redesign asks:
Why does the business require this cost in the first place?
The first can produce savings quickly.
The second can produce a structurally better business.
The distinction matters even more when businesses are preparing for growth, investment or a future transaction.
A buyer can see reduced headcount.
But a sophisticated buyer will also look at whether the business is genuinely scalable.
Whether management dependency has reduced.
Whether processes are repeatable.
Whether systems support the operating model.
Whether decision-making happens at the right level.
Whether EBITDA improvement is structural or simply the result of short-term restraint.
Temporary austerity is not operating leverage.
The real opportunity
Most businesses know what they spend.
Far fewer understand what makes them expensive.
That is why some of the best cost opportunities are not found by starting with the P&L.
They are found by following the work.
Watch where it stops.
Watch where it loops.
Watch where it gets checked again.
Watch where somebody builds a spreadsheet.
Watch where a manager intervenes.
Watch where a decision moves upwards.
Watch where an exception has become normal.
Then ask why.
The shadow cost base is rarely one dramatic inefficiency.
It is the accumulated economic cost of an organisation that has become harder to operate than it needs to be.
And once you can see it, the cost conversation changes.
You stop asking only where expenditure can be cut.
You start asking what the organisation can stop requiring.
That is usually where sustainable operational efficiency—and sustainable EBITDA improvement—begins.