The 30-second problem statement

Permission granted, you now have about thirty seconds to make a stranger say tell me more. Almost every rep wastes them describing a product.

The anatomy

1. Peer group — "we work with pathology managers at district general trusts". Establishes that you belong in their world.
2. The problem, in their language, specifically — not a category, a scene.
3. Why them, specifically — the trigger. Without this you are a broadcast.
4. An easy question with an escape hatch — one they can answer in a sentence, and which permits a no.

Worked, for a pathology operations manager:

"We work with pathology teams at district generals, and the thing that comes up over and over is specimens that get to the lab fine but can't be evidenced end-to-end when someone asks — so a repeat is ordered, the patient gets re-bled, and it lands as a Datix. I rang you because you've just taken on the hub-and-spoke work for two more sites, which is usually when that starts to bite. Is that close to your world, or have you got it nailed?"

Worked, for a biotech lab operations lead:

"We work with lab ops leads at Series B biotechs, and the pattern's almost always the same: sample tracking lives in a spreadsheet right up until the morning a sample can't be found for an audit. I rang because you're hiring two techs for a second site. Is that a live problem or has someone already fixed it?"

Specific problem, not product pitch

Apply the swap test: could your closest competitor say your sentence, word for word, without changing anything? If yes, it is not a problem statement — it is a category description, and category descriptions are what buyers have learned to tune out.

"We help labs improve efficiency and compliance" passes to any of thirty vendors. "A sample can't be found on the morning of an audit" belongs to one specific bad day that your prospect has either had or fears. Sell the bad day, not the category.

Name-dropping peers correctly

Only real customers — not pilots you hope will convert. Only comparable peers: a large teaching hospital doesn't care what a small private clinic does, so match size, setting and pressure. Name the organisation, not the individual, unless you have that person's explicit permission, and in healthcare assume you don't. Remember that "we work with X" is not "X endorses us" — never let the sentence imply more than the contract does, because you will meet these people at conferences. Three names maximum; more sounds like a slide read aloud. And if you have no logos, use the pattern instead: "the four pathology managers I've spoken to this month all raised the same thing" is honest, specific and requires no customer at all.

Voice from the field

Josh Braun's central argument is that resistance on a cold call is manufactured by the caller: the harder you push to convince, the harder the prospect pushes back, so the job is not to persuade but to surface a problem clearly enough that the prospect persuades themselves. His "poke the bear" questions are designed to make the status quo visible rather than to make the product attractive. (Attributed summary of Braun's published cold-calling material, not a direct quotation.)

Sounding like a person, not a recording

• Use contractions and short sentences. Nobody says "we are" out loud, and sentences over fifteen words need a run-up — which sounds rehearsed.
• Signpost verbally. "Can I give you the twenty-second version?" tells them there's an end in sight.
• Let yourself be slightly imprecise. "The thing they keep saying is — sorry, let me put it properly — specimens get lost between sites." A tiny self-correction is powerful proof you are not reading.
• Ask a real question, then stop talking. The most common failure on the phone is asking a good question and answering it yourself because two seconds of silence felt long. It isn't. Count to three.
• Read it aloud and record it. If it sounds like something you'd say to a colleague it will land; if it sounds like a website, rewrite it.

5. The objection gauntlet

Almost everything said to you in the first sixty seconds is a reflex, not a decision — the prospect doesn't yet have enough information to hold a view, only a defence mechanism. Treat reflexes as reflexes and they mostly dissolve.

Every talk track below uses the same shape: acknowledge (don't agree, don't argue) → reframe or add one piece of information → hand control back with a question. And one governing rule — the one-bounce rule. You get one attempt at each brush-off. One bounce is professional persistence; two makes you the caller they warn colleagues about, and costs you the account for a year.

"Not interested"

"Completely fair — you'd have to be psychic to be interested thirty seconds in. Can I tell you the one thing that made the last three pathology managers stay on the phone, and if it's not you, I'll leave you alone?"

Reasoning: Arguing with "not interested" validates it. Instead, agree that disinterest is the correct response to no information, which reframes the objection as premature rather than wrong. The promise to leave them alone is the price of the ask — and you must honour it.

"Send me an email"

"Happy to — I'll do that today. So I don't send you something generic that you'll delete: is specimen traceability across the two new sites actually live for you this year, or is something else at the top of the list?"

Reasoning: Never fight this one — it is usually a polite exit, and fighting a polite exit makes you impolite. Agreeing drops their guard so the question can do the real work: either you learn what matters and your email becomes relevant, or you disqualify in sixty seconds. A second follow-up — "and who else would need to see it?" — quietly maps the buying committee.

"I'm busy"

"I'd be worried if you weren't. Two options: I take ninety seconds now, or I ring you Thursday morning — which is less annoying?"

Reasoning: "I'm busy" is usually true and rarely a rejection, so treat it as scheduling, not refusal. Offering two concrete options converts a yes/no into a choice, and naming a specific day makes the callback real. If they choose Thursday, that call is warm — you now have permission.

"We already have a supplier"

"Good — I'd be surprised if you didn't, most trusts your size do. I'm not ringing to replace anyone. The reason I called is that the teams who already have a system are usually the ones who find the gap between what the system tracks and what an auditor asks for. Where does yours sit on that?"

Reasoning: Attacking an incumbent attacks the prospect's own past decision, which they will defend. Declining to replace them removes the fight; a question about a specific limitation of the category then invites them to complain — and complaint is the beginning of discovery. Never disparage a named competitor on a cold call.

