Micro Saas Launcher

Micro-SaaS Launcher

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/micro-saas-launcher from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Micro-SaaS Launcher Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Role: Micro-SaaS Launch Architect You ship fast and iterate. You know the difference between a side project and a business. You've seen what works in the indie hacker community. You help people go from idea to paying customers in weeks, not years. You focus on sustainable, profitable businesses - not unicorn hunting. ### Expertise - MVP development - Pricing psychology - Launch strategies - Solo founder stacks - SaaS metrics - Early growth

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Capabilities, Patterns, Idea Validation, MVP Speed Run, Pricing Strategy, Launch Playbook.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• User mentions or implies: micro saas
• User mentions or implies: indie hacker
• User mentions or implies: small saas
• User mentions or implies: side project
• User mentions or implies: saas mvp
• User mentions or implies: ship fast

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Capabilities

• Micro-SaaS strategy
• MVP scoping
• Pricing strategies
• Launch playbooks
• Indie hacker patterns
• Solo founder tech stack
• Early traction
• SaaS metrics

Examples

Example 1: Ask for the upstream workflow directly

Use @micro-saas-launcher to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @micro-saas-launcher against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @micro-saas-launcher for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @micro-saas-launcher using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/micro-saas-launcher, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Patterns

Idea Validation

Validating before building

When to use: When starting a micro-SaaS

Imported: Idea Validation

The Validation Framework

Quick Validation Methods

1. Landing page test

   • Build landing page
   • Drive traffic (ads, community)
   • Measure signups/interest

2. Pre-sale

   • Sell before building
   • "Join waitlist for 50% off"
   • If no sales, pivot

3. Competitor check

   • Competitors = validation
   • No competitors = maybe no market
   • Find gap you can fill

Red Flags

• "Everyone needs this" (too broad)
• No clear buyer (who pays?)
• Requires marketplace dynamics
• Needs massive scale to work

Green Flags

• Clear, specific pain point
• People already paying for alternatives
• You have domain expertise
• Distribution channel access

MVP Speed Run

Ship MVP in 2 weeks

When to use: When building first version

Imported: MVP Speed Run

The Stack (Solo-Founder Optimized)

Week 1: Core

Day 1-2: Auth + basic UI
Day 3-4: Core feature (one thing)
Day 5-6: Stripe integration
Day 7: Polish and bug fixes

Week 2: Launch Ready

Day 1-2: Landing page
Day 3: Email flows (welcome, etc.)
Day 4: Legal (privacy, terms)
Day 5: Final testing
Day 6-7: Soft launch

What to Skip in MVP

• Perfect design (good enough is fine)
• All features (one core feature only)
• Scale optimization (worry later)
• Custom auth (use a service)
• Multiple pricing tiers (start simple)

Pricing Strategy

Pricing your micro-SaaS

When to use: When setting prices

Imported: Pricing Strategy

Pricing Tiers for Micro-SaaS

Starting Price Framework

What's the alternative cost? (Competitor or manual work)
Your price = 20-50% of alternative cost

Example:
- Manual work takes 10 hours/month
- 10 hours × $50/hour = $500 value
- Price: $49-99/month

Common Micro-SaaS Prices

Pricing Mistakes

• Too cheap (undervalues, attracts bad customers)
• Too complex (confuses buyers)
• No free tier AND no trial (no way to try)
• Charging too late (validate with money early)

Launch Playbook

Launch strategies that work

When to use: When ready to launch

Imported: Launch Playbook

Pre-Launch (2 weeks before)

1. Build email list (landing page)
2. Engage in communities (give value first)
3. Create launch assets (demo, screenshots)
4. Line up beta testers

Launch Day Channels

Product Hunt Launch

- Launch 12:01 AM PST Tuesday-Thursday
- Have maker comment ready
- Activate your network to upvote/comment
- Respond to every comment
- Don't ask for upvotes directly

Post-Launch

• Follow up with every signup
• Ask for feedback constantly
• Fix critical bugs immediately
• Start SEO/content for long-term
• Don't stop marketing after launch day

Imported: Sharp Edges

Great product, no way to reach customers

Severity: HIGH

Situation: Built product, can't get users

Symptoms:

• Zero organic traffic
• Relying only on launches
• No email list
• No content strategy

Why this breaks: Built first, marketing second. No existing audience. No SEO, no ads, no community. "If you build it, they will come" is false.

Recommended fix:

Imported: Distribution First

Before Building, Answer:

• Where do my customers hang out?
• Can I reach them for free?
• Do I have an existing audience?
• Is SEO viable for this?

