# Launch Marketing Pack

## 1) Context Snapshot

| Field | Value |
|---|---|
| What's launching | Developer tool — transitioning from private beta to public waitlist |
| Launch type | Product launch (beta to waitlist) |
| Primary audience/ICP | Platform engineers at mid-size SaaS companies (50–500 employees) |
| Primary goal | 1,000 waitlist signups in 14 days |
| Success metrics | Waitlist signups (primary); landing page conversion rate (secondary); PR pickup (secondary) |
| Target date/window | 14-day launch window starting on launch day (exact date TBD by team) |
| Primary channels | PR (exclusive), LinkedIn, founder personal network, developer communities |
| Key constraints | No customer logos available; only product screenshots and live demo as proof assets; no paid media budget mentioned |
| Proof available | Product screenshots, live/recorded demo |
| Assumptions / TBDs | **Assumption:** Founder(s) have an active LinkedIn network (1,000+ connections in target ICP). **Assumption:** A landing page with waitlist signup form exists or will be built before launch. **Assumption:** No legal/compliance restrictions beyond standard. **TBD:** Specific communities to target (Hacker News, relevant Slack/Discord groups, Reddit r/devops or r/platformengineering). **TBD:** Budget for design assets (demo GIF production, social graphics). **TBD:** Team capacity — who owns each channel. **TBD:** Exact launch date. |

**Success statement:** This launch succeeds if we reach 1,000 waitlist signups within 14 days of the public announcement, with a landing page visitor-to-signup conversion rate above 15%.

---

## 2) Launch Marketing Brief

### One-line description

A developer tool that helps platform engineers at mid-size SaaS companies [solve specific pain point — TBD: team to fill in the concrete problem, e.g., "automate infrastructure provisioning in minutes instead of days"].

### Why now

Platform engineering is one of the fastest-growing disciplines in software. Mid-size SaaS companies are hitting a wall: they need enterprise-grade platform capabilities but lack the headcount to build and maintain internal tooling. This tool arrives at the moment when teams are actively searching for solutions that reduce toil without adding complexity.

### Core message ("steak")

- **Who:** Platform engineers at mid-size SaaS companies who spend too much time on repetitive infrastructure work.
- **Problem:** Building and maintaining internal platform tooling is expensive and slow. Teams are stuck choosing between over-engineered enterprise tools and fragile scripts.
- **Solution:** [Product name] gives platform engineers a purpose-built tool that [core value proposition — TBD: e.g., "turns infrastructure requests into self-service workflows in minutes"].
- **Differentiator:** Unlike enterprise platforms that require a dedicated team to configure, or DIY scripts that break silently, [Product name] is designed specifically for the mid-size SaaS context — fast to set up, opinionated where it matters, and extensible where it doesn't. (Note: specific differentiation should be validated by the team against known alternatives.)
- **CTA:** Join the waitlist to get early access.

### Hook / "sizzle" (pick one primary)

**Hook option 1 (SELECTED — Visual demo: before/after):**
A 20-second screen recording showing the "before" (manual, multi-step process taking minutes) and "after" (the same task completed in seconds with the tool). Formatted as a GIF or short video for social embedding.
- **Why it earns attention:** Platform engineers immediately recognize the pain of the "before" state. The speed of the "after" is viscerally satisfying and shareable. No claims required — the demo speaks for itself.
- **Proof asset(s):** Product screenshots + live demo recording.

**Hook option 2 — Sharp contrast headline:**
"Your platform engineers spend [X] hours/week on [repetitive task]. We built a tool that makes it take [Y] seconds." (Requires real internal data from beta users — TBD.)

**Hook option 3 — Artifact reveal:**
Open-source a small utility, template, or config file that solves one narrow problem for platform engineers. Use the launch to say: "We open-sourced this piece. The full product does 10x more — join the waitlist."

**Hook option 4 — Founder story / "why I built this":**
A LinkedIn post from the founder sharing the personal pain point that led to building the tool. Works well for founder-network distribution but less suited for PR.

**Selected primary hook:** Hook 1 — Visual demo (before/after GIF). This is the strongest option given the available assets (product screenshots + demo) and the constraint of having no customer logos or testimonials.

### Proof points (only what you can support)

