12 video prospecting templates, script and email body included

The 4-part script skeleton (with timings and word budgets)

Every template on this page is built on the same four beats. Learn the skeleton and you can write a new template for any scenario in about two minutes, which matters more than memorizing twelve scripts.

The word budgets assume a normal conversational pace of roughly 140 to 150 words per minute. If you speak faster, cut the words rather than the beats. Keeping the whole thing under a minute is the single highest-leverage choice you make: Vidyard’s 2025 Video in Business Benchmark Report found that videos under one minute hold 65% of viewers all the way to the end, the highest completion rate of any length band, while 20-minute-plus videos retain only 20%.

1. 1

   Beat 1 — Proof of research (0:00–0:06, 12–18 words)

   Their name, then one specific thing only someone who looked would know. A hiring post, a product change, a number from their pricing page, a line from a podcast. Not “I came across your profile.” This beat exists to buy you the next twenty seconds, and it is the beat most people skip.

2. 2

   Beat 2 — The problem you are naming (0:06–0:22, 35–50 words)

   Describe the consequence of the thing you just observed, in their language, without mentioning your product. State it as a hypothesis they can disagree with (“usually when a team does that, X starts breaking”) rather than a diagnosis. Disagreeable framing invites a reply; a confident diagnosis invites a delete.

3. 3

   Beat 3 — The relevance bridge (0:22–0:40, 30–45 words)

   One sentence on what you do, one sentence on why it connects to beat 2, and one concrete artifact if you have it. Resist listing features. Gong’s 2025 analysis of more than 28 million cold emails found that pitching reduces reply rates by as much as 57%, so this beat should feel like context, not a pitch.

4. 4

   Beat 4 — The low-friction ask (0:40–0:50, 15–25 words)

   One ask, phrased so a two-word reply is a valid answer. “Worth a look?” beats “do you have 30 minutes Thursday?” on a first touch. Say the ask out loud in the video and repeat it in the email body, because some prospects only read one of the two.

On screen throughout: your face in the frame for at least the first five seconds, good light from the front, and whatever you are referencing visible behind you (their site, their LinkedIn, their job post) from beat 2 onward.

12 scenario templates

Each block below gives you the runtime, the word count, the spoken script, and the email body that carries it. Bracketed text is research you supply; double-brace tokens are merge fields your sending tool fills in.

The email bodies are deliberately short. The video is the message; the email exists to get the video played and to survive being read on a phone with images blocked.

SPOKEN SCRIPT

Hey {{firstName}} — I saw {{company}} posted [three enterprise AE roles] this month, so I made you a quick 45-second thing.

When a team scales AEs that fast, the part that usually breaks first isn’t pipeline, it’s the top of it: the SDRs behind them can’t research and personalize fast enough, so the outbound quietly gets more generic right when the quota gets bigger.

We help teams in that exact spot keep outbound personal while the headcount grows — I put a one-page breakdown together for [their vertical] if that’s useful.

Worth a look, or is that not where you’re feeling it?

---

EMAIL BODY

Subject: {{firstName}} — 45 seconds on those three AE roles

Hi {{firstName}},

Noticed the [three enterprise AE hires] at {{company}}. Recorded a short video on the thing that usually breaks next when a team scales that way.

[Video thumbnail — 45 sec]

If I’ve read it wrong, tell me and I’ll stop.

[Your name]

SPOKEN SCRIPT

{{firstName}}, thanks for connecting. Quick one, twenty seconds.

I read your post on [migrating off the legacy CRM] — the bit about losing the activity history is the part nobody warns you about.

We deal with that a lot. No pitch here, just wanted to put a face to the connection. If it’s ever relevant, I’m around.

---

MESSAGE BODY (LinkedIn DM, keep it above the fold)

Thanks for connecting, {{firstName}}. Twenty-second video on the point you made about activity history — no ask attached.

SPOKEN SCRIPT

{{firstName}}, two emails from me, no reply — completely fair, so I’m switching formats.

Thirty seconds: the reason I keep coming back is [their engineering team shipped the self-serve tier in March]. Teams that do that usually end up with a support queue they didn’t staff for within about two quarters.

If that’s already handled, say “handled” and I’ll close the loop. If it isn’t, I’ll send one page on how three teams in [their vertical] dealt with it.

---

EMAIL BODY

