My first product launch went like this: I spent 4 weeks building, 2 days panicking, and 1 afternoon throwing together a landing page, an email, and a prayer.
No financial model. No launch checklist. No competitor research. No outreach plan. I just shipped and hoped.
The second time, I used a system. 10 Claude Code skills that covered every step from idea validation to post-launch metrics. I launched 3 products in 30 days, and each one was more structured than anything I had shipped before.
Here is what each skill does, why the order matters, and the exact launch sequence I follow.
The Real Problem With Solo Launches
You know how to build. That is not the bottleneck. The bottleneck is everything around the building:
- Validating the idea before you invest 200 hours
- Knowing what your competitors charge and where they are weak
- Writing a landing page that converts, not just describes
- Modeling the finances so you know if the unit economics work
- Planning the launch so day one is not chaos
- Following up with the right people at the right time
- Measuring what happened after the dust settles
Each of these tasks takes a full day when you do it manually. And most solo founders skip half of them because there is no time.
These 10 skills automate the parts that do not require creative judgment but absolutely require execution.
What Are Claude Code Skills?
If you are new here: Claude Code is Anthropic's CLI tool that puts Claude in your terminal. Skills are markdown files you drop into ~/.claude/commands/ and run with /skill-name.
No API keys. No dependencies. No configuration. Copy the file, restart, run the command. Each skill has specialized logic for a specific job.
The Launch Sequence
The order matters. Each skill produces output that feeds into the next. Here is the sequence I follow:
Day 1-3: /mvp-builder → scope and spec
Day 4: /competitor-mapper → landscape and gaps
Day 5-6: /landing-page-gen → conversion-focused page
Day 7: /financial-model → unit economics and runway
Day 8-14: /launch-checklist → day-by-day plan
Day 14: /outreach-sequence → cold emails and partnerships
Day 15+: /metrics-tracker → KPI dashboard
The other 3 skills - User Research Synthesizer, Pitch Deck Creator, and Product Roadmap - slot in based on your situation. Raising money? Pitch Deck moves to day 5. Have survey data? User Research goes to day 1.
Let me walk through each one.
Skill 1: MVP Builder (Days 1-3)
The problem: "What is the minimum I can build that validates this idea?" sounds simple until you are 6 weeks into building features nobody asked for.
What it does:
- Takes your idea description and target user
- Identifies core features vs nice-to-haves using a strict MoSCoW framework
- Recommends a tech stack based on your constraints (solo dev, budget, timeline)
- Generates a buildable spec with acceptance criteria for each feature
- Estimates development time per feature
- Outputs a prioritized backlog
Example output:
Product: URL shortener with analytics
Timeline: 2 weeks solo
MUST HAVE (Week 1):
├── URL shortening (create, redirect) - 4 hours
├── Click tracking (count, timestamp, referrer) - 6 hours
├── Basic dashboard (list links, show clicks) - 8 hours
└── User auth (signup, login) - 4 hours
SHOULD HAVE (Week 2):
├── Custom aliases - 2 hours
├── UTM parameter passthrough - 3 hours
└── CSV export - 2 hours
WON'T HAVE (v1):
├── Team features
├── API access
└── Custom domains
Tech stack: Next.js + Supabase + Vercel
Reason: Fastest path to production for solo dev. Free tier covers MVP traffic.
The spec is specific enough to build from. Not a vague idea doc - an actual buildable plan with time estimates.
Skill 2: Competitor Mapper (Day 4)
The problem: You know competitors exist. You do not know their exact pricing tiers, positioning language, feature gaps, or where they are losing customers.
What it does:
- Maps the competitive landscape across 5-15 competitors
- Extracts pricing tiers with feature comparisons
- Identifies positioning gaps (what nobody is saying)
- Analyzes their landing pages for messaging patterns
- Finds product gaps (features users request that nobody builds)
- Outputs a positioning recommendation for your product
Example output:
Competitor Grid:
┌──────────────┬────────┬──────────┬───────────────┐
│ Competitor │ Price │ Focus │ Gap │
├──────────────┼────────┼──────────┼───────────────┤
│ Bitly │ $35/mo │ Enterprise│ Overkill for │
│ │ │ │ solo projects │
│ Short.io │ $25/mo │ Teams │ No free tier │
│ TinyURL │ Free │ Casual │ Zero analytics│
│ Dub.co │ $24/mo │ Devs │ Complex setup │
└──────────────┴────────┴──────────┴───────────────┘
Positioning gap: No one targets solo developers who want
simple analytics without enterprise pricing.
Recommended position: "Link analytics for developers.
Free tier. No team features you won't use."
This output feeds directly into the Landing Page Generator and the Financial Model. You know what to charge, who to target, and what to say.
If you are building products and doing this kind of research manually, the Solo Founder Launch Kit automates the entire research and launch process.
Skill 3: Landing Page Generator (Days 5-6)
The problem: You can build the product but the landing page takes longer than the product itself. And half the time, it describes features instead of selling outcomes.
What it does:
- Generates full HTML/CSS landing pages (not wireframes, actual deployable pages)
- Conversion-focused copy structure: hero, social proof, features-as-benefits, objection handling, pricing, CTA
- Responsive design out of the box
- Dark mode and light mode variants
- Multiple CTA placements optimized for scroll depth
- Outputs clean code you can host anywhere
The copy structure follows a proven pattern:
<section class="hero">
<!-- Outcome-focused headline, not feature-focused -->
<h1>Track every click. Zero setup. Free forever.</h1>
<p>Link analytics for developers who ship fast
and don't need enterprise dashboards.</p>
<a href="#pricing" class="cta">Start Free</a>
</section>
<section class="social-proof">
<!-- Numbers or logos -->
<p>2,400+ links tracked this week</p>
</section>
<section class="features">
<!-- Each feature is a user outcome -->
<div class="feature">
<h3>Know where your clicks come from</h3>
<p>Referrer, country, device - no JavaScript
snippet needed.</p>
</div>
</section>
<section class="objections">
<!-- Handle the "why not just use X" -->
<h2>You don't need Bitly</h2>
<p>If you're a solo dev tracking project links,
you need 10% of what enterprise tools offer.
We built that 10%.</p>
</section>
The page is ready to deploy to Vercel, Netlify, or any static host. No framework dependencies.
Skill 4: Financial Model (Day 7)
The problem: "Will this make money?" is a question most founders answer with feelings instead of math.
What it does:
- Revenue projections across 3 scenarios (conservative, baseline, optimistic)
- Unit economics: CAC, LTV, payback period, gross margin
- Runway calculations based on your current burn rate
- Breakeven analysis: how many customers at what price
- Sensitivity tables: what happens if conversion drops 20%?
Example output:
BASELINE SCENARIO (Month 6):
Revenue: $2,400/mo (120 paid users x $20/mo)
COGS: $180/mo (hosting + API costs)
Gross margin: 92.5%
CAC: $8.50 (content marketing + ProductHunt)
LTV: $140 (7-month avg retention x $20)
LTV:CAC ratio: 16.5x
Breakeven: Month 3 (at 45 paid users)
SENSITIVITY:
If conversion rate drops 30%: breakeven at month 5
If churn doubles: LTV drops to $80, still 9.4x CAC
If price drops to $15: breakeven at month 4
This is not a spreadsheet you fill in manually. The skill builds the model from your inputs and runs the scenarios automatically.
Skill 5: Launch Checklist (Days 8-14)
The problem: Launch day arrives and you realize you forgot to set up analytics, prepare your email list, write the ProductHunt tagline, or tell anyone the product exists.
What it does:
- Generates a day-by-day launch plan customized to your product type (SaaS, info product, marketplace, physical product)
- Pre-launch tasks: beta testers, email list warm-up, social teasers
- Launch day: platform-specific submissions, email blast, social posts
- Post-launch: follow-up sequences, feedback collection, iteration plan
- Each task has a time estimate and dependency map
Example (SaaS launch):
DAY -7: PREPARATION
□ Set up analytics (Plausible/PostHog) - 30 min
□ Create ProductHunt draft - 45 min
□ Write launch email (for existing list) - 30 min
□ Prepare 3 social posts (teaser, launch, recap) - 20 min
□ Line up 5 beta testers for testimonials - 60 min
DAY -3: WARM-UP
□ Send "something's coming" email - 15 min
□ Post teaser on Twitter/LinkedIn - 10 min
□ DM 10 people who might share - 30 min
DAY 0: LAUNCH
□ 06:00 - Go live on ProductHunt (PST)
□ 06:30 - Send launch email
□ 07:00 - Post on Twitter, LinkedIn, HN
□ 12:00 - Respond to all comments
□ 18:00 - Thank-you post with early stats
DAY +1 to +7: FOLLOW-UP
□ Email non-openers with different subject line
□ Collect feedback from first 20 users
□ Fix top 3 reported issues
□ Write "launch retrospective" post
No more forgetting steps. No more scrambling on launch morning.
The Solo Founder Launch Kit includes this checklist generator plus 9 other skills that cover the full journey from idea to post-launch.
Skill 6: User Research Synthesizer
The problem: You have survey responses, interview notes, and support tickets. The insights are in there somewhere, buried under 50 pages of raw text.
What it does:
- Ingests any research data (interview transcripts, survey CSV, support tickets, forum posts)
- Identifies patterns: top pain points, feature requests, language patterns
- Groups findings by user segment
- Extracts exact quotes usable in marketing copy
- Outputs a prioritized insight report with confidence levels
This skill is most valuable before you build. Feed it Reddit threads, competitor reviews, or survey responses from your target audience. It tells you what people actually want, in their own words.
Skill 7: Pitch Deck Creator
The problem: Investor decks follow a specific structure that is well-documented but time-consuming to execute. You know you need a problem slide, solution slide, market size, traction, and ask. Writing all of it takes days.
What it does:
- Generates content for each standard slide (10-12 slides)
- Problem/Solution with narrative structure
- Market sizing (TAM/SAM/SOM with logic)
- Business model slide with revenue mechanics
- Traction slide formatted for your stage
- Team slide even for solo founders (skills + advisors)
- The Ask: specific amount, use of funds, milestones
This outputs slide content, not a PowerPoint file. You paste it into your template of choice. The structure and narrative are the hard part - that is what this skill handles.
Skill 8: Outreach Sequence
The problem: Cold email is a numbers game with a skill component. You need volume and you need quality. Writing 50 personalized cold emails manually is not realistic.
What it does:
- Generates cold email templates for 3 audiences: press, partners, and early users
- 3-email sequence per audience with follow-up timing
- Personalization variables for each template
- Subject lines A/B tested with the same scoring as the Headline Tester
- Response handling: what to say when they reply (positive, neutral, objection)
Example sequence:
EMAIL 1 (Day 0) - The opener:
Subject: "Quick question about [their product/content]"
Body: 2 sentences of genuine context + 1 sentence about
what you built + 1 clear ask (demo, feedback, share)
EMAIL 2 (Day 3) - The value add:
Subject: "Re: [original subject]"
Body: Share a specific insight or resource relevant to
them + soft reminder of your ask
EMAIL 3 (Day 7) - The breakup:
Subject: "Last one from me"
Body: Acknowledge they're busy + final CTA + leave the
door open
The templates are customized to your product and audience. Not generic "Hi {first_name}" garbage.
Skill 9: Product Roadmap
The problem: After launch, feature requests start pouring in. Without a framework for prioritization, you build whatever the loudest customer asks for.
What it does:
- Organizes features into phases (Now, Next, Later)
- Scores by impact and effort (2x2 matrix)
- Groups by user segment (which features matter to which users)
- Estimates development effort per feature
- Identifies dependencies (what must ship before what)
- Outputs a structured roadmap document
Example:
NOW (Sprint 1-2):
├── Custom aliases [High impact, Low effort] - 3 hrs
├── Click geography [High impact, Med effort] - 8 hrs
└── Email notifications [Med impact, Low effort] - 4 hrs
NEXT (Sprint 3-4):
├── API access [High impact, High effort] - 20 hrs
├── Team sharing [Med impact, Med effort] - 12 hrs
└── UTM builder [Med impact, Low effort] - 5 hrs
LATER (Backlog):
├── Custom domains
├── A/B testing for links
└── Slack integration
This keeps you focused. When a customer asks for custom domains on week 2, you have a documented reason for why it is in the "Later" bucket.
Skill 10: Metrics Tracker
The problem: You launched. Now what? You check Stripe revenue, maybe Google Analytics, and your email open rates. But there is no unified view. No week-over-week trends. No early warning signals.
What it does:
- Defines your KPI framework based on your product type and stage
- Sets up tracking for: activation, retention, revenue, referral
- Creates a weekly review template
- Identifies leading indicators (metrics that predict outcomes before they happen)
- Outputs a dashboard structure you can implement in any tool
Example framework:
NORTH STAR: Weekly Active Links Created
HEALTH METRICS:
├── Activation: % of signups who create first link (target: 60%)
├── Retention: % who create a link in week 2 (target: 40%)
├── Revenue: MRR and MRR growth rate
└── Referral: % of users from word-of-mouth
LEADING INDICATORS:
├── Links created per user per week (predicts retention)
├── Dashboard views per user (predicts activation)
└── Feature request volume (predicts churn when it spikes)
WEEKLY REVIEW:
□ Compare metrics to last week
□ Identify biggest mover (up or down)
□ One action item from the data
This is the skill you run every week after launch. It turns raw numbers into decisions.
How They Work as a System
The output chain looks like this:
MVP Builder ──→ defines what to build
│
Competitor Mapper ──→ defines positioning
│
Landing Page Gen ──→ uses positioning for copy
│
Financial Model ──→ validates unit economics
│
Launch Checklist ──→ plans execution
│
Outreach Sequence ──→ drives launch traffic
│
Metrics Tracker ──→ measures results
│
Product Roadmap ──→ plans next iteration
│
User Research ──→ validates direction
│
Pitch Deck ──→ if raising money
Each skill produces structured output that the next one can use. The Competitor Mapper finds your positioning gap, the Landing Page Generator uses it for copy, and the Financial Model validates that the price point works.
This is not 10 random tools. It is a launch system.
Installation
Same as every Claude Code skill:
# Copy to your commands folder
cp *.md ~/.claude/commands/
# Restart Claude Code
# Run any skill
/mvp-builder
No npm install. No environment variables. No framework. The files are the skills.
Frequently Asked Questions
Is this only for SaaS products?
No. The skills adapt to your product type. I have used them for info products, physical goods, and marketplace launches. The Launch Checklist, for example, asks what you are launching and adjusts the plan accordingly. SaaS gets ProductHunt and Hacker News. Physical products get Amazon and influencer outreach. Info products get Gumroad and community seeding.
Can I use just one or two skills instead of all 10?
Absolutely. Each skill works standalone. The MVP Builder is useful even if you never run the Financial Model. The Outreach Sequence works for any cold email campaign, not just launches. Start with the skill that solves your current bottleneck.
How long does a full launch sequence take?
Following the day-by-day sequence, about 2 weeks from idea to launched product. The skills handle the research, planning, and writing. You handle the building and decision-making. Most of the time savings come from Competitor Mapper (replaces 1-2 days of manual research), Landing Page Generator (replaces 2-3 days of design and copywriting), and Launch Checklist (replaces the planning you would otherwise skip).
I am pre-revenue. Is the Financial Model useful for me?
Especially for you. The model shows you exactly how many customers you need at a given price to cover your costs. It runs scenarios so you know that if your conversion rate is 2% instead of 5%, you need 3x the traffic. Better to know that on day 7 than on day 60.
Get the Kit
The Solo Founder Launch Kit includes all 10 skills for $39. Run the launch sequence once and you will never go back to winging it.
If you also create content or run a store, the Complete Bundle includes all 22 skills across ecommerce, content creation, and product launch for $69 (saves $18 vs buying separately).
Related: Building a content engine to drive traffic to your launch? Read How I Built a Content Machine That Publishes to 4 Platforms Simultaneously for the content side of the system. Already selling products? Check out 5 Claude Code Skills That Run My Entire Ecommerce Operation.
Built by Nex Tools - we build automation tools for online businesses.