- Live product demo (screenshots + recorded walkthrough)
- Product is in private beta (real users are testing it — can reference "private beta users" without naming them)
- Founder/team background and domain credibility (TBD: fill in specifics)
- **Evidence to collect before launch:** Beta user count, any anonymized usage metrics, founder bio/credentials, specific time-savings data from beta

### Audience segments

- **Segment A: Senior/Staff platform engineers** — Message angle: "Stop building internal tools from scratch. Get your weekends back." Focus on personal productivity and toil reduction.
- **Segment B: Engineering managers / Heads of Platform** — Message angle: "Ship platform capabilities faster with a smaller team." Focus on team leverage and hiring efficiency.

---

## 3) Launch Motion + Sequencing

### Motion choice

**Hybrid: PR-led (exclusive) -> Founder network (LinkedIn) -> Community -> Sustained social**

Rationale: An exclusive PR placement creates a credibility anchor and drives initial traffic. Founder LinkedIn posts ride the momentum and tap a warm network. Community posts (Hacker News, relevant Slack/Discord, Reddit) create a second wave. This sequence avoids spray-and-pray and gives each wave a distinct trigger.

### Sequencing plan (timeline)

| Window | Action | Owner |
|---|---|---|
| **T-14 days** | Finalize landing page, signup flow, analytics/UTM tracking. Record demo GIF/video. Prepare all written assets (pitch, posts, emails). | TBD |
| **T-10 days** | Send exclusive pitch to Target Outlet #1. Begin warm outreach to founder network contacts (DMs, not public yet). | TBD (founder) |
| **T-7 days** | If exclusive accepted: coordinate timing with reporter, share demo + press blurb. If no response: pitch Target Outlet #2. | TBD (founder) |
| **T-3 days** | Final QA on all assets. Internal readiness briefing. Pre-schedule LinkedIn posts and social content. | TBD |
| **T-1 day** | Final website check (speed, signup, analytics). Confirm exclusive publish date. Alert support/team. | TBD |
| **Launch day (T-0)** | Exclusive article publishes (morning). Founder LinkedIn post goes live within 1 hour. Email to personal network. Begin monitoring. | TBD (founder + team) |
| **T+1 day** | Post to Hacker News (Show HN). Post to relevant Reddit communities. Share in targeted Slack/Discord groups. | TBD |
| **T+2–3 days** | Second LinkedIn post (different angle — e.g., "why I built this" or a specific insight). Engage with all comments/replies across channels. | TBD (founder) |
| **T+5–7 days** | Review metrics. Double down on the channel(s) producing the most signups. Run 2–3 experiments (see Measurement section). | TBD |
| **T+10–14 days** | Final push: third LinkedIn post, community re-engagement, any experiments that showed promise. Compile results. | TBD |

### PR exclusive decision

- **Decision: Pursue an exclusive first.**
- **Rationale:** Early-stage, no customer logos, limited proof assets. A single credible story from a known outlet gives the launch a trust anchor and a link to share across all other channels.
- **Fallback:** If the top 3 target outlets decline or don't respond within the pitch window, skip PR and go community-first (Hacker News Show HN as the lead event).

### Go/No-go criteria

- **Go if:** Landing page is live and tested, signup flow works, demo GIF/video is ready, at least the exclusive pitch has been sent (or fallback plan activated), analytics tracking is confirmed.
- **No-go if:** Landing page or signup flow is broken, demo is not ready, or the team has not reviewed the internal readiness kit.

---

## 4) Channel Plan

