How to Write a VSL (Video Sales Letter) Script: Structure, Template and Examples

A video sales letter is a sales page you can hear. The viewer gives you a few minutes of attention, and your script decides whether that time feels like a useful conversation or a pitch they want to escape. Writing one is less about clever lines and more about putting the right ideas in the right order, in words that sound natural out loud.

This guide covers what a VSL script contains, how to prepare before you write, a section-by-section structure, a template you can copy, and an editing pass that catches the problems most first drafts have. No script can promise a particular result, but a clear structure removes the most common reasons viewers drift away.

What a VSL script actually is

HubSpot describes a video sales letter as a video that pitches your product or service to a prospect. Like a traditional sales letter, it grabs attention, discusses the prospect's pain points, shows your product as a solution, and inspires action.

Shootsta's VSL script template guide frames the script in similar terms: a written outline that opens with a hook, names the buyer's problem, presents the solution, surfaces proof, and ends with a clear next step. Vengreso compares the script to a GPS that guides viewers from curiosity to conversion.

All three point to the same thing. The script is the backbone. Camera, lighting and editing matter, but a weak script can't be rescued by good production.

A VSL is different from a short-form reel in one important way. A reel earns a few seconds at a time, while a VSL asks someone who has already shown some interest (they clicked an ad, opened an email, or landed on your page) to stay for a longer, more deliberate pitch. That changes how you pace it, but the core job is the same: keep the next sentence worth hearing.

Before you write: five answers to get first

Most weak VSLs fail before the first line is written. The writer doesn't yet know who they're talking to or what they want that person to do. Spend twenty minutes answering these in plain sentences.

1. Who is the one viewer? Describe a single person, not a demographic. What is their job, what have they already tried, and what are they worried about?
2. What is the problem in their words? Pull phrases from customer emails, call notes, reviews and comments. Their wording beats yours.
3. What is the single outcome you offer? Pick one. A VSL that promises five different things usually persuades of none.
4. What proof do you actually have? Real customer results, before-and-after examples, a process you can demonstrate, credentials, or a clear guarantee-free explanation of how the thing works. List only what is true and that you can show.
5. What is the one next step? Book a call, start a trial, buy, or join a waitlist. Choose one.

If you can't answer number five in a short sentence, stop and decide before you write. A VSL with two competing calls to action asks the viewer to do your thinking for you.

The VSL structure, section by section

This order follows the shape described by the sources above, with a couple of additions that help in practice. Treat it as a spine, not a cage.

1. The hook

Your opening line has one job: make the right person feel "this is about me." Be specific about the person or the problem rather than vague about the benefit. If you want a refresher on what makes a good opener, the glossary entry on hook is a quick read, and the free hook generator can give you several angles to compare before you commit.

Three hook shapes that work well for VSLs:

• The named audience: "If you run a small bookkeeping practice and your weekends keep disappearing into invoices, this is for you."
• The costly mistake: "Most freelancers price their first retainer the same way, and it quietly caps what they can earn."
• The honest question: "What would your week look like if client onboarding took one afternoon instead of five?"

Avoid inflated promises. Claims you can't back up cost you trust in the first ten seconds and make the rest of the script harder to believe.

2. The problem

Describe the situation so accurately that the viewer nods. Use their language. Name the symptoms first (what it looks like day to day), then the cause (why it keeps happening). This is where research from the earlier step pays off.

A good test: could the viewer say "that's exactly it" without you mentioning your product once? If so, you've earned the right to continue.

3. The story or the stakes

Before you present your solution, give the problem some weight. You can do this two ways:

• A short story: a customer, or you, in the middle of the problem. Specific details such as a time of day, a spreadsheet, or a sentence someone said make it believable. The storytelling script style is a useful reference for shaping this beat.
• The cost of waiting: what happens if nothing changes. Keep it honest and proportionate. Pressure that feels manufactured is easy to detect and hard to recover from.

4. The solution

Now introduce what you offer, and explain how it works before you praise it. Viewers trust a mechanism more than an adjective. "We give you a three-step onboarding checklist and the email templates that go with it" is more convincing than "a powerful, complete onboarding system."

Keep this section about the viewer's outcome, not your feature list. For each feature you mention, finish the sentence "which means you can..."

5. The proof

Proof turns claims into something the viewer can check. Options include:

• Customer stories, in their words, with permission
• A screen recording or demo of the thing working
• Before-and-after examples
• Your direct experience, described specifically
• Credentials or background that are relevant to this problem

Only use numbers you can source and show. If you don't have strong numbers yet, don't invent them. A clear demo and one honest customer story do more than a vague statistic.

6. The offer

Say exactly what the viewer gets, what it costs (or what the next step costs), and what happens after they act. Remove ambiguity. If there is a refund policy, trial, or support, state it plainly and as it really works.

7. Objections

