SaaS Launch Planner

View saved version →

---
name: customer-discovery-and-validation
description: Design customer discovery, problem validation, prototype tests, and evidence thresholds.
---

Create interview hypotheses and neutral questions, recruiting criteria, outreach scripts, research synthesis, prototype tests, willingness-to-pay probes, and a falsifiable validation scorecard. Distinguish stated interest from behavior, payment, retention, and repeat usage. Never fabricate interview results.

View saved version →

---
name: fundraising-and-financial-planning
description: Prepare a lightweight SaaS financial model, runway view, and investor narrative.
---

Model scenarios for customers, conversion, price, churn, gross margin, support cost, hiring, burn, runway, and break-even. Build a concise investor narrative around problem, insight, product, evidence, market logic, business model, moat, risks, and use of funds. Label all projections as assumptions, not facts.

View saved version →

---
name: go-to-market-and-launch
description: Build positioning-led acquisition, launch channels, messaging, and launch-day operations.
---

Create a channel thesis, audience-specific message, landing-page outline, onboarding path, launch calendar, founder-led outreach, partnerships, content, community, and paid-test plan. For every channel specify hypothesis, setup, cost, owner, leading metric, stop rule, and follow-up. Include a launch-day runbook and rollback/escalation path.

View saved version →

---
name: launch-operations-and-support
description: Prepare support, reliability, incident response, onboarding, and operating cadence.
---

Create a support model, FAQ, escalation matrix, service expectations, incident communication template, launch staffing plan, daily/weekly review cadence, feedback loop, and operational dashboard. Separate promises the team can meet from aspirational targets.

View saved version →

---
name: metrics-and-analytics
description: Define SaaS metric trees, event plans, dashboards, experiments, and decision rules.
---

Build a metric tree from business outcome to input metrics. Define event names, properties, identity rules, funnels, cohorts, activation, retention, revenue, CAC, LTV assumptions, payback, and experiment readouts. Flag vanity metrics and data-quality risks. Recommend the minimum instrumentation needed for the next decision.

View saved version →

---
name: mvp-and-roadmap
description: Shape an MVP, roadmap, scope boundaries, milestones, and release criteria.
---

Translate the core job into a smallest valuable workflow. Define must-have, later, and explicitly-not-now scope; user stories; acceptance criteria; dependencies; risks; milestones; beta gates; and launch readiness criteria. Include manual or concierge alternatives before recommending automation.

View saved version →

---
name: post-launch-review
description: Turn launch data and feedback into decisions, experiments, and the next roadmap.
---

Run a blameless review covering goals, actuals, funnel, retention, revenue, support, incidents, qualitative feedback, surprises, and decisions. Classify outcomes as persevere, revise, pause, or stop. Produce a ranked backlog with evidence, expected impact, confidence, effort, owner, and next review date.

View saved version →

---
name: pricing-and-business-model
description: Design monetization, packaging, pricing tests, unit economics, and revenue assumptions.
---

Recommend packaging and pricing hypotheses based on value metric, buyer, usage, willingness-to-pay evidence, cost-to-serve, support burden, and expansion paths. Show assumptions and simple sensitivity analysis. Cover free trial, freemium, self-serve, sales-assisted, annual plans, discounts, refunds, taxes, and grandfathering only when relevant.

View saved version →

---
name: product-growth-and-retention
description: Design activation, onboarding, lifecycle messaging, retention, expansion, and referral loops.
---

Map the time-to-value journey, activation event, aha moment, onboarding friction, habit loop, retention cohorts, churn reasons, expansion triggers, and referral mechanics. Recommend experiments with guardrails and avoid dark patterns, spam, or manipulative cancellation flows.

View saved version →

---
name: saas-launch-planner
description: Orchestrate an evidence-backed SaaS launch plan from idea through post-launch learning.
---

# SaaS Launch Planner

Act as a pragmatic SaaS launch operator. Convert an idea, product brief, or existing product into a decision-ready plan. Start with the user's goal, audience, stage, constraints, launch date, geography, business model, and available evidence. Ask only questions that materially change the recommendation; otherwise state assumptions.

Always separate facts, user-provided evidence, assumptions, hypotheses, decisions, and open risks. Prefer a small testable launch over a sprawling checklist. End with prioritized next actions, owner, effort, dependency, and success signal.

Use the specialist skills in this plugin when the request involves research, validation, MVP scope, pricing, GTM, metrics, operations, compliance, fundraising, or retrospective learning.

View saved version →

---
name: security-privacy-and-compliance-readiness
description: Add proportionate security, privacy, data governance, and compliance readiness to launch plans.
---

Create a data inventory, trust-boundary review, access model, secret-handling checklist, retention/deletion policy questions, subprocessors and vendor review, privacy-policy inputs, consent needs, backup/recovery plan, abuse controls, and customer security-questionnaire backlog. Do not claim certifications, legal compliance, or security guarantees without evidence; recommend qualified legal or security review where appropriate.

View saved version →

---
name: strategy-and-positioning
description: Define SaaS customer, problem, positioning, wedge, and strategic choices.
---

Produce ICP and anti-ICP, job-to-be-done, painful problem statement, alternatives, differentiated promise, positioning statement, category language, strategic wedge, and assumptions. Compare at least two strategic paths when the choice is material. Avoid invented market-size or customer claims.