Market requirements document
em-are-DEE
A document that defines market needs, target segments, and competitive landscape to guide product development decisions.
An MRD captures what the market needs before anyone starts building. It covers the target market, customer pain points, competitive landscape, market sizing, and high-level requirements. The MRD answers 'what should we build?' while the PRD answers 'how exactly should it work?'
MRDs are more common in larger organizations where product marketing and product management are separate functions. Product marketing owns the MRD (market perspective), and product management owns the PRD (product perspective).
In smaller companies and startups, the MRD and PRD often merge into a single document. The founder or PM captures market context and product requirements together because one person owns both.
Examples
A product marketing manager writes an MRD for a new market.
The MRD covers: target buyer (DevOps managers at companies with 200+ engineers), market size ($2B TAM), top 5 pain points (from 30 customer interviews), competitive landscape (3 direct competitors, 2 adjacent), and 10 high-level requirements the product must meet.
An MRD informs the product roadmap.
The MRD identifies that 80% of target buyers rank 'automated compliance reporting' as a top-3 need. No competitor has it. The PM prioritizes this feature on the roadmap based on the MRD's market evidence.
An MRD reveals a gap between product and market.
The MRD shows that the market has shifted toward AI-assisted workflows. The current product has no AI capabilities. The leadership team uses the MRD to justify investing in an AI initiative for the next two quarters.
In practice
Read more on the blog
Frequently asked questions
What is the difference between an MRD and a PRD?
An MRD defines what the market needs (external perspective). A PRD defines what the product should do (internal perspective). The MRD comes first: market insights inform product requirements. In practice, many teams combine both into a single document.
Do startups need MRDs?
Formal MRDs are rare in startups. But the thinking behind an MRD (who is the customer, what do they need, who are the competitors) is essential. Startups capture this in pitch decks, one-pagers, or the market context section of their PRDs.
Related terms
A document that defines what a product or feature should do, who it serves, and how success will be measured.
A strategic plan that outlines upcoming product features, priorities, and timelines to align the team and communicate direction.
A structured method for deciding which features or initiatives to work on first based on impact, effort, and strategic alignment.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.