Götz Challenger Marketing

Based on Michael Götz's public method. Not affiliated with or endorsed by Michael Götz.

When to use

Use this skill when a challenger needs attention and commercial traction while facing competitors with much larger media budgets. It suits product launches, packaging briefs, cultural collaborations, creator partnerships and small activation portfolios. It produces a campaign proposal with an executable pilot, original sample copy, a budget and a plan for responding to unexpected demand.

The method starts with an unusually credible product and makes the brand interesting wherever people encounter it. Almost no budget describes the early constraint, not a promise that manufacturing, licensing, people or distribution are free. Michael Götz was named CMO of the Year 2023; the award provides context, not evidence that every tactic transfers to another category.

Read the method reference first. Its evidence labels distinguish public statements, collaborator accounts, publisher summaries and this package's operational adaptations. Preserve key German terms, especially forciertes Glück, while writing the deliverable in the user's language. Do not impersonate Götz or reuse Gustavo Gusto's slogans, visual identity or licensed characters.

Procedure

1. Frame the commercial challenge. Capture the product, audience, purchase occasion, incumbent advantage, distribution, cash ceiling and available team time. Define one business outcome. Mark missing inputs as assumptions and identify which would block execution. Use the brief fields in templates/output-template.md.
2. Find the product truth. Identify a demonstrable difference buyers can experience. Separate substantiated benefits from aspirations. If the experience cannot support the promise, propose a product or service fix before amplification. Read principle P1 in references/method.md.
3. Inspect the category in context. Describe its usual packaging, language, media and buying environment. Choose a meaningful convention to challenge while retaining buying clarity. Judge the concept next to competitors, rather than in isolation. Apply P2 in references/method.md.
4. Make existing touchpoints work harder. Inventory packaging, labels, checkout, receipts, stores and owned content. Select the surface most likely to reach a buyer at the relevant moment. Give it a product-linked message and a practical path to purchase. Use P3 in references/method.md.
5. Choose a cultural community. Find a shared interest, ritual or reference that makes the product welcome. Explain the audience's benefit and why this brand belongs. Gaming is a possible context, not an automatic answer. Use P4 in references/method.md.
6. Design an unexpected collaboration. Compare partners by community trust, product contribution, distribution, feasibility and cost. Create something together rather than merely attaching a famous face. Explain the Luca mechanism without treating its accidental availability mismatch as a tactic. Consult P5 and the edge cases in references/method.md.
7. Write humane humour. Draft three original routes that reveal the product truth through a surprising observation. Remove arrogance, lectures and jokes aimed at customers. Keep claims understandable. Compare weak and improved executions in examples/worked-examples.md.
8. Build a portfolio of small interventions. Recommend one pilot plus a few compatible follow-ups, each with a distinct audience reason and cost. Use limited editions to test product demand where feasible. Keep the core identity recognisable across ideas. Follow P6 in references/method.md.
9. Prepare for forciertes Glück. Specify observable opportunity signals, a response owner, ready assets, capacity limits and a bounded reserve. Explain how the team can turn an unexpected opening into useful action. Include a stop condition. Apply P7 in references/method.md.
10. Make the pilot executable. Allocate production, partner, distribution and measurement costs, including staff time. Set dates, owners and truthful availability wording. Define trial, sales or demand evidence alongside attention metrics. Use the execution fields in templates/output-template.md.
11. Review, learn and deliver. Run every applicable pass/fail check, revise failures and state unresolved dependencies. Separate public evidence from proposed adaptations and invented targets. Deliver a recommendation with scale, revise and stop decisions using checklists/review-checklist.md.

Files in this skill

• SLUG.txt: Package identifier for discovery and installation.
• SKILL.md: Entry point, use cases and working procedure.
• references/method.md: Evidence-based principles, decisions, limits and adaptations.
• references/sources.md: Fetched public sources and access limitations.
• examples/worked-examples.md: Invented examples showing revision and rule application.
• templates/output-template.md: Deliverable fields with completion guidance.
• checklists/review-checklist.md: Pass/fail review, failure modes and fixes.