Get Started
Long-form YouTube for builders

Mission 2 of 6

Write a script that holds attention for 12 minutes, without a face on screen.

Long-form is won in minute four, minute seven and minute ten, where the viewer has every reason to leave. You'll learn the structure that gives them a reason to stay, then draft, time and read aloud your first script.

50 minBeginnerFreeStep 1 free

What you'll do

Learn the retention shape

Use a cold open with the result, a promise with open loops, a chaptered body and an ending that hands over the next video.

Apply the 'but, therefore' rule

Turn a list of steps into a story, using a markdown template and a full worked outline.

Time and read aloud your script

Run a timing script to catch long sections before you record a word, then read the script aloud once.

  • A reusable script template with the timings built in
  • Your first script drafted, timed and checked by ear
Before you start
  • Your plan.md from the previous mission, with the first video chosen
  • The tool or project from that video, installed and working. You can't script a build you haven't done
  • A text editor and Python 3 for the timing check
Your progress0/6
01/06The retention shape of a 12-minute video0 done
STEP 01 of 06~10 min

The retention shape of a 12-minute video

The retention graph of a good video has a specific shape. Build the script to produce that shape, not to explain the topic.

Before you write a word, decide what shape the video needs.

Open any retention graph in YouTube Studio and you'll see the same three features:

  • A drop in the first 30 seconds (people who clicked and bounced).
  • A slow slope through the middle (people leaving as they lose interest).
  • Spikes where people rewind or skip to.

A script's job is to make the first drop small, the slope shallow, and the spikes land where you want them. Four parts do that.

Cold open, 15 to 25 seconds

The result, working, on screen, with one sentence of what it is. Not your name, not the channel, not 'in this video'.

The viewer clicked a thumbnail that promised something; show them it's real before they decide you're wasting their time.

For a build, the finished thing running. For a teardown, the moment the tool did something surprising. For a report, the winner winning.

The promise, 20 to 30 seconds

What they'll have or know by the end, and two things you'll get to that you don't resolve yet.

Those are open loops and they're the reason someone stays through a slow chapter: they're waiting for the thing you mentioned.

The body, chaptered, a payoff at least every 90 seconds

A payoff is something visibly happening: a command that runs, a result that appears, a diff, a number.

If 90 seconds pass with you talking and nothing changing on screen, that's where the slope steepens. The timing script below measures this for you.

The ending, the last 60 seconds

The honest catch (every tool has one; saying it is what makes the rest believable), then the next video, by name, as the natural next step.

Then stop. No 'like and subscribe', no outro music over nothing. The end screen does the work.

What's missing on purpose

There's no intro in any of that. Faceless channels can't buy the first 30 seconds with charisma, so they buy it with proof. The result on screen is your charisma.

Tip
Count the payoffs in your favourite builder video. A 12-minute video that holds you usually has eight to twelve. That's the target.
Checkpoint
You can draw the four parts on paper with their timings, and name the two open loops you'd plant in the promise of your first video.
If it breaksMy build has a boring five-minute install in the middle + 1 more
My build has a boring five-minute install in the middle
Cut it to 15 seconds: 'this takes five minutes, the command's in the description' and show the end of it. Nobody watches an install. If the install is the point of the video (it's a hard one), make the breakages the payoffs.
The result isn't visual, it's a terminal printing text
Then the cold open is the terminal printing the text, zoomed so the key line fills the frame, with your voice saying what it means. Terminals are fine. Small text is not.
Still stuck? Ask the community
Next mission · Long-form YouTube for buildersRecord screen and voice that look and sound like a studio made them, with no face and no budget
→