Generate a comprehensive business opportunity report for micro-SaaS solutions targeting a specific market segment. Triggers on phrases like "micro-SaaS opportunity", "SaaS market analysis", or "analyze [market] for SaaS".
Generate a comprehensive business opportunity report analyzing a target market segment for micro-SaaS potential.
The user provides a target market segment - this can be:
Before writing the report, conduct thorough web research to gather real data:
Important: Save URLs for all sources. The final report must include reference links.
Generate a single markdown document with this structure:
Generated: [Date]
Market Segment: [Full description of target market]
[2-3 paragraph overview of the opportunity, key findings, and top recommendation]
[Precise definition of who is in this market segment]
Total market size: [Number of businesses/professionals]
Geographic breakdown: [If relevant]
Growth trends: [Growing, stable, declining - with data]
Sources: [List URLs]
Average business size/revenue
Technology adoption level
Typical budget for software tools
Key decision-making factors
Sources: [List URLs]
[Table or list of primary workflows performed by this segment. Data in the table should be backed by real data from identifiable sources and URLs]
| Workflow | Frequency | Time Spent | Pain Level |
|----------|-----------|------------|------------|
| [Name] | Daily/Weekly/etc | X hrs/week | High/Med/Low |
Sources: [List URLs]
Rank workflows by automation potential:
| Rank | Workflow | Why It's a Good Candidate |
|------|----------|---------------------------|
| 1 | [Name] | [Reasoning: repetitive, rule-based, high time cost, etc.] |
| 2 | [Name] | [Reasoning] |
| 3 | [Name] | [Reasoning] |
| Solution | Target Market | Key Features | Pricing | Limitations |
|----------|---------------|--------------|---------|-------------|
| [Name] | [Who they serve] | [Top 3 features] | [$/mo] | [Gaps/complaints] |
[Analysis of what existing solutions are missing or doing poorly]
Sources: [List URLs for competitor info, reviews, complaints]
Target Workflow: [Which workflow this automates]
Value Proposition: [One sentence on why this is better than alternatives]
Core Features:
[Feature 1]
[Feature 2]
[Feature 3]
Differentiation: [Why this beats existing solutions for this specific market]
Technical Complexity: [Low/Medium/High - brief justification]
[Same structure as Solution 1]
[Same structure as Solution 1]
| Criteria | Solution 1 | Solution 2 | Solution 3 | [Top Competitor] | [Competitor 2] |
|----------|------------|------------|------------|------------------|----------------|
| Target workflow fit | | | | | |
| Ease of use | | | | | |
| Pricing accessibility | | | | | |
| Feature completeness | | | | | |
| Integration options | | | | | |
| Mobile support | | | | | |
| Overall Score | X/10 | X/10 | X/10 | X/10 | X/10 |
[Freemium, flat-rate, tiered, usage-based - with justification]
| Tier | Price | Features | Target Customer |
|------|-------|----------|-----------------|
| Free | $0 | [Limited features] | [Who this attracts] |
| Pro | $X/mo | [Full features] | [Primary paying customer] |
| Team | $Y/mo | [Multi-user features] | [Larger customers] |
[Why this pricing works for this market - reference competitor pricing and market willingness to pay]
Total market segment size: [X businesses/professionals]
Estimated software budget per entity: $[Y]/year
TAM: $[Z]
Entities not using an existing or competitive solution: [X%] = [Y entities]
SAM: $[Z]
Achievable market capture in Year 1-3: [X%]
SOM: $[Z]
Methodology notes: [How these numbers were derived]
Sources: [List URLs]
Conversion rate (free to paid): [X%]
Monthly churn rate: [X%]
Average revenue per user (ARPU): $[X]
Customer acquisition cost (CAC): $[X]
| Metric | Year 1 | Year 2 | Year 3 |
|--------|--------|--------|--------|
| Total users | | | |
| Paying customers | | | |
| Monthly recurring revenue (MRR) | | | |
| Annual recurring revenue (ARR) | | | |
[Brief analysis of when the product could become profitable]
| Rank | Solution | Score | Rationale |
|------|----------|-------|-----------|
| 1 | [Name] | X/10 | [Why this is the top pick] |
| 2 | [Name] | X/10 | [Strengths and considerations] |
| 3 | [Name] | X/10 | [Strengths and considerations] |
[Validation step]
[Research step]
[Development step]
[Numbered list of all URLs cited in the report]
[Title/Description] - [URL]
[Title/Description] - [URL]
...
The report must:
Use real data: All market sizes, competitor info, and pricing must come from web research, not estimates. If data isn't available, state "Data not publicly available" rather than guessing.
Cite sources: Every factual claim needs a reference link. Group references by section.
Be actionable: Recommendations should be specific enough that someone could act on them immediately.
Show reasoning: Don't just state conclusions - explain why each workflow is a good automation candidate, why each solution beats competitors, etc.
Be realistic: Revenue projections should use conservative, defensible assumptions. Avoid hockey-stick optimism.
Consider the niche: Micro-SaaS succeeds by serving underserved niches extremely well. Proposed solutions should be laser-focused on the specific market segment, not generic tools.
When searching, try queries like:
Deliver the complete report as a single markdown document. The markdown document should be saved to a markdown text file. If certain data couldn't be found despite research efforts, note this explicitly rather than fabricating numbers.
Base directory for this skill: ~/.config/opencode/skills/lean-canvas-analysis Relative paths in this skill (e.g., scripts/, reference/) are relative to this base directory. Note: file list is sampled.