Hook, Retain, Reward Scorecard

Score every piece on three numbers before it ships, not after it flops.

Most content teams have exactly one quality gate: does the room like it. That is not a metric, it is a mood, and a mood does not tell you whether a video gets watched past the first three seconds or abandoned halfway through. Alex Hormozi built the content operation behind his book $100M Leads on a harder gate than that. Score every piece on three separate numbers before it goes out, and if any one of the three fails, the piece does not ship no matter how good the other two look.

What to do: Before anything publishes, grade it on three independent checks: hook, does the open earn the next three seconds with a specific promise, retain, does the middle run an open loop that carries the reader past the point where attention normally drifts, and reward, does the close actually deliver the exact thing the hook promised. Score each one pass or fail on its own, and hold the piece if any single check fails, no matter how strong the other two are.

Why it works: A single overall impression hides which of the three stages actually broke, so a team keeps polishing the wrong part of a piece that is failing for a completely different reason.

Example: Hormozi built this scorecard into the content engine behind $100M Leads, a book Acquisition.com's own store page says has sold more than 800,000 copies since it published in August 2023. In the book, hook is graded on whether people actually stop and start consuming a piece, retain is graded on whether an open loop, a story or an unresolved question, carries them through the middle, and reward is graded on one rule: the audience decides if they were rewarded, not the person who made the content.

Walk it through

There's no dashboard for this one. It is three questions you ask by hand before anything ships. Here's the pass.

1. Isolate the hook and grade it on its own, out of context from the rest of the piece. Read or watch only the first line, the first three seconds, nothing else. Ask one question: does this create a specific, resolvable promise, or is it just a topic sentence with no tension in it. "Five ways to cut churn" is a topic. "The one onboarding change that finally stopped our churn" is a hook, because now there is a gap the reader needs closed.

2. Read the middle for the open loop, not for quality. A well-written paragraph that resolves its own question immediately is not retaining anyone. Check whether the piece is still holding something back three-quarters of the way through, the mechanism behind the claim in the hook, the next step in a list, the turn in a story. If everything is already answered by the middle, nothing is pulling the reader to the end.

3. Check the reward against the hook's exact wording, not the piece's general vibe. Go back to the promise you graded in step one and confirm the ending pays off that specific thing, not a nearby, easier promise. A hook about the onboarding change that stopped churn has to end with the actual change and the actual result, or the reward fails even if the writing is good.

4. Fail the whole piece the moment one score fails. A strong reward cannot rescue a piece that lost the reader at the hook, and a great hook is worse than useless if it opens a loop the piece never closes. Score all three before you decide anything ships.

The read

• Hook is a rate, not a feeling. Its real measure is the percentage of people who actually stop and start consuming, a number you can track and move, not an opinion from the room.
• Retain lives or dies on the open loop. A question, a story, or a countdown left hanging is what keeps someone in the middle third. Resolve it too early and nothing is left pulling them forward.
• Reward is judged by the audience, against the hook, not by the creator, against their own effort. Hormozi's rule is that the audience decides if they were rewarded. Feeling proud of an ending is not the same thing as it paying off the specific promise you opened with.

Steal it

Build the scorecard into your own publishing checklist as three separate pass-fail columns, hook, retain, reward, scored by someone other than the writer before anything goes out. Score the hook cold, without reading the rest of the piece first, since context makes a weak opening look stronger than it actually is. Kill anything that fails a single column and send it back, even when the other two scores are strong. A great retain section bolted to a dead hook still dies in the first three seconds, so there is no partial credit worth shipping.

Defend the scorecard by checking it against real numbers once you have them, open rate or view-through for hook, drop-off point for retain, shares or replies for reward. If a piece you scored as a strong hook keeps failing on actual open rate, the scorecard is not broken, your definition of a strong hook is, and you tighten the standard rather than throwing the grading system out.

Gotchas

• A score is still a guess until you have real data behind it. Treat the pass-fail grade as a prediction to check against actual performance, not a verdict, especially early on when you have no baseline to compare it to.
• Retain and reward can fight each other. Stretch the open loop too long to protect retention and you can blow past the point where the reward still feels earned, the audience feels strung along instead of paid off.
• Honest caution: no scorecard saves a boring idea. Hook, retain, and reward are structure. If nobody wanted to know the thing at the center of the piece in the first place, scoring the structure perfectly still ships something nobody shares.