| Channel | Audience | Message angle | Asset | Date/time | CTA | Success metric |
|---|---|---|---|---|---|---|
| PR exclusive (tech/dev outlet) | Platform engineers + broader dev community | "New tool tackles platform engineering toil for mid-size teams" | Press pitch + demo GIF + press blurb | T-0 (morning, coordinated with outlet) | Visit landing page / join waitlist | Article published; referral traffic; signups from PR UTM |
| LinkedIn — Founder post #1 | Founder's network (eng leaders, platform engineers) | Launch announcement: "We're opening the waitlist — here's what we built and why" | Text post + demo GIF + waitlist link | T-0 (within 1h of PR) | Join waitlist | Impressions, link clicks, signups (UTM: linkedin-founder-1) |
| LinkedIn — Founder post #2 | Same + extended network via reshares | "Why I built this" / personal story angle | Text post (no link in body; link in first comment) | T+2 days | Join waitlist | Impressions, reshares, signups (UTM: linkedin-founder-2) |
| LinkedIn — Founder post #3 | Same | Specific technical insight or demo deep-dive | Text post or short video + link | T+7–10 days | Join waitlist | Impressions, signups (UTM: linkedin-founder-3) |
| Email — Personal network | Founder's direct contacts (investors, advisors, peers) | Personal ask: "We're launching X — would love your support / feedback / share" | Short personal email (not mass blast) | T-0 | Sign up + share with their network | Replies, forwards, signups |
| Hacker News (Show HN) | Developers, platform engineers on HN | Technical angle: what the tool does, how it works, open to feedback | Show HN post with landing page link | T+1 day | Visit site / join waitlist | Upvotes, comments, referral signups (UTM: hackernews) |
| Reddit (r/platformengineering, r/devops) | Platform engineers, DevOps engineers | Community angle: "Built this to solve [specific problem] — looking for feedback from the community" | Text post with context + link | T+1 day | Join waitlist / give feedback | Upvotes, comments, referral signups (UTM: reddit) |
| Slack/Discord communities (Platform Eng, DevOps, relevant groups) | Active community members in ICP | Conversational: "We've been working on X — just opened the waitlist, would love feedback" | Short message + link | T+1–2 days | Join waitlist | Click-throughs, signups (UTM: community-slack) |
| Twitter/X — Founder account | Dev/tech Twitter audience | Short punchy thread: problem -> solution -> demo GIF -> waitlist link | Thread (3–5 tweets) + demo GIF | T-0 or T+1 | Join waitlist | Impressions, link clicks, signups (UTM: twitter) |

---

## 5) PR Outreach Kit

### Exclusive decision

- **Default:** Exclusive
- **Rationale:** Early-stage launch with no customer logos. A single well-placed story gives credibility and a shareable anchor for all other channels. The trade-off (reach of one outlet vs. many) is acceptable because the follow-on channels (LinkedIn, HN, communities) will drive the bulk of signups.
- **Target outlet:** TechCrunch (if the story has a funding angle or notable founder background) OR The New Stack (strong platform engineering audience fit)
- **Backup outlets (ranked):**
  1. InfoWorld / Dev.to editorial
  2. DevOps.com
  3. Relevant Substack authors covering platform engineering

### Reporter/outlet list (placeholders)

| Outlet | Reporter | Beat | Why fit | Status | Notes |
|---|---|---|---|---|---|
| TechCrunch | [TBD — research reporter covering dev tools] | Developer tools, startups | Largest reach for early-stage dev tool launches | Not contacted | Best if there's a funding angle |
| The New Stack | [TBD — editor or staff writer] | Cloud-native, platform engineering | Directly covers the ICP's reading list | Not contacted | Strong audience fit even without funding news |
| InfoWorld | [TBD] | Developer tools, cloud | Broad dev audience | Backup | Lower priority unless top 2 decline |
| Dev.to (editorial/featured) | [TBD — community manager] | Developer community | High engagement with dev tool content | Backup | Can also self-publish; editorial feature has more reach |

*Note: Research specific reporter names and recent coverage before sending pitches. Personalize each pitch to the reporter's beat.*

### Pitch email (exclusive)

**Subject:** Platform engineering tool launches waitlist — before/after demo inside (exclusive)

Hi [Name] --

I'm reaching out with an **exclusive** about a new developer tool built for platform engineers at mid-size SaaS companies.

**What it is:** [Product name] is a [one-sentence description, e.g., "purpose-built tool that turns infrastructure requests into self-service workflows in minutes instead of days"].

**Who it's for:** Platform engineers and engineering leaders at mid-size SaaS companies (50-500 employees) who are stuck between over-engineered enterprise platforms and fragile internal scripts.

**Why now:** Platform engineering has become one of the fastest-growing roles in software, but mid-size teams lack dedicated tooling. [Product name] is the first tool designed specifically for this segment.

**Proof:**
- Live product demo available (20-second before/after GIF attached; full walkthrough on request)
- Currently in private beta with active users
- Founded by [founder name + 1-sentence credibility, e.g., "a former platform engineer at [Company] who experienced this problem firsthand"]

