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. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Best use case
micro-saas-launcher is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Teams using micro-saas-launcher should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/micro-saas-launcher/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How micro-saas-launcher Compares
| Feature / Agent | micro-saas-launcher | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# Micro-SaaS Launcher **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. ## Capabilities - Micro-SaaS strategy - MVP scoping - Pricing strategies - Launch playbooks - Indie hacker patterns - Solo founder tech stack - Early traction - SaaS metrics ## Patterns ### Idea Validation Validating before building **When to use**: When starting a micro-SaaS ```javascript ## Idea Validation ### The Validation Framework | Question | How to Answer | |----------|---------------| | Problem exists? | Talk to 5+ potential users | | People pay? | Pre-sell or find competitors | | You can build? | Can MVP ship in 2 weeks? | | You can reach them? | Distribution channel exists? | ### 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 ```javascript ## MVP Speed Run ### The Stack (Solo-Founder Optimized) | Component | Choice | Why | |-----------|--------|-----| | Frontend | Next.js | Full-stack, Vercel deploy | | Backend | Next.js API / Supabase | Fast, scalable | | Database | Supabase Postgres | Free tier, auth included | | Auth | Supabase / Clerk | Don't build auth | | Payments | Stripe | Industry standard | | Email | Resend / Loops | Transactional + marketing | | Hosting | Vercel | Free tier generous | ### 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 ```javascript ## Pricing Strategy ### Pricing Tiers for Micro-SaaS | Strategy | Best For | |----------|----------| | Single price | Simple tools, clear value | | Two tiers | Free/paid or Basic/Pro | | Three tiers | Most SaaS (Good/Better/Best) | | Usage-based | API products, variable use | ### 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 | Type | Price Range | |------|-------------| | Simple tool | $9-29/month | | Pro tool | $29-99/month | | B2B tool | $49-299/month | | Lifetime deal | 3-5x monthly | ### 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) ``` ## Anti-Patterns ### ❌ Building in Secret **Why bad**: No feedback loop. Building wrong thing. Wasted time. Fear of shipping. **Instead**: Launch ugly MVP. Get feedback early. Build in public. Iterate based on users. ### ❌ Feature Creep **Why bad**: Never ships. Dilutes focus. Confuses users. Delays revenue. **Instead**: One core feature first. Ship, then iterate. Let users tell you what's missing. Say no to most requests. ### ❌ Pricing Too Low **Why bad**: Undervalues your work. Attracts price-sensitive customers. Hard to run a business. Can't afford growth. **Instead**: Price for value, not time. Start higher, discount if needed. B2B can pay more. Your time has value. ## ⚠️ Sharp Edges | Issue | Severity | Solution | |-------|----------|----------| | Great product, no way to reach customers | high | ## Distribution First | | Building for market that can't/won't pay | high | ## Market Selection | | New signups leaving as fast as they come | high | ## Fixing Churn | | Pricing page confuses potential customers | medium | ## Simple Pricing | ## Related Skills Works well with: `landing-page-design`, `backend`, `stripe`, `seo`
Related Skills
saas-multi-tenant
Design and implement multi-tenant SaaS architectures with row-level security, tenant-scoped queries, shared-schema isolation, and safe cross-tenant admin patterns in PostgreSQL and TypeScript.
microservices-patterns
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
async-python-patterns
Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.
slack-automation
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
gitops-workflow
Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.
github-automation
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
github-actions-templates
Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
tanstack-query-expert
Expert in TanStack Query (React Query) — asynchronous state management. Covers data fetching, stale time configuration, mutations, optimistic updates, and Next.js App Router (SSR) integration.