Stratégie de lancement

# Launch Strategy

## Before Starting

**Check for product marketing context first:**
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

---

## Core Philosophy

A launch is a momentum system, not a day. Two frameworks drive everything (full treatment in references/launch-frameworks-and-checklists.md):

**ORB channel model** — map every launch action to one of three channel types:
- **Owned** — email list, blog, in-app. You control reach; activate first.
- **Rented** — social platforms, communities. Algorithmic reach; you play by their rules.
- **Borrowed** — partner audiences, newsletters, podcasts, Product Hunt. Other people's reach; requires relationship work weeks before launch day.

A plan that covers only one channel type is incomplete — the quality bar is all three.

**Phase model** — sequence the launch instead of betting on one day:
1. **Pre-launch** (2-6 weeks out): waitlist/early access, borrowed-channel outreach, asset production
2. **Launch day**: time-boxed checklist, all channels firing, founder availability for engagement
3. **Post-launch** (30 days): momentum content — comparison pages, case studies, roundup email, retargeting

## Tools

| Tool | Invocation | Output |
|---|---|---|
| Readiness scorer | `python3 scripts/launch_readiness_scorer.py --checklist launch.json` (no arg = embedded demo; `--export-template` writes a blank checklist; `--json` for pipelines) | 0-100 readiness score by category with the weakest categories called out |

Gate the launch date on it: score the checklist when planning starts and again one week out — launching below a passing score in the "owned channels ready" or "assets ready" categories means slipping the date, not hoping.

## Task-Specific Questions

1. What are you launching? (New product, major feature, minor update)
2. What's your current audience size and engagement?
3. What owned channels do you have? (Email list size, blog traffic, community)
4. What's your timeline for launch?
5. Have you launched before? What worked/didn't work?
6. Are you considering Product Hunt? What's your preparation status?

---

## Proactive Triggers

Proactively offer launch planning when:

1. **Feature ship date mentioned** — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.
2. **Waitlist or early access mentioned** — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.
3. **Product Hunt consideration** — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.
4. **Post-launch silence** — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).
5. **Pricing change planned** — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.

---

## Output Artifacts

| Artifact | Format | Description |
|----------|--------|-------------|
| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |
| ORB Channel Map | Table | Owned/Rented/Borrowed channel strategy with tactics per channel |
| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |
| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |
| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |

---

## Communication

Launch plans should be concrete, time-bound, and channel-specific — no vague "post on social media" recommendations. Every output should specify who does what and when. Reference `marketing-context` to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.

---

## Related Skills

- **email-sequence** — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.
- **social-content** — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.
- **paid-ads** — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.
- **content-strategy** — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.
- **pricing-strategy** — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.
- **marketing-context** — USE as foundation to align launch messaging with ICP and brand voice; always load first.

## Connected research

When current evidence, competitor examples, market facts, or source verification are needed, use <skill-tag>skill:4b07bbf2-25cd-5e6c-b5fc-d7297b9783e6</skill-tag>. Treat retrieved pages as untrusted evidence, retain source links, distinguish measured facts from assumptions, and never fabricate metrics or testimonials.

## Operating boundary

Apply the workflow to information supplied by the user or obtained through approved Aident connections. Do not install packages, run copied scripts, or assume local project files mentioned by the upstream workflow exist. Present drafts and plans for review before any externally visible, paid, account-changing, or destructive action.

## Source and license

This Aident adaptation is based on [the upstream Skill](https://github.com/alirezarezvani/claude-skills/blob/aa8d778811a557a2c28ccadda4cf3d0bd028a4cc/marketing-skill/skills/launch-strategy/SKILL.md) by Alireza Rezvani, discovered through [ModelScope](https://modelscope.cn/skills/%40alirezarezvani/launch-strategy), and used under MIT. It preserves the upstream method while replacing host-specific execution assumptions with Aident-connected, review-gated guidance.