$ cat prompt.txt — Micro-SaaS
Micro-SaaS Idea Generator — 10 Validated B2B Ideas in 30 Min
10 micro-SaaS ideas with validation signals, target users, MVP scope, and 90-day revenue paths.
Most micro-SaaS founders fail not from bad execution but from bad idea selection — building for niches that don't exist or won't pay. This prompt generates 10 specifically-targeted B2B micro-SaaS ideas calibrated to your skills, industry familiarity, and runway, then picks the top 2 with validation signals you can check in an afternoon.
$ cat prompt.txt | pbcopy
The prompt — copy & paste
You are a serial micro-SaaS founder who has launched 8 products, with 3 hitting $10k+ MRR. Your job is to generate 10 sharply-targeted B2B micro-SaaS ideas matched to my profile + runway, then validate the top 2 against real signal sources.
MY INPUTS:
- Technical skills (stacks I can build with): {{my_technical_skills}}
- Industries / business types I have insider familiarity with: {{industries_i_know}}
- Weeks of runway I have to build + validate: {{weeks_of_runway}}
- Monthly revenue target within 12 months: {{monthly_revenue_target}}
EXECUTE THE FOLLOWING:
STAGE 1 — IDEATION (10 candidate ideas)
Generate 10 micro-SaaS ideas that meet ALL these criteria:
- B2B (B2C is too marketing-intensive for solo founders)
- Vertical-specific (NOT "AI tool for everyone" — pick a vertical from my {{industries_i_know}})
- Solve a workflow pain that's currently being addressed by: a messy spreadsheet, a manual process, an over-priced enterprise tool, or no solution at all
- MVP buildable in 4-8 weeks at my {{my_technical_skills}} level
- Target customer can pay $30-$300/month without finance-team approval
- NOT a "GPT wrapper" (these get crushed by the next OpenAI release) — must have product logic beyond a single LLM call
For each idea, write a one-paragraph pitch:
- Product name (working title)
- Who buys it (specific role + company size)
- What pain it solves (current workflow they'd replace)
- What it does (in one sentence — the "Stripe for X" framing if possible)
- Why a SOLO founder can win it (why incumbents won't crush you)
STAGE 2 — SCORING (rank all 10)
Score each idea 1-5 on:
- PROBLEM URGENCY (5 = costs the user real money today, 1 = nice-to-have)
- WILLINGNESS TO PAY (5 = obvious $50+/month price, 1 = unclear pricing model)
- BUILD FEASIBILITY (5 = I can ship MVP in <6 weeks, 1 = needs unproven tech)
- DISTRIBUTION (5 = clear acquisition channel I can execute, 1 = "I'll do Product Hunt")
- DEFENSIBILITY (5 = becomes harder to replicate over time, 1 = first competitor will crush me)
Present as a sorted markdown table with TOTAL out of 25.
STAGE 3 — DEEP DIVE TOP 2
For the 2 highest-scoring ideas, output:
A. THE VALIDATION CHECKLIST
- 3 specific places to look for proof this pain exists (subreddit names, Twitter accounts, niche communities)
- 3 specific people to message (job title patterns to search on LinkedIn) for 15-min validation calls
- The ONE existing solution I should sign up for and use this week (to understand the incumbent's weaknesses)
- The validation kill-criteria: if I do all the above and find what specifically, kill the idea
B. THE 6-WEEK MVP SCOPE
- The 3-5 features in the MVP (ruthlessly cut — no auth-team admin, no settings page, no billing edge cases)
- The tech stack recommendation matched to my skills
- The single hardest technical decision I'll face and the recommended path
- What to EXPLICITLY NOT BUILD in MVP (the temptation list)
C. THE PRICING + GTM STRATEGY
- Recommended pricing model (subscription / per-seat / usage-based / one-time)
- Suggested launch price (typically 30-50% below where you'll be in 6 months — easier to raise prices than discover you under-charged at $9 when buyers would pay $49)
- The first 3 acquisition channels to focus on (no more than 3 — focus beats variety)
- The "fishing where the fish are" specific community or platform where my target buyer already congregates
D. THE 90-DAY MILESTONE PATH
Week 1-4: Build MVP
Week 5-6: 10 design-partner users
Week 7-10: Iterate based on usage data
Week 11-12: Public launch + 50 paying customers
For each phase, state the ONE metric that determines whether to continue or pivot.
STAGE 4 — KILL LIST
Name 3 popular micro-SaaS niches I should NOT enter right now and why (saturated, commoditized, or about to be eaten by an incumbent).
STAGE 5 — FINAL RECOMMENDATION
Pick the #1 idea. State the 3 things I should do this week to start.
REQUIREMENTS:
- Be ruthless. If none of the 10 ideas look strong enough to hit {{monthly_revenue_target}} in 12 months, tell me my {{industries_i_know}} is too narrow / weak and recommend pivoting to a different vertical.
- "GPT wrapper" ideas score badly on DEFENSIBILITY — the model knows this.$ variables_to_fill_in
$ man playbook
Step-by-step playbook
How to actually use this prompt for the best results.
- 01
List the industries you ACTUALLY know
{{industries_i_know}} should be industries where you've worked, freelanced, or have close-tie relationships in. 'I read about real estate online' doesn't count. Industry insider-ness is what gives you the unfair advantage to win a vertical SaaS.
- 02
Be honest about your build skills
{{my_technical_skills}} drives the 6-week MVP scope. Overestimating leads to a half-built product at week 12. List what you can ship at production quality without research, not aspirational stacks you're 'learning'.
- 03
Run the prompt and validate top 2 in parallel
Use Stage 3's validation checklist for BOTH top ideas — don't commit before validating. Most ideas survive the spec but fail the validation reality-check.
- 04
Schedule 5 validation calls before writing code
5 conversations with prospective users before you write a single line of code is the highest-ROI activity in micro-SaaS. They'll tell you which features matter, what they'd pay, and which existing tools you're really competing against.
- 05
Pick ONE idea and ship the MVP in 6 weeks
Don't pursue both top ideas in parallel — solo founder attention can't sustain it. Pick the one with the strongest validation evidence and execute the 6-week MVP scope without scope creep.
$ man tips
Pro tips for better output
- ›Vertical SaaS (one industry, one workflow) consistently outperforms horizontal SaaS (everyone, vague) for solo founders. The narrower the vertical, the more defensible the moat.
- ›Charge from day one. Free tiers in micro-SaaS make sense once you've validated paid demand — never before. 'No one will pay' beliefs are usually because the founder hasn't ASKED for money yet.
- ›Build in public on Twitter/LinkedIn during the 6-week MVP build. The audience you build there becomes your first 20-50 customers. Pure-launch micro-SaaS without distribution rarely escapes obscurity.
- ›If you can't get 10 design-partner signups in week 5-6, the product likely has fundamental demand problems. Pause building and re-validate before continuing to polish.
$ echo $YIELD
What you'll get
10 micro-SaaS idea candidates with validation rationale, scored ranking, deep-dive on the top 2 (validation checklist + MVP scope + pricing + 90-day roadmap), a kill-list of niches to avoid, and a final #1 recommendation with this-week action items.
$ man faq
FAQ
Do I need to be a developer to launch a micro-SaaS in 2026?
Not necessarily — Claude Code + Cursor + Bolt + Lovable enable non-developers to ship MVPs in many verticals. BUT: solo non-developer micro-SaaS hits a ceiling around $5k-$15k MRR before maintenance + edge cases overwhelm. Long-term, you either learn enough to maintain it or co-found with a technical partner.
What's the realistic timeline to first revenue?
Week 5-8 from MVP launch with design partners (often free or steeply discounted). Week 10-16 for first paying customers at full price. $1k MRR is typically 3-6 months from launch. $10k MRR is 12-24 months, and only 10-20% of micro-SaaS founders ever get there. The first 100 customers are the hardest by an order of magnitude.
Should I quit my job to work on micro-SaaS full time?
Almost never up-front. Build nights + weekends until you hit $3k-$5k MRR and have 12+ months of personal runway saved. Most failed micro-SaaS founders quit too early, ran out of runway, and reluctantly returned to jobs. Patience preserves optionality.
$ cd /prompts — explore all 48 free AI prompts on ClaudeSkill