lsauer/gist:a73c924fe09fd5b5469401363176a059

## gistfile1.txt
# Product Market Fit Research Prompt

> **KICKOFF:** I have a product idea I need to validate before I waste time building it. I'm providing the user stories and 4P doc for context. Follow this process systematically. Your job is to tell me if this idea is dead on arrival or worth my next 3 months.

---

## Role

You are a ruthless, evidence-driven marketing researcher. You are not my cheerleader. Your job is to find reasons this idea will **fail** first, then — only if it survives — find reasons it could work. Optimism without data is useless to me.

## Inputs

- Product Overview
- Product Features
- User Stories.md

## Tools

Run this through ALL of the following deep research tools, then synthesize into a single document. Use the web-app "Deep Research" mode for each — standard chat models miss too much.

- ChatGPT Deep Research
- Claude Deep Research
- Grok Deep Research
- Perplexity Deep Research
- Gemini Deep Research

## Output

Single markdown document. Q/A format. Do **not** rewrite the questions — answer inline directly under each one. Keep answers dense, not padded.

## Hard Constraints

- I'm a solo indie dev. No team. No marketing budget. No existing audience.
- Zero users today. Brand new.
- **MANDATORY: Every answer must cite a source, link, data point, or screenshot. If you couldn't find evidence, say "NO DATA FOUND" — do not fabricate, speculate, or hedge with "it's likely that..." filler. I'd rather have 5 honest answers than 30 hallucinated ones.**
- If a question is unanswerable with available tools, say so and explain what data I'd need to get the answer manually.

---

## 1 — KILL CRITERIA (Answer these first. If any are fatal, stop here.)

1. Is there a free, good-enough solution that already exists and has network effects or lock-in? Name it.
2. Will a frontier AI model (ChatGPT/Claude/Gemini) make this product pointless within 12 months? Be specific about which capabilities would kill it.
3. Does this require a critical mass of users to deliver value (marketplace/network effect)? If yes, how do you cold-start that alone?
4. Is the target user someone who actually pays for software, or are they notorious cheapskates in this category? Cite evidence.
5. Can a competitor with resources clone the core value prop in a weekend? What's the actual defensibility?

---

## 2 — UNIT ECONOMICS (Hard numbers only)

1. **Revenue ceiling:** Based on comparable solo-dev products in this space, what's a realistic monthly revenue at 6mo, 12mo, 24mo? Cite specific comparables (IndieHackers revenue posts, Starter Story, open-startup dashboards, Sensor Tower, etc.).
2. **Operating costs:** Itemize hosting, API costs, tools, domain, auth provider, etc. Give a monthly burn estimate at 100 users, 1,000 users, 10,000 users.
3. **Margins:** Given the above, what are realistic profit margins? Flag any cost that scales dangerously with usage (e.g., LLM API calls per user).

---

## 3 — CUSTOMER

1. **Who exactly is the buyer?** Define the niche. Not "developers" — be specific. Job title, company size, budget authority, context where the pain hits.
2. **Where do they congregate online?** List specific subreddits, Discord servers, Slack groups, forums, newsletters, Twitter accounts, YouTube channels. Not categories — URLs.
3. **Why would they use this?** What trigger event makes them search for a solution?
4. **Why would they NOT buy?** List every objection. Be harsh.
5. **What pain does this actually solve?** Map each core feature to a specific, named pain point. If a feature doesn't map to a pain point, flag it as scope creep.
6. **What are they really buying?** (Time saved? Status? Risk reduction? Convenience?) This determines positioning.
7. **What would make them feel stupid for NOT using it?** This is the over-delivery question.
8. **What are they doing today instead?** Describe the current janky workflow step-by-step, including the friction points.

---

## 4 — MARKET RESEARCH

### 4a — Keyword & Demand Signals

Generate 5–10 keywords first (include long-tail). Then run each source below. For each, log what you found or "NO DATA FOUND."

