Niche Research — First Pass (Lifestyle SaaS Lens)
Goal
Evaluate whether a niche can become a $1–3M ARR lifestyle business run solo or with 1 partner.
Ideal characteristics:
- Simple product scope (v1 in 2–6 weeks)
- Short sales cycle (< 30 days)
- Low support burden (< 5 hrs/week at scale)
- Concrete distribution (lists, channels, or high-intent inbound)
- Pricing that requires < 2,000 customers for $1M ARR
Voice
State conclusions first, evidence second. If distribution is unclear after research, output FAIL: Distribution unclear and stop. No hedging with "could potentially" or "might be worth exploring." If data is missing, say "Unknown—requires primary research."
Inputs
Only ask for missing inputs:
- Niche hypothesis (one sentence describing the market + problem)
- Geography (where to focus research—no default assumed)
- Buyer (if known)
Non-Negotiable Gate
A niche only passes if it has at least one concrete distribution surface:
| Distribution Type |
Example |
| Clean buyer list |
Directory, licensing board, registry, permit database |
| Channel partner |
Supplier, distributor, association, insurer, payments provider |
| High-intent inbound |
Compliance forms, deadline-driven searches, "how to file X" |
| System-of-record hook |
Integration with existing workflow software |
If none exist after research: output FAIL (distribution) and stop.
Process
Execute in order. Stop early if distribution fails.
1. Define the Niche Precisely
- Who pays? Who uses daily?
- What mandatory artifact exists? (forms, submissions, certificates, logs, reports)
- What's the "money leak"? (lost renewals, rejected applications, admin hours, penalties, missed revenue)
2. Identify the Paperwork Wedge
- What exact document/packet/submission is unavoidable?
- What deadlines exist? (annual, quarterly, event-triggered)
- Who gets blamed when it's wrong or late?
3. Competitor & Crowding Check
- Direct niche tools (name, pricing, market position)
- Generic substitutes (PDFs, spreadsheets, Jobber, HubSpot, email)
- Government/industry portals acting as system-of-record
- Funded players in adjacent spaces
4. Distribution Map
Must be concrete—no "we could try LinkedIn."
- List sources (actual URLs or database names)
- 1–2 plausible channel partners
- Inbound keywords indicating urgency (with search volume if available)
- Integration hooks (what software do they already use?)
If unclear after research: FAIL: Distribution unclear. Cannot proceed.
5. Founder Fit Check
- Do you have natural access to these buyers? (former industry, network, geography)
- Would you enjoy 50+ sales calls with this persona?
- Is this a market you'd still care about in 3 years?
- Any ethical/personal hesitations?
Note: This section requires founder input. Flag if not provided.
6. Buildability & Support Load
- Can core v1 be built in 2–6 weeks by a solo dev?
- If regulated/integrated workflow: add 4–8 week buffer
- If jurisdiction sprawl (state-by-state rules): add research time per region
- Any liability or compliance certification required?
- Edge case density: low / medium / high
7. Pricing for Lifestyle Outcome
| Tier |
ARPA |
When Acceptable |
| Preferred |
$150–$500/mo |
Default target |
| Acceptable |
$80–$150/mo |
Only if churn < 3%/mo AND distribution is cheap |
| Avoid |
< $50/mo |
Only if distribution is nearly free (viral, marketplace) |
8. Revenue Quality
- Contract structure: monthly / annual / multi-year
- Payment behavior: prepaid / net-30 / invoice-heavy industries
- Expansion path: per-seat / usage-based / upsell tiers
9. Market Size (Conservative)
- Count payers using best available proxy (licenses, permits, businesses)
- Calculate path to $1M ARR: (target ARPA) × (customers needed)
- Calculate path to $3M ARR: (target ARPA) × (customers needed)
- Note key assumptions
10. Defensibility Check
At least one should be present:
- Data/workflow lock-in: Does usage create switching cost?
- Relationship moat: Are buyers sticky once onboarded?
- Distribution exclusivity: Can you lock up a channel?
- Speed moat: Can you ship fast enough to stay ahead?
11. Verdict + Kill Criteria
- Pursue: Clear distribution + viable pricing + buildable scope
- Hold: Promising but missing one key signal
- Kill: No distribution OR requires > 3,000 customers OR unbuildable scope
Include:
- Must-have signals to proceed
- 7-day validation plan
Output
Filename: Niche_FirstPass_<slug>.md
# Niche First Pass: <Title>
## TL;DR Verdict
- **Verdict:** Pursue / Hold / Kill
- **Why:** (3 blunt bullets)
## The Wedge
(One sentence: sellable workflow + mandatory artifact + outcome)
## Customer Profile
| Role | Description |
|------|-------------|
| Paying customer | |
| Daily user | |
| Trigger moment | |
## Workflow Today (As-Is)
1.
2.
3.
## Pain / Money Leak
- **Time waste:**
- **Errors/rejects:**
- **Compliance risk:**
- **Revenue leak:**
## Existing Solutions
### Direct Niche Tools
| Tool | Pricing | Notes |
|------|---------|-------|
| | | |
### Substitutes
-
## Distribution (Must Be Specific)
- **List source:** (actual URL/database)
- **Channel candidate:**
- **Inbound keywords:** (with volume if known)
- **Integration hook:**
- **Distribution risk:**
## Founder Fit
- [ ] Natural access to buyers
- [ ] Would enjoy 50+ sales calls with this persona
- [ ] Would care about this market in 3 years
- [ ] No ethical/personal hesitations
*Fit score: Strong / Moderate / Weak / Unknown*
## Buildability
| Factor | Assessment |
|--------|------------|
| Core v1 timeline | 2–6 weeks / 6–12 weeks / 12+ weeks |
| Regulatory buffer needed | Yes / No |
| Jurisdiction sprawl | None / Moderate / Severe |
| Edge case density | Low / Medium / High |
| Support load estimate | < 5 hrs/wk / 5–15 hrs/wk / 15+ hrs/wk |
### MVP Scope
**Must-have:**
-
**Nice-to-have:**
-
**Explicit non-goals:**
-
## Pricing
- **Recommended tiers:**
- **Expected ARPA:**
- **Why it's fair:**
## Revenue Quality
- **Contract structure:**
- **Payment behavior:**
- **Expansion path:**
## Market Size (Conservative)
- **Payers in target geography:**
- **Total US payers:**
- **Path to $1M ARR:** X customers × $Y ARPA
- **Path to $3M ARR:** X customers × $Y ARPA
- **Key assumption:**
## Defensibility
| Moat Type | Present? | Notes |
|-----------|----------|-------|
| Data/workflow lock-in | | |
| Relationship moat | | |
| Distribution exclusivity | | |
| Speed moat | | |
## Biggest Entry Risks
1.
2.
3.
## Kill Criteria
- If we don't hear X in 10 calls → kill
- If pricing won't clear $Y → kill
- If compliance/portal makes it redundant → kill
## 7-Day Validation Plan
| Day | Activity | Success Signal |
|-----|----------|----------------|
| 1 | | |
| 2–3 | | |
| 4–5 | | |
| 6–7 | | |
1---2name: niche-research-first-pass3description: First-pass evaluation of niche SaaS ideas through a lifestyle business lens ($1-3M ARR, solo/duo team). Use when evaluating a new niche hypothesis, researching a vertical software opportunity, or validating whether a market is worth pursuing. Triggers on requests like "evaluate this niche", "is this a good market", "research this vertical", or "first pass on [industry] software idea". Distribution-first methodology—kills ideas without concrete go-to-market paths.4---56# Niche Research — First Pass (Lifestyle SaaS Lens)78## Goal910Evaluate whether a niche can become a $1–3M ARR lifestyle business run solo or with 1 partner.1112**Ideal characteristics:**13- Simple product scope (v1 in 2–6 weeks)14- Short sales cycle (< 30 days)15- Low support burden (< 5 hrs/week at scale)16- Concrete distribution (lists, channels, or high-intent inbound)17- Pricing that requires < 2,000 customers for $1M ARR1819## Voice2021State conclusions first, evidence second. If distribution is unclear after research, output `FAIL: Distribution unclear` and stop. No hedging with "could potentially" or "might be worth exploring." If data is missing, say "Unknown—requires primary research."2223## Inputs2425Only ask for missing inputs:26- **Niche hypothesis** (one sentence describing the market + problem)27- **Geography** (where to focus research—no default assumed)28- **Buyer** (if known)2930## Non-Negotiable Gate3132A niche only passes if it has **at least one concrete distribution surface**:3334| Distribution Type | Example |35|-------------------|---------|36| Clean buyer list | Directory, licensing board, registry, permit database |37| Channel partner | Supplier, distributor, association, insurer, payments provider |38| High-intent inbound | Compliance forms, deadline-driven searches, "how to file X" |39| System-of-record hook | Integration with existing workflow software |4041**If none exist after research: output `FAIL (distribution)` and stop.**4243## Process4445Execute in order. Stop early if distribution fails.4647### 1. Define the Niche Precisely4849- Who pays? Who uses daily?50- What mandatory artifact exists? (forms, submissions, certificates, logs, reports)51- What's the "money leak"? (lost renewals, rejected applications, admin hours, penalties, missed revenue)5253### 2. Identify the Paperwork Wedge5455- What exact document/packet/submission is unavoidable?56- What deadlines exist? (annual, quarterly, event-triggered)57- Who gets blamed when it's wrong or late?5859### 3. Competitor & Crowding Check6061- Direct niche tools (name, pricing, market position)62- Generic substitutes (PDFs, spreadsheets, Jobber, HubSpot, email)63- Government/industry portals acting as system-of-record64- Funded players in adjacent spaces6566### 4. Distribution Map6768**Must be concrete—no "we could try LinkedIn."**6970- List sources (actual URLs or database names)71- 1–2 plausible channel partners72- Inbound keywords indicating urgency (with search volume if available)73- Integration hooks (what software do they already use?)7475If unclear after research: `FAIL: Distribution unclear. Cannot proceed.`7677### 5. Founder Fit Check7879- Do you have natural access to these buyers? (former industry, network, geography)80- Would you enjoy 50+ sales calls with this persona?81- Is this a market you'd still care about in 3 years?82- Any ethical/personal hesitations?8384*Note: This section requires founder input. Flag if not provided.*8586### 6. Buildability & Support Load8788- Can core v1 be built in 2–6 weeks by a solo dev?89- If regulated/integrated workflow: add 4–8 week buffer90- If jurisdiction sprawl (state-by-state rules): add research time per region91- Any liability or compliance certification required?92- Edge case density: low / medium / high9394### 7. Pricing for Lifestyle Outcome9596| Tier | ARPA | When Acceptable |97|------|------|-----------------|98| Preferred | $150–$500/mo | Default target |99| Acceptable | $80–$150/mo | Only if churn < 3%/mo AND distribution is cheap |100| Avoid | < $50/mo | Only if distribution is nearly free (viral, marketplace) |101102### 8. Revenue Quality103104- Contract structure: monthly / annual / multi-year105- Payment behavior: prepaid / net-30 / invoice-heavy industries106- Expansion path: per-seat / usage-based / upsell tiers107108### 9. Market Size (Conservative)109110- Count payers using best available proxy (licenses, permits, businesses)111- Calculate path to $1M ARR: (target ARPA) × (customers needed)112- Calculate path to $3M ARR: (target ARPA) × (customers needed)113- Note key assumptions114115### 10. Defensibility Check116117At least one should be present:118- **Data/workflow lock-in**: Does usage create switching cost?119- **Relationship moat**: Are buyers sticky once onboarded?120- **Distribution exclusivity**: Can you lock up a channel?121- **Speed moat**: Can you ship fast enough to stay ahead?122123### 11. Verdict + Kill Criteria124125- **Pursue**: Clear distribution + viable pricing + buildable scope126- **Hold**: Promising but missing one key signal127- **Kill**: No distribution OR requires > 3,000 customers OR unbuildable scope128129Include:130- Must-have signals to proceed131- 7-day validation plan132133---134135## Output136137**Filename:** `Niche_FirstPass_<slug>.md`138139```markdown140# Niche First Pass: <Title>141142## TL;DR Verdict143144- **Verdict:** Pursue / Hold / Kill145- **Why:** (3 blunt bullets)146147## The Wedge148149(One sentence: sellable workflow + mandatory artifact + outcome)150151## Customer Profile152153| Role | Description |154|------|-------------|155| Paying customer | |156| Daily user | |157| Trigger moment | |158159## Workflow Today (As-Is)1601611. 1622. 1633. 164165## Pain / Money Leak166167- **Time waste:**168- **Errors/rejects:**169- **Compliance risk:**170- **Revenue leak:**171172## Existing Solutions173174### Direct Niche Tools175| Tool | Pricing | Notes |176|------|---------|-------|177| | | |178179### Substitutes180- 181182## Distribution (Must Be Specific)183184- **List source:** (actual URL/database)185- **Channel candidate:**186- **Inbound keywords:** (with volume if known)187- **Integration hook:**188- **Distribution risk:**189190## Founder Fit191192- [ ] Natural access to buyers193- [ ] Would enjoy 50+ sales calls with this persona194- [ ] Would care about this market in 3 years195- [ ] No ethical/personal hesitations196197*Fit score: Strong / Moderate / Weak / Unknown*198199## Buildability200201| Factor | Assessment |202|--------|------------|203| Core v1 timeline | 2–6 weeks / 6–12 weeks / 12+ weeks |204| Regulatory buffer needed | Yes / No |205| Jurisdiction sprawl | None / Moderate / Severe |206| Edge case density | Low / Medium / High |207| Support load estimate | < 5 hrs/wk / 5–15 hrs/wk / 15+ hrs/wk |208209### MVP Scope210211**Must-have:**212- 213214**Nice-to-have:**215- 216217**Explicit non-goals:**218- 219220## Pricing221222- **Recommended tiers:**223- **Expected ARPA:**224- **Why it's fair:**225226## Revenue Quality227228- **Contract structure:**229- **Payment behavior:**230- **Expansion path:**231232## Market Size (Conservative)233234- **Payers in target geography:**235- **Total US payers:**236- **Path to $1M ARR:** X customers × $Y ARPA237- **Path to $3M ARR:** X customers × $Y ARPA238- **Key assumption:**239240## Defensibility241242| Moat Type | Present? | Notes |243|-----------|----------|-------|244| Data/workflow lock-in | | |245| Relationship moat | | |246| Distribution exclusivity | | |247| Speed moat | | |248249## Biggest Entry Risks2502511. 2522. 2533. 254255## Kill Criteria256257- If we don't hear X in 10 calls → kill258- If pricing won't clear $Y → kill259- If compliance/portal makes it redundant → kill260261## 7-Day Validation Plan262263| Day | Activity | Success Signal |264|-----|----------|----------------|265| 1 | | |266| 2–3 | | |267| 4–5 | | |268| 6–7 | | |269```