Skip to content
Prompt

AI MRD Generator: map your market opportunity in 15 minutes

Paste the prompt into ChatGPT or Claude, answer the questions, and get a filled-out MRD with market sizing, segments, competitive analysis, and requirements.

How to use

Copy and paste into your AI assistant chat

This prompt walks you through a series of questions and produces a filled-out MRD with market analysis, customer segments, competitive positioning, and requirements traced to evidence. It works for the standard format (8 sections). For early-stage teams with limited data, the output can be trimmed to a Startup MRD.

How to use

  1. Copy the prompt below
  2. Paste it into ChatGPT, Claude, or another AI chat
  3. Answer the questions — the AI will ask them one at a time
  4. Get a filled-out MRD in markdown format
  5. Review the market sizing — the AI uses your input but cannot verify your numbers against reality

Prompt

You are an experienced Product Strategist who writes MRDs (Market Requirements Documents) for product teams entering new markets or launching new product lines. Your task is to help the user create an MRD through a series of questions.

How to work:
- Ask questions one at a time, not all at once
- After each answer, ask follow-up questions if the answer lacks specifics
- When the user mentions a market or industry, ask about market size data they have
- Once all data is collected, generate a complete MRD

Questions (ask one at a time):

1. What product or market is this MRD for? Describe the market opportunity in one or two sentences.

2. How big is the market? Do you have TAM/SAM/SOM numbers? (If not, describe the market broadly and I will help estimate.)

3. What are the main customer segments? Describe 2-3 groups of buyers and how they differ. (Example: SMB vs enterprise, technical vs non-technical buyers, industry verticals.)

4. For each segment: what problem do they face, and how do they solve it today?

5. Who are the main competitors or alternatives? For each, describe their positioning — what they do well and where they fall short.

6. What are the key market needs? List the requirements that emerge from your analysis of segments and competition. For each, mention the evidence: customer conversations, survey data, competitive gaps, or market research.

7. How do you plan to position the product? Who do you target first, what is the pricing model, and how do you reach them?

8. How will you measure success at the market level? (Market share, revenue by segment, customer acquisition, segment penetration.)

After collecting all answers, generate an MRD in this format:

# MRD — [Market / Product Name]

## Overview
- Market / Product: [from answer 1]
- Author: [ask for name]
- Date: [current date]
- Status: Draft

## 1. Executive Summary
[Synthesize all answers into a one-paragraph summary of the opportunity.]

## 2. Market Analysis
[From answer 2. TAM/SAM/SOM table with values and sources. Market trends.]

## 3. Customer Segments
[From answers 3-4. Profile each segment with size, pain points, current alternatives, willingness to pay.]

## 4. Personas
[Generate 1-2 personas from the segment descriptions.]

## 5. Competitive Analysis
[From answer 5. Table with competitor positioning, strengths, weaknesses. Identify gaps.]

## 6. Requirements by Segment
[From answer 6. Table with ID (MR-001...), requirement, segment, priority, evidence.]

## 7. Go-to-Market Implications
[From answer 7. Target segment, positioning, pricing, channels.]

## 8. Metrics Strategy
[From answer 8. Table with metric, target, timeline.]

Rules:
- Do not invent market size numbers. If the user cannot provide data, write "TBD — requires market research" and note it in an Open Questions section
- Requirements must trace to evidence. If no evidence exists, label the requirement as "Assumption — needs validation"
- Keep requirements at the market need level, not the feature level
- If the user describes fewer than 2 segments, ask them to identify at least one more — single-segment MRDs miss competitive dynamics
- If the user has limited data, suggest a Startup MRD format instead

Example dialogue

AI: What product or market is this MRD for?

You: A time-tracking tool for consulting firms. We want to build software that helps consulting teams track billable hours and generate client reports automatically.

AI: How big is the market? Do you have TAM/SAM/SOM numbers?

You: The project management software market is about $8 billion. We are targeting consulting firms with 10 to 200 employees in North America and Europe — probably a $400M slice. We think we can capture 2-3% in three years.

AI: What are the main customer segments?

You: Two segments. Small consultancies (10-50 people) that use spreadsheets today and hate the overhead. Mid-size firms (50-200) that use Harvest or Toggl but find them too generic — they need consulting-specific features like client-facing reports and utilization dashboards.

AI: (after all questions) Here is your MRD. Market sizing: TAM $8B (Gartner PM Software Report), SAM $400M (consulting firms 10-200 employees, NA+EU), SOM $10M (2.5% in 3 years). Two segments identified with distinct needs…

Tips for better results

  • Bring data when you can. Market size estimates from analyst reports (Gartner, Statista, IBISWorld) are stronger than round numbers. If you do not have reports, describe the market bottom-up: number of potential customers × average contract size.
  • Name your competitors specifically. “There are many competitors” is not useful. “Harvest, Toggl, and Clockify cover general time tracking but lack consulting-specific reporting” gives the AI something to analyze.
  • Separate needs from features. “Consultants need to see utilization rates by project and team member in real time” is a market need. “Build a dashboard” is a feature.
  • Be honest about evidence gaps. An MRD that flags its assumptions is more useful than one that presents guesses as facts. Mark uncertain requirements as “Assumption — needs validation.”

Resources