Subject: Re: [original subject]

{{firstName}} — switching formats since text hasn’t landed.

[Video thumbnail — 30 sec]

Two words is a complete reply here: “handled” or “send it.”

[Your name]

SPOKEN SCRIPT

{{firstName}} — you missed our 2pm, which I’m assuming means something more urgent landed. No problem at all.

I held the same slot next Tuesday in case it’s useful. If the timing has just gone bad entirely, tell me and I’ll get out of your calendar.

Either way, no hard feelings.

---

EMAIL BODY

Subject: No worries about today

{{firstName}} — 25 seconds, genuinely no guilt in it.

[Video thumbnail — 25 sec]

Same slot held for Tuesday: [booking link]. Or reply “pause” and I’ll stop.

[Your name]

SPOKEN SCRIPT

{{firstName}}, recap from this morning so you have something to forward.

Three things came up. One, [Priya] wanted to know whether this touches the CRM directly — it doesn’t, it writes back through the existing sync, so nothing in your Salesforce setup changes. Two, security asked about data residency; the short answer is [EU region available, doc attached]. Three, you asked what week one actually looks like — it’s about two hours of setup and then it runs.

The open question is still budget timing. You said [Q1 planning locks in November], so the useful next step is probably a 20-minute session with [Priya] before that closes.

I’ll send times. If I’ve mischaracterized anything, correct me and I’ll re-record.

---

EMAIL BODY

Subject: Recap + the three open questions

{{firstName}} — one-minute recap you can forward instead of retyping.

[Video thumbnail — 60 sec]

Covered: CRM impact, data residency, week-one effort. Open: budget timing.

Attached the security doc [Priya] asked for.

[Your name]

SPOKEN SCRIPT

{{firstName}}, you said you’re on [incumbent] — that’s a good tool and I’m not going to tell you to rip it out.

The reason I recorded this anyway: [incumbent] is built around [one rep, one recording]. That works right up until you need [200 personalized touches a week], and then the bottleneck stops being the software and starts being your reps’ afternoons.

If you’re not at that volume, ignore me. If you are, that’s the whole conversation.

---

EMAIL BODY

Subject: On [incumbent] — one narrow point

{{firstName}} — 35 seconds, and I’m not asking you to switch anything.

[Video thumbnail — 35 sec]

Short version: the constraint is rep hours, not tooling. If that isn’t biting yet, this is a no.

[Your name]

SPOKEN SCRIPT

{{firstName}}, you asked about pricing, so here’s the actual number rather than a discovery call.

For a team your size it lands around [$X per seat per month] on annual, [$Y] monthly. That includes [the two things people assume are add-ons]. The two things that move it are [seat count] and [volume tier], nothing else.

The reason I’m saying it on camera is that I’d rather you rule us out on price now than three calls from now.

If the number works, I’ll send the paperwork. If it doesn’t, tell me where it needed to land.

---

EMAIL BODY

Subject: The actual number

{{firstName}} — pricing, said out loud, no call required.

[Video thumbnail — 40 sec]

Roughly [$X/seat/mo] annual. Full breakdown: [pricing link].

If it’s outside range, tell me the range.

[Your name]

SPOKEN SCRIPT

{{firstName}}, we spoke in [March]. You passed, and the reason was [no native LinkedIn sending] — I wrote it down.

That shipped in [September]. That’s the entire reason for this video.

I’m not assuming anything changed on your end, and if [the priority moved on], this is a no and I’ll leave it. But it felt wrong not to tell you, since it was the specific blocker.

---

EMAIL BODY

Subject: The thing you passed on in March

{{firstName}} — you said no because of [native LinkedIn sending]. That shipped.

[Video thumbnail — 35 sec]

That’s the whole email. Happy to close the file again if it’s still a no.

[Your name]

SPOKEN SCRIPT

{{firstName}} — we talked at [SaaStock], by the coffee thing, about [why your team gave up on sequences].

I’ve been thinking about the point you made on [attribution being unusable once you add a second channel]. That’s the objection I hear most and I don’t think anyone has fully solved it.

I put together what we do have on it. Want me to send it over, or would a fifteen-minute call be easier?

---

EMAIL BODY

Subject: The coffee-queue conversation at [SaaStock]

{{firstName}} — following up on the attribution point you raised.

[Video thumbnail — 30 sec]

