Cut a Product Demo Recording Into Standalone Teach Beats

Cut a Product Demo Recording Into Standalone Teach Beats

Turn a long product demo recording into several standalone vertical teach clips by extracting intents, mapping beats, and rebuilding scenes—do not "just shorten the video" or stitch the raw screen capture into a Reel.

Founder demos and sales recordings are gold for teaching, but they are paced for meetings, not mute-autoplay feeds. Stitching creates a shorter meeting; beat mapping creates teach units. The same extraction mindset as from one webinar to a week of vertical explainers applies here with tighter UI focus.

Step 1 — Intent extraction (not chapter markers)

Watch the recording once with a notepad. For every 60–90 seconds of footage, ask: what can a stranger do after watching this alone? Write one intent sentence per candidate clip. Discard stretches that only make sense with prior context.

Good intents:

• "Set an intent label before auto-assign"
• "Invite a teammate with the right role"
• "Export last month's invoice PDF"

Weak intents:

• "Continue the demo"
• "Show the rest of settings"
• "Recap what we just did"

Cap your first pass at five to seven intents. More than that usually means you need a series, not one heroic edit week.

Step 2 — Beat map each intent

For each surviving intent, fill a four-row beat map:

Mark each UI moment as scene (must show the real control) or B-roll / metaphor (can be stylized). Most "walk and talk" frames become B-roll or get cut.

Step 3 — Which UI moments become scenes vs B-roll

Keep as demo scenes:

• The exact control that teaches the claim
• Before/after states that prove the mechanism
• Error states you intentionally teach in a Gotcha clip

Demote to B-roll or cut:

• Mouse wandering while narrating strategy
• Login, blank dashboards, "let me find that…"
• Multi-monitor chaos and unread notification badges
• Competitor tab switching

Zoom to the control cluster; do not show the entire desktop. Plan crop against safe zones for 9:16 educational Reels.

You dropped twelve minutes of architecture storytelling into a blog link. The three Reels teach without requiring the meeting.

Rebuild as a storyboard (do not stitch)

Stitching fails because:

• Meeting framing fights 9:16 safe zones
• Spoken digressions kill mute retention
• Timing follows conversation, not teach pacing

Instead:

1. Write intents and beat maps
2. Capture or regenerate clean UI stills dated to a UI freeze
3. Approve the board (claim + demo + CTA)
4. Render motion only after approval

This is the storyboard-first vs generate-then-fix choice applied to existing footage. For single-feature focus, keep each clip inside a 45-second teach budget unless the how-to truly needs 60s.

Packaging and measurement

• Name files by intent, not by recording timestamp
• Publish Why / How / Gotcha as a set when the demo covers a release (changelog trio pattern)
• Point CTAs to docs anchors, not to "watch the full demo"
• Measure saves and assisted demos—not whether the stitched cut looks like the meeting

Checklist

• Intent list capped and prioritized
• Beat map per intent with scene vs B-roll marks
• Hook rewritten for mute
• New vertical stills—not full-frame meeting crops
• Board approved before any stitch or render
• Full recording retained as deep link for sales, not as the social cut

Transcript pass (optional but fast)

If you have a transcript, highlight sentences that already sound like teach claims. Those lines often become VO notes; the surrounding digressions become blog links. Do not paste the full transcript onto captions—density will kill the Reel.

Sales vs marketing cuts

Keep two artifacts:

• Full recording — for AE enablement and deep objections
• Beat-mapped Reels — for social and onboarding

Never replace the full recording with a montage and call it enablement. AEs still need the long path; social needs standalone intents.

QA stranger test

Before publish, show a Reel to someone who never attended the demo. They must restate the intent in one clause. If they say "it was part of a longer walkthrough," you still stitched. Rebuild the hook and claim beats until the clip stands alone.

Naming and storage convention

YYYYMMDD_intent-slug_stage.mp4 beats final_final_demo_cut7.mp4. Store beat maps next to the master recording so the next marketer inherits the extraction work instead of rewatching eighteen minutes cold.

Soft tool note

Whatever stack you use, rebuild demo footage as approved storyboard beats before render so each clip teaches alone. Platforms such as Scro are built around that storyboard-first gate; the intent→beat map still works in a sheet beside your recording.