micro-saas-launcher
Skill43 starsChanged 9 months agoMITView on GitHub
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.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillsword for word, first seen Nov 16, 2026
- Ivan-propio/claude-skillsword for word, first seen Nov 16, 2026
- MaxMiksa/Autonomous-Companyword for word, first seen Oct 15, 2026
- xfstudio/skillsword for word, first seen Oct 13, 2026
- MaxMiksa/Auto-Companyword for word, first seen Oct 2, 2026
- DrifterXXX/auto-companyword for word, first seen Jun 21, 2026
Other versions8 projects use a version of this.
Word for word · 8
- MaxMiksa/Auto-Company★ 3.2k100% same
- MaxMiksa/Autonomous-Company★ 3.2k100% same
- nicepkg/auto-company★ 188100% same
- xfstudio/skills★ 9100% same
- ai4brands-design/claude-skills★ 2100% same
- AtilaMedeiros/skills★ 1100% same
- DrifterXXX/auto-company★ 0100% same
- Ivan-propio/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- code-review-securitySkill
- cold-email-sequence-generatorSkill
- community-led-growthSkill
- competitive-intelligence-analystSkill
- content-strategySkill
- deep-analysisSkill
- deep-reading-analystSkill
- deep-researchSkill
- devopsSkill
- email-sequenceSkill
- financial-unit-economicsSkill
- find-skillsSkill
- github-explorerSkill
- market-sizing-analysisSkill
- ph-community-outreachSkill
- premortemSkill
- pricing-strategySkill
- product-strategistSkill
- scientific-critical-thinkingSkill
- security-auditSkill
- senior-qaSkill
- seo-auditSkill
- seo-content-strategistSkill
- skill-creatorSkill
- startup-business-modelsSkill
- startup-financial-modelingSkill
- tailwind-v4-shadcnSkill
- teamSkill
- user-persona-creationSkill
- user-research-synthesisSkill
- ux-audit-rethinkSkill
- web-scrapingSkill
- webshSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
When to use: When starting a micro-SaaS
- Distinctive: line 79
When to use: When building first version
- Distinctive: line 124
When to use: When setting prices
- Distinctive: line 167
Why bad: No feedback loop. Building wrong thing.
- Distinctive: line 179
Why bad: Never ships. Dilutes focus.
- Distinctive: line 197
Start higher, discount if needed.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
## 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 accessMVP Speed Run
Ship MVP in 2 weeks
When to use: When building first version
## 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: CoreDay 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 ReadyDay 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
## 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 FrameworkWhat'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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