Happy to just send the doc if a call is overkill.

[Your name]

SPOKEN SCRIPT

{{firstName}} — you just asked for a demo, so hi, this is who you’ll be talking to.

I had a look at {{company}} before recording this. Given [you’re running outbound across three channels already], I’ll skip the intro slides and go straight to [multi-channel sequencing] on the call.

Times are in the email. See you soon.

---

EMAIL BODY

Subject: Re: your demo request — quick hello

{{firstName}} — 25-second hello so the call isn’t cold on either side.

[Video thumbnail — 25 sec]

Book a time: [booking link]. I’ll tailor it to [multi-channel sequencing] unless you tell me otherwise.

[Your name]

SPOKEN SCRIPT

{{firstName}}, [Dana at Northbeam] said I should talk to you, so blame her.

She mentioned you’re [rebuilding the outbound motion from scratch this quarter]. We worked with her team through roughly the same thing, and the part that surprised her was [how much of it was list quality, not messaging].

Happy to just tell you what we learned there, no pitch. Fifteen minutes?

---

EMAIL BODY

Subject: [Dana] suggested I reach out

{{firstName}} — [Dana at Northbeam] pointed me your way.

[Video thumbnail — 30 sec]

Short version: happy to share what we learned rebuilding her outbound motion. Fifteen minutes if useful.

[Your name]

SPOKEN SCRIPT

{{firstName}}, congratulations on [the Series B] — and I’ll keep this to thirty seconds because you’re getting a lot of these this week.

The reason I’m one of them: [raising at that stage usually means a revenue-team headcount plan lands within about sixty days]. That’s the window where outbound quality tends to slip, because you’re hiring faster than you’re onboarding.

We work in exactly that window. If it’s too early, say so and I’ll come back in a quarter.

---

EMAIL BODY

Subject: Congrats on [the Series B] — one thought

{{firstName}} — 35 seconds, and I know your inbox looks like this right now.

[Video thumbnail — 35 sec]

The short version: the 60-day window after a raise is where outbound quality usually slips. Happy to come back in a quarter if it’s early.

[Your name]

Category context, not a promise: SalesLoft data reported by Vidyard in 2024 found sales teams adding video to their sequences saw a 16% bump in open rates and a 26% increase in replies. Treat that as directional, not as what these specific scripts will do on your list.

Subject lines for the email carrying the video

The subject line does one job: earn the open so the thumbnail gets seen. Saleshandy’s 2026 dataset of 53.1 million cold emails put the average cold email open rate at 21% and the average reply rate at 3.7%, so most of your video assets never get looked at because of this one line.

A note on the most-repeated advice in this category: you will see a specific open-rate lift quoted for putting the word “video” in the subject line. We could not trace that figure to a reachable primary source, so we are not repeating the number. The tactic is still worth testing; the number attached to it is not worth citing.

Keep subject lines under about 45 characters so they survive truncation on mobile, and never put a personalization token you cannot guarantee into the subject. A subject line reading “Hi , quick question” is worse than no personalization at all.

The thumbnail and the first five seconds

The thumbnail is the actual call to action of a video email. Nothing in the script matters if the still image does not read as a person who recorded something for this specific human.

• Put something prospect-specific in the frame of the still: a whiteboard with their company name, their homepage open behind you, or a handwritten sign. This is the difference between a thumbnail that looks like an asset and one that looks like a message.
• Use an animated thumbnail (a short looping GIF) where your sending tool supports it, and always host it. Motion in a static inbox is what earns the click.
• Never autoplay. Autoplay in email is either stripped by the client or actively hostile on mobile data.
• Say their name in the first three seconds, out loud, on camera. Sound is off by default in most previews, so also make sure your face and their name are visible in the still frame itself.
• Do not open with your own name and job title. Nobody has ever watched a second longer because of a title card.
• Keep the first five seconds free of screen-share. Show your face, then cut to the screen from beat 2 onward. Gong’s analysis of recorded sales interactions, reported by Vidyard, found closed deals involve using webcams 41% more often than lost deals, which is at least a reason to be on camera rather than behind a slide.

Practical test: mute the video, look at it for two seconds, and ask whether it could have been sent to anyone else. If yes, the first five seconds need rewriting, not the script.

Personalization tokens: what survives at scale