| Source | What to extract |
|---|---|
| **Google Trends** | 5-year trend line, then 1-year zoom. Is it growing, flat, or dying? |
| **Ahrefs / Ubersuggest** | Search volume + keyword difficulty for top 5 keywords. Flag any with high volume + low KD. |
| **Sensor Tower** | Monthly revenue estimates for top 5 competitors (mobile). |
| **Flippa / Acquire.com** | Top 5 similar products sold. Sale price + revenue multiples. Filter: iOS/Android apps, web products. |
| **Udemy / Skillshare** | Courses on this topic. Enrollment numbers = demand signal. |
| **Gumroad / Lemon Squeezy** | Digital products in this space. Sales counts if visible. |
| **Etsy** (if applicable) | Related products, review counts, pricing. |
| **Reddit** | Search: `"alternatives to [competitor]"`, `"frustrated with"`, `"I hate"`, `"does anyone else"`, `"wish there was"` + category terms. Log **exact quotes, upvote counts, recency.** |
| **X/Twitter** | Advanced search: `("[competitor]" OR "[category]") (bug OR broken OR annoying OR "wish" OR "why can't")` — last 90 days. Log counts by theme. |
| **App Store / Play Store reviews** | 1–3★ reviews of top 5 competitors. Extract recurring complaints. **Log exact quotes.** |
| **Chrome Web Store** | 1–3★ reviews of competitor extensions. Extract "it breaks when..." edge cases. **Log exact quotes + repeat counts.** |
| **G2 / Capterra / TrustRadius** | Sort by lowest rating. Extract pain themes. Log quotes. |
| **Competitor bug trackers** | Check UserVoice / Canny / Nolt / GitHub Issues. Search: "still broken", "regression", "frustration". Log open issue counts + age. |
| **Google Keyword Planner** | ⚠️ Requires manual access. Flag for me to run. |

### 4b — Competitive Landscape

1. **Top 5 competitors.** For each: name, pricing, estimated revenue (cite source), funding status, team size, years in market. Format as a table.
2. **How is this problem currently solved?** Describe the status quo. What's good about it? What's bad? Be specific.
3. **How much competition?** Saturated, moderate, or blue ocean? Evidence.

### 4c — Market Sizing

1. **TAM/SAM/SOM.** Show your math. Don't just throw out a number from a Statista report — build it bottom-up from number of potential users × realistic ARPU.

### 4d — Strategic Assessment

1. **Pricing:** What's the no-brainer price point? What's the "good deal for me" price? What are natural upsell tiers? Cite competitor pricing as anchors.
2. **Automation potential:** Can the core delivery be fully automated, or does it require ongoing manual work from me?
3. **AI obsolescence risk:** Specific capabilities that would need to emerge to kill this. Timeline estimate.
4. **Distribution channels:** Rank by effort-to-impact ratio for a solo dev with $0 budget.
5. **SEO keywords:** List 10+ relevant keywords that aren't saturated (KD < 30, volume > 100/mo).
6. **Opportunities worth time:** What should I focus on?
7. **Gaps this product can fill:** Specific unmet needs competitors aren't addressing.
8. **What to ignore:** Features, markets, or channels that are traps for a solo dev.

---

## 5 — GO-TO-MARKET (Solo Dev, $0 Budget)

1. **Unfair advantages:** What can I do that funded competitors can't or won't? (Speed, niche focus, pricing, community presence, etc.)
2. **Paths to customers:** Rank by realistic conversion potential. No "post on Product Hunt and go viral" fantasy.
3. **Differentiation:** What's the wedge? Not "better UX" — something concrete and defensible.
4. **First 10 customers:** Exact playbook. Where, how, what to say.
5. **First $100:** Fastest realistic path. Pre-sales? Lifetime deals? Beta access?
6. **Business model:** One-time vs. recurring. Impact on LTV, churn, and cash flow. Recommend one and justify.
7. **Engineering as Marketing — 3-5 ideas:** Free micro-tools related to the core product that attract the target audience and funnel to paid. Each must be buildable in < 1 week solo.
8. **Lead magnets — 3-5 ideas:** Single-page micro-apps, calculators, checklists, or templates that solve a small adjacent problem and capture emails. Must be directly relevant — not generic.

---

## 6 — VERDICT

1. **Rate this idea: 0–100.** 100 = obvious, urgent, large market, no competition, prints money. 0 = dead on arrival. Be brutal. Justify with evidence from above.
2. **Top 3 reasons this fails.**
3. **Top 3 reasons this succeeds.**
4. **If you had to bet your own money on this, would you? Why or why not?**
5. **Suggested pivots or adjacent ideas** that scored better in the research above.

---

## 7 — MVP SPEC

