Hook Format

4P

Four beats: Promise, Pain, Proof, Plan. Best when the viewer already trusts the topic and just wants to know what they’ll get.

Promise	2-4 concrete outcomes the viewer gets. “Cut onboarding time by 40%, reduce support tickets, and get every account to activation faster.”
Pain	The viewer’s exact stuck-state. “Your implementation team spends weeks rebuilding the same onboarding plan for every enterprise account.”
Proof	A number, a name, or a result. “We used this process to onboard 200 enterprise customers without adding headcount.”
Plan	3+ enumerated items. “Three things: the implementation template, the data handoff, and the adoption checkpoint.”

7 Beat

Seven beats, led by credibility. Best when the viewer needs a reason to trust you before they’ll follow you anywhere.

Credibility	A number, name, or result in the first 5 seconds. “I’ve led enterprise implementations for three public SaaS companies.”
Audience	Who this is for, specifically. “If you lead customer success at a B2B software company with six-month onboarding cycles…”
Internal stakes	What the viewer feels. “Your team is working harder while customers still feel like implementation has stalled.”
External stakes	What it costs them. “Every delayed launch pushes renewal value further out and puts the account at risk.”
Payoff	2-4 concrete outcomes. “Shorten onboarding, surface risk earlier, and get customers to first value without adding meetings.”
Overview	3+ explicit roadmap items. “First the kickoff, then the data handoff, then the activation checkpoint.”
First lesson	One real piece of value before they could bounce. “Start here: define one measurable activation event before the kickoff call.”

If-Then

Six beats that connect the viewer’s desired outcome to the constraint keeping them from it. This is Hitfactor’s default format.

Desired outcome	Name what the viewer wants. “If you want enterprise customers to reach first value in half the time…”
Hidden constraint	Identify what is quietly blocking it. “…the problem may not be your implementation team. It may be that every account starts from a blank plan.”
Named solution	Give the approach a clear name. “You need an activation-based onboarding system.”
Transformation	Show the before and after. “Instead of tracking completed tasks, the team works backward from the first customer behavior that predicts retention.”
Roadmap	Preview the path. “I’ll show you how to define the event, redesign the handoff, and build the checkpoint.”
Proof	Give the viewer a reason to trust the method. “This is the system we used across 200 enterprise implementations.”

Tip: In every format, the weak version of a beat is the vague version. “Years of experience” loses to a concrete result.