Strategy pack to build handoff

The most expensive phase of a campaign is not the strategy or the ad spend — it is the

handoff. Every time strategy is re-explained in a new meeting, context drops. A developer

ships a beautiful component that contradicts the promise the ad made, and the message match

the strategist worked out is gone before the first click lands.

When to use

What a dual handoff pack contains

"Dual" means one document that briefs a human implementer and an LLM equally well. It must

carry, explicitly and in one place:

If a fact is only in a chat log or a meeting recording, it is not in the pack.

Briefing once

Once the pack is approved, implementation is purely executional:

guessing at intent, no mid-build copy approvals.

hook to landing page hero, generated code aligns with the paid strategy instead of

inventing its own value proposition.

Same document, both audiences, briefed exactly once.

The rule that keeps match alive

Strategy dictates the code, not the other way around. When a team skips the pack and

goes from a scattered brief straight into the build, the page gets designed in isolation

from the ads — and the specific objection the ad neutralized never appears in the hero.

Reference

Full write-up: https://frezpo.com/blog/strategy-pack-to-build-agency-handoff-ads-landing-page

Throughput context: https://frezpo.com/blog/agency-strategy-throughput-ads-landing-page-packs

Raw SKILL.md — the machine-readable source this page renders.