1. **Tracer-bullet MVP:** What's the absolute minimum feature set that tests the core value prop? Must be buildable solo in 1–2 weeks. If it can't be, the scope is wrong — cut harder.
2. **What to explicitly leave out of v1** and why.
3. **How to measure if it's working:** Define 2–3 metrics that tell you within 30 days if this has legs.
	# Product Market Fit Research Prompt

	> KICKOFF: I have a product idea I need to validate before I waste time building it. I'm providing the user stories and 4P doc for context. Follow this process systematically. Your job is to tell me if this idea is dead on arrival or worth my next 3 months.

	---

	## Role

	You are a ruthless, evidence-driven marketing researcher. You are not my cheerleader. Your job is to find reasons this idea will fail first, then — only if it survives — find reasons it could work. Optimism without data is useless to me.

	## Inputs

	- Product Overview
	- Product Features
	- User Stories.md

	## Tools

	Run this through ALL of the following deep research tools, then synthesize into a single document. Use the web-app "Deep Research" mode for each — standard chat models miss too much.

	- ChatGPT Deep Research
	- Claude Deep Research
	- Grok Deep Research
	- Perplexity Deep Research
	- Gemini Deep Research

	## Output

	Single markdown document. Q/A format. Do not rewrite the questions — answer inline directly under each one. Keep answers dense, not padded.

	## Hard Constraints

	- I'm a solo indie dev. No team. No marketing budget. No existing audience.
	- Zero users today. Brand new.
	- MANDATORY: Every answer must cite a source, link, data point, or screenshot. If you couldn't find evidence, say "NO DATA FOUND" — do not fabricate, speculate, or hedge with "it's likely that..." filler. I'd rather have 5 honest answers than 30 hallucinated ones.
	- If a question is unanswerable with available tools, say so and explain what data I'd need to get the answer manually.

	---

	## 1 — KILL CRITERIA (Answer these first. If any are fatal, stop here.)

	1. Is there a free, good-enough solution that already exists and has network effects or lock-in? Name it.
	2. Will a frontier AI model (ChatGPT/Claude/Gemini) make this product pointless within 12 months? Be specific about which capabilities would kill it.
	3. Does this require a critical mass of users to deliver value (marketplace/network effect)? If yes, how do you cold-start that alone?
	4. Is the target user someone who actually pays for software, or are they notorious cheapskates in this category? Cite evidence.
	5. Can a competitor with resources clone the core value prop in a weekend? What's the actual defensibility?

	---

	## 2 — UNIT ECONOMICS (Hard numbers only)

	1. Revenue ceiling: Based on comparable solo-dev products in this space, what's a realistic monthly revenue at 6mo, 12mo, 24mo? Cite specific comparables (IndieHackers revenue posts, Starter Story, open-startup dashboards, Sensor Tower, etc.).
	2. Operating costs: Itemize hosting, API costs, tools, domain, auth provider, etc. Give a monthly burn estimate at 100 users, 1,000 users, 10,000 users.
	3. Margins: Given the above, what are realistic profit margins? Flag any cost that scales dangerously with usage (e.g., LLM API calls per user).

	---

	## 3 — CUSTOMER

	1. Who exactly is the buyer? Define the niche. Not "developers" — be specific. Job title, company size, budget authority, context where the pain hits.
	2. Where do they congregate online? List specific subreddits, Discord servers, Slack groups, forums, newsletters, Twitter accounts, YouTube channels. Not categories — URLs.
	3. Why would they use this? What trigger event makes them search for a solution?
	4. Why would they NOT buy? List every objection. Be harsh.
	5. What pain does this actually solve? Map each core feature to a specific, named pain point. If a feature doesn't map to a pain point, flag it as scope creep.
	6. What are they really buying? (Time saved? Status? Risk reduction? Convenience?) This determines positioning.
	7. What would make them feel stupid for NOT using it? This is the over-delivery question.
	8. What are they doing today instead? Describe the current janky workflow step-by-step, including the friction points.

	---

	## 4 — MARKET RESEARCH

	### 4a — Keyword & Demand Signals

	Generate 5–10 keywords first (include long-tail). Then run each source below. For each, log what you found or "NO DATA FOUND."

	\| Source \| What to extract \|
	\|---\|---\|
	\| Google Trends \| 5-year trend line, then 1-year zoom. Is it growing, flat, or dying? \|
	\| Ahrefs / Ubersuggest \| Search volume + keyword difficulty for top 5 keywords. Flag any with high volume + low KD. \|
	\| Sensor Tower \| Monthly revenue estimates for top 5 competitors (mobile). \|
	\| Flippa / Acquire.com \| Top 5 similar products sold. Sale price + revenue multiples. Filter: iOS/Android apps, web products. \|
	\| Udemy / Skillshare \| Courses on this topic. Enrollment numbers = demand signal. \|
	\| Gumroad / Lemon Squeezy \| Digital products in this space. Sales counts if visible. \|
	\| Etsy (if applicable) \| Related products, review counts, pricing. \|
	\| Reddit \| Search: `"alternatives to [competitor]"`, `"frustrated with"`, `"I hate"`, `"does anyone else"`, `"wish there was"` + category terms. Log exact quotes, upvote counts, recency. \|
	\| X/Twitter \| Advanced search: `("[competitor]" OR "[category]") (bug OR broken OR annoying OR "wish" OR "why can't")` — last 90 days. Log counts by theme. \|
	\| App Store / Play Store reviews \| 1–3★ reviews of top 5 competitors. Extract recurring complaints. Log exact quotes. \|
	\| Chrome Web Store \| 1–3★ reviews of competitor extensions. Extract "it breaks when..." edge cases. Log exact quotes + repeat counts. \|
	\| G2 / Capterra / TrustRadius \| Sort by lowest rating. Extract pain themes. Log quotes. \|
	\| Competitor bug trackers \| Check UserVoice / Canny / Nolt / GitHub Issues. Search: "still broken", "regression", "frustration". Log open issue counts + age. \|
	\| Google Keyword Planner \| ⚠️ Requires manual access. Flag for me to run. \|

	### 4b — Competitive Landscape

	1. Top 5 competitors. For each: name, pricing, estimated revenue (cite source), funding status, team size, years in market. Format as a table.
	2. How is this problem currently solved? Describe the status quo. What's good about it? What's bad? Be specific.
	3. How much competition? Saturated, moderate, or blue ocean? Evidence.

	### 4c — Market Sizing

	1. TAM/SAM/SOM. Show your math. Don't just throw out a number from a Statista report — build it bottom-up from number of potential users × realistic ARPU.

	### 4d — Strategic Assessment

	1. Pricing: What's the no-brainer price point? What's the "good deal for me" price? What are natural upsell tiers? Cite competitor pricing as anchors.
	2. Automation potential: Can the core delivery be fully automated, or does it require ongoing manual work from me?
	3. AI obsolescence risk: Specific capabilities that would need to emerge to kill this. Timeline estimate.
	4. Distribution channels: Rank by effort-to-impact ratio for a solo dev with $0 budget.
	5. SEO keywords: List 10+ relevant keywords that aren't saturated (KD < 30, volume > 100/mo).
	6. Opportunities worth time: What should I focus on?
	7. Gaps this product can fill: Specific unmet needs competitors aren't addressing.
	8. What to ignore: Features, markets, or channels that are traps for a solo dev.

	---

	## 5 — GO-TO-MARKET (Solo Dev, $0 Budget)

	1. Unfair advantages: What can I do that funded competitors can't or won't? (Speed, niche focus, pricing, community presence, etc.)
	2. Paths to customers: Rank by realistic conversion potential. No "post on Product Hunt and go viral" fantasy.
	3. Differentiation: What's the wedge? Not "better UX" — something concrete and defensible.
	4. First 10 customers: Exact playbook. Where, how, what to say.
	5. First $100: Fastest realistic path. Pre-sales? Lifetime deals? Beta access?
	6. Business model: One-time vs. recurring. Impact on LTV, churn, and cash flow. Recommend one and justify.
	7. Engineering as Marketing — 3-5 ideas: Free micro-tools related to the core product that attract the target audience and funnel to paid. Each must be buildable in < 1 week solo.
	8. Lead magnets — 3-5 ideas: Single-page micro-apps, calculators, checklists, or templates that solve a small adjacent problem and capture emails. Must be directly relevant — not generic.

	---

	## 6 — VERDICT

	1. Rate this idea: 0–100. 100 = obvious, urgent, large market, no competition, prints money. 0 = dead on arrival. Be brutal. Justify with evidence from above.
	2. Top 3 reasons this fails.
	3. Top 3 reasons this succeeds.
	4. If you had to bet your own money on this, would you? Why or why not?
	5. Suggested pivots or adjacent ideas that scored better in the research above.

	---

	## 7 — MVP SPEC

	1. Tracer-bullet MVP: What's the absolute minimum feature set that tests the core value prop? Must be buildable solo in 1–2 weeks. If it can't be, the scope is wrong — cut harder.
	2. What to explicitly leave out of v1 and why.
	3. How to measure if it's working: Define 2–3 metrics that tell you within 30 days if this has legs.
No results found