How to Write a VSL: A Record-Ready Script Process

1. Turn Your Research Into a Message Brief

Do not begin by polishing the opening line. First, reduce your customer, product, and offer research to a one-page brief.

Answer these questions:

• Who is the intended viewer?
• When does the problem occur?
• What outcome does the viewer want?
• What has the viewer already tried or come to believe?
• Why might the usual approach be incomplete?
• What does the product provide?
• What mechanism, or cause-and-effect explanation, connects the product to the outcome?
• Which claims have approved evidence?
• Which objections could prevent action?
• What should the viewer do next?

Label any unverified statistic, mechanism, credential, testimonial, comparison, guarantee, scarcity statement, or offer term PRIMARY SOURCE NEEDED. Do not soften the wording and present the claim as established.

Original example: FlowRelay

The examples in this guide use FlowRelay, a fictional workflow product. Its features, evidence, and script are illustrations. They have not been tested or observed.

• Audience: Operations leaders managing requests across email, chat, and project tools
• Problem: Requests lose context or ownership during handoffs
• Desired outcome: A visible path from request to owner to completion
• Existing belief: The team needs another project dashboard
• Alternative explanation: The larger gap may be inconsistent intake and ownership rules
• Offer: A fictional system for standardizing intake, assignment, and status
• Evidence plan: Interface demonstration, process documentation, and approved customer evidence
• Action: Request a guided walkthrough

Now write the argument in one sentence:

[Audience] experiences [problem] because [obstacle or incomplete approach]. [Offer] provides [different path], supported by [evidence], so the audience can pursue [desired outcome].

For example:

Operations teams lose requests because work enters through disconnected channels without consistent ownership. FlowRelay creates one intake-and-routing process, demonstrated through a documented workflow comparison, so teams can see what needs action and who owns it.

This sentence organizes the draft. It does not prove its factual or causal claims.

2. Choose a Lead That Fits the Argument

A lead is the opening approach used to introduce the sales argument. It may begin directly with the offer or desired outcome, or indirectly through a problem, assertion, or short story.

Masterson and Forde describe six practitioner categories: Offer, Promise, Problem-Solution, Big Secret, Proclamation, and Story. Treat these as writing lenses. They are not exhaustive, mutually exclusive, or empirically validated. [1]

Compare genuinely different concepts:

Direct promise

What if every incoming request could enter one visible workflow with an assigned owner and next step?

Problem-Solution

Your team may not be missing deadlines because people are careless. The request may have disappeared before anyone clearly owned it.

Indirect story

Two teams handled similar requests. One spent Monday chasing status updates. The other began with a queue that already showed each owner and next action. The difference appeared before either team opened its project board.

The practitioner framework includes comparing benefit-led openings with approaches centered on a dominant emotion. That is a way to generate alternatives, not evidence that one approach is generally superior. [2]

Keep the main argument, proof, product explanation, and offer constant while comparing leads. Write each opening as a replaceable module with its own transition into the shared script.

Keep the hook relevant

The hook is the opening idea that gives the intended viewer a reason to continue. Record:

• How it identifies the intended audience
• What question it opens
• What explanation it promises
• Which later beat answers the question
• How that answer connects to the product

Indirect leads can become too subtle, delay relevance, or fail to reconnect with the offer. That warning comes from practitioner theory, not performance research. [3]

For a dedicated treatment, see how to write a VSL hook.

3. Map the Argument Before Writing Full Prose

A useful working sequence is:

1. Recognition
2. Stakes
3. Belief shift
4. Mechanism
5. Proof
6. Product
7. Offer
8. Objections
9. Risk reversal
10. Call to action

A risk reversal is a verified term that reduces the buyer’s perceived downside, such as an approved trial or refund policy. A call to action, or CTA, states the next step.

This order is an editorial starting point. Combine or rearrange beats when the audience, evidence, or offer requires it.

For every beat, ask:

• What must the viewer understand?
• What claim creates that understanding?
• What evidence does the claim need?
• Why should the following beat come next?

Move from a recognizable situation to an inspectable explanation. Avoid invented enemies, secret pathologies, or universal root causes.

