The canonical objections — worked examples

The same nine come up in almost every NHS, clinical-AI and lab-software deal (strictly, 4.5 is usually a stall and 4.9 a condition — handled here because you'll meet them in the same breath). In these dialogues "you" sell clinical AI to an NHS trust or lab software to a life-sciences company. They illustrate the process; the questions matter more than the answers.

4.1 "It's too expensive"

Usually a value or comparison problem, rarely pure price. Never lead with a discount.

CDIO (Chief Digital Information Officer): "£120k a year is more than we can justify." You: "Fair — it's a serious number. What are you comparing it against?" CDIO: "Honestly? Doing nothing." You: "But the backlog is being handled somehow — outsourced reporting, overtime?" CDIO: "Both. About £400k last year." You: "So 'doing nothing' costs £400k. If we built the model with your reporting lead and it showed payback inside a year — would price still be the blocker, or is anything else in the way?" CDIO: "If the numbers held up, no." You: "Then let's build them — thirty minutes with your reporting lead this week?"

Note the moves: acknowledge, explore the comparison, reframe against the true alternative's cost, isolate, close on a next step.

4.2 "There's no budget"

Different from "too expensive": this is about whose money and when. The NHS financial year runs April–March, budgets largely set in the autumn/winter planning round — so "no budget" often means "not in this year's plan": a timing problem you can work.

Service manager: "There's genuinely no budget for this." You: "Understood — I won't ask you to conjure money. How does it work here: when does next year's planning start, and whose budget would this sit in?" Manager: "October, and it'd be the divisional director's." You: "Two thoughts. Sometimes this gets funded off-cycle from transformation or digital programmes — anything like that in flight? And if not, shall we draft the business case together in September so it lands in the October round with your director's name on it?" Manager: "The transformation route might exist. And yes to September."

You've converted "no" into two live paths and a diary entry. "No budget" plus no interest in either path is a stall in a budget costume — qualify accordingly.

4.3 "We already use a competitor"

Never criticise the incumbent — your prospect chose it, so you'd be criticising them. Explore for gaps; find the renewal date.

Lab operations lead: "We already run [incumbent ELN] across the labs." (ELN = electronic lab notebook.) You: "Makes sense. What's it doing well for you?" Lead: "The chemistry teams like it fine." You: "And if you could change one thing?" Lead: "The biologics group ignores it. Everything ends up in spreadsheets." You: "We see that pattern a lot. Would it be worth letting the biologics group trial us alongside it for one project, so you compare evidence rather than brochures? And when does the current contract renew?"

That's the wedge: get in beside the incumbent on the gap, prove value, expand at renewal. Timelines beat arguments here.

4.4 "It's not a priority right now"

Means you haven't connected to whatever is the priority — or the deal isn't qualified.

COO: "I see the value, but it's not a priority this year." You: "Fair — you can't run twelve priorities. What are the top two or three?" COO: "Elective recovery. The waiting list." You: "Then tell me if this is a stretch: trusts using us have cut reporting turnaround, which is one constraint on elective throughput. If we showed a credible link to waiting-list performance, does this become part of the priority rather than competing with it?" COO: "If the link is credible, yes."

If you can't honestly connect, don't force it: "Would it be sensible if I checked back when the picture changes — say February?" Graceful patience keeps doors open.

4.5 "Just send me some information"

The politest brush-off in the language — or a genuine request. You find out which by attaching a next step.

Manager: "Send me some information and I'll take a look." You: "Happily. So it's useful rather than a generic deck — what should it cover?" Manager: "The information-governance side, and pricing structure." You: "I'll send exactly that today. Once you've read it, what usually happens next on your side?" Manager: "I'd discuss it with the IG lead." You: "Shall we pencil twenty minutes with the three of us for Thursday week — and if the material doesn't warrant it, cancel with one line?"

Refusal of any next step tells you the truth cheaply: brush-off. File it rather than crafting a document nobody will read.

4.6 "We tried something like this and it failed"

Discovery gold in disguise: the failure story tells you exactly what this buyer fears and what your deal must prove.

Clinical director: "We piloted an AI chest X-ray tool in 2023. It went nowhere." You: "Genuinely useful to know — and it explains some healthy scepticism. What actually killed it?" Director: "Radiologists had to log into a separate portal. Nobody did. Usage flatlined by month two." You: "So the algorithm may have been fine — it was workflow. Everything we do surfaces inside your existing PACS (Picture Archiving and Communication System — the radiology image viewer): no second screen, no second login. But I'd rather show than claim — would it help to speak to a clinical director at a trust with exactly that failed-pilot history before they worked with us?"

You've validated their experience, differentiated against the specific failure mode, and offered peer evidence — the most credible currency in healthcare sales.

4.7 "The clinicians won't adopt it"

Usually one of three roots: no clinical champion, a workflow that adds clicks, or scar tissue from 4.6. Explore which.

Programme manager: "Honestly, the consultants won't use it. They hate new systems." You: "They're right to — most new systems add work. Which group worries you most?" PM: "The vascular surgeons. They barely tolerate the EPR." (EPR = electronic patient record.) You: "Then two things must be true before anyone asks them to adopt anything. One: it saves them time in week one, not in a year. Two: one of their own leads it, not IT. Is there a vascular consultant vocal about this problem? Our strongest deployments started with one grumpy sceptic co-designing the pilot — success criteria set with them, not for them."

You've reframed adoption as a design problem you have a method for, and recruited them into finding the champion.

4.8 "What about data protection and IG?"

IG (information governance) is the NHS umbrella term for lawful, safe handling of patient data. This is a good objection — nobody scrutinises data flows for a product they don't intend to buy. Answer crisply, never bluff, route to their specialists.

IG lead: "Where does patient data actually go, and who's the controller?" You: "You should get precise answers. Data is processed and stored in UK data centres and never leaves the UK. The trust remains data controller — deciding why and how data is used — and we're the data processor, acting only on your instructions under a standard NHS data-processing agreement. We support your DPIA (Data Protection Impact Assessment, required under UK GDPR for high-risk processing like this) with a pre-filled template; we hold 'Standards Met' on the DSPT (Data Security and Protection Toolkit, the NHS's annual security self-assessment) and a completed DTAC (Digital Technology Assessment Criteria, the NHS baseline check for digital health tools). Shall I send the full IG pack and set up a call with your DPO?"

A direct factual question from a specialist gets a direct answer — "explore first" applies to concerns, not information requests.

The specifics vary by employer; the behaviour to copy: treat it as a buying signal, know your compliance artefacts cold, volunteer the meeting with their IG people.

Sellers who can hold this conversation without fetching an engineer have a real edge — if you come from a technical or scientific background, this is where it pays; if you don't, the vocabulary above is entirely learnable, and learning it cold is one of the fastest credibility wins available to a new seller.

4.9 "We'd have to go through procurement"

Not an objection — a condition (section 3). Welcome it and build it into the plan.

Head of service: "Anything like this has to go through procurement." You: "Absolutely — better to map that now than discover it at month nine. How does it usually work here: direct award under a framework, or full tender?" (A framework is a pre-approved public-sector purchasing route — e.g. G-Cloud for cloud software — allowing purchase without a full open tender, a formal competitive bidding process.) Head: "Under £100k we can usually direct-award off a framework." You: "Helpful — we're on G-Cloud, which keeps this in that lane. Could we bring your procurement contact into the next conversation, and I'll draft a timeline including their steps so nothing surprises us?"

Sellers who fear procurement get ambushed by it; sellers who befriend it early turn it into a project plan — in the NHS, a competitive advantage in itself.