1. ./brands/{brand-slug}/brand-context.md

   -- brand identity, audience, USP

2. ./brands/{brand-slug}/product-marketing-context.md

   -- deep positioning, customer language, objections (read if it exists)

3. ./brands/{brand-slug}/sostac/03-strategy.md

   -- target segments, positioning, phasing

4. ./brands/{brand-slug}/sostac/04-tactics.md

   -- channel plan, launch role, budget, priorities

5. ./brands/{brand-slug}/sostac/05-action.md

   -- action plan and timeline (read if it exists)

./brands/{brand-slug}/campaigns/launch/

./brands/{brand-slug}/sostac/00-auto-discovery.md

Setup: Before running research, check if

agent-browser

is available (

agent-browser --version

). If the command is not found, install it:

npm install -g agent-browser && npx playwright install chromium

. If installation fails, use

WebFetch

and

WebSearch

tools as alternatives for all research tasks in this section.

undefined

• Tier 1 (Major launch -- full treatment): New product, major feature, category entry, or partnership. Full ORB channel activation, Product Hunt strategy, press outreach, launch content suite, phased timeline.
• Tier 2 (Minor launch -- scaled treatment): Monthly minor feature or improvement. Blog announcement, email to user base, 3-5 social posts. No press release, no Product Hunt.
• Tier 3 (Patch cadence): Weekly or biweekly changelog update, one social post, in-app notification if relevant.

1. What is the specific product or feature being launched?
2. Is this a Tier 1, 2, or 3 launch?
3. What is the target launch date?
4. What channels does the brand currently own (email list size, social accounts, community)?
5. Is Product Hunt being considered? Does the brand have a support network that can vote?
6. Is there a PR / press budget or existing journalist relationships?
7. Are there any partners, influencers, or early users to activate?

• Email list (highest conversion channel in a launch)
• Blog / website
• In-product notifications and in-app banners
• Community (if the brand has one -- bridge to marketing-community)
• SMS / push notifications (if active)

• X / Twitter (threads, product announcements)
• LinkedIn (company page + founder posts)
• Instagram (feed posts, Stories, Reels)
• TikTok (if audience is present)
• YouTube (if brand has video presence -- bridge to marketing-video)
• App stores (if relevant -- featured section)

• Guest posts and editorial placements
• Podcast appearances (book 6-8 weeks ahead)
• Influencer seeding (micro to mid-tier -- bridge to marketing-influencer)
• Press coverage (bridge to marketing-pr)
• Partner email blasts and co-marketing
• Indie Hackers / Reddit / Hacker News organic posts
• Newsletter sponsorships or feature placements

• Product Hunt ranking (refresh hourly)
• Website traffic (GA4 real-time view)
• Signups / trial starts (product dashboard)
• Social mentions (search brand name on X, LinkedIn)
• Email open and click rate (ESP dashboard)
• Press coverage (Google Alerts + Google News)
• Server performance (ensure the site doesn't go down under traffic)

• Day 1: Monitor and respond to every mention, comment, and review. Thank every supporter personally.
• Day 2: Send "thank you" email with launch recap and milestone. Update landing page with social proof (PH badge, press logos, quotes).
• Day 3-5: Publish launch recap blog post. This performs well on Hacker News, Indie Hackers, and LinkedIn.
• Day 5-7: Follow-up email to signups who have not activated. Subject: "[First name], did you get a chance to try it?"
• Day 7: Report: signups, activation rate, traffic source breakdown, PH position, press mentions, social reach.

• Week 1: Begin onboarding email sequence (bridge to marketing-email). Personal outreach to top 20-30 highest-engaged signups for user interviews.
• Week 2: Publish first case study. Launch retargeting campaigns (bridge to marketing-paid-ads).
• Week 3: Evaluate early cohort metrics: activation rate, day-7 retention, NPS.
• Week 4: Send "one month in" email. Publish full launch performance report. Feed learnings into SOSTAC action plan.

• For pitches that did not convert, follow up at day 5-7 with launch results as the new angle.
• For journalists who covered the launch: thank them personally, share internally, stay on their radar.
• Bridge to marketing-pr for ongoing journalist relationship management.

• Press kit: updated product screenshots, founder headshots, company boilerplate, recent coverage logos. Store at

  ./brands/{brand-slug}/campaigns/launch/assets/press-kit/

  .
• Launch email templates: maintain 3-5 subject line formulas and body templates that can be adapted per launch.
• Social proof library: rotating bank of testimonials, case study quotes, and metrics. Update monthly.
• Supporter list: maintain a rolling list of launch supporters (Product Hunt voters, beta users who responded) for future launches.

• AI-native launches: Products with AI features should demo the AI in action in PH gallery and social content. Show the before/after, not the architecture.
• Short-form video: TikTok and Reels are increasingly effective for product launches targeting younger demographics. A 30-second founder-to-camera video can outperform a blog post for awareness.
• Community-led growth: Building a community pre-launch (Discord, Slack, Circle) creates a built-in supporter base. Bridge to marketing-community.
• Micro-launch cadence: Ship smaller updates publicly more often rather than saving everything for one big launch. Each update is a content moment.

1. Read brand context and SOSTAC (Section 0). Always. Ground every recommendation in the brand's actual strategy.
2. Run Research Mode for Tier 1 launches: Product Hunt category research and competitor launch analysis before finalizing strategy.
3. Clarify launch type (Section 1): Is this Tier 1, 2, or 3? New product or feature? What is the target date?
4. Assess current state: Check

   ./brands/{brand-slug}/campaigns/launch/

   for prior deliverables. Check what phase the brand is currently in.
5. Deliver specific, actionable output: Complete launch plans, full content drafts, day-by-day timelines -- never vague frameworks without specifics.
6. Save deliverables: Write all outputs to

   ./brands/{brand-slug}/campaigns/launch/

   with appropriate filenames.
7. Recommend next steps: What to do first, who owns it, and when the next gate decision is.

• Press release writing and journalist outreach -- bridge to marketing-pr.
• Email sequence for post-launch onboarding and nurture -- bridge to marketing-email.
• Paid retargeting for launch traffic -- bridge to marketing-paid-ads.
• Influencer or creator seeding program -- bridge to marketing-influencer.
• Community building for long-term audience ownership -- bridge to marketing-community.
• SEO optimization of launch blog post and landing page -- bridge to marketing-seo.
• Video production for demo GIF or launch Reel -- bridge to marketing-video.
• Analytics, UTM setup, and attribution reporting -- bridge to marketing-analytics.
• No SOSTAC plan exists -- recommend marketing-sostac before full launch planning.