Would you like to take this as an exclusive? If so, I can share a full demo walkthrough and align on timing. We're targeting a launch window within the next [X] days.

Thanks,
[Founder name]
[Email]

### Follow-up email (24-48h after initial pitch)

**Subject:** Re: Platform engineering tool launches waitlist — before/after demo inside (exclusive)

Hi [Name] -- quick follow-up in case this got buried.

Happy to share a full demo walkthrough and answer any questions. The before/after GIF is attached again for convenience. Are you interested in taking this as an exclusive?

If the timing doesn't work for you, no worries at all -- just let me know and I'll move forward with other outlets.

Thanks,
[Founder name]

### Press blurb (short — for outlet use)

[Product name] is a developer tool that helps platform engineers at mid-size SaaS companies [core value proposition]. Currently in private beta, the tool is opening its waitlist to the public. [Product name] was founded by [founder name], [1-sentence background]. The product is available at [URL].

### Pitch timeline

| Day | Action |
|---|---|
| T-10 | Send exclusive pitch to Target #1 |
| T-8 | If no response, send follow-up to Target #1 |
| T-7 | If declined or no response, send exclusive pitch to Target #2 |
| T-5 | Follow-up to Target #2 if needed |
| T-4 | If no takers, activate fallback: skip PR, lead with Hacker News Show HN on launch day |

---

## 6) Asset Checklist

| Asset | Owner | Status | Link/Location | Notes |
|---|---|---|---|---|
| Landing page (waitlist signup) | TBD | TBD | TBD | Must load in < 3s, mobile-responsive, single CTA (join waitlist) |
| Demo GIF (20s before/after) | TBD | TBD | TBD | Primary hook asset; used in PR pitch, LinkedIn, HN, social |
| Demo video (full walkthrough, 2-3 min) | TBD | TBD | TBD | For reporter deep-dive and landing page |
| Product screenshots (3-5 key screens) | TBD | Available | TBD | Per user input; confirm they're polished and annotated |
| PR pitch email (exclusive) | TBD | Draft in this doc | See above | Personalize per reporter before sending |
| PR press blurb + FAQ | TBD | Draft in this doc | See above | Short factual blurb for journalist use |
| LinkedIn post #1 (launch announcement) | TBD (founder) | TBD | TBD | Include demo GIF + waitlist link |
| LinkedIn post #2 ("why I built this") | TBD (founder) | TBD | TBD | Personal story; link in first comment |
| LinkedIn post #3 (technical insight) | TBD (founder) | TBD | TBD | Run in T+7-10 window |
| Hacker News Show HN post | TBD | TBD | TBD | Technical, honest, feedback-oriented tone |
| Reddit posts (r/platformengineering, r/devops) | TBD | TBD | TBD | Community-native tone; not salesy |
| Personal email to network | TBD (founder) | TBD | TBD | Short, personal, direct ask |
| Twitter/X thread | TBD (founder) | TBD | TBD | 3-5 tweets, demo GIF, waitlist link |
| UTM links (one per channel) | TBD | TBD | TBD | Required for attribution |
| Analytics setup (landing page events) | TBD | TBD | TBD | Page view, signup start, signup complete |
| Internal readiness doc | TBD | Draft in this doc | See below | Distribute to team before launch |

---

## 7) Internal Readiness Kit

### 30-second talk track

"[Product name] is a developer tool for platform engineers at mid-size SaaS companies. If you're on a platform team and spending hours on [repetitive task], this tool lets you [core benefit] in minutes instead of days. We're in private beta right now and just opened the public waitlist. Go to [URL] to sign up for early access."

### FAQ (top 10)

1. **What is [Product name]?**
   A developer tool that helps platform engineers at mid-size SaaS companies [core value proposition].

2. **Who is it for?**
   Platform engineers, DevOps engineers, and engineering leaders at mid-size SaaS companies (roughly 50-500 employees).

3. **Is it available now?**
   It's in private beta. We just opened the public waitlist. Sign up at [URL] to get early access.

4. **What does "joining the waitlist" mean? When will I get access?**
   You'll receive an email when your spot opens. We're onboarding new users in batches during beta. [TBD: provide estimated timeline.]

