Sanchez Three Role Ugc

---
name: sanchez-three-role-ugc
description: "Build UGC ad production briefs, hook libraries, and weekly test plans using Savannah Sanchez's separate strategist, creator, and editor roles. Use for Meta or TikTok creative planning, production handoffs, and performance-led iteration."
---

# Sanchez Three-Role UGC Production

Based on Savannah Sanchez's public method. Not affiliated with or endorsed by Savannah Sanchez.

## When to use

Use this skill when a brand or agency needs a repeatable UGC ad production package: researched concepts, filmable hooks, separate creator and editor briefs, a weekly delivery schedule, and a learning plan. It also supports diagnosing an existing creative pipeline or rebuilding ads whose opening, story, or conversion journey underperforms.

The central rule is organizational: the strategist develops and owns the creative direction, the creator supplies raw performance and footage, and the editor assembles the ad. Assign separate people to these jobs for each production unit. An agent can prepare strategy documents and review artifacts, but cannot stand in for a filmed human creator or prove ad performance by writing a script.

Savannah's reported 200+ ads per week describes agency-wide throughput. It is neither a minimum for one brand nor a promised outcome. Scale the batch to available specialists, review capacity, and the budget that can support useful tests. Public hook examples are starting hypotheses rather than permanent winners. Read the evidence boundaries in [references/method.md](references/method.md) before attributing a recommendation.

## Procedure

1. **Define the assignment.** Read the intake section of [templates/output-template.md](templates/output-template.md). Capture product, audience, buying situation, platform, objective, offer, destination, claim evidence, existing assets, and constraints. Mark missing inputs explicitly. Deliver a provisional brief when inputs are incomplete; never fill gaps with invented testimonials or performance.

2. **Establish three owners.** Apply the role contract in [references/method.md](references/method.md). Name a strategist, creator, and editor, with distinct responsibilities and handoff conditions. If staffing combines them, flag the mismatch and propose a smaller batch or outside specialist. Do not disguise the conflict by renaming tasks.

3. **Inspect evidence and past ads.** Follow research and measurement guidance in [references/method.md](references/method.md). Review available results alongside the actual creatives. Separate observed account performance, outside inspiration, and untested ideas. Record source links, dates, audience context, and what can plausibly transfer to this brand.

4. **Build a usable inspiration library.** Use the library fields in [templates/output-template.md](templates/output-template.md). Tag examples by audience, pain point, hook mechanism, visual treatment, and funnel stage. Paraphrase the mechanism and write original brand-specific executions. Link to references without assuming permission to reuse another advertiser's footage.

5. **Choose concept families.** Consult the curated library in [references/method.md](references/method.md). Pick concepts that connect a customer motivation to a demonstrable benefit. Select prospecting or consideration treatments deliberately. For apps and services, show the interface, workflow, or outcome instead of waiting for a physical-product shot.

6. **Design written and visual hooks together.** Apply the variation rules in [references/method.md](references/method.md). Specify the first frame, the opening action, spoken line, and overlay. Create genuinely different visual openings. For each controlled hook test, preserve the body and CTA so the result answers a defined question.

7. **Write the creator handoff.** Fill the creator brief in [templates/output-template.md](templates/output-template.md). Provide script lines, shot identifiers, reference links, lighting and framing instructions, props, raw takes, and B-roll requirements. Allow trusted creators natural wording within approved meaning; the strategist retains ownership of the concept and claims.

8. **Gate footage before editing.** Run the footage checks in [checklists/review-checklist.md](checklists/review-checklist.md). Confirm coverage, usable audio, visible product or interface, legible demonstrations, and agreed usage rights. Return precise pickup requests for missing shots instead of asking an editor to invent a replacement strategy.

9. **Write the editor handoff.** Use the line-by-line table in [templates/output-template.md](templates/output-template.md). Map voiceover, captions, visuals, and transitions to raw assets for every variant. Include readable text, sound-off comprehension, licensed audio, duration, and exports. Route strategic changes back to the strategist.

10. **Schedule and review delivery.** Apply the weekly cadence and final checks in [references/method.md](references/method.md) and [checklists/review-checklist.md](checklists/review-checklist.md). Track filming, footage review, editing, revisions, and client review in a shared board. Count concepts separately from finished variants; include capacity and dependencies.

11. **Define evaluation before launch.** Complete the testing section of [templates/output-template.md](templates/output-template.md). Specify metric definitions, comparable audiences, spend constraints, evaluation window, and success criteria. Use thumbstop, hold, clickthrough, and click-to-purchase as diagnostic signals alongside the business objective. Insufficient evidence produces an inconclusive decision.

12. **Turn results into next week's brief.** Follow the iteration rules in [references/method.md](references/method.md). Identify the likely bottleneck, preserve working elements, and change one variable when learning is the goal. Use [examples/worked-examples.md](examples/worked-examples.md) to calibrate deliverable quality. Finish with review status, unresolved dependencies, and assigned next actions.

## Files in this skill

- [SLUG.txt](SLUG.txt): Package identifier for discovery and naming.
- [SKILL.md](SKILL.md): Entry point, use cases, role rule, and production procedure.
- [references/method.md](references/method.md): Detailed method, curated hooks, decision rules, edge cases, and attribution boundaries.
- [references/sources.md](references/sources.md): Numbered register of fetched public sources and their contributions.
- [examples/worked-examples.md](examples/worked-examples.md): Invented physical-product and app illustrations with weak and improved drafts.
- [templates/output-template.md](templates/output-template.md): Fill-in production deliverable with guidance for each field.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail gates and common failure modes with fixes.