Agent skill
indie-saas-validation-master
Guide the complete 18-month solo SaaS journey from validation to scaling decision point with phase-specific tactics, success metrics, and risk mitigation. Use when starting a new SaaS venture or planning any phase of the indie SaaS journey.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/indie-saas-validation-master
SKILL.md
When to Use This Skill
Use this skill when you need to:
- Plan the complete SaaS journey from idea to sustainable business
- Test a new SaaS idea before investing development time
- Prove market demand exists before building the full product
- Launch an MVP and get to first paying customers
- Grow to $10K MRR with sustainable unit economics
- Decide between lifestyle and hypergrowth at the scaling decision point
- Pre-sell a product concept to gauge willingness to pay
- Validate with no-code tools to test hypotheses quickly
- Avoid building in a vacuum and ensure product-market fit
The 4-Phase Framework Overview
| Phase | Timeline | Goal | Practical Checkpoint |
|---|---|---|---|
| Phase 1: Validation | Months 0-2 | Prove demand exists | Early commitment signals (pre-orders/emails/calls) |
| Phase 2: MVP Launch | Months 2-6 | Launch to early adopters | First paying users and repeat usage |
| Phase 3: Growth | Months 6-18 | Reach sustainable revenue | Improving retention and repeatable acquisition |
| Phase 4: Scaling Decision | 18+ months | Choose your path | Clear choice: lifestyle optimization or scale push |
Core Concepts
The Idea-Seeking Approach
Don't start with an idea—start with a market. The most successful indie SaaS founders follow the "idea-seeking" path: embed in a community, discover critical problems through active listening, validate demand exists, then build a laser-focused solution.
Why this matters: Idea-first execution often burns time on low-signal work. Idea-seeking founders gather evidence earlier, before committing major build cycles.
The Validation Hierarchy
Validation methods ranked by effectiveness:
- Pre-selling (Highest confidence) - Get customers to pay before building
- Fake door testing - Landing pages collect emails to measure interest
- No-code MVP - Test with Bubble/Webflow in days not months
- Community immersion - Direct conversations in niche communities
- Competitor gap analysis - 3-star reviews reveal unmet needs
Step-by-Step Validation Process
Phase 1: Problem Discovery (Week 1)
- Choose your target community - Where do your potential customers congregate? (Indie Hackers, Reddit r/SaaS, niche Slack/Discord communities)
- Listen for friction signals - Look for complaints about "pain points" and problems people want solved
- Identify quantifiable pain - Can customers say "this costs me $X and Y hours/month"?
- Research existing solutions - What alternatives exist? What are people complaining about?
Phase 2: Validation Testing (Weeks 2-4)
- Create fake door landing page - Describe your solution, benefits, and pricing
- Drive traffic to landing page - Share in target communities, run small ads
- Collect email addresses - Measure conversion quality and follow-up response, not just raw volume
- Pre-sell to early adopters - Offer discount for founding members
- Conduct customer interviews - Talk to 10-15 potential customers
Phase 3: Decision (Week 4-6)
Validation success criteria:
- ✅ Meaningful commitment signals (for example: pre-orders, qualified waitlist, and interview demand)
- ✅ Follow-up conversion from email to conversation shows real buyer intent
- ✅ Clear willingness to pay at a price point that supports your economics
- ✅ Specific pain points quantified by customers
- ✅ Competitor gaps clearly identified
If validated → Proceed to MVP development (4-week build)
If not validated → Pivot to new concept or double down on problem discovery
Common Mistakes
Mistake 1: Building without talking to customers
- Symptom: "I'm in stealth mode" or "I don't want to share my idea"
- Solution: Share your idea widely and gather feedback immediately
Mistake 2: Validating with friends and family
- Symptom: Positive feedback from people who won't buy
- Solution: Only validate with potential customers in your target market
Mistake 3: Asking "Would you buy this?"
- Symptom: People say yes but don't actually pay
- Solution: Ask for commitment (email address, pre-order, deposit)
Mistake 4: Ignoring pricing signals
- Symptom: "I'll figure out pricing later"
- Solution: Always include pricing in validation to test willingness to pay
Mistake 5: Falling in love with the solution
- Symptom: Refusing to pivot despite negative validation data
- Solution: Stay objective—let data drive decisions, not ego
Success Metrics
Validation Health Indicators:
| Metric | Weak Signal | Strong Signal |
|---|---|---|
| Email signups | Low conversion and poor follow-up | Good conversion plus interview demand |
| Pre-orders | No commitment behavior | Repeated commitment signals |
| Customer interviews | <5 conversations | 10-15+ relevant conversations |
| Pricing acceptance | "Too expensive" | "Where do I pay?" |
| Competitor gaps | "Everything's fine" | "I wish X did Y" |
Red flags:
- ❌ Can't reach potential customers directly
- ❌ Problem isn't quantifiable in time/money
- ❌ No urgency (customers can wait months)
- ❌ Buyers only engage at very low pricing that cannot support your model
- ❌ Target market is B2C with no viral mechanism
Deep Dives
For comprehensive validation frameworks, templates, and case studies, see the references:
references/validation-checklist.md
- Complete 5-point validation checklist with detailed criteria
- Quantifiable pain assessment framework
- Market reachability evaluation
- MVP scoping guidelines (4-week target)
- Pricing validation benchmarks
references/fake-door-templates.md
- Landing page copy templates (headline, benefits, CTA)
- A/B testing framework for messaging variations
- Traffic source strategies (organic vs paid)
- Conversion rate benchmarks by channel
- Real-world fake door case studies with results
references/community-platforms.md
- Community engagement strategy by platform and audience intent
- Reddit niche community identification and engagement
- 90/10 rule for community value vs promotion
- 4-month community-building timeline
- Multi-platform sequencing strategy
Research Notes
This skill synthesizes findings from comprehensive indie SaaS research:
Primary Research:
Key Case Studies:
- FeedbackPanda: launched via niche communities and documented a rapid bootstrap trajectory
- Formula Bot: community-led distribution drove large initial top-of-funnel
- Geocodio: documented long-term growth from early community exposure
Validation Benchmarks:
- Multiple commitment signals (not one metric) should drive build/no-build calls
- B2B problems preferred (businesses pay to save time)
- Price point must support CAC, support burden, and desired margins
- Keep MVP scope small enough to ship quickly and learn fast
Next Steps After Validation
Once your idea validates successfully, proceed to Phase 2.
After Validation: Phases 2-4
For detailed guidance on MVP launch, growth, scaling decisions, timeline expectations, and risk mitigation by phase, see references/growth-phases.md.
Sources
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?