The narrative arc for a 60-second product explainer

Most product explainer videos are spec sheets dressed up as videos. They list features, show screen recordings, end with a button. The viewer remembers nothing. The fix isn't more polish - it's a story shape. A 60-second video can carry exactly one arc, and the arc is the difference between a video that informs and a video that converts.

Here's the working structure I use for product explainers in the 60-second runtime.

The five-beat arc

A 60-second product explainer has room for five beats:

1. The Problem (~10s) - the thing the viewer recognizes.
2. The Cost (~10s) - what the problem is actually costing them.
3. The Solution (~15s) - your product, shown solving the problem.
4. The Proof (~15s) - evidence the solution works.
5. The Action (~10s) - what the viewer does next.

Five beats, 60 seconds. The temptation is always to add a sixth or seventh beat; resist. The arc only works if each beat lands; cramming six beats into 60 seconds means at least two of them won't.

Beat 1 - The Problem

The opening beat names a specific, concrete problem the viewer already has. Specificity is the lever here - generic problems ("scaling is hard") don't engage; concrete problems ("you keep buying templates and never using them") do.

A useful exercise: write down the problem in 22 words or fewer, then read it to someone in your target audience. If they say "yes, that's me," the problem is concrete enough. If they say "I guess?" - back to specificity.

Three rules for the Problem beat:

• No villains. Don't blame competitors or industry trends. Blame the situation; the viewer is the one in it.
• No symptoms list. Pick the one most-felt symptom and name it. A list of five symptoms reads as marketing.
• Use the viewer's words. If your target audience says "stuck on the homepage," don't dress it up as "obstructed user journey."

Beat 2 - The Cost

The Cost beat is the one most product explainers skip. Naming the problem isn't enough - the viewer has to feel what the problem is costing them in concrete terms.

Cost can be measured in:

• Time - "you've been doing this for two hours a week, for two years."
• Money - "that's three subscriptions you're paying for and never using."
• Opportunity - "every video you don't ship is one a competitor did."
• Mental load - "every Monday morning, you wonder what to do first."

Pick the one cost that lands hardest for your audience. The other costs can stay implied; the named one is the one the viewer will feel.

Why this beat matters: the Solution beat (beat 3) is the moment of relief. Without a felt Cost, the Solution lands as nice-to-have rather than need. The Cost beat creates the gravitational pull that makes the Solution feel like rescue.

Beat 3 - The Solution

Now you introduce the product. The temptation is to demo every feature; the discipline is to show the one capability that solves the cost from beat 2.

A working pattern:

"VideoCue writes the script, picks the voice, cuts the timeline. From topic to MP4 in nine minutes."

That's 19 words. It identifies the product (VideoCue), shows the capability (writes/picks/cuts), and quantifies the outcome (nine minutes). It does not list every feature.

Three rules:

• Show, don't claim. If you say "fast," show the timer. If you say "smart," show the result. Claims without footage read as marketing.
• One capability per beat. Even if the product does many things, the explainer beats the one that solves the named Cost.
• The capability should be visibly continuous with the cost. If the Cost was "two hours a week," the Solution beat shows the same task done in two minutes. The viewer connects the two without you having to narrate the connection.

Beat 4 - The Proof

The Proof beat is the evidence that the Solution actually works. Three options, in order of strength:

• A real user, named, with a specific result. "Sarah at Maple Foods went from one video a month to four per week."
• A real statistic, with a credible source. "Creators using VideoCue publish 3.2× more often."
• A visible demo of the outcome. A side-by-side comparison; a finished video with its production timeline overlaid.

What doesn't work as Proof:

• Generic testimonials ("it's amazing, life-changing").
• Featured-in logos with no actual claim attached.
• Numbers without context ("used by thousands" - thousands of what?).

The Proof beat is the most-skipped beat in product explainers, and the most-important one for conversion. Without Proof, the viewer reads the Solution as a claim; with Proof, they read it as a track record.

Beat 5 - The Action

The Action beat is the call to action, with the same rule from earlier guides: one thing. Not a checklist. Not a menu. One action.

The action should be:

• Concrete. "Try it free" beats "learn more."
• Aligned with the problem you named. If beat 1 was about getting unstuck, the action is "make your first video in nine minutes."
• No friction in the call. Don't say "sign up for our newsletter" - that's a different conversion than the rest of the arc has been building toward.

A working pattern:

"Make your first one this afternoon. Free, no credit card. videocue.io."

15 words. The action is concrete (make your first one), the timing is specific (this afternoon), the friction is named (free, no credit card), and the destination is given.

What gets cut to fit

If your draft of the five beats is 80 seconds rather than 60, the cut comes from three places, in order:

1. Reduce the Cost beat to one sentence. Most drafts spend too long on the Cost.
2. Tighten the Solution beat by removing adjectives. "VideoCue quickly and easily writes the script" becomes "VideoCue writes the script."
3. Move the Proof beat into the Solution beat by overlapping them. Show the demo while the narration delivers the proof line.

What you don't cut: any of the beats themselves. A four-beat arc reads as incomplete; a six-beat arc reads as cluttered. Five is the number.

When the arc breaks

Two cases where the five-beat structure doesn't hold:

• Pure demonstration content. A 60-second "how-to" or tutorial doesn't have a Problem-Solution arc; it has a sequence of steps. Use a different structure - usually intro / step 1 / step 2 / step 3 / outcome.
• Brand-building content. A 60-second piece that's introducing the brand rather than selling a product uses a different arc - usually identity / values / proof / invitation.

For everything in the product-explainer zone, the five-beat arc is the default. Break it intentionally; don't drift away from it accidentally.

A worked example

Here's the arc applied to a fictional product - a meal-planning app called Plate.

PROBLEM
  "It's Sunday night. You're staring at the fridge.
  You don't know what to cook this week."

COST
  "Last week you spent $200 on groceries and ordered takeout twice
  because you couldn't figure out what to make on Wednesday."

SOLUTION
  "Plate plans your week in two minutes - based on what's in your
  fridge, what you've cooked before, and how much time you have on
  Tuesday night."

PROOF
  "Hannah, a working parent of two, hasn't ordered takeout in six weeks.
  She told us she has Sundays back."

ACTION
  "Plan this week, free, at plate.app. No card required."

Five beats, roughly 155 words, fits comfortably in 60 seconds. Each beat has a job; each beat hands off to the next.

Bring it to VideoCue

The Narrative Arc Plotter runs the five-beat exercise as a guided form - you fill in each beat, and it tells you whether the arc is balanced (i.e., no beat is taking more than its share of the runtime). The output is a script skeleton you can hand to a voiceover (human or AI) without further structural work.