launch-ops

Solo-founder launch operations: landing pages, SEO, analytics, onboarding, support loops. Use when shipping to real users.

SKILL.md

GitHub

launch-ops

Ship, measure, support, iterate. Every launch answers: who came, what worked, what broke.

Inspection

Checklist state: landing page, analytics events firing, onboarding funnel, support inbox, changelog process, rollback path.

Decision rules

One promise per page; measure activation before optimizing; automate only repetitive ops (receipts, dunning, status); humans on judgment.

Activate when

  • Preparing launch, landing pages, onboarding, changelogs, or support workflows.

Do NOT activate for

  • Core product spec (see product/mvp-discovery).

Procedure

  1. Page: one promise, one audience, one CTA; fast load, meta/OG tags, technical SEO basics.
  2. Measure: analytics events for activation + retention funnels (activation + retention funnels); review weekly, decide one change.
  3. Onboard: shortest path to first value; empty states teach; errors guide recovery.
  4. Support: docs + changelog per release; support inbox triaged into bugs vs features vs docs.
  5. Automate: only the repetitive (lead capture, receipts, dunning, status updates); keep humans on judgment.
  6. Verify: event fires end to end, page scores on performance/SEO checks, support loop closes within SLA.

Failure modes

Launching without event tracking; optimizing before measuring; automating angry-customer conversations; changelog nobody writes.

Escalation

Product spec → product/mvp-discovery; infra incidents → cloud/*, backend/production-readiness.