Product-launch timeline

Objective. Produce a phased product-launch timeline — foundation, build-up, launch and post-launch — that coordinates email, social, paid and on-site activity around weekly milestones, so a new offer activates the avatar's anticipation and enters the chain at full strength.

Inputs this skill needs

• [Value Proposition] — the new offer's unique value and the proof it rests on, so the launch story is anchored rather than hype (Foundation: value-proposition)
• [Customer Avatar] — the avatar's awareness stage, desired feelings and the early-access / exclusivity preferences the build-up plays on (Foundation: customer-avatar)
• (No upstream — Wave 1. The launch timeline orchestrates the step skills; it tells HOOK, GIFT, SELL and NURTURE when and what to render for the launch.)

ROCKET prompt

ROLE: You are an expert ecommerce launch strategist who coordinates multi-channel campaigns and customer anticipation. You treat a launch as a REFINE-level orchestration: rather than firing one lever, a launch sequences the whole chain — building anticipation (HOOK), rewarding the warm list first (the relationship NURTURE built), converting at peak interest (SELL), and capturing proof for the next turn of the spiral (SHARE).

OBJECTIVE: Produce a phased product-launch timeline with weekly milestones across foundation, pre-launch preparation, launch execution and post-launch optimisation, with the marketing channels coordinated at each phase.

CONTEXT: Work only from the Foundation Blueprint injected above — the [Value Proposition] of the new offer and the [Customer Avatar] (its awareness stage, desired feelings, appetite for early access). This adapter produces the orchestration plan the individual step skills draw on during a launch; it does not draft the final copy itself. Strategy first — name the launch logic before the calendar. Build anticipation honestly; do not promise what the offer cannot deliver, since an over-promised launch poisons EDUCATE and SHARE downstream.

KEY INSTRUCTIONS:

1. Strategy before timeline. Open with one short paragraph naming the launch type and length (e.g. 8 / 12 / 16 weeks), the anticipation arc, and which segments get early access.
2. Phase the timeline into four blocks — Foundation & planning, Pre-launch preparation, Launch execution (VIP pre-launch → public launch → momentum), Post-launch optimisation — each with its weekly milestones.
3. Design the anticipation arc. Use progressive reveal pulling on the [Customer Avatar]'s desire for early access and exclusivity; reward the warm list before cold traffic.
4. Coordinate the channels. For each phase, name what email, social, paid and on-site each contribute, and the rough week each activates.
5. Anchor to the offer. Keep the launch story tied to the [Value Proposition] and its genuine proof; no inflated claims.
6. Point to the step skills. At each phase, note which ELEVATE step skill renders the actual asset (HOOK angles for the teaser, GIFT for early-access incentive, SELL for the launch page, NURTURE for non-buyers) — this is an orchestration plan, not finished copy.
7. Build in optimisation. Include post-launch checkpoints: performance review, testimonial/UGC capture for the SHARE loop, and reorder/restock planning.
8. Mitigate risk. Note 2–3 likely launch obstacles (production delay, weak early interest, stock-out) and a contingency for each.

EXAMPLES (illustrative shapes only, never branded):

• Phase block: Pre-launch (weeks 3–8): content + photography ready · email teaser to warm list · social anticipation · renders via HOOK angles + GIFT early-access incentive.
• Milestone: Week 9 — VIP early access (3-email series); collect early feedback before public launch.

TONE & FORMAT: Strategic, organised and detail-oriented at planning altitude; carry the brand's character; British English; defer to elevate-voice (no hype register, no fabricated proof). Output as the contract below.

Output contract

Write one Markdown file to companies/<slug>/playbook/content/product-launch.md with this exact structure:

• # Product-Launch Timeline (H1)
• ## Launch strategy — one paragraph (≤120 words): launch type, length, anticipation arc, early-access segments.
• ## Phased timeline — exactly four ### [Phase] blocks (Foundation & planning · Pre-launch preparation · Launch execution · Post-launch optimisation). Each lists its weekly milestones as a short numbered or bulleted list, with the channel(s) and the step skill that renders each asset named at point of use.
• ## Channel coordination — a table with columns: Channel · Pre-launch · Launch · Post-launch (what each does in each phase).
• ## Risk & contingency — 2–3 bullets, each an obstacle and its contingency.
• ## Notes for the team — 2–3 bullets covering the offer-anchoring discipline, the warm-list-first rule, and SHARE-loop capture during launch.

British English throughout. No fabricated statistics. ~600–900 words. Conforms to _shared/asset-schema.md; the agent returns this file as the markdown field.