Weak fictional version

The software industry does not want you to know why your projects fail.

Clearer fictional version

A project board organizes work after someone enters it. But when requests arrive through five channels without shared intake rules, the board may begin with incomplete information.

The revision proposes an explanation the script can demonstrate.

4. Open and Close Curiosity Loops

A curiosity loop is a specific question raised in one beat and answered in a later beat. Curiosity should organize information, not excuse vague claims or indefinite delay.

Curiosity gaps involving an overlooked component or process appeared in a convenience sample of Daily Intel VSLs. The observation establishes only that the pattern was present in that sample; it provides no conversion evidence and does not represent the wider market. [4]

Use a simple ledger:

Give every seed a named payoff. Delete questions the script cannot answer clearly or support.

5. Use Story as a Bridge

Within the supplied practitioner framework, a Story Lead carries its promise inside an unresolved narrative. The viewer sees a result or contrast before learning what caused it. [5]

For an introductory story, include:

• A recognizable tension
• One central idea
• A desirable outcome
• A briefly withheld cause
• A clear payoff
• An explicit product connection

Original fictional example

On Monday morning, Maya and Jordan each opened a backlog of 40 requests. By noon, Maya was messaging six people to identify owners. Jordan could already see an owner and next step beside every accepted request.

The difference was not how hard they worked. Jordan’s team assigned ownership during intake. That is the workflow FlowRelay is designed to demonstrate.

The reveal answers the question and returns to the sales argument. For advanced narrative development, see how to write a VSL story.

6. Build a Proof Plan

Assign every factual assertion a status:

Specific details can make an assertion concrete within practitioner theory. Specificity means using precise details rather than broad language, but those details do not prove the claim. [6]

Place evidence beside the claim it supports. Do not expect a later testimonial or demonstration to validate every earlier statement.

7. Connect the Mechanism to the Offer

Plan the offer before polishing its prose:

Do not invent a guarantee, deadline, or discount. If no verified risk-reversal term exists, record none.

Useful transitions include:

• Mechanism to product: “If inconsistent intake creates the gap, the next question is how to standardize it.”
• Proof to offer: “You have seen the proposed workflow. Now let’s look at what the product includes.”
• Offer to CTA: “If you want to examine this process, request a walkthrough.”

8. Create a Timestamped VSL Beat Map

This original FlowRelay map separates the argument, evidence, visuals, and transitions. Its timing and drop-off hypotheses are planning assumptions.

9. Rewrite for Speech and Production

Draft in this order:

1. Write the rough voiceover.
2. Mark every evidence requirement.
3. Add visuals that clarify or demonstrate.
4. Read the voiceover aloud.
5. Add pauses, emphasis, pronunciation notes, and approval flags.

Original record-ready example

Requests arrive through email, chat, and forms.
[VISUAL: three channels entering one queue]
FlowRelay puts those requests through the same intake step.
[PAUSE]
The team can then see the assigned owner and next action.
[EVIDENCE: verified interface demonstration]

10. Review the Script Before Recording

Check the complete draft:

• Does every factual claim have an evidence status?
• Are fictional and hypothetical examples labeled?
• Does every curiosity loop receive a payoff?
• Does the opening reconnect to the product?
• Does each transition explain why the next beat follows?
• Are duplicated beats removed?
• Are the words clear when heard without visuals?
• Are testimonials, credentials, comparisons, guarantees, and terms verified?
• Does every evidence insert identify its approved source?
• Are legal, accessibility, platform, medical, or financial questions flagged for qualified review?

A VSL is record-ready when the argument is complete, unsupported claims are blocked, curiosity loops have planned payoffs, offer terms are verified, and the production team can record the script without guessing what the writer intended.

Sources and Method Notes

Books support theory/history; corpus notes are observational, not performance evidence.

1. Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 41.
2. Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 40.
3. Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 40.
4. Daily Intel transcript corpus. Convenience sample (n=12); observational, not conversion evidence.
5. Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 104.
6. Book — Great Leads: The Six Easiest Ways to Start Any Sales Message, by Michael Masterson and John Forde, (American Writers & Artists, Inc.), p. 92.