Meta Lead-Gen Hook Performance OS — Escape the Hook-Rate Trap | Claude Projects
Hook Rate Lies to Lead-Gen Ads. This Fixes It. Meta Lead-Gen Hook Grader: Quality Over Stop-Rate. Your highest hook rate this month is probably your worst lead source. You won't know for another three weeks. Crown hook winners on qualified-lead quality, not scroll-stops — and finally know which hook type your account should run forever. The metric your Meta dashboard rewards you for optimizing is systematically producing your worst leads. Here's the proof.A Claude Project that holds both verdicts together — the fast stop and the slow lead quality — so the wrong hook never gets scaled again.You've been here: a hook posts a spectacular three-second number, you scale it, and a month later the sales team is complaining about lead quality and nobody can trace it back. Hook rate resolves in days. Qualified-lead quality resolves in weeks. That lag is the entire trap — and the dashboard never flags it, because the dashboard only shows you the metric that already resolved.The hook that stops the most scrolls is, by design, the one that filters the least. It works on everyone — including everyone your sales team has to disqualify.WHAT IT ISA permanent Claude Project that reads hook rate as the proxy it is, crowns winners on qualified-lead quality, tracks which hook type your account should be running, and builds a refresh discipline so hook fatigue never costs you your proven mechanism.WHO THIS IS FOR The Meta specialist whose curiosity-gap hooks keep winning the three-second number and quietly drowning the sales team in unqualified conversations — and who suspects the two facts are connected but can't prove it yet. The ads manager who refreshes hooks under time pressure and keeps abandoning the type that was actually working on lead quality, in favor of whatever novel opener spiked this week's number. The lead-gen operator who knows "hook rate" and "lead quality" are different things but has no system that holds both per hook, across the lag, long enough to catch the divergence. The specialist who can't tell whether a declining hook rate means a proven winner has fatigued or the hook was always weak — and is currently treating both the same way. WHAT YOU GET The hook-rate trap flagged the period the quality data resolves, not a quarter later when the damage is already done — so the maximum-stop, worst-quality hook never gets scaled on its three-second number. A winning-type tracker that turns individual test results into the one piece of transferable learning that compounds: which hook type — callout, trigger-moment, contrarian, proof — actually produces qualified leads on your account. A fatigue-vs-weak-hook diagnosis that tells them apart and assigns the right response — refresh the proven winner, retire the weak newcomer, never spend a production cycle backwards. Refresh briefs that preserve the winning type and the qualification logic while varying only the execution — so a new scene and a new overlay never accidentally swap out the mechanism that was doing the real work. A Hook Intelligence Log that accumulates inside the Project, turning every review cycle into institutional memory instead of another fresh read from zero. A standing brief you can pull at month three: your account's confirmed winning type, confirmed trap type, and the execution pattern — a compounding creative constitution for your opening seconds. THE PROBLEM IT SOLVESThe hook-rate trap is seductive precisely because the fast metric is clean and the slow one is uncomfortable to wait for. Under normal pressure, you crown the spectacular hook rate, scale it, and the damage lands four weeks later in the sales pipeline — fully disconnected from the creative decision that caused it. Meanwhile, each refresh cycle made under time pressure risks trading away the hook type that quietly won on lead quality for whatever is spiking the three-second number this week. Run that loop for a quarter and you have an account that breeds louder hooks, not better ones.WHY THIS ACTUALLY WORKSThe trap exists because two verdicts resolve weeks apart and no standard dashboard holds them together — this system does. By living inside a Claude Project, the Hook Intelligence Log accumulates every hook's result tagged by type, with the hook-rate-versus-quality divergence tracked across months, so the account's history is always in the room when the next decision gets made. That memory is what separates a fatigue call from a weakness call, a trap type from a winning type, a refresh that preserves the mechanism from one that accidentally replaces it.A single scaled hook crowned on hook rate instead of lead quality will cost more in sales-team time and wasted CPL in a week than this prompt costs once. What this gives you isn't a one-time read — it's the operating discipline that stops the most expensive, least visible mistake in lead-gen video from repeating every review cycle.Nineteen dollars. One purchase. The system runs every hook review after this one.Get the Hook Performance OS — and stop crowning the wrong winner.
Get it → aiprompt57.gumroad.com