Think about the three reasons someone might hesitate: price, time, or doubt that it works for their situation. Answer each in a sentence or two, directly. "You might be thinking you don't have time to set this up. Here's what the first week actually involves."

8. The call to action

Repeat the one next step, say why now is a sensible time (only if there's a true reason), and tell them exactly where to click or what to do. For phrasing options, see our guide to writing a call to action people actually follow.

A copy-ready VSL script template

Fill in the brackets. Read each line aloud as you go. If it sounds stiff, rewrite it the way you'd say it to one person across a table.

HOOK
"If you're a [specific person] who [specific frustration], this video is for you."

PROBLEM
"Here's what usually happens. [Symptom 1]. [Symptom 2].
And the reason it keeps happening is [cause]."

STORY / STAKES
"A [customer type] I worked with was [situation in one concrete detail].
They'd already tried [common fix], and it didn't hold because [reason]."

SOLUTION
"So we built [offer]. It works in [number of steps, only if true] steps:
First, [step]. Then, [step]. Finally, [step].
Which means you can [outcome in the viewer's terms]."

PROOF
"Here's what that looks like in practice. [Demo or customer story].
[One specific, true result or observation]."

OFFER
"When you [take the next step], you get [item], [item] and [item].
[Price or terms, stated plainly]. [Refund or trial terms, if real]."

OBJECTIONS
"If you're worried that [objection], here's how that works: [answer]."

CTA
"If this sounds like your situation, [single action] using the button below.
It takes about [honest time estimate]."

A short worked example

Imagine a bookkeeper selling an onboarding toolkit to other freelancers. The opening of the script might read:

"If you're a freelance bookkeeper and every new client turns into a week of back-and-forth emails, this video is for you. Here's what usually happens. The client sends documents in three different formats. You chase the missing ones. And by the time you start the actual work, you're already behind. The reason it keeps happening is that nobody told the client what 'ready' looks like."

Notice what the example does. It names a person, describes a believable sequence of events, and ends on a cause rather than a pitch. The solution can now arrive as a natural answer.

Write it to be heard, not read

A VSL script is spoken, so edit it as speech.

• Use short sentences. If you run out of breath, the sentence is too long.
• Use contractions. "You're" and "it's" sound human. "You are" and "it is" sound like a form letter.
• Say one idea per sentence. Viewers can't re-read a line they missed.
• Cut warm-up. Lines like "Before we get started" or "I want to tell you about" can usually go.
• Vary the rhythm. Mix a long sentence with a short one. A short line after a longer explanation gives the viewer a place to land.
• Add visual cues. Note where a screen recording, text overlay or customer clip will appear. Our guide to planning B-roll from your script shows a simple way to do this.

Read the whole thing out loud, once, before anyone films. Mark every spot where you stumble, and rewrite those lines. Stumbling in a read-through usually means the viewer will stumble too.

Length and pacing

There's no single correct VSL length, and it depends on what you sell and how much your viewer already knows. A low-cost, simple offer can be explained quickly. A higher-priced or more complex service often needs more room for proof and objections. Instead of aiming for a number, decide how long each section needs to do its job, then cut anything that doesn't move the viewer toward the next section.

A useful rule when trimming: if you delete a sentence and the viewer would not miss it, it was filler. If you delete it and the logic breaks, keep it.

It's also worth checking your pacing against the section list. Many first drafts spend too long on the problem and rush the offer, or the other way around. Highlight each section in a different colour and see where the balance is off.

Edit, record and test

Treat your first VSL as a first version. After you publish, watch how people behave: where they stop watching, which sections get replayed, and whether they take the next step. Many creators and small businesses find that the most useful changes come from the hook and the offer clarity, so test those first. Change one thing at a time so you know what made the difference.

A simple revision loop:

1. Write the full draft in one sitting without editing.
2. Cut anything that doesn't serve the single outcome.
3. Read aloud and fix every stumble.
4. Ask one person who matches your viewer to read it and tell you what they'd do next.
5. Record, publish and review where attention drops.

If you'd like a faster first draft, an AI script generator such as Viral OS can produce a structured starting point, but you still need to supply the real proof, the real offer and your own voice. Generated drafts need an honest edit before they go in front of customers.

Wrap-up: your next 30 minutes

You don't need a studio or a big budget to write a solid VSL script. You need clarity about one viewer, one outcome and one next step, followed by a structure that walks them there.

Here's a practical way to start today:

1. Write your five answers (viewer, problem, outcome, proof, next step).
2. Draft three hooks and choose the most specific one.
3. Fill in the template above, section by section, without polishing.
4. Read it aloud and fix every line you trip over.
5. Record a rough version on your phone and watch it as if you were a stranger.

That rough version will teach you more than another week of planning. Results depend on your offer, your audience and your follow-through, so treat each VSL as something you refine over time.