

Founder's Lens
Manpower Cost to Revenue – How it misleads CEOs in healthcare.
-By Vivek Shukla
Founder & Managing Partner
Surge Growth Partners
"Aggregate hospital manpower metrics frequently mislead leadership by blending disparate operational realities into a single average. Healthcare manpower challenges are rarely headcount problems; they are distribution problems.
The key is to stop asking what your aggregate manpower cost is as a percentage of revenue, and start asking which departments generate enough revenue to justify their full operational and allocated support costs."

Most hospital CEOs know their manpower cost.
Many of them do not know what it actually means.
They see the number. 48% of revenue. Sometimes even higher. They benchmark it against the industry average, decide it is acceptable or alarming, and then they either breathe easy or initiate a hiring freeze.
That is not financial management. That is pattern recognition dressed up as analysis.
Here is what the number actually hides.
The aggregate manpower cost is one of the most misleading figures in healthcare finance.
Because it averages everything together, and in a hospital, averaging everything together is how you make good decisions invisible, resulting in bad ones surviving for years longer than they should be.
Break it apart and a completely different picture emerges.
Take your direct clinical departments like surgery, internal medicine, ICU, maternity, diagnostics. Calculate manpower cost as a percentage of revenue generated by each one individually. What you will find, almost without exception, is a small number of departments running at genuinely efficient ratios and a larger number that could not justify their cost base if they were evaluated as standalone units.
The high performers are subsidizing the underperformers silently and consistently. Every single month.
And because the aggregate looks acceptable, or at least explainable, nobody is having the conversation that needs to be had.
Then there is the support function problem. And this one is worse.
Support functions like HR, finance, administration, facilities, IT, PRO services, call centers, do not generate revenue. They enable it. Which means the question is never whether they cost money. The question is whether what they cost is proportionate to the clinical and commercial output they are supporting.
In most hospitals, that answer is no.
Not because support teams are incompetent or bloated by design. Because they were built for a facility that was planned to reach a certain scale, and either that scale was never achieved, or it was achieved and the support structure was never rightsized to match what actually materialized.
The result is a support cost base that was calibrated for a different hospital than the one that exists today.
When you map support function manpower costs against the revenue-generating departments they serve, the cross-subsidization becomes visible in a way that an aggregate percentage will never show you.
Some clinical departments are carrying a support overhead that is structurally incompatible with their margin profile. They are not underperforming. They are overloaded.
The reframe that changes everything.
Stop asking: what is our manpower cost as a percentage of revenue?
Start asking: which departments are generating enough revenue to justify what they cost to run them, including the support infrastructure allocated to them?
That second question will make some people in your leadership team uncomfortable. Good. Discomfort directed at the right question is how organizations improve.
It will also show you something that a hiring freeze never will: that your manpower problem is almost never a headcount problem. It is a distribution problem. Costs concentrated in the wrong places. Revenue too thin to carry the structure above it. Support functions scaled to a strategy that may no longer exist.
The hospitals that manage this well do not have fewer people.
They know exactly what every cluster of people costs — and exactly what revenue that cluster is responsible for generating or enabling.
That is not a finance function capability.
That is a leadership discipline.
