[TERMINAL · SKILLS]
> mounting /skills...
> indexing skill manifests...
> linking agents: claude · codex · gemini · cursor
> ready.
[░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0%
Use Cases/Launch a SaaS Product to Market

Launch a SaaS Product to Market

Plan and execute a product launch that drives signups, press coverage, and early revenue from day one.

Business#launch#go-to-market#product-hunt#release-planning#product-marketing
Works with:claude-codeopenai-codexgemini-clicursor
agent@terminalskills — playground
full playground →

Try this use case on your own files

simulated preview
$
$

real run in an isolated sandbox · files auto-deleted after 7 days · nothing touches your machine

Skills stack · 3 skills

Avg quality 93/100·All SAFE
>

launch-strategy

v2.0.0

Turns "we ship on this date" into a dated launch plan: how big the announcement should be, the rollout stages and their exit criteria, the message, channels ranked by the audience the team really has, an asset list with owners, a launch-day runbook with rollback triggers, and the numbers to review afterwards. Includes the published rules for Product Hunt and Show HN. Use when someone says "plan our launch", "launch on Product Hunt", "Show HN", "announce this feature", "go-to-market plan", "beta launch", "waitlist", "early access rollout" or "how do we announce the new pricing".

100/100 quality
1.45× impact
SAFE
View skill
>

pricing-strategy

v2.0.0

Sets and reworks software pricing: which unit to charge for, how to split features and limits into plans, where to set each price, and how to move new and existing customers to it. Covers a first price for a product with no customers yet, diagnosis of the weak lever from billing and usage data, willingness-to-pay research, revenue modelling, and the migration and notice plan. Use when someone says "how much should I charge", "pricing tiers", "packaging", "value metric", "per seat or usage-based", "should we raise prices", "grandfather existing customers", "Van Westendorp", "willingness to pay", "free plan or trial", or "annual discount".

80/100 quality
1.40× impact
SAFE
View skill
>

product-marketing-context

v2.0.0

Creates and maintains `.claude/product-marketing-context.md`, one sourced file that records what the product is, who buys it, what they use instead, the proof behind each claim, customer wording, pricing and goals, so later marketing tasks read facts instead of asking again or guessing. Drafts it from the repository and site, interviews the user for the gaps, tags every statement with its source, and checks the file with a script. Use when someone says "set up marketing context", "product context", "positioning document", "write down our messaging", "we repositioned, update the context", or before the first copywriting, CRO, SEO or email task in a project.

100/100 quality
2.00× impact
SAFE
View skill
$

The Problem

You have built a working SaaS product and need to launch it. But "launching" is not a single event -- it is a sequence of positioning, pricing, channel selection, and timing decisions that compound on each other. Get the pricing wrong and your best launch day traffic converts at $0. Position the product poorly and journalists ignore your pitch. Launch without a plan and you get a brief spike followed by silence.

Most founders either over-engineer the launch (spending months on a perfect plan that never ships) or under-plan it (tweeting "we're live!" to 200 followers and calling it a day). Neither approach works. A successful launch requires clear positioning, validated pricing, and coordinated execution across multiple channels within a tight window.

The Solution

Combine launch-strategy to build a phased launch plan with timeline and channel tactics, pricing-strategy to model tiers and validate willingness-to-pay before launch day, and product-marketing-context to define positioning, ICP, and competitive differentiation that anchors all launch messaging.

Step-by-Step Walkthrough

1. Define positioning and ideal customer profile

Start by establishing who the product is for and why they should care. This grounds every downstream decision.

Analyze our product (an AI meeting note-taker for sales teams) and define our positioning, ICP, and key differentiators versus Otter.ai, Fireflies, and Grain.

The agent produces a positioning document with a one-line value prop, three ICP segments ranked by fit, a competitive matrix showing feature gaps you win on, and messaging pillars for each segment.

2. Model and validate pricing tiers

Before launch, pricing needs to be locked. Guessing leads to leaving money on the table or scaring off early adopters.

Design pricing tiers for our meeting note-taker. Our competitors charge $16-30/user/month. We want a free tier for virality and a team tier for revenue. Model expected revenue at 1,000, 5,000, and 10,000 users.

The agent produces a three-tier pricing model (Free, Pro at $19/user/month, Team at $29/user/month) with feature gates, projected conversion rates between tiers, and revenue curves at each user milestone.

3. Build the phased launch plan

A launch is not one day -- it is a pre-launch, launch day, and post-launch sequence spanning 4-6 weeks.

Create a 6-week launch plan. We have a 400-person waitlist, $2,000 budget, and access to 3 podcast hosts in the sales tech space. Target: 500 signups in week one.

The agent delivers a week-by-week calendar with projected reach at each phase:

6-WEEK LAUNCH PLAN
====================

PHASE 1: PRE-LAUNCH (Weeks 1-3)
  Week 1  Send waitlist teaser email #1 ("something is coming")
          Expected: 62% open rate, build anticipation
  Week 2  Send waitlist email #2 (early access offer for referrals)
          Expected: 40-80 referral signups from 400-person list
  Week 3  Record 3 podcast episodes (air dates: weeks 4-6)
          Draft Product Hunt listing, recruit 20 upvoters

PHASE 2: LAUNCH (Week 4)
  Tuesday  Product Hunt submission at 12:01 AM PT
           Waitlist email #3 ("we are live — get your early access")
           Twitter thread + LinkedIn post
           Budget: $800 on targeted Twitter ads to PH listing
           Target: 300-500 signups on day one

PHASE 3: POST-LAUNCH (Weeks 5-6)
  Week 5  Podcast episode #1 airs, Hacker News Show HN post
          Budget: $1,200 on retargeting ads to PH and HN visitors
  Week 6  Podcast episodes #2-3 air, case study from early users
          Email sequence to convert free signups to paid

Each tactic includes expected reach, conversion estimates, and dependencies. The plan front-loads waitlist activation so launch day has built-in momentum rather than starting from zero.

4. Prepare launch day assets and messaging

With positioning locked and the plan built, generate all the assets needed for execution.

Generate our Product Hunt listing copy, launch day email to the waitlist, Twitter thread announcing the launch, and a press pitch for TechCrunch and The Information.

The agent produces each asset using the positioning and ICP from step one, ensuring consistent messaging across every channel. The Product Hunt tagline emphasizes the core differentiator. The press pitch leads with a market trend, not a feature list.

Real-World Example

Anya built an AI meeting note-taker for sales teams and had been "about to launch" for two months. She had a 400-person waitlist but no launch plan, no pricing page, and no press strategy. She ran the three-skill workflow on a Monday. The positioning exercise revealed her strongest differentiator was not transcription accuracy (where Otter.ai dominates) but automatic CRM field population -- something no competitor offered. That insight reshaped her entire launch angle.

The pricing model settled on Free (5 meetings/month), Pro ($19/user), and Team ($29/user with Salesforce integration). The launch plan targeted Product Hunt on a Tuesday (historically the best day for B2B tools) with a coordinated email blast and three podcast appearances scheduled the same week. Launch day brought 847 signups -- 347 above target. The Product Hunt listing finished #4 of the day. Within 30 days, 62 users had converted to Pro, generating $1,178 in MRR from a product that had zero revenue six weeks earlier.

Related use cases