What patient experience is worth on the P&L
Patient experience in most hospital groups is a department with a small budget, a feedback form, a quarterly score and no line in the P&L. It reports to operations or to quality. It is invoked in NABH audits and in the CEO’s town hall. It is the first thing cut when the quarter is tight, because nobody can say what it is worth.
I think that is a failure of the growth function, not of the experience team. The people who run experience are measuring the wrong thing for a budget conversation — satisfaction — when the thing that moves the P&L is what patients do afterwards: whether they leave a review, whether they come back, whether they bring their family, whether they tell the contact centre “I’m only calling because my neighbour said to”. Those are demand outcomes, and demand is what growth owns.
This is about putting experience on the P&L in terms a CFO will accept: reviews as a demand asset, the digital touchpoints that decide experience before and after the visit, the economics of getting a patient back, and how to make the case for experience spend in money rather than sentiment.
Reviews are a demand asset, not a reputation metric
Start with the one place where experience already has a visible price: the review profile.
A hospital’s rating and review count on maps and the aggregators is read by a large share of patients before they call. In Tier 2 cities, where the group brand is less established than in the metro, it is read by almost all of them. A unit with a strong profile converts a larger share of the searches it appears in, and pays less per enquiry in paid channels because the click-through is higher. A unit with a weak profile leaks demand at the point where the patient compares two hospitals side by side — and that leak never appears in any report, because the patient who chose the competitor never entered your funnel.
You can put a number on this without claiming anything about your own results. Take two units of similar size and catchment with different review profiles and compare share of search captured and enquiry conversion. Take the same unit before and after a sustained review programme. Take the paid channel data and look at click-through by unit against rating. The direction is consistent, and the CFO does not need it to be precise. She needs to see that the review profile is a lever with a demand consequence, and that the lever is currently pulled by nobody.
Then look at what generates a review. It is not the outcome of the treatment, mostly. It is the discharge experience, the billing counter, whether the nurse explained the medication, whether the follow-up call came. The experience team owns those touchpoints. The growth team owns the demand consequence. Right now those two are not in the same meeting.
The experience before the visit is digital
The patient’s experience of a hospital begins well before the building, and every step of it is something the digital front door controls.
Whether the search result was accurate. Whether the doctor listed is actually available on the day the site says. Whether the contact centre answered, and whether the agent knew that the consultant she wanted was on leave. Whether the appointment confirmation arrived and in a language the patient reads. Whether the estimate the contact centre gave matched the one at the counter. Whether the cashless status with the patient’s insurer was known before she arrived or discovered at admission.
Each of these is an experience failure that the experience team never sees, because it happened outside the building. And each of them shows up in the demand data as a lost enquiry, a no-show, a cancelled admission, or a one-star review that begins with “I called three times”.
This is where growth should be spending experience money, because it is where the return is fastest. A contact centre knowledge base that is actually current. A confirmation flow in the patient’s language. An estimate process that does not contradict itself. A cashless check at booking rather than at admission. None of it is glamorous. All of it converts.
The experience after the visit is also digital
The other end is where retention lives, and it is almost entirely neglected.
A patient leaves with a discharge summary, a prescription and a follow-up date. What happens next, in most groups, is nothing. No reminder about the follow-up. No call to ask whether the medication was collected. No route back to the doctor short of calling the general number and starting again. The patient’s next interaction with the group is the next emergency, if she comes back at all.
The CRM exists to close this gap and rarely does. A follow-up reminder that lands a week before the date, with a booking link. A recall for the chronic patient whose review is overdue. A note to the family member who was registered as the contact that the annual check is due. A message after discharge that asks one question and routes a bad answer to a human within the hour — before it becomes a review.
This is the layer where experience and growth are the same function. A recall programme is a retention programme is a revenue programme. It is also an experience programme, because the patient who is reminded and looked after tells people. The reason it does not exist is that experience does not own the CRM and growth does not own the follow-up. Put them in the same room and give one of them the number.
The economics of getting a patient back
The arithmetic a CFO will follow is simple and it is rarely done.
Acquiring a new patient through paid channels has a cost, and it is known — the growth team reports it monthly. Bringing an existing patient back through a recall message has a cost that is a small fraction of it. If a unit’s patient base returns at a certain rate without any programme, and returns at a higher rate with one, the difference in visits multiplied by the average revenue per visit is the value of the programme. Subtract the cost of running it. What remains is a margin contribution that appears nowhere in the current pack because nobody built the programme.
The catch is that you need the baseline, and most groups do not have one. The CRM either does not track repeat visits cleanly, or the patient exists three times because of deduplication failures, or the HIS integration was never completed. So the first experience investment is data hygiene, which is the least attractive item on any list and the one without which the rest cannot be measured.
Make the case anyway. A unit with a defined patient base and a plausible return rate and a known revenue per visit gives you a range. Present the range. The CFO will not argue with the direction; she will ask what it takes to narrow the range, and that is your data hygiene budget approved.
Family, referral and the second patient
The Indian patient rarely arrives alone. The person who books for an elderly parent will, if the experience holds, book for herself, her children and her in-laws. A paediatric relationship becomes a family relationship. A maternity patient is a customer for a decade if the group gives her a reason.
This is the retention economics that groups underrate most. The CRM, if it is structured for it, can hold the family as a unit rather than as unrelated registrations. The recall programme can address the household. The contact centre can see, when a name calls, that this family has been with the group for six years and route accordingly. All of this is product work — the data model, the journey, the tooling — and it belongs to growth.
And it is where the experience of one visit compounds. A bad billing counter does not lose a patient. It loses a household, and a household is a demand asset that no paid campaign can replace at any price.
What to measure so the CFO believes it
Satisfaction scores will not carry this conversation. They are reported by the experience team, they are always high, and they have no obvious P&L consequence. Replace them, in the growth pack, with demand outcomes that experience drives:
- Review velocity and rating by unit, and share of search captured against it.
- Return visit rate by unit and specialty, against a baseline, with the recall programme’s contribution isolated.
- Household growth — the number of registered families adding a second and third patient.
- Referral-source enquiries — the share of enquiries where the patient names a person, not a channel.
- Pre-visit failure rate — no-shows, cancelled admissions and estimate disputes, which are experience failures the digital front door caused.
Each of these has a revenue line behind it. Each can be moved by a specific investment. Together they replace “experience matters” with “this programme returned this many visits at this cost”.
Making the case in money
The case I have made, more than once, has three parts.
The leak: where demand is being lost before the visit — no-shows, contact centre failures, estimate disputes — and what those enquiries would have been worth at the unit’s conversion rate. This is the fastest money and needs the least new capability.
The return: what a recall and follow-up programme would produce against the unit’s patient base, shown as a range with the assumptions visible, and with the data hygiene cost included as the first step.
The asset: the review profile, shown as a demand lever with a comparison across units, and the cost of a programme to move it — response, prompting, the escalation loop from a bad answer to a human.
Then the ask, which is not “fund the experience team”. It is “fund these three programmes, owned by growth, measured on these numbers, reviewed in the P&L pack quarterly”. The experience team is a partner in delivering them, and its budget conversation gets easier because the outcomes are now visible.
The mistake is to try to fund experience as a virtue. It is not funded as a virtue anywhere. It is funded as a return.
If you’re starting this next quarter
- Get the baseline — return visit rate, household count, review velocity — for two units, and accept that the data will be ugly. Budget the hygiene work.
- Fix the pre-visit leak first: contact centre knowledge base, confirmation flow, cashless check at booking, estimate consistency. Measure no-shows and disputes before and after.
- Stand up one recall programme in one specialty with a natural follow-up cycle, and report the visits it produced in money.
- Put review response and escalation on a named person per unit, with the group supplying tooling and standards.
- Bring experience and growth into one monthly review with the five demand outcomes on the table.
- Take the case to the CFO as three programmes with a return, not as a budget for a department.
Every hospital says the patient comes first. The P&L says what the hospital actually believes. Put experience on it, and see whether the sentence survives.
Questions people ask
Because the experience team measures satisfaction, and satisfaction has no P&L consequence. What moves the P&L is what patients do afterwards — leave a review, come back, bring their family, tell the contact centre a neighbour sent them. Those are demand outcomes, and demand is what growth owns. Experience sits under operations or quality with a feedback form and a quarterly score, and it is cut first when the quarter is tight because nobody can say what it is worth.
A unit with a strong rating and review count converts more of the searches it appears in and pays less per enquiry in paid channels because click-through is higher. A weak profile leaks demand at the moment a patient compares two hospitals side by side — and that leak never appears in any report, because the patient who chose the competitor never entered your funnel. In Tier 2 cities, where the group brand is thinner, almost every patient reads the reviews first.
Fixing the pre-visit leak. A contact centre knowledge base that is actually current, a confirmation flow in the patient’s language, an estimate that does not contradict the counter, a cashless check at booking rather than admission. Each failure there shows up as a lost enquiry, a no-show, a cancelled admission or a one-star review beginning “I called three times”. None of it is glamorous and all of it converts, usually within a quarter.
Take the unit’s patient base and its return rate without any programme. Estimate the higher return rate with one. The difference in visits, multiplied by average revenue per visit, minus the cost of running the programme, is the margin contribution — and it appears nowhere in the current pack because nobody built the programme. Present it as a range with the assumptions visible. The CFO will ask what narrows the range, and that is your data budget approved.
The baseline, and most groups do not have one. The CRM does not track repeat visits cleanly, the same patient exists three times because deduplication failed, or the HIS integration was never completed. So the first experience investment is data hygiene — the least attractive item on any list and the one without which nothing else can be measured. Budget it openly as step one rather than hoping the numbers will be usable.
Five demand outcomes that experience drives. Review velocity and rating by unit, against share of search captured. Return visit rate by unit and specialty, with the recall programme’s contribution isolated. Household growth — registered families adding a second and third patient. Referral-source enquiries, where the patient names a person rather than a channel. And pre-visit failure rate: no-shows, cancelled admissions and estimate disputes. Each has a revenue line behind it and a specific investment that moves it.
The touchpoints that generate a review — discharge, billing counter, the nurse explaining medication, the follow-up call — belong to the experience team. The demand consequence belongs to growth. Right now those two are rarely in the same meeting. Put them in one monthly review with the demand outcomes on the table and give one of them the number. The experience team becomes a partner in delivering funded programmes, and its own budget conversation gets easier.
Less than they fear. Reviews are mostly not about the treatment outcome — they are about discharge, billing, whether medication was explained, whether the follow-up call came. The growth side of this is a follow-up reminder with a booking link, a recall for the overdue chronic patient, and a post-discharge message that asks one question and routes a bad answer to a human within the hour. Clinicians define the follow-up cycle; nobody automates the interpretation.
In three parts. The leak: demand lost before the visit through no-shows, contact centre failures and estimate disputes, valued at the unit’s conversion rate. The return: what a recall and follow-up programme would produce against the patient base, as a range, with data hygiene as step one. The asset: the review profile compared across units and the cost of a programme to move it. Then ask for three programmes owned by growth, not a department budget.
The number of registered families adding a second and third patient. The Indian patient rarely arrives alone — the person booking for an elderly parent will, if the experience holds, book for herself, her children and her in-laws. A CRM structured to hold the family as a unit lets recall address the household and lets the contact centre see a six-year relationship when a name calls. A bad billing counter does not lose a patient; it loses a household.
It matters more there. In a Tier 2 city the group brand carries less, so the review profile is read by almost every patient before they call, and the pre-visit leak — an unanswered call, a wrong estimate — is decisive. A single unit can start with its own baseline, one recall programme in one specialty, and a named person for review response. The arithmetic is the same at any scale; only the data hygiene job is smaller.
When it is funded as a virtue rather than a return. Spend on lounges, signage or a satisfaction survey while the contact centre gives wrong estimates and follow-ups never arrive will not move the P&L. Also wrong: launching recall before the data hygiene is done, because you cannot isolate what the programme produced. Fix the pre-visit leak, get the baseline, and only then argue for the softer investments.
A named person per unit who responds and escalates, with the group supplying tooling and standards. An escalation loop that takes a bad answer to a human within the hour, before it becomes a public review. A prompting mechanism at the touchpoints that actually generate reviews — discharge and billing. And access to the demand data, so the vendor’s work is measured on rating, velocity and share of search, not on volume of responses posted.
Get the baseline — return visit rate, household count, review velocity — for two units, accepting the data will be ugly, and budget the hygiene. Fix the pre-visit leak and measure no-shows and disputes before and after. Stand up one recall programme in one specialty with a natural follow-up cycle and report the visits in money. Put review response on a named person per unit. Then take three programmes with a return to the CFO.