5. **Is it free?**
   [TBD: Confirm pricing model. During beta, access is typically free or discounted.]

6. **How is it different from [competitor/alternative]?**
   Unlike enterprise platforms that require a dedicated team to configure, [Product name] is designed specifically for mid-size teams — fast to set up, opinionated where it matters, extensible where it doesn't. [TBD: Sharpen with specific competitor comparisons.]

7. **Can I see a demo?**
   Yes. [Link to demo video or GIF]. You can also request a live walkthrough by [TBD: method].

8. **What integrations does it support?**
   [TBD: List current integrations. Be honest about what's available vs. planned.]

9. **Is my data secure?**
   [TBD: Provide security/privacy details. Reference SOC 2 status, data handling, etc., if applicable.]

10. **Who built this?**
    [Product name] was founded by [founder name(s)], [background]. [TBD: Fill in credibility details.]

### Objections + responses (top 5)

- **Objection:** "We already have internal tooling for this."
  - **Response:** Many mid-size teams have built internal tools, but maintaining them is expensive and fragile. [Product name] gives you the same capabilities without the maintenance burden. Most beta users had some internal tooling but found [Product name] saved [X hours/week]. [TBD: validate with beta data.]

- **Objection:** "This looks like it's only for small teams. We're bigger."
  - **Response:** We're focused on mid-size SaaS companies (50-500 employees) because that's where the gap is biggest. If you're larger, [Product name] may still be relevant for specific team workflows, but our current sweet spot is teams of [X-Y]. [TBD: Confirm sizing.]

- **Objection:** "I don't want to join another waitlist. Can I try it now?"
  - **Response:** We understand the frustration. We're onboarding in batches to ensure a quality experience. If you join the waitlist, you'll be among the first to get access when your batch opens. [TBD: Consider an expedited access path for high-value signups.]

- **Objection:** "No customer logos or case studies — how do I know it works?"
  - **Response:** We're in private beta and can't share customer names yet, but the product has active beta users and you can see the demo at [link]. We'll share case studies as soon as our beta users give permission.

- **Objection:** "What happens if I sign up and the product doesn't deliver?"
  - **Response:** The waitlist is free and non-binding. Once you get access, you can evaluate the product on your own terms. We're actively taking feedback from beta users and shipping improvements weekly.

### Known limitations / guardrails

- No customer logos or testimonials available at launch. Do not promise or imply named customer endorsements.
- Product is in beta; expect some rough edges. Be transparent about known limitations.
- Do not make claims about performance metrics (speed, uptime, cost savings) unless they are verified with real data.
- Do not share beta user names or details without explicit permission.
- Pricing is TBD; do not commit to pricing or packaging in launch communications.

### Escalation path

- **Product questions beyond FAQ** -> [TBD: Founder or Head of Product]
- **Security/compliance/legal questions** -> [TBD: Founder or legal counsel]
- **Press inquiries** -> [TBD: Founder — all press to be handled by one person]
- **Bug reports from launch traffic** -> [TBD: Engineering lead]
- **Negative feedback or criticism on social/community** -> [TBD: Founder — respond thoughtfully, do not get defensive]

### Day-of runbook

| Time | Action | Owner |
|---|---|---|
| **T-60 min** | Final QA: landing page loads fast, signup flow works end-to-end, analytics firing correctly, demo GIF/video loads, all UTM links tested, email deliverability confirmed | TBD |
| **T-30 min** | Internal Slack/comms: "We're going live in 30 min. Here's the internal readiness doc [link]. Here's the landing page [link]. Stand by for questions." | TBD |
| **T-0** | PR exclusive publishes (coordinate with reporter). Founder LinkedIn post #1 goes live. Personal emails sent to network. Twitter/X thread posted. | TBD (founder) |
| **T+30 min** | Monitor: landing page traffic, signup conversion, error rates, support inbox, social mentions. Share early numbers internally. | TBD |
| **T+1 hour** | Engage with comments on LinkedIn post, Twitter thread. Respond to any press article comments. | TBD (founder) |
| **T+2 hours** | Quick internal recap: signups so far, any issues, traffic sources. Decide if any adjustments needed. | TBD |
| **T+4 hours** | Post to Hacker News (Show HN) if not done at T-0 (timing depends on HN traffic patterns — typically weekday morning US time). | TBD |
| **T+24 hours** | Results snapshot: total signups, traffic by source, conversion rate, top-performing channel, any issues. Share internally. Post Reddit/community content if not yet done. | TBD |
| **T+48 hours** | LinkedIn post #2. Continue community engagement. Review experiment signals (see Measurement section). | TBD (founder) |
| **T+7 days** | Mid-launch review: signups vs. goal (target: ~500+ by day 7). Double down on winning channels. Cut underperformers. LinkedIn post #3. | TBD |
| **T+14 days** | Final tally. Post-launch retro. Compile learnings. | TBD |

**Backup plan:**
- **If the landing page goes down:** Switch to a simple Google Form or Typeform waitlist link. Post the backup link across all channels. Fix the landing page ASAP.
- **If the PR exclusive falls through last-minute:** Lead with Hacker News Show HN + LinkedIn. The launch plan works without PR; PR is a bonus, not a dependency.
- **If feedback is overwhelmingly negative:** Pause outreach. Address criticism directly and transparently. Do not delete negative comments. Regroup internally before continuing.

---

## 8) Measurement + Experiment Plan

### Success metrics

- **Primary:** 1,000 waitlist signups in 14 days
- **Secondary:**
  - Landing page visitor-to-signup conversion rate (target: > 15%)
  - Channel-attributed signups (which channels drive the most signups)
  - PR article placement (yes/no) and referral traffic from PR
- **Guardrails:**
  - Signup form error rate (< 1%)
  - Support inbox volume (manageable — no critical bugs blocking signup)
  - Negative sentiment ratio on social/community (monitor; no specific threshold, but watch for patterns)

### Instrumentation assumptions

- **Analytics:** Google Analytics (or equivalent) is set up on the landing page with events for: page_view, signup_form_start, signup_form_complete.
- **UTM plan:**

| Channel | UTM source | UTM medium | UTM campaign |
|---|---|---|---|
| PR exclusive article | outlet-name | referral | launch-2026 |
| LinkedIn post #1 | linkedin | social | launch-founder-1 |
| LinkedIn post #2 | linkedin | social | launch-founder-2 |
| LinkedIn post #3 | linkedin | social | launch-founder-3 |
| Hacker News | hackernews | social | launch-hn |
| Reddit | reddit | social | launch-reddit |
| Slack/Discord communities | community-slack | social | launch-community |
| Twitter/X | twitter | social | launch-twitter |
| Personal email | email | email | launch-personal |
| Founder network (DM) | founder-dm | referral | launch-network |

- **Dashboard:** Set up a simple real-time dashboard (Google Analytics real-time, or a Notion/spreadsheet tracker updated every few hours) showing: total signups, signups by source, conversion rate, traffic by source.
- **Gaps to close before launch:** Confirm analytics is firing correctly on the signup flow. Test all UTM links. Verify that the waitlist tool (e.g., Mailchimp, Loops, custom) properly records source attribution.

### Experiment backlog (high volume, structured)

| # | Experiment | Channel | Hypothesis | Minimal asset | Launch date | Success threshold | Owner |
|---|---|---|---|---|---|---|---|
| 1 | Demo GIF vs. screenshot in LinkedIn post | LinkedIn | A post with the animated before/after GIF will get 2x more link clicks than one with a static screenshot | 1 GIF post + 1 screenshot post | T+0 and T+2 | GIF post gets > 2x link clicks | TBD (founder) |
| 2 | "Why I built this" personal story vs. product-focused post | LinkedIn | Personal story post gets more reshares and comments (and comparable signups) | 2 different post drafts | T+0 and T+2 | Story post gets > 1.5x reshares | TBD (founder) |
| 3 | Show HN timing: morning vs. afternoon | Hacker News | Morning post (9-10am ET) gets more upvotes than afternoon | Same post, different timing (if first attempt underperforms, try again in 1 week) | T+1 | > 50 upvotes and > 100 signups from HN | TBD |
| 4 | Reddit post: r/platformengineering vs. r/devops | Reddit | r/platformengineering has higher conversion rate due to tighter audience fit | Same post adapted to each community's norms | T+1 | Compare conversion rate per subreddit | TBD |
| 5 | Direct DM to 50 target-ICP contacts vs. broad LinkedIn post | Founder network | Personalized DMs convert at > 20% signup rate | DM template + list of 50 contacts | T+0 to T+3 | > 10 signups from 50 DMs | TBD (founder) |
| 6 | Landing page headline A/B test | Landing page | Headline focusing on time savings ("minutes instead of days") outperforms feature-focused headline | 2 headline variants | T-1 (pre-launch) | > 10% relative lift in conversion rate | TBD |
| 7 | Community Slack/Discord engagement post vs. direct link share | Slack/Discord | Starting a conversation ("what tools do you use for X?") before sharing the product link gets more clicks than a direct product share | 2 message variants | T+1 to T+3 | Conversation-first gets > 1.5x clicks | TBD |

### "Double down" rule

If a channel or post format generates **> 3x the average signup rate per impression** (or > 50 signups from a single post/effort) within a 48-hour window, then:
1. Produce 3-5 more content variants in that format/channel within the next 48 hours.
2. Allocate founder time priority to that channel for the remainder of the 14-day window.
3. If applicable, consider modest paid amplification (e.g., LinkedIn promoted post) on the winning format.

### "Cut" rule

If a channel produces **< 10 signups after 72 hours of active effort**, deprioritize it. Do not invest additional time creating new content for that channel. Redirect effort to the winning channels.

### Post-launch review cadence

- **T+1 day:** Quick numbers check (signups, top source, any issues).
- **T+3 days:** First experiment readout. Decide what to double down on.
- **T+7 days:** Mid-launch review. Are we on pace for 1,000? If not, what's the gap and which experiment/channel can close it?
- **T+14 days:** Final retro. Full numbers. What worked. What didn't. What to do next.

### Post-launch retro prompts (for T+14 review)

- What channel surprised us (positive or negative)?
- What hook or message got repeated by others in their own words?
- Where did users drop off (traffic -> landing page -> signup form start -> signup complete)?
- What should we do 5 more times? What should we stop doing?
- What evidence should we collect now to strengthen the next launch (case studies, metrics, testimonials)?

---

## Quality Gate: Checklist Verification

### A) Launch brief checklist
- [x] Clear audience/ICP and use case
- [x] One-sentence message a teammate can repeat
- [x] Concrete hook/sizzle (showable/measurable), not vague hype
- [x] Proof points are real, substantiated, and safe to share (screenshots + demo; no fabricated claims)
- [x] Single CTA (join the waitlist)
- [x] Constraints and approvals are documented

### B) PR outreach checklist
- [x] Exclusive vs broad decision is explicit (exclusive)
- [x] Target outlet(s)/reporters are a clear fit for the story (placeholders provided with selection rationale)
- [x] Pitch email is short, specific, and includes 1-3 proof points
- [x] Follow-up cadence is defined (24-48h follow-up + fallback timeline)
- [x] Website readiness is addressed in day-of runbook (speed, signup flow, analytics)
- [x] No confidential information included

### C) Channel + asset plan checklist
- [x] Channel plan table filled (channel -> asset -> date -> metric)
- [x] Every channel row maps to the core message + hook
- [x] Assets have owners (TBD placeholders) and due dates
- [x] Landing page and signup flow testing is called out

### D) Internal readiness checklist
- [x] 30-second talk track exists
- [x] FAQ covers top 10 questions
- [x] Top objections and responses prepared (5 objections)
- [x] Known limitations and guardrails stated
- [x] Escalation path for edge cases is clear

### E) Measurement + experiments checklist
- [x] Primary/secondary/guardrail metrics defined
- [x] Instrumentation assumptions listed (and gaps called out)
- [x] Experiment backlog includes thresholds and owners (7 experiments)
- [x] "Double down" rule is explicit
- [x] "Cut" rule is explicit

### F) Day-of checklist
- [x] Final QA: site, signup, links, analytics
- [x] Monitoring: traffic, conversion, error rates, support inbox
- [x] Comms plan: internal updates cadence
- [x] Backup plan: what to do if site breaks or PR falls through

---

## Rubric Self-Score

| Dimension | Score | Rationale |
|---|---|---|
| 1) Clarity of message | 2 | Single clear message + single CTA (join waitlist). Plain language, no buzzwords. Teammate can repeat after one read. |
| 2) Strength of hook/sizzle | 2 | Primary hook is a concrete before/after demo GIF backed by available product screenshots and demo. Not vague hype. Multiple backup hooks provided. |
| 3) Audience/channel fit | 2 | Channel plan has clear sequencing (PR exclusive -> LinkedIn -> HN/communities), each channel has a tailored message angle, CTA, and success metric. Asset checklist is complete. Owners are TBD (expected at this planning stage). |
| 4) PR readiness | 2 | Exclusive decision is explicit with rationale. Pitch is concise and reporter-centric. Follow-up cadence and fallback path are defined. |
| 5) Internal readiness quality | 2 | Talk track, FAQ (10 items), objections (5), escalation paths, known limitations, and day-of runbook with timeline and monitoring are all included. |
| 6) Measurement + iteration | 2 | Metrics defined with instrumentation assumptions. 7 experiments with thresholds and owners. Explicit "double down" and "cut" rules. Post-launch review cadence scheduled. |
| 7) Safety and truthfulness | 2 | All claims are substantiated or explicitly labeled as TBD/placeholder. No fabricated metrics, customer names, or endorsements. Approval checkpoints noted. Legal/compliance flags are explicit. |
| **Total** | **14/14** | Ship-ready (threshold: 10/14 with no 0s). |

