47 ready-to-use artefacts
Swipe file — scripts, templates & talk tracks
On this page
47 ready-to-use artefacts matching the Sales Academy modules — copy the structure, personalise every placeholder with real research before sending, and remember the honest rule: templates get replies when personalised; copied verbatim they get ignored.
Cold emails (8)
Every email below follows the Module 3 structure: short subject (2–5 words, casual lower-case), personalised opener proving research, their problem in their language, one proof point, low-friction interest-based CTA. Keep the body 60–120 words. Personalise at two of three levels: account, person, timing.
1. First touch — hiring signal (biotech-flavoured)
Subject: sample tracking at {SITE_NAME}
Hi {FIRST_NAME},
Saw you're hiring {NUMBER} lab technicians for the new {SITE_NAME} facility — congratulations on the expansion. Scaling lab operations across sites is usually the point where spreadsheet-based sample tracking starts costing real money: mislocated samples, failed audits, freezer capacity bought that isn't needed.
We help teams like {PEER_BIOTECH} manage sample inventory across sites — they recovered roughly {PERCENTAGE}% of freezer capacity in the first quarter from visibility alone.
How are you handling sample tracking across sites today?
{YOUR_NAME}
The trigger (job adverts = expansion) is timing-level personalisation, and the CTA is a discovery question — any answer starts a conversation.
2. First touch — funding/news trigger
Subject: congrats on the series B
Hi {FIRST_NAME},
Congratulations on the {AMOUNT} raise — the {PUBLICATION} piece mentioned you're doubling the {TEAM_NAME} team over the next year.
That growth stage is usually when {PROBLEM_AREA} stops being a spreadsheet problem and starts being a hiring-plan problem: every new starter inherits the workarounds. {PEER_COMPANY} hit the same point at a similar headcount and cut {PROCESS} time from {BEFORE} to {AFTER} in their first quarter with us.
Is {PROBLEM_AREA} on the roadmap for the post-raise build-out, or further down the list?
{YOUR_NAME}
Funding news is public and timing-level; the CTA asks about priority, not for a meeting.
3. First touch — problem-led (NHS-flavoured)
Subject: reporting backlog & the 28-day standard
Hi {FIRST_NAME},
Your trust's {MONTH} board papers flag {DEPARTMENT} reporting turnaround as a risk to the 28-day Faster Diagnosis Standard — and the published digital strategy commits to evaluated AI adoption this financial year.
That combination is exactly where we work: {PRODUCT} triages {MODALITY} imaging so urgent findings are reported first. {PEER_TRUST} cut median time-to-report for critical findings by {PERCENTAGE}% in a published evaluation, on their existing PACS infrastructure.
Is AI triage part of the plan for this financial year, or later? Happy to share the evaluation either way.
{YOUR_NAME}
Board papers are public — reading them is a genuine differentiator, and the problem cited is a standard they're measured on.
4. Bump / one-line follow-up
Subject: RE: {ORIGINAL_SUBJECT}
Hi {FIRST_NAME} — any reaction to the below? Even a "not relevant" saves us both the follow-ups.
{YOUR_NAME}
Send 2–4 days after the first touch, as a reply in the same thread. It works because it is easy to answer — never dress it up as "just checking in".
5. Value-add follow-up (new angle)
Subject: {PEER_ORGANISATION}'s numbers
Hi {FIRST_NAME},
Different angle from my last note. {PEER_ORGANISATION} published their evaluation of {SOLUTION_CATEGORY} last month — the headline: {SPECIFIC_RESULT} within {TIMEFRAME}, measured against {METRIC} rather than vendor claims.
Two pages, independently written, and directly comparable to your situation given {SHARED_CHARACTERISTIC}. Worth a read even if you never speak to us: {WHAT_THEY_LEARNED_THE_HARD_WAY} is the section most people quote back.
Want me to send it over?
{YOUR_NAME}
Every touch must add something new — an insight, asset or angle. This one offers an asset that is useful whether or not they buy.
6. Break-up email
Subject: closing the file
Hi {FIRST_NAME},
I've dropped you a few notes about {PROBLEM_AREA} and haven't heard back — which usually means the timing isn't right, priorities have shifted, or this simply isn't a problem for you.
I don't want to clutter your inbox, so I'll assume the timing isn't right and close the file for now.
If I've misread it, one line back and we'll pick it straight up. Either way — good luck with {RELEVANT_INITIATIVE}.
{YOUR_NAME}
Send after the cadence completes (around day 21). It's costless to answer and gives a genuine no permission to be said — these often get the most replies of the whole sequence. Send it only when you mean it.
7. Re-engagement after ghosting (new trigger)
Subject: {NEW_TRIGGER_EVENT} — picking this back up?
Hi {FIRST_NAME},
When we spoke in {MONTH} you were interested in {PROBLEM_AREA}, but the timing wasn't right — so I closed the file as promised.
Reopening it for one reason: {NEW_TRIGGER_EVENT} — e.g. your {PUBLISHED_PLAN} now names {RELEVANT_COMMITMENT}, which changes the "why now". Since we last spoke, {PEER_ORGANISATION} has gone live and published {RESULT}.
Has {NEW_TRIGGER_EVENT} moved this up the list, or is the picture unchanged?
{YOUR_NAME}
Only re-engage with a genuine new trigger — a compelling event on their side, never your own quota. Reference the earlier conversation honestly; pretending it didn't happen reads as spam.
8. Referral-ask to a colleague
Subject: right person for {TOPIC}?
Hi {FIRST_NAME},
I wrote to {COLLEAGUE_NAME} about {PROBLEM_AREA} — specifically {ONE_LINE_PROBLEM_SUMMARY} — but I may have the wrong door.
Rather than guess my way around the org chart: are you the right person for {TOPIC}, or could you point me to whoever owns it? A one-word reply with a name is genuinely helpful, and I'll take it from there.
Either way, thanks — and apologies for the cold email.
{YOUR_NAME}
Asking to be redirected is a low-friction CTA that most people will answer — and the answer starts mapping the buying committee.
Cold call scripts (6)
The Module 3 structure: acknowledge the interruption, earn each next 20 seconds, aim for a conversation and a next step — not a pitch.
9. Permission-based opener
"Hi {FIRST_NAME} — {YOUR_NAME} calling from {COMPANY}. I'll be honest,
this is a cold call — can I take 30 seconds to tell you why I rang,
and you can tell me if it's relevant?"
[If yes → 30-second problem statement.]
[If no] "Completely fair. Is there a better time this week, or is it
a hard no? Either answer is fine."
It trades a little momentum for a lot of trust: the prospect keeps control, so they don't need to seize it by hanging up. Most people, asked politely for 30 seconds, grant them.
10. The 30-second problem statement
"The reason for the call — we work with {PERSONA_PLURAL} at
{ICP_DESCRIPTION}, and the pattern we keep hearing is that
{PROBLEM_IN_THEIR_WORDS} — usually surfacing as {CONCRETE_SYMPTOM}.
I saw {TRIGGER — e.g. you're scaling to a second site / your board
papers flag the backlog}, which is usually when that bites.
Is that close to your world, or have you got it solved?"
Anatomy: who we work with → the problem in their words → why I called you specifically → an easy question. The escape hatch ("or have you got it solved?") gives permission to say no — which paradoxically increases honest yeses.
11. "Just send me an email" response
"Happy to. So I don't send you generic rubbish — is
{SPECIFIC_PROBLEM} actually a live issue for you right now, or is
something else at the top of your list?"
[They answer → note it, tailor the email to it.]
"Useful — I'll send exactly that today. Who else on your side would
need to see it?"
Never fight the brush-off; use it. Either you learn what matters (and your email becomes relevant), or you disqualify in sixty seconds — and "who else would need to see it?" quietly maps the buying committee.
12. Gatekeeper approach
"Morning — {YOUR_NAME} from {COMPANY}. I'm hoping to reach
{PROSPECT_NAME} about {TOPIC_IN_PLAIN_WORDS}. Are they the right
person for that, or is someone else closer to it?"
[If asked "what's it regarding?"]
"Of course — we work with {PERSONA_PLURAL} on {PROBLEM_AREA}, and I
wanted to ask {PROSPECT_NAME} whether it's relevant to {ORGANISATION}
before sending anything over. Is there a better time to catch them —
or would you suggest email first?"
Be straightforwardly honest — gatekeepers hear every trick daily and reward the callers who don't try one. Treat them as the expert on the organisation they are, and take any advice they offer.
13. Voicemail — first attempt
"Hi {FIRST_NAME}, {YOUR_NAME} from {COMPANY}. Calling because
{ONE_LINE_TRIGGER — e.g. your board papers flag the reporting
backlog} — we've helped {PEER_ORGANISATION} with exactly that, and I
wanted to ask one question about how you're handling it.
I'll send you an email now with '{EMAIL_SUBJECT}' in the subject
line so you can deal with it in ten seconds. Otherwise I'm on
{PHONE_NUMBER}. Thanks, {FIRST_NAME}."
Under 30 seconds, one trigger, one reason. Don't expect a call back — the job of a first voicemail is to make your name and email familiar, so pair it with the email the same day.
14. Voicemail — final attempt (break-up)
"Hi {FIRST_NAME}, {YOUR_NAME} at {COMPANY} — last call from me, I
promise. I've tried you a few times about {PROBLEM_AREA} and I'll
take the silence as 'not right now', so I'll close the file and stop
calling.
If I've got that wrong, one line to {EMAIL_ADDRESS} or a call to
{PHONE_NUMBER} and we'll pick it straight up. Either way, good luck
with {RELEVANT_INITIATIVE}. Thanks, {FIRST_NAME}."
The spoken twin of the break-up email — warm, pressure-free, and it genuinely lets go. Log the outcome and move the account to nurture.
Objection talk tracks (12)
All twelve follow the Module 5 process: listen → acknowledge → explore (and isolate) → respond → confirm. Never respond to an objection you haven't explored — the surface words are rarely the root concern. One carve-out: factual security/compliance questions (see #23) get direct answers first; explore applies to concerns. These are talk tracks, not scripts: the questions matter more than the answers.
15. "It's too expensive"
Acknowledge: "Fair — it's a serious number, and budgets are brutal this year."
Explore: "Can I ask what you're comparing it against?"
[Often the answer is "doing nothing" — cost that alternative:
"But the problem's being handled somehow — overtime, locums,
outsourcing? What did that cost last year?"]
Isolate: "If we built the numbers together and they showed payback inside
{TIMEFRAME} — would price still be the blocker, or is anything
else in the way?"
Confirm: "Then let's build them — {NEXT_STEP} this week?"
Usually a value or comparison problem, rarely pure price. Never lead with a discount — reframe against the true alternative's cost.
16. "There's no budget"
Acknowledge: "Understood — I won't ask you to conjure money that isn't there."
Explore: "How does it work here: when does next year's planning round
start, and whose budget would this sit in?"
Respond: "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
{MONTH} so it lands in the planning round with
{BUDGET_HOLDER}'s name on it?"
Confirm: "Shall I put {DATE} in the diary for that?"
"No budget" is about whose money and when, not price — in the NHS, budgets are largely set in the autumn/winter round. No interest in either path marks it as a stall in a budget costume: qualify accordingly.
17. "We already use a competitor"
Acknowledge: "Makes sense — most teams we work with had something in place."
Explore: "What's it doing well for you?" [Let them defend it — they
chose it.] "And if you could change one thing?"
Respond: "That gap is exactly where we usually start. Would it be worth
{AFFECTED_TEAM} trialling us alongside it on one
{PROJECT_TYPE}, so you compare evidence rather than brochures?"
Confirm: "And when does the current contract come up for renewal?"
Never criticise the incumbent — your prospect chose it, so you'd be criticising them. Wedge in beside it on the gap, prove value, expand at renewal: timelines beat arguments.
18. "It's not a priority right now"
Acknowledge: "Fair — you can't run twelve priorities at once."
Explore: "What are the top two or three this year?"
Respond: "Tell me if this is a stretch: {YOUR_OUTCOME} is one constraint
on {THEIR_STATED_PRIORITY} — {PEER_ORGANISATION} used it for
exactly that. If we showed a credible link, does this become
part of the priority rather than competing with it?"
Confirm: "And if I can't show that link honestly — would it be sensible
for me to check back when the picture changes, say {MONTH}?"
"Not a priority" means you haven't connected to whatever is the priority — or the deal isn't qualified. If you can't honestly connect, don't force it; graceful patience keeps doors open.
19. "Just send me some information"
Acknowledge: "Happily."
Explore: "So it's useful rather than a generic deck — what should it
cover?"
Respond: "I'll send exactly that today. Once you've read it, what
usually happens next on your side?"
Confirm: "Shall we pencil twenty minutes with {STAKEHOLDERS} for
{DATE} — and if the material doesn't warrant it, cancel with
one line?"
The politest brush-off in the language — or a genuine request. Attaching a next step tells you which, cheaply: refusal of any next step means file it rather than crafting a document nobody will read.
20. "We tried something like this before and it failed"
Acknowledge: "Genuinely useful to know — and it explains some healthy
scepticism. Most people in your position would feel the same."
Explore: "What actually killed it — the tool, the workflow, the
training, or nobody owning it?"
Respond: [To the specific failure mode only:] "So the {COMPONENT} may
have been fine — it was {ROOT_CAUSE}. Here's how we're
different on exactly that: {SPECIFIC_DIFFERENCE}. But I'd
rather show than claim — would it help to speak to
{PEER_ROLE} at {PEER_ORGANISATION}, who had the same failed
history before working with us?"
Confirm: "Does that address the core of what went wrong last time, or
is there more to it?"
Discovery gold in disguise: the failure story tells you exactly what this buyer fears and what your deal must prove. Never defend the category or promise "this time is different" before you know what last time actually was.
21. "Call me next quarter"
Acknowledge: "Of course — happy to time this properly."
Explore: "So I don't misread it: is it genuinely timing, or is
something about the approach not landing?"
[If timing:] "What changes next quarter — budget round,
project finishing, someone joining?"
Respond: "Then let's make it real: I'll book {DATE} now, and in the
meantime I'll send {RELEVANT_ASSET} so you arrive with
evidence rather than memory of one call."
Confirm: "If {TRIGGER} moves, will you tell me — and I'll do the same?"
A stall, not an objection — delay without content. Probe it into either a real objection or the truth; if it survives two gentle probes, the deal probably isn't qualified — downgrade it rather than chase it.
22. "The clinicians won't adopt it"
Acknowledge: "They're right to be sceptical — most new systems add work."
Explore: "Which group worries you most? And what's the history —
a failed pilot, or just too many clicks in the day already?"
Respond: "Two things have to be true before anyone asks them to adopt
anything: it saves them time in week one, not in a year, and
one of their own leads it, not IT. Is there a {SPECIALTY}
consultant who's vocal about {PROBLEM}? Our strongest
deployments started with one grumpy sceptic co-designing the
pilot — success criteria set with them, not for them."
Confirm: "If we found that person, does the adoption concern change
shape?"
Usually one of three roots: no clinical champion, a workflow that adds clicks, or scar tissue from a failed pilot. Reframe adoption as a design problem you have a method for — and recruit the objector into finding the champion.
23. "What about data protection?"
Acknowledge: "You should get precise answers — and it's the right question."
Respond: "{DATA_RESIDENCY_STATEMENT — where data is processed and
stored; state only what is actually true of your product}.
{ORGANISATION} remains data controller; we're the data
processor, acting only on your instructions under a
standard {DPA_TYPE}. {DPIA_SUPPORT_STATEMENT — describe the
DPIA support you actually offer}, and we hold
{COMPLIANCE_ARTEFACTS — e.g. DSPT 'Standards Met', a
completed DTAC, ISO 27001 — list only those you hold}."
Explore: "What does your IG process usually need from a supplier at
this stage?"
Confirm: "Shall I send the full IG pack and set up a call with your
DPO or IG lead this week?"
A good objection — nobody scrutinises data flows for a product they don't intend to buy. One rule governs every placeholder here: never claim what you can't evidence. Know your compliance artefacts cold, never bluff, and volunteer the meeting with their specialists rather than dreading it.
24. "We'd have to go through procurement"
Acknowledge: "Absolutely — better to map that now than discover it at
month nine."
Explore: "How does it usually work here: direct award under a
framework, or full tender? And is there a threshold?"
Respond: "Helpful — we're on {FRAMEWORK — e.g. G-Cloud}, which keeps
this in the direct-award lane. Could we bring your
procurement contact into the next conversation?"
Confirm: "I'll draft a timeline including their steps — mutual action
plan, owners and dates both sides — so nothing surprises us."
Not an objection — a condition. You don't overcome conditions; you meet them and build them into the plan. Sellers who befriend procurement early turn it into a project plan — in the NHS, a competitive advantage in itself.
25. "I'm not the right person"
Acknowledge: "Thanks for telling me straight — better than six polite
meetings with the wrong door."
Explore: "Who owns {PROBLEM_AREA} here? And is it worth me mentioning
you pointed me their way, or would you rather I didn't?"
Respond: "One question before I go, since you'll know: is
{PROBLEM} actually a live issue here, or am I barking up the
wrong tree entirely?"
Confirm: "Really helpful — I'll write to {NAME} and copy you out of it.
Thanks for the steer."
Take the redirect gracefully and mine it: a name, a warm-ish handover, and one insider's read on whether the pain is real. This person may become a coach even though they'll never be the buyer.
26. "We're happy with how we do things now"
Acknowledge: "That's fair — and if it's genuinely working, you shouldn't
change it."
Explore: "Can I ask how you're measuring that? When {PROCESS} has a
bad week, what does it look like — and what did
{SYMPTOM — e.g. the backlog, the failed audit, the overtime}
cost last year?"
Respond: "That's the comparison I'd want on the table: not us versus
your current way, but your current way versus what it's
quietly costing. {PEER_ORGANISATION} thought the same until
they measured it — {SPECIFIC_FINDING}."
Confirm: "Would it be worth quantifying that together, even if the
answer is 'stay as you are'?"
The status quo is the default winner of every evaluation — free, installed and blameless — and "no decision" kills more deals than any competitor. You beat it with the quantified cost of inaction, never with a feature list.
LinkedIn (6)
Your profile is part of every channel — buyers check who you are before replying to anything. Connection notes have a 300-character limit; keep them shorter.
27. Connection note — mutual interest
Hi {FIRST_NAME} — I keep seeing your name in {SHARED_SPACE — e.g. the
UK health-tech community / {GROUP_NAME}}, and we're both working on
{SHARED_TOPIC} from different angles. No pitch — I'd just rather have
the people doing interesting work in this space in my feed. {YOUR_NAME}
"No pitch" only works if it's true — the first message after connecting must not be a pitch either.
28. Connection note — content-triggered
Hi {FIRST_NAME} — your post on {TOPIC} landed with me, especially
{SPECIFIC_POINT}. I see the same pattern from the {YOUR_ANGLE} side.
Connecting so I catch the next one. {YOUR_NAME}
Naming the specific point is the whole trick — it proves you read it rather than clicked "connect" from a list.
29. Connection note — event
Hi {FIRST_NAME} — we were both at {EVENT_NAME} {yesterday/last week}.
Your question in the {SESSION_NAME} session about {TOPIC} was the best
one of the day — I didn't manage to catch you afterwards. Good to
connect. {YOUR_NAME}
Works even if you never actually spoke — a shared room plus a specific detail is warmer than most first emails.
30. Post-connection message (value-first, no pitch-slap)
Thanks for connecting, {FIRST_NAME}. No agenda — but since you're
working on {THEIR_TOPIC}, you might find this useful:
{ASSET — e.g. a published peer evaluation / a report / a talk}, which
covers {ONE_LINE_RELEVANCE}. It's genuinely worth the ten minutes
whether or not we ever speak.
Out of interest — how are you finding {RELEVANT_CHALLENGE} at
{ORGANISATION}?
The instant pitch after connecting ("pitch-slap") burns the warmth you just built. Lead with something useful, close with a question they can answer in one line — an interest-based CTA, exactly as in cold email.
31. Headline formula for career-changers (+2 examples)
Formula:
{WHERE_YOU'RE_GOING} | {WHAT_YOU_BRING} | {PROOF_OR_SPECIFIC}
Example 1 (scientist → sales):
Aspiring SDR/AE in life-science tech | Lab scientist who's run the
workflows I'll be selling to | MSc Molecular Biology
Example 2 (commercial background → health tech):
Moving into health-tech sales | 6 years client-facing delivery —
scoping, renewals, stakeholder management | Learning MEDDPICC in public
Never headline yourself as "Seeking opportunities" — headline the value, not the need. Recruiters search headlines by keyword, so name the target role explicitly.
32. About-section skeleton — no-experience candidate
{HOOK: one line on the problem you want to work on, not on yourself —
e.g. "Great products fail in {INDUSTRY} because nobody translates
between the lab and the buyer. That translation is the job I want."}
{BRIDGE: 2–3 lines on what you've actually done and how it transfers —
client-facing work, projects delivered, budgets managed, stakeholders
handled. Specific and quantified beats senior-sounding.}
{EVIDENCE OF INTENT: 2–3 lines on what you're doing about it now —
courses, books, frameworks learned (MEDDPICC, SPICED), mock discovery
calls, people you're learning from. This is what separates "interested
in sales" from "preparing for sales".}
{DOMAIN EDGE: 1–2 lines on your unfair advantage — scientific
training, clinical exposure, technical fluency — and the buyer it
helps you understand.}
{CTA: one line — "If you're hiring {ROLE_TYPE}s who {YOUR_EDGE},
I'd love to talk: {EMAIL}."}
Write it first person and concrete. Hiring managers read the About section to answer one question — "does this person understand what the job actually is?" — so show the work, not the enthusiasm.
Discovery (5)
Discovery is the questioning phase where you learn the prospect's problems and buying process. Diagnose before prescribing — and every call ends with a calendared next step.
33. Call agenda / upfront contract
"Before we dive in — can I suggest a shape for the next {DURATION}
minutes?
I'd like to spend most of it understanding how {PROBLEM_AREA} works
at {ORGANISATION} today — I'll ask quite a few questions. I'll leave
{N} minutes to show you the one part of what we do that seems most
relevant, and keep the rest for yours.
At the end, one of two things happens: if there's a fit, we agree a
specific next step before we hang up. And if there isn't, the most
useful thing either of us can say is a straight no — you won't
offend me, and I'll do you the same courtesy. Does that work? Anything
you want to make sure we cover?"
The up-front contract (a Sandler idea): agree time, agenda and outcomes — including that "no" is an acceptable answer. It removes the pressure that makes prospects guard information.
34. Ten layered discovery questions
Situation
1. "Walk me through how {PROCESS} works today — from {START_POINT}
to {END_POINT}."
2. "What have you already tried or looked at to change it?"
Pain
3. "Where does that break down? What does a bad week look like?"
4. "How often does {FAILURE_MODE} actually happen?"
5. "Who feels it worst when it does?"
Impact
6. "What does that cost — in money, hours or risk? Rough numbers
are fine."
7. "If nothing changes for twelve months, what happens?"
Decision
8. "Is there a date by which this has to be solved — an audit, a
contract expiry, a planning deadline?"
9. "Who else would be involved in a decision like this, and how did
the last comparable purchase actually get made?"
10. "What would need to be true for this to get approved?"
Layered means each layer earns the next: situation before pain, pain before impact, impact before process. Question 10 is a calibrated question — the answer is pure discovery about criteria, budget and blockers in their own words.
35. Pain-quantification question set
"You mentioned {PAIN}. Can I put some numbers around it?
- How many times a {week/month} does it happen?
- What does each occurrence cost — staff hours, rework, overtime,
locum or outsourcing spend?
- What did that add up to last year, roughly?
- What's the worst single incident it's caused — and what did that
one cost, in money or in risk-register terms?
- And if you solved it completely, what would you do with the
{MONEY/HOURS} you'd get back?"
Quantified pain is what beats the status quo — "interesting" is not a budget line. Aim for a number the customer said out loud, because a business case built on their numbers is one your champion can defend.
36. Next-step close script (end of every call)
"This has been genuinely useful — here's what I suggest as a next
step: {SPECIFIC_STEP — e.g. thirty minutes with your {STAKEHOLDER}
to validate the numbers we discussed}.
Does {DAY} at {TIME} work? I'll send the invite now, while we're
both here, with a two-line agenda so {STAKEHOLDER} knows why they're
in the room.
And between now and then, I'll send {DELIVERABLE} — is there
anything you need from me beyond that?"
Every call ends with a specific, calendared next step booked before you hang up — "I'll follow up soon" is a hope, not a deal. The invite sent live, during the call, is the discipline that separates pipeline from wishful thinking.
37. Multi-thread ask ("who else should be in the room")
"A pattern I want to avoid: we build this up between the two of us,
and then in month three it meets everyone else for the first time —
finance, IG, clinical, procurement — and starts again from zero.
Who else has a stake in {PROBLEM_AREA}? Specifically: who owns the
budget it would come from, who would actually use it day to day, and
who could veto it?
Could we get {NAME_OR_ROLE} into the next conversation — or would it
help if I gave you {ASSET — a one-pager / the business case draft}
to socialise with them first, so nobody arrives cold?"
Single-threaded deals die when your one contact goes quiet, changes role or turns out to be a coach rather than a champion. How your contact responds to this ask is itself diagnostic — a real champion creates access; repeated deflection is a red flag.
Job-search extras (10)
Selling yourself into a sales job is itself a sales process: research, personalised outreach, discovery, objection handling, and asking for the business.
38. CV bullet formula — transferable achievement
Formula:
{ACTION_VERB} {WHAT_YOU_DID} for/with {SCALE — clients, users,
budget, team size}, {HOW — the skill you used}, {RESULT}.
Example:
Managed relationships with {N} client accounts worth {£VALUE},
resolving scope disputes and renewal negotiations directly with
senior stakeholders — retained {N–1} of {N} accounts year on year.
Lead with the verb, land on the result. For sales roles, the transferable skills to surface are: stakeholder management, negotiation, presenting, handling rejection, working to targets.
39. CV bullet formula — project
Formula:
{LED/DELIVERED} {PROJECT} from {START_STATE} to {END_STATE}, working
across {STAKEHOLDER_GROUPS}, {ON_TIME/UNDER_BUDGET/AGAINST_CONSTRAINT}.
Example:
Delivered a {PROJECT_TYPE} project from scoping to sign-off in
{TIMEFRAME}, coordinating {N} departments and an external supplier,
landing {DELIVERABLE} two weeks ahead of the regulatory deadline.
Projects prove you can run a process with owners and dates across stakeholders — which is exactly what a mutual action plan is. Draw the line for the reader; don't make them infer it.
40. CV bullet formula — quantified result
Formula:
{VERB} {METRIC} by {PERCENTAGE_OR_VALUE} in {TIMEFRAME}, by
{THE_SPECIFIC_THING_YOU_CHANGED}.
Example:
Increased {ACTIVITY_METRIC} by {N}% in six months by redesigning
{PROCESS} and introducing weekly {MEASUREMENT_RITUAL} — the approach
was adopted by two other teams.
One number per bullet, honestly derived — interviewers probe numbers, so only claim what you can defend in a follow-up question. An honest small number beats an unprovable big one.
41. Outreach email to a hiring manager (not via the portal)
Subject: {ROLE_TITLE} — {ONE_SPECIFIC_HOOK}
Hi {FIRST_NAME},
I've applied for the {ROLE_TITLE} role, but I wanted to write to you
directly because {SPECIFIC_REASON — e.g. the advert says the
territory is {SEGMENT}, which is exactly the world I come from}.
Short version: {TWO_LINES — your domain edge and one concrete,
relevant achievement}. I understand {BUYER_TYPE} because
{ONE_LINE_PROOF — I've been one / I've worked alongside them}.
I don't expect you to shortcut the process — but if it's useful to
know who's behind the application, I'm happy to answer anything
directly. Is {PROBLEM_THE_ROLE_SOLVES} the hard part of the
territory right now, or is it something else?
{YOUR_NAME}
This is a first-touch cold email — same rules: proof of research, their problem, one proof point, an interest-based question. It also demonstrates the exact skill the role requires, which no portal application can.
42. Follow-up after applying
Subject: RE: {ROLE_TITLE} application
Hi {FIRST_NAME},
I applied for {ROLE_TITLE} on {DATE} and wanted to add one thing the
form didn't have room for: {NEW_VALUE — e.g. since applying, I
completed {RELEVANT_THING} / this week's {INDUSTRY_NEWS} is exactly
the trigger the role sells into, and here's how I'd use it}.
I know you'll be working through a stack of these — no reply needed
unless useful. If the process is moving, I'd value the chance to
show how I'd approach {TERRITORY_OR_PROBLEM}.
{YOUR_NAME}
Every touch adds something new — a follow-up that only says "checking on my application" is the job-search version of "just checking in". One follow-up after 7–10 days is persistence; three in a week is a red flag.
43. Interview thank-you note (same day)
Subject: thank you — and the {TOPIC} question
Hi {FIRST_NAME},
Thank you for today — I particularly enjoyed the discussion about
{SPECIFIC_TOPIC_FROM_THE_INTERVIEW}.
One thing I kept thinking about afterwards: you asked {QUESTION},
and on reflection I'd add {SHORT_SHARPER_ANSWER — two or three
lines}.
The conversation confirmed what drew me to the role: {ONE_SPECIFIC —
the territory, the problem, the team's approach}. I'd be delighted
to take the next step, whatever shape it takes.
{YOUR_NAME}
Send within 24 hours. The "on reflection" paragraph is the differentiator — it shows you kept working the problem after the meeting ended, which is precisely what good salespeople do after discovery calls.
44. "Any reservations?" interview close script
"Before we finish — I want to ask the question I'd ask at the end of
any important meeting.
Based on everything we've covered, do you have any reservations
about my fit for this role that I could speak to now, while we're
in the room?
[Listen fully. Acknowledge — don't argue: 'That's fair — the CV
can't show that.' Then respond to the specific concern with
evidence, and confirm:] 'Does that address it, or is part of it
still a concern?'
And can I ask what the next step in the process is, and when I
should expect to hear?"
This is objection handling applied to yourself: surface the concern while you can still respond to it, instead of letting it kill the deal in a meeting you're not in. Asking it also demonstrates closing behaviour — interviewers for sales roles notice.
45. Salary-conversation holding line
[Asked "what are your salary expectations?" early in the process:]
"I'd rather not anchor us to a number before we both know the fit —
if we get to offer stage, I'm confident we'll land somewhere fair.
Can I ask what range is budgeted for the role?"
[If pressed for a number:]
"From my research, similar roles are landing around
{RESEARCHED_RANGE} base with OTE of {OTE_RANGE} — and I'd weigh the
whole package: territory quality, ramp support, commission structure.
Does that fit the range you've budgeted?"
Anchoring works on salaries exactly as it works on deals: whoever names a number first frames the negotiation, so invite them to go first. If you must name one, give a researched range and open at the defensible top of it — and at offer stage, trade give-get (start date, review timing) rather than conceding for nothing.
46. Recruiter outreach — registering with an agency recruiter
Subject: SDR/AE candidate — {YOUR_SECTOR} background
Hi {FIRST_NAME},
I'm targeting {ROLE_TYPE — e.g. SDR/BDR} roles in {SECTOR — e.g.
life sciences / health tech}, and I understand you place into
exactly that market.
The short version: {ONE_LINE_BACKGROUND — e.g. science background,
trained end-to-end in the full sales process}, based in {LOCATION},
available from {AVAILABILITY}, looking around {RESEARCHED_BASE_RANGE}
base — flexible for the right seat.
Rather than just sit in your database: are you working any live
briefs now where a {YOUR_EDGE} candidate is a genuine fit? And if
not, what would make my profile easier to place?
Happy to send my CV straight over.
{YOUR_NAME}
Recruiters match candidates to live briefs, so lead with exactly what they filter on — role, sector, location, availability, expectations — and close with a question they can act on. Remember the launchpad's caveat: their incentive is a placement, not your best outcome, so keep your own targeted search running in parallel.
47. Job-referral request — contact at a target company
Subject: the {ROLE_TITLE} opening at {COMPANY}
Hi {FIRST_NAME},
Thanks again for {THE_INTERACTION — e.g. the chat about life on the
team last month} — it's a big part of why I've applied for the
{ROLE_TITLE} opening.
If you felt comfortable referring me, I'd be grateful — and if not,
no problem at all; the conversation was valuable on its own. To make
it easy either way: {TWO_LINES — your background, why this role
specifically, one concrete proof point}. My CV is attached.
Whichever way it goes, I'll let you know how it lands.
{YOUR_NAME}
Distinct from #8, which prospects for the right buyer — this asks a contact at a target employer to lend their credibility to your application. Ask only someone who has actually interacted with you (a rep from an informational chat, a connection who knows your work), keep the ask easy and revocable, never resent a no — and always close the loop afterwards; people who report back get referred again.