This post is for the founder or first sales hire at a healthtech company that has a working product and a few warm conversations inside Indian hospitals, but no clear picture of who actually decides. It also suits the marketing lead who has been asked to "build content for hospitals" without being told which hospital role that content is meant to move.
The question it answers is narrow: when a hospital buys software or a connected device, who is in the chain between the first meeting and a signed purchase order, what does each person worry about, and what should you have ready for them? The map below is a working framework drawn from how hospitals are generally organised, not a survey. Every hospital differs, and you should treat the roles as hypotheses to confirm in your first two calls.
Why the person who likes your product rarely signs
In most Indian hospitals, the person who wants your product is a clinician, a department head or an operations manager. The person who can approve spend is someone else. Between them sit IT, finance, purchase, sometimes legal, and in a chain, a central team that may not sit in the same city as the hospital you are talking to.
A founder who meets an enthusiastic head of department and reads that as a deal has found a champion, which is useful, but has not yet found a buyer. The practical consequence is that you need a map of the chain written down for each account, and a plan for each person on it.
Hospital types change the shape of the chain. A single-site trust hospital may let a medical director or managing trustee approve a modest spend in one meeting. A corporate chain usually routes anything touching clinical systems or patient data through a central IT and procurement function. A government or public-sector hospital buys through formal procedures; the national Government e-Marketplace is one route for public buyers, and your product or category may need to be listed or the purchase may need a tender. Ask early which route applies instead of assuming.
The buyer map
Use the table as a starting template. The "typical objection" column describes the concerns these roles commonly raise, phrased as questions you can prepare for. Confirm each one with the actual person.
| Role | What they own | Typical objection | What you bring |
|---|---|---|---|
| Medical director or CMO | Clinical quality, doctor relations, patient experience | "Will my doctors use it, and will it add to their workload?" | A one-page workflow showing steps removed from the clinician's day; a clinical reviewer's name on the product description |
| Head of department (clinical champion) | Day-to-day use in one specialty | "Does this fit how we really work?" | A short demo on their own scenario; a trial plan that needs little training |
| CIO or head of IT | Systems, integration, uptime, security | "Does it connect to our HIS, and who supports it at 2 a.m.?" | Integration notes, a data-flow diagram, a support and escalation sheet |
| CFO or finance head | Budget, payback, cash flow | "What does it cost over three years, and what does it replace?" | A cost model with the hospital's own assumptions, clearly labelled |
| Purchase or materials head | Vendor onboarding, quotations, terms | "Is the paperwork complete, and can we compare you with other vendors?" | A complete vendor pack: registration documents, quotation format, references |
| Nursing head or operations head | Floor-level process, staffing | "Will this slow the ward or need extra staff?" | A walk-through of the nursing steps and what changes |
| Legal or compliance | Contracts, data protection, liability | "Who is responsible if data leaks or the tool is wrong?" | A plain data-processing summary and a draft contract with limits of liability |
| Managing director, promoter or trustee | Final approval, strategic fit | "Does this move our priorities?" | A two-line case tied to the hospital's stated goals |
Not every hospital has all of these. In a smaller facility one person may hold three of them. The value of the table is that it stops you skipping the roles that cause late-stage delays.
Champion, economic buyer, blocker
Beyond the formal titles, assign every person on the chain one of three working roles.
- Champion: wants the outcome and will spend political capital on it. Usually clinical or operational.
- Economic buyer: controls the budget line. Usually finance, the medical director, or the promoter.
- Blocker: can stop the deal without being able to approve it. Often IT, legal or purchase, because their role is to protect the hospital from risk.
A single person can hold more than one role, and roles can change during the deal. Record them in your CRM, not in your head. If you use a pipeline tool, a short custom field for "role in deal" on each contact is enough. Pioneer CRM is how we keep enquiries, owners and follow-ups together at Branding Pioneers, and any system that lets you attach several contacts to one deal will do the same job.
A useful rule: do not ask for a purchase decision from a champion. Ask them to introduce you to the economic buyer and to tell you what the blocker will ask. A champion who cannot name the economic buyer is a warning sign.
Mapping an account in the first two calls
You do not need a formal research project. Two conversations and a few public sources are enough to get a working map.
- Ask how a similar tool was bought last time. "When the hospital last bought software for the lab or the billing desk, who was involved?" The answer usually names the real chain.
- Ask who would be unhappy if this went wrong. That person is often a blocker you have not met.
- Ask about the approval threshold. Many hospitals have a spend level above which a committee or the promoter must sign. You do not need the number from a stranger; you need to know whether one exists.
- Ask whether a pilot goes through the same route as a purchase. Some hospitals treat a free pilot as informal; others require the same IT and legal review. This changes your timeline by months.
- Check public information. Hospital websites, annual reports of listed chains, press releases and the leadership pages often name the CIO, CFO and medical director. Use them to confirm names, not to start cold outreach to a stranger with a pitch.
Write the result as a single page per account: names, roles, working role (champion, economic buyer, blocker, unknown), what each has asked for, and the next step owner on your side.