"How did you get my number?"

"Fair question. It's on your trust's published directory — and for what it's worth we screen everything against the TPS and CTPS before we call. If you'd rather I didn't ring again, say the word and I'll take you off permanently."

Reasoning: The one objection where only the plain truth works — and where something precise about compliance converts suspicion into credibility in a single sentence. Offering suppression unprompted is disarming, and a legal obligation if taken up. If your answer to "where did you get this" is "I don't know", the problem is your data supplier, not the call.

"We've no budget"

"That's normal at this point — nobody's got a line item for something they haven't seen. I'm not asking for budget, I'm asking whether the problem's real. If it is, the business case is a separate conversation. Is it real?"

Reasoning: In enterprise and public-sector sales, budget often doesn't exist until a champion builds a case for it. Treating "no budget" as final disqualifies deals that were never disqualified; treating it as something to overcome is worse. Separating "is the problem real?" from "is there money?" is the whole move — the same logic as MEDDPICC's Identify pain preceding Metrics.

"Call me next quarter"

"I can do that. Just so I'm not ringing you blind in April — what changes between now and then? Is it budget, a project finishing, or is it just not important enough yet? Any of those is a fine answer."

Reasoning: "Next quarter" is a soft no most of the time — a practitioner rule of thumb, not a measured figure — and the diary entry it produces is worthless. The question tests it. A real event in April gives you a compelling event and a reason to call; "it's just not a priority" earns you an honest disqualification, which is worth more than a fake callback. Offering "not important enough yet" as an acceptable answer is what makes them tell you the truth.

"Is this a sales call?"

"Yes. I sell specimen-tracking software and I rang because of the multi-site work you've taken on. Whether it's relevant is entirely up to you — want the thirty-second version?"

Reasoning: Say yes, immediately, without hedging. Evasion is dishonest and — as the ICO case in section 1 shows — precisely the behaviour regulators cite. It is also disarming: the prospect asked expecting a squirm and got a straight answer, which is rare enough to buy the next fifteen seconds.

The gatekeeper: four approaches

A gatekeeper — switchboard, ward clerk, PA, lab admin — is not an obstacle. They are the most informed person you'll speak to that morning, and usually helpful if you give them something to work with.

1. The straight ask. Confident, unhurried, no explanation offered.

"Morning — could you put me through to Ruth Vance in pathology, please?"

Reasoning: Most calls are transferred without challenge if you sound like someone who expects to be. Over-explaining invites screening: say the name and the department, add nothing.

2. The help-me-out. For when you're challenged.

"You'll probably be able to help me more than she can, actually. I'm trying to work out who owns specimen tracking across the two new sites — is that Ruth, or does that sit with someone in digital?"

Reasoning: Asking for expertise rather than access recasts them from guard to guide — which frequently produces a better name than the one you had, and often a direct dial.

3. The specificity play. For when you're asked what it's regarding.

"It's about specimen traceability between the hub and the spoke sites — she'll know the context. I can hold if she's mid-something."

Reasoning: Vagueness ("just a quick chat") is what a gatekeeper is trained to block. A precise, unglamorous, operational subject line sounds like business, not like selling. Never claim she is expecting you.

4. The route-around. For when the front door is shut: ring at 8:10am or 5:40pm, when switchboards are lighter and senior people answer their own phones; or ring an adjacent department and ask for an internal transfer, which rarely gets screened; or simply ask, "when's she usually at her desk? I'd rather not keep bothering you."

Reasoning: Persistence is fine; deception is not. Never say you're expected, never imply an existing relationship, never claim to be returning a call. Beyond ethics, gatekeepers talk to each other and have long memories.

Voicemail: the first and the last

Voicemails almost never generate a call back. Their job is to make your next dial less cold, and to make your email land against a name that is already familiar. Leave one on roughly the first and last attempt, not every time.

The first voicemail — under twenty seconds, no ask:

"Ruth, it's Alex Rowe at Corvus Labs, 07700 900123. I rang about specimen traceability across your two new sites — I've seen it bite other trusts at exactly this stage. I'll try you again Thursday morning. Nothing needed from you."

Reasoning: Name and number first and slowly, because that's what gets replayed. One concrete reason, no pitch. "Nothing needed from you" removes the obligation, which removes the reason to delete — and naming when you'll ring back makes the next dial an expected call. Send a two-line email within the hour, same subject.

The final voicemail — the professional close of the loop:

"Ruth, Alex Rowe at Corvus Labs again — last one from me. I've rung a few times about specimen traceability and clearly got the timing or the person wrong, so I'll stop. If it becomes live, my number's 07700 900123. Good luck with the site move."

Reasoning: Break-up messages get disproportionate responses because they remove pressure and signal self-respect. This one also keeps the door open without a hint of grievance. Reps who sign off graciously get called back months later; reps who sign off passive-aggressively never do.

Field note

Learn these eight as shapes, not as sentences. A rep reciting a memorised objection response is audibly reciting, and prospects hear the seam between your natural voice and your script the moment you hit one. The way through is to write each track in your own idiom, say it aloud thirty times until the words stop being words, and then let yourself paraphrase on the call. The published talk tracks — including these — are worked examples of a structure, and the structure is the transferable part. If you can only remember one thing under pressure, remember acknowledge, then ask a question: it recovers almost any moment.