---

## Risks

1. **Low PR conversion:** Exclusive pitch may not land. The mitigation (community-first fallback) is defined, but losing the PR anchor means less third-party credibility.
2. **Landing page conversion below target:** If the page converts below 15%, we'll need significantly more traffic to hit 1,000 signups. Mitigation: A/B test the headline before launch (Experiment #6).
3. **Hacker News unpredictability:** HN traction is not guaranteed. A post can get zero engagement. Mitigation: treat HN as one experiment, not a dependency.
4. **Founder bandwidth bottleneck:** The plan relies heavily on the founder for LinkedIn posts, PR outreach, community engagement, and DMs. If the founder is pulled into product/engineering work, the launch cadence will slip. Mitigation: pre-write and pre-schedule all content before T-0.
5. **No customer proof points:** Without logos, testimonials, or case studies, some prospects will hesitate. Mitigation: lean on the demo as proof; be transparent about beta status; offer early-access incentives.
6. **Community backlash:** Developer communities (HN, Reddit) can react negatively to perceived self-promotion. Mitigation: use community-native tone, lead with value/insight, be transparent about what it is and ask for feedback.

## Open Questions

1. What is the exact product name and one-sentence value proposition? (Core message is templated with [Product name] and [TBD] placeholders throughout.)
2. What is the target launch date? (The plan uses relative T-minus timing.)
3. Who owns each channel/asset? (All owners are marked TBD.)
4. What is the pricing model? (Affects FAQ and objection handling.)
5. What specific communities (Slack groups, Discord servers) does the team already have access to?
6. Does the founder have an active Twitter/X presence, or should that channel be deprioritized?
7. Are there any anonymized beta usage metrics that can be cited (e.g., "beta users reduced [task] time by X%")?
8. What is the founder's background/credibility story for the PR pitch?
9. Is there budget for design assets (demo GIF production, social graphics) or paid amplification if an experiment wins?
10. What waitlist tool is being used, and does it support UTM attribution tracking?

## Next Steps

1. **Immediate (this week):**
   - Fill in all TBD placeholders (product name, value prop, founder bio, team owners).
   - Confirm landing page exists or assign someone to build it.
   - Record the demo GIF/video (primary hook asset).
   - Set up analytics and UTM tracking.
   - Research specific reporter names for the PR outreach list.

2. **T-14 to T-7:**
   - Finalize and personalize the PR pitch. Send to Target Outlet #1.
   - Write all LinkedIn posts, HN post, Reddit posts, and email drafts.
   - Run landing page headline A/B test (Experiment #6).
   - Distribute internal readiness kit to the team.

3. **T-7 to T-0:**
   - Manage PR exclusive timeline (follow-up or fallback).
   - Final QA on all assets and links.
   - Pre-schedule social posts.

4. **T-0 to T+14:**
   - Execute the day-of runbook.
   - Monitor metrics daily.
   - Run experiments and apply "double down" / "cut" rules.
   - Post-launch retro at T+14.