Teaching One SaaS Feature in Under 45 Seconds

Teaching One SaaS Feature in Under 45 Seconds

Compress a single feature teach into hook → one claim → one demo beat → one CTA, with a hard word ceiling—and board those four beats first so regenerations stay local. Forty-five seconds is a constraint that forces clarity; it is not always the right length.

If you need a finer scene checklist inside the same duration, use scene-by-scene checklist for a 45-second product explainer alongside this outline.

The forced outline

Total spoken guide: ~100–120 words. If you need more, you are teaching two features—or you need 60s (pacing templates).

One claim means one claim

Bad claim (multi): “Invite teammates, set roles, and sync SSO in one place.”

Good claim (single): “Invite a teammate with the right role in under a minute.”

Park SSO for another Reel. Multi-claim hooks create mid-video cliffs when viewers realize the scope ballooned.

Demo beat discipline

In the demo window:

• Show one cluster of UI (or one stylized metaphor)
• Narrate only what changes on screen
• Avoid hover tours and settings archaeology
• Prefer real approved UI or honest stylized cards—not invented chrome

Crop for 9:16 safe zones so the control you teach is not under the right rail (aspect and framing).

Hook and CTA that fit 45s

Hook patterns that work at this length: promise, mistake, demo-first (non-clickbaity hook formulas).

CTA options:

• “Open Settings → Team to try it”
• “Docs link for role permissions”
• “Next Reel: SSO setup”

Do not use the CTA to sneak a second feature teach.

When 45 seconds is the wrong length

Choose 30s when the job is a definition or myth-bust with no UI.

Choose 60s when:

• The happy path needs two dependent screens
• Compliance requires a spoken disclaimer
• You must show before/after states slowly

Board the four beats first

1. Write intent + single claim
2. Fill four beat cards (notes / VO / style separated)
3. Approve muted stills
4. Render
5. If a beat fails, regenerate that beat only

That locality is the point of storyboard-first and prevents the regeneration spiral (common mistakes).

Worked example: “saved views”

• Hook: “Stop rebuilding the same filter every Monday.”
• Claim: “Saved views reopen your filter set in one click.”
• Demo: Open Issues → Save view → Rename → Reopen from sidebar
• CTA: “Create one saved view for your team’s daily queue.”

Word count stays inside the ceiling because SSO, notifications, and dashboards never enter the script.

Ship checklist

• One feature named; siblings parked
• Four beats boarded and approved muted
• Spoken words ≤120 (or length bumped deliberately)
• Demo cluster fits safe zones
• CTA is one step, not a second lesson

Pre-production one-pager

Before boarding, fill:

• Feature name (one)
• Viewer restatement sentence
• Out-of-scope siblings
• Success metric (e.g. settings completion, doc CTR)
• Owner for claim accuracy

If the one-pager disagrees with the product UI, stop—do not “teach aspirations.”

Editing inside the ceiling

When the cut runs 52 seconds:

1. Delete second examples first
2. Delete adjectives second
3. Shorten CTA third
4. Never delete the claim beat to “feel faster”

Speed that removes the teach is just a short brand ad.

Series planning

A feature family (invite / roles / SSO) becomes three 45s Reels, not one 90s compromise. Publish as a playlist with consistent bible and numbered CTAs (“Part 2: roles”). Viewers learn more from clean parts than from a stuffed single cut.

Hook/claim alignment drill

Read the hook and claim aloud. If a listener cannot hear they are the same teach, rewrite until they match. Misalignment is the top reason 45s clips feel “random” despite correct UI.

Soft launch internal first

Ship the 45s cut to Support and Sales before social. If they cannot use it in replies or calls, fix the claim—not the music. Internal refusal is a free learning metric.

Timing rehearsal

Read the script with a timer while watching the still sequence:

• If hook spills past 3s, cut words—not visuals
• If demo needs >26s, drop a substep or move to 60s
• If CTA feels rushed, steal two seconds from demo adjectives—not from the claim

Rehearsal prevents “we’ll fix timing in the edit” wishful thinking after render spend.

Soft tool note

Whatever stack you use, board the four beats before render so regenerations stay local when teaching one feature fast. Platforms such as Scro are built around that storyboard-first gate; the outline still works on paper sticky notes beside your UI screenshots.