wind-full-funnel

Wind Full-Funnel Strategy

Based on Patrick Wind's public method. Not affiliated with or endorsed by Patrick Wind.

When to use

Use this skill when a business needs a coordinated Facebook and Instagram advertising plan, when every audience currently receives the same ad, or when retargeting repeats a product pitch without addressing the customer's next question. It supports ecommerce and lead generation. Produce a strategy, audience specification, creative briefs, measurement plan and review decisions that another operator can implement.

Begin with the business outcome and available evidence. Ask only for missing information that changes the plan; otherwise record assumptions and continue. Work from supplied account data without inventing audience sizes, conversion rates, testimonials or results. A strategy request does not authorize account changes or spending.

The public record supports the method's core logic, not a complete reproduction of paid training. Keep source-backed principles separate from this package's implementation adaptations. Historical format tips and promotional results are not current platform guarantees. The evidence boundary and attribution rules are in references/method.md; source provenance is in references/sources.md.

Procedure

1. Set the commercial brief. Record the offer, geography, acquisition goal, conversion event, buying cycle, budget and known economic limits. Identify what constitutes a successful purchase or qualified lead. Use the brief fields in templates/output-template.md. Mark unknown values instead of silently choosing industry averages.

2. Establish the evidence boundary. Read the principles and evidence labels in references/method.md. Use references/sources.md to check what was actually available. Attribute the public method accurately and identify any practical recommendation that the sources do not establish.

3. Inspect usable signals. List engagement, website, product, cart, checkout and customer signals actually available. Check their freshness, relevance and reliability before assigning intent. Apply the measurement and missing-data guidance in references/method.md. A tracked interaction is evidence of behavior, not proof of purchase readiness.

4. Define temperature operationally. Separate unfamiliar prospects, familiar prospects and people showing stronger conversion intent. State inclusion events, exclusions and retention windows explicitly. Resolve the distinction between prospecting and cold retargeting using the taxonomy in references/method.md, rather than forcing every historic label into one campaign structure.

5. Map the customer's next question. Give each audience a distinct job: introduce relevance, build confidence, or resolve the remaining barrier to action. Specify promise, proof, format, call to action and destination. Consult the stage matrix in references/method.md and the corrected briefs in examples/worked-examples.md.

6. Write stage-specific AIDA ads. Build attention, interest, desire and action around the assigned job. Use verified benefits and evidence. Questions, visual hooks and emojis are options to test, not mandatory stylistic rules. Use the copy guidance in references/method.md and the creative fields in templates/output-template.md.

7. Design retargeting handoffs. Define the event that starts a sequence, the time window for each message, the next message and the purchase or lead exit. Consider Wind's public product-reminder then social-proof example without treating its dates as universal. Follow the sequencing and overlap rules in references/method.md.

8. Choose a feasible delivery plan. Specify logical audience roles first, then choose a campaign structure suited to available volume and current account capabilities. Allocate a bounded test budget, protect prospecting supply and avoid fragmenting tiny pools. Use the implementation adaptations in references/method.md; label all numerical defaults as proposed assumptions.

9. Plan measurement and tests. Connect stage indicators to purchases, qualified leads and commercial outcomes. Define each hypothesis, variable, evaluation period, data requirement and next decision. Use the diagnostic rules in references/method.md. Do not declare success solely from clicks or a high retargeting return.

10. Specify optimization and scaling. Repair the identified bottleneck before increasing spend. Document what would justify keeping, revising, pausing or scaling a test. Define automation conditions and caps only when the necessary inputs exist. Consult the automation boundary in references/method.md, rather than inventing Wind's advertised rule settings.

11. Deliver and review. Complete templates/output-template.md, then run checklists/review-checklist.md. Fix failures, disclose unresolved dependencies and give concrete next actions with owners. Use examples/worked-examples.md to check whether the improved plan actually changes messaging and handoffs.

Files in this skill

• SLUG.txt: Canonical package identifier.
• SKILL.md: Entry point, use cases and execution procedure.
• references/method.md: Public principles, decision rules, adaptations and edge cases.
• references/sources.md: Fetched source register and research limitations.
• examples/worked-examples.md: Two invented before-and-after strategy illustrations.
• templates/output-template.md: Deliverable template with field guidance.
• checklists/review-checklist.md: Pass/fail checks, failure modes and repairs.