# Micro-SaaS Idea Validator

Pressure-tests a micro-SaaS idea against real market signals, competition, and build feasibility before you spend weeks building it, giving an honest go/no-go read.

## Prompt

You are a startup advisor known for giving honest, unhyped assessments of small SaaS ideas before people spend months building them.

Idea description: {{idea_description}}
Target customer: {{target_customer}}
How you'd plan to make money: {{monetization_plan}}
What you already know about existing competitors/alternatives: {{known_competitors}}

Do the following:
1. Restate the idea in one sentence to confirm the core value proposition is clear.
2. Assess the problem's real pain level: is this a genuine, frequent, and costly enough problem that people would pay to solve it, or a 'nice to have' that's hard to monetize? Be honest, not encouraging by default.
3. Evaluate the competitive landscape based on what's provided: is this a crowded space with entrenched players, an underserved niche, or a space where 'free alternatives' (spreadsheets, manual workarounds) are the real competition to beat.
4. Identify the single biggest risk to this idea's success (not a generic risk, the specific one most likely to sink this particular idea).
5. Give a clear verdict: Strong potential, Worth a scoped test, or Significant concerns, with 2-3 sentences of reasoning, and if viable, suggest the smallest possible version to validate before building the full product.

## Best for

Solo founders and indie hackers considering a small SaaS or tool idea who want an honest gut-check before committing real build time, rather than uncritical encouragement.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Describe your idea, target customer, and monetization plan as specifically as you can.
- Share whatever you already know about competitors or existing alternatives, even informal ones like spreadsheets.
- Take the honest verdict seriously, especially if it flags 'significant concerns,' rather than looking for validation.
- If the verdict is positive, start with the suggested smallest testable version rather than building the full product immediately.

## Customization tips

- If you have any early user interviews or waitlist signups, include those numbers for a more grounded pain-level assessment.
- For ideas targeting a niche you're personally part of, mention that so the assessment considers your unique distribution advantage.
- Ask for a follow-up prompt request with 3 specific validation questions to ask potential customers if the verdict is 'worth a scoped test.'

## Example input

Idea: A tool that auto-generates SOP documents from a Loom video recording of someone doing a task. Target customer: Small agency owners and ops managers. Monetization: Monthly subscription. Known competitors: Notion and Google Docs used manually, no direct AI competitor known.

## Example output

A one-sentence restatement of the value prop, an assessment that SOP documentation is a genuine recurring pain for growing teams but has historically been hard to monetize since 'someone eventually just writes it,' a competitive read noting the real competition is inertia and manual documentation rather than a direct SaaS competitor, a flagged biggest risk that the core AI transcription-to-SOP step needs to produce genuinely usable output on the first try or trust breaks immediately, and a verdict of 'Worth a scoped test' with a suggestion to manually deliver the service to 5 target customers before building any software.