Greger Creator Squad

---
name: greger-creator-squad
description: "Design and review a recurring in-house creator squad using Elisabeth Greger's public method: local recruitment, brand immersion, retainer sprints, balanced creative ownership and weekly performance learning. Use when replacing one-off UGC sourcing or planning a market launch."
---

# Greger Creator Squad

Based on Elisabeth Greger's public method. Not affiliated with or endorsed by Elisabeth Greger.

## When to use

Use this skill to turn repeated UGC purchases into a continuing creator operation, prepare a local market launch, or repair a squad that produces assets without retaining learning. The deliverable is an operating plan covering recruitment, immersion, production, feedback and a three-month review. It should give the brand and creators enough clarity to run the next sprint together.

The core configuration is at least five locally relevant creators, a brand workshop lasting one to four hours, a physical onboarding kit, weekly or monthly retainers with defined output, an equal split between brand briefs and creator ideas, and one weekly meeting lasting thirty minutes. Preserve these anchors when describing the full method. Explicitly label a smaller experiment or another altered configuration as an adaptation.

Use the public sources as evidence, not as promises about results or present-day prices. Greger's older marketplace advice and her larger organic account programs serve different needs. The procedure below connects their useful lessons without making every variation mandatory. Draft plans and supporting materials within the user's scope; a request for a plan does not authorize contacting creators, signing agreements or spending money.

## Procedure

1. **Establish the operating problem.** Read [method context](references/method.md#1-purpose-and-evidence). Capture product, market, audience, channel, conversion goal, current sourcing friction, budget and internal owner. Separate supplied facts from assumptions. If a crucial input is missing, ask a focused question and continue drafting the independent sections.

2. **Choose the appropriate configuration.** Use [configuration rules](references/method.md#2-configuration-and-readiness). Default to the full squad for recurring production. If the brand cannot support it yet, describe a bounded test and the conditions for graduating. Keep dedicated organic accounts optional and identify who would operate them.

3. **Specify the local squad.** Follow [recruitment guidance](references/method.md#3-recruitment-and-role-design). Define five or more creator slots by language, cultural relevance, product fit, communication, editing and reliability. Record selection evidence and gaps. A roster can contain unnamed slots; never invent available candidates or their rates.

4. **Design brand immersion.** Use [workshop guidance](references/method.md#4-brand-workshop-and-onboarding). Schedule one to four hours around positioning, audience, product use and goals. Include a creator exercise that reveals misunderstanding before filming. Assemble a kit of products and company merchandise plus the operational information needed to start.

5. **Make recurring work concrete.** Consult [retainer rules](references/method.md#5-retainers-and-sprints) and fill the economics fields in [the output template](templates/output-template.md). Define output per creator, cadence, editing responsibilities, delivery dates, revision expectations and agreed usage. Show total production costs with assumptions rather than importing historical platform prices.

6. **Allocate both creative lanes.** Apply [the ownership rules](references/method.md#6-the-two-creative-lanes). Allocate half the agreed deliverables to briefs informed by performance and half to creator-originated concepts. Label each item's origin. Give both lanes equal visibility and specify how an odd total will balance over consecutive sprints.

7. **Write actionable briefs and idea cards.** Use [brief specifications](references/method.md#6-the-two-creative-lanes). For brand briefs, supply an opening, three supported benefits and essential scenes. For creator concepts, give constraints and a hypothesis while preserving the creator's proposed story. Consult [worked examples](examples/worked-examples.md) when vague instructions or excessive scripting obscure the distinction.

8. **Close the measurement loop.** Read [measurement guidance](references/method.md#7-performance-learning). Connect asset IDs to business outcomes and record observation windows. Distinguish direct conversion evidence from coincident organic spikes. Feed the result and its uncertainty back into the next production decision.

9. **Run the single weekly meeting.** Use [the meeting agenda](references/method.md#8-weekly-meeting-and-incentives). Reserve thirty minutes for results, lessons and new angles. Send routine status asynchronously. Define weekly and monthly recognition with understandable criteria and a declared bonus budget.

10. **Review the first three months.** Follow [scaling rules](references/method.md#9-three-month-review-and-edge-cases). Assess creator reliability, learning, workload and economics. Identify reliable creators who could manage the system and describe their responsibilities. Resolve operational bottlenecks before adding creator slots.

11. **Deliver and review the plan.** Complete [the output template](templates/output-template.md), then apply [the pass/fail checklist](checklists/review-checklist.md). Repair failures or identify unresolved dependencies. Check factual attribution against [the source register](references/sources.md); mark implementation choices explicitly.

## Files in this skill

- `SLUG.txt`: Package identifier for discovery and packaging.
- `SKILL.md`: Entrypoint, use cases and procedure.
- `references/method.md`: Evidence-backed method, decision rules and adaptations.
- `references/sources.md`: Numbered register of fetched public sources and research limits.
- `examples/worked-examples.md`: Invented before-and-after applications with rule explanations.
- `templates/output-template.md`: Deliverable structure with field guidance.
- `checklists/review-checklist.md`: Pass/fail checks, common failures and repairs.