A token that breaks in an email is embarrassing. A token that breaks inside a video is unfixable, because the audio is already rendered. This is the difference most template guides never mention, and it is the reason our token rules are stricter for the spoken script than for the email body.

Sopro’s 2026 outreach data found advanced personalization lifts response rates to 18% compared with 9% for generic emails, so tokens are worth the trouble. But the failure modes are asymmetric: a blank token in an email is a typo, while a blank token in a script produces a sentence with a hole in it that a text-to-speech engine will read straight through, and you will not know until the prospect does.

• Write every spoken sentence so it still parses if the token is empty. “Hey {{firstName}}” degrades gracefully; “your work as {{jobTitle}} at {{company}}” does not.
• Set a fallback value for every token, and make the fallback a real word rather than a blank. “there” for first name, “your team” for company.
• Validate the list before you render, not after. Rendering video for rows with missing values spends production on assets you will have to throw away.
• Escape commas and quotes when exporting your CSV. A stray comma shifts every column right, which is how {{firstName}} ends up containing a job title.
• Never put a token inside a number or a date you speak aloud. Numbers read by a synthesis engine are the least forgiving thing on the page.

The rule we run by: tokens carry the frame, research carries the message. If the only personalized thing in your script is a merge field, you have built a mail merge with a face on it.

Deliverability rules for the email that carries the video

A video email is a normal cold email with a heavier payload and more ways to trip a filter. These rules are not optional; the best script in the world does not matter from the spam folder.

• Never attach the video file. Gmail caps attachments at 25MB and Outlook at 20MB per Google’s and Microsoft’s published limits, and even a compliant 15MB attachment from an unknown sender is a strong spam signal. Host the video and link to it.
• Link a hosted thumbnail image rather than embedding video markup. Most major email clients do not play inline video reliably, so a linked still or GIF that opens a hosted page is the only pattern that renders everywhere.
• Give the thumbnail real alt text (“45-second video for {{firstName}}”). A meaningful share of recipients read with images off, and alt text is the only thing they see where your thumbnail should be.
• Warm the sending domain before a video campaign, not during it. Video sequences tend to launch with higher volume than the domain has ever sent, and a cold domain plus a sudden spike is the classic bounce pattern.
• Send from a subdomain, not your primary corporate domain, so a bad campaign cannot damage the deliverability your finance and support teams rely on.
• Keep the email body under about 75 words. The video is doing the work; a long email next to a video reads as two pitches.
• Do not put a tracking-heavy link farm under the thumbnail. One link to the video, one optional booking link, and nothing else.
• Watch bounce rate per campaign, not per day. Belkins’ 2026 analysis of 7.5 million cold emails put the average reply rate at 0.45% when measured strictly as unique replies over emails sent, which means small deliverability problems are invisible in reply data until the domain is already damaged.

If you take one rule from this section: host the video, link a thumbnail, and never attach the file. Everything else is a refinement of that.

Do and don’t

Running these templates at volume

Twelve templates is a content problem solved. The remaining problem is production: a rep who records each of these by hand realistically manages ten to twenty a day before quality drops, which is not enough to feed a full outbound motion.

The workflow that closes that gap is record-once, generate-per-prospect. You record one short base video so the system has your real face and voice to work from, keep the four-beat skeleton as the structure, and let a per-prospect researched script fill beats 1 through 3 while beat 4 stays constant. What ships is a unique video per prospect with your actual face on camera, not a synthetic presenter, and the same asset can then run across email, LinkedIn, WhatsApp and Instagram rather than being rebuilt per channel.

That channel spread matters more each year: Wistia’s 2026 State of Video report found 81% of teams now share videos on LinkedIn, which has overtaken YouTube as the primary B2B video distribution channel. A template library that only produces email assets is leaving the busiest surface unserved.

• Keep the skeleton fixed and vary only beats 1 to 3. Consistency in the ask makes reply-rate comparisons across templates meaningful.
• Version your templates. When you change the beat 4 ask, change it in one place, or you will be comparing two different offers and calling it a channel test.
• Measure watch-through and reply separately. Low watch-through is a thumbnail and first-five-seconds problem; high watch-through with low reply is a beat 4 problem.
• Run one template per scenario for at least a few hundred sends before rewriting. Sopro’s 2026 figure of 5.1% as the average cold email response rate is a reminder that outreach data is noisy at small volumes.