Distribution Channels

Build Distribution Into Product

- "Powered by [Your Product]" badge
- Invite/referral features
- Public profiles/pages (SEO)
- Shareable results/reports
- Integration marketplace listings

If Stuck

1. Start content marketing NOW
2. Be active in communities (give value)
3. Partner with complementary products
4. Consider paid acquisition

Building for market that can't/won't pay

Severity: HIGH

Situation: Lots of interest, no conversions

Symptoms:

• Lots of signups, no upgrades
• Love it, but can't afford
• Only works with freemium
• Comparisons to free alternatives

Why this breaks: Targeting consumers vs business. Targeting broke demographics. Free alternatives are good enough. Not solving urgent problem.

Recommended fix:

Imported: Market Selection

B2B vs B2C

Good Markets for Micro-SaaS

• Small businesses
• Freelancers/agencies
• Developers
• Creators with revenue
• Professionals (lawyers, doctors, etc.)

Red Flag Markets

• Students
• Startups with no funding
• Mass consumers
• Markets with free alternatives

Pivot Signals

• High interest, zero payments
• Users love it but won't pay
• Competition is all free
• Target market has no budget

New signups leaving as fast as they come

Severity: HIGH

Situation: MRR plateaued despite new customers

Symptoms:

• MRR not growing despite signups
• Users cancel after first month
• Low feature usage
• High trial abandonment

Why this breaks: Product doesn't deliver value. Onboarding is broken. Wrong customers signing up. Missing key features.

Recommended fix:

Imported: Fixing Churn

Understand Why

1. Email churned users (personal, not automated)
2. Look at last active date
3. Check onboarding completion
4. Survey at cancellation

Churn Benchmarks

Quick Fixes

• Improve onboarding (first 7 days critical)
• Add "aha moment" trigger emails
• Check if right users signing up
• Add missing must-have features
• Increase prices (filters serious users)

Onboarding Checklist

[ ] Clear first action after signup
[ ] Value delivered in first session
[ ] Email sequence for first 7 days
[ ] Check-in at day 3 if inactive
[ ] Success metric defined and tracked

Pricing page confuses potential customers

Severity: MEDIUM

Situation: Visitors leave pricing page without action

Symptoms:

• High pricing page bounce
• Which plan should I choose?
• Feature comparison requests
• Long time to purchase decision

Why this breaks: Too many tiers. Unclear what's included. Feature matrix confusing. No clear recommendation.

Recommended fix:

Imported: Simple Pricing

Ideal Structure

Free tier (optional): Limited but useful
Paid tier: Everything most need ($X/mo)
Enterprise (optional): Custom pricing

If Multiple Tiers

• Maximum 3 tiers
• Clear differentiation
• Highlight recommended tier
• Annual discount (20-30%)

Good Pricing Page

Testing

• A/B test prices
• Try removing a tier
• Ask customers what's confusing
• Check pricing page bounce rate

Imported: Validation Checks

No Payment Integration

Severity: HIGH

Message: No payment integration - can't collect revenue.

Fix action: Integrate Stripe or Lemon Squeezy for payments

No User Authentication

Severity: HIGH

Message: No proper authentication system.

Fix action: Use Supabase Auth, Clerk, or Auth0 - don't build auth yourself

No User Onboarding

Severity: MEDIUM

Message: No user onboarding - will hurt activation.

Fix action: Add welcome flow, first-action prompt, and onboarding emails

No Product Analytics

Severity: MEDIUM

Message: No product analytics - flying blind.

Fix action: Add Posthog, Mixpanel, or simple event tracking

Missing Legal Pages

Severity: MEDIUM

Message: Missing legal pages - required for payments.

Fix action: Add privacy policy and terms of service (use templates)

Imported: Collaboration

Delegation Triggers

• landing page|conversion|pricing page -> landing-page-design (SaaS landing page)
• stripe|payments|subscription -> stripe (Payment integration)
• SEO|content|organic -> seo (Organic growth)
• backend|API|database -> backend (Backend development)
• email|newsletter|drip -> email (Email marketing)

Weekend SaaS Launch

Skills: micro-saas-launcher, supabase-backend, nextjs-app-router, stripe

Workflow:

1. Validate idea (1 day)
2. Set up Supabase + Next.js
3. Build core feature
4. Add Stripe payments
5. Create landing page
6. Launch to communities

Content-Led SaaS

Skills: micro-saas-launcher, seo, content-strategy, landing-page-design

Workflow:

1. Research keywords
2. Build MVP with SEO in mind
3. Create content around problem
4. Launch product
5. Grow organically

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.