What This Template Is For
Market research answers questions that product analytics cannot: Why are potential customers choosing a competitor? What adjacent problems do they care about? Is there demand for a product category that does not exist yet? Analytics tells you what is happening. Market research tells you why, and what might happen next.
Most product teams skip formal market research because it feels slow and academic. The result is teams that build based on internal conviction rather than external evidence. This template provides a practical, time-boxed framework for market research projects that a PM can execute in 1-2 weeks without a dedicated research team.
The template covers five phases: defining research objectives, selecting methodology, recruiting participants, collecting data, and synthesizing findings into actionable recommendations. It is designed for product decisions like entering a new market segment, validating a new product category, evaluating pricing, or understanding competitive dynamics.
The Product Discovery Handbook covers the broader discovery process that market research feeds into. For competitive-specific research, the Competitive Intelligence Template provides a focused tracking structure. The TAM Calculator can help quantify the market opportunity your research uncovers.
How to Use This Template
- Start with the Research Brief. Define what decision this research will inform. If you cannot name the decision, the research is not worth doing.
- Select your methodology. The Methodology Selection Guide helps you choose between qualitative, quantitative, and secondary research based on your question type and timeline.
- Plan recruitment. For qualitative research, 8-12 participants is usually sufficient. For quantitative, aim for statistical significance (typically n>100 for surveys).
- Collect data using the structured guides in the Data Collection section.
- Analyze findings using the Synthesis Framework. Group insights by theme, not by participant.
- Present findings using the Research Report structure. Lead with the decision recommendation, not the methodology.
The Template
Research Brief
| Field | Details |
|---|---|
| Project Name | [e.g., "Enterprise Buyer Needs Assessment"] |
| Research Lead | [Name] |
| Stakeholders | [Who will use the findings: PM, VP Product, Marketing, Sales] |
| Decision to Inform | [Specific decision, e.g., "Should we build an enterprise tier with SSO and RBAC?"] |
| Research Questions | [3-5 specific questions. See below.] |
| Timeline | [Start date - End date] |
| Budget | [Participant incentives, tool costs, panel costs] |
| Deadline for Findings | [Date: when the decision needs to be made] |
Research Questions
Good research questions are specific, answerable, and decision-relevant. Avoid vague questions like "What do customers want?"
- [e.g., "What percentage of our target market (50-500 employee SaaS companies) considers SSO a must-have vs. nice-to-have for PM tools?"]
- [e.g., "What security and compliance features do enterprise buyers evaluate when choosing a PM tool?"]
- [e.g., "What is the typical budget range for PM tooling at companies with 200+ employees?"]
- [e.g., "Which competitors are winning enterprise deals, and what do buyers cite as their primary reasons?"]
- [e.g., "What would trigger a company to switch from their current PM tool to ours?"]
Methodology Selection Guide
| Research Question Type | Best Method | Sample Size | Timeline | Cost |
|---|---|---|---|---|
| "Why do users behave this way?" | In-depth interviews | 8-12 | 2-3 weeks | $50-100/participant incentive |
| "How many users have this need?" | Survey | 100-300+ | 1-2 weeks | $0-5K (panel cost) |
| "How do users complete this task?" | Usability testing / observation | 5-8 | 1-2 weeks | $50-100/participant |
| "What does the market look like?" | Secondary research (reports, data) | N/A | 3-5 days | $0-2K (report purchases) |
| "What would users pay?" | Van Westendorp / Conjoint survey | 200+ | 2-3 weeks | $2-5K (panel + tool) |
| "Who are our competitors?" | Competitive audit | N/A | 1-2 weeks | $0-500 |
Recommended approach for most product decisions: Combine secondary research (3-5 days) with 8-10 interviews (1-2 weeks) to build a qualitative understanding, then optionally validate quantitatively with a survey.
Participant Recruitment
Target Profile
| Dimension | Criteria |
|---|---|
| Job Title / Role | [e.g., "VP Product, Director of Product, Senior PM"] |
| Company Size | [e.g., "50-500 employees, SaaS or tech company"] |
| Industry | [e.g., "B2B SaaS, excluding agencies and consulting firms"] |
| Geography | [e.g., "US and Western Europe"] |
| Current Tool | [e.g., "Currently using a PM tool (any) OR evaluating PM tools"] |
| Exclusions | [e.g., "Not current customers. Not competitors' employees."] |
Recruitment Channels
| Channel | Best For | Expected Response Rate | Cost |
|---|---|---|---|
| Your user base (non-customers) | Qualitative interviews | 5-15% | Free (incentive only) |
| LinkedIn outreach | Qualitative interviews with specific personas | 2-5% | Free + incentive |
| UserTesting / Respondent.io | Qualitative + quantitative, fast | 80%+ (pre-screened) | $50-150/participant |
| SurveyMonkey Audience / Pollfish | Quantitative surveys at scale | N/A (panel) | $1-5/response |
| Industry communities (Slack, Reddit) | Qualitative screening | 1-3% | Free + incentive |
Screening Questions
Use these to qualify participants before scheduling:
- What is your current role? [Must match target profile]
- How many employees are at your company? [Must match size criteria]
- What PM tool(s) does your team currently use? [Captures competitive data]
- Are you involved in purchasing or evaluating PM tools? [Decision-maker filter]
- Have you evaluated or switched PM tools in the past 12 months? [Recency filter]
Data Collection
Interview Guide (Qualitative)
| Phase | Duration | Questions |
|---|---|---|
| Warm-up | 3-5 min | Tell me about your role. How is your product team structured? What tools do you use day-to-day? |
| Current State | 10-15 min | Walk me through how you [relevant workflow]. What works well? What is frustrating? How did you choose your current tool? |
| Problem Exploration | 10-15 min | [Research question-specific probes. e.g., "How does your team handle security requirements when evaluating tools?"] What has this cost you in terms of time, money, or missed opportunities? |
| Solution Reaction | 5-10 min | [Optional: show a concept, mockup, or feature description.] How would this fit into your current workflow? What would need to change? |
| Prioritization | 5 min | If you could only fix one thing about [category], what would it be? What would you pay for that solution? |
| Wrap-up | 2-3 min | Is there anything I should have asked but did not? Can I follow up if I have questions? |
Interview Notes Template
| Field | Notes |
|---|---|
| Participant | [Name / ID, Title, Company size] |
| Date | [Date] |
| Key Quote 1 | ["Direct quote about a key insight"] |
| Key Quote 2 | ["Direct quote"] |
| Key Quote 3 | ["Direct quote"] |
| Unmet Needs | [Bulleted list] |
| Current Workaround | [How they solve the problem today] |
| Willingness to Pay | [Signal: strong / moderate / weak] |
| Competitor Mentioned | [Which competitors, in what context] |
| Surprise / Unexpected | [Anything you did not anticipate] |
Survey Template (Quantitative)
Structure surveys in this order:
- Screening questions (2-3): Confirm eligibility
- Behavioral questions (3-5): What they do today (easier to answer, builds momentum)
- Attitudinal questions (3-5): What they think, feel, prefer
- Prioritization (1-2): Forced ranking or MaxDiff
- Pricing (1-3): Van Westendorp or direct WTP questions
- Demographics (2-3): Company size, role, industry
Keep the total survey under 15 questions. Every question beyond 15 reduces completion rate by approximately 5%.
Analysis Framework
Qualitative Synthesis (Interviews)
Group findings by theme, not by participant. Use this affinity mapping structure:
| Theme | Evidence | Frequency | Impact | Quotes |
|---|---|---|---|---|
| [e.g., Security is a dealbreaker for enterprise] | [7/10 participants mentioned SSO as mandatory] | [70%] | [High: blocks purchase decision] | ["We cannot buy any tool without SSO. It is non-negotiable." - VP Product, 200-person SaaS] |
| [Theme 2] | [Evidence] | [Frequency] | [Impact] | [Quote] |
| [Theme 3] | [Evidence] | [Frequency] | [Impact] | [Quote] |
Quantitative Analysis (Surveys)
| Analysis Type | When to Use | Tool |
|---|---|---|
| Frequency distribution | Understand how common a need/behavior is | Spreadsheet |
| Cross-tabulation | Compare segments (e.g., enterprise vs SMB) | Spreadsheet / SPSS |
| Statistical significance | Verify that differences are real, not random | Chi-square or t-test |
| Cluster analysis | Identify distinct customer segments | Python / R |
Research Report Structure
Lead with the recommendation, not the methodology.
| Section | Content | Length |
|---|---|---|
| Executive Summary | Decision recommendation + 3 key findings | 1 paragraph |
| Research Questions & Methodology | What we asked, how we asked it, who we asked | 0.5 page |
| Key Findings | Themed findings with evidence (quotes, data) | 2-4 pages |
| Market Sizing | Addressable market for the opportunity identified | 0.5 page |
| Competitive Context | How competitors address (or fail to address) the need | 0.5 page |
| Recommendations | Specific product/strategy recommendations with rationale | 1 page |
| Appendix | Raw data, full survey results, interview transcripts | As needed |
Filled Example: Enterprise Market Expansion Research
Research Brief
| Field | Details |
|---|---|
| Project Name | Enterprise PM Tool Requirements |
| Research Lead | Sarah Kim, Senior PM |
| Decision to Inform | Should we invest in building an enterprise tier ($50K+ ACV) in Q2-Q3 2026? |
| Timeline | February 10 - February 28, 2026 (3 weeks) |
| Budget | $2,500 (participant incentives + survey panel) |
Methodology
- Phase 1 (Days 1-5): Secondary research. Industry reports, competitor enterprise pages, G2 enterprise reviews.
- Phase 2 (Days 5-15): 10 in-depth interviews with VP/Director Product at 200-500 person SaaS companies.
- Phase 3 (Days 12-18): Survey of 150 PM leaders (50-500 employee companies) via Respondent.io panel.
Key Finding: SSO is a Non-Negotiable Gate
| Theme | Evidence | Frequency | Impact |
|---|---|---|---|
| SSO is mandatory | 9/10 interview participants stated SSO is required for any tool purchase over $5K/year | 90% in interviews, 78% in survey | Dealbreaker: without SSO, enterprise deals will not close |
| RBAC is expected but negotiable | 7/10 mentioned role-based access as important but would work around it | 70% interviews, 62% survey | Important but not a blocker |
| SOC 2 compliance asked about in 80%+ of enterprise evaluations | 8/10 asked about compliance during the interview | 80% interviews, 71% survey | Required for procurement process |
Recommendation
Invest in the enterprise tier. The research supports a $45K+ ACV market with clear feature requirements (SSO, RBAC, SOC 2, audit logs). Estimated 6-month engineering investment. Recommend shipping SSO first (unblocks deals) then RBAC and compliance features in Q3.
Common Mistakes to Avoid
- Researching without a decision in mind. "Let's see what users think" is not a research project. It is a fishing expedition. Define the specific decision the research will inform before starting.
- Only talking to your existing users. Your users are a biased sample. They already chose your product. To understand the market, talk to non-users, competitor users, and people who evaluated your product and chose something else.
- Leading questions in interviews. "Would you find it helpful if we added SSO?" will get you a "yes" every time. Ask "Tell me about your tool evaluation process" and listen for whether security comes up organically.
- Small survey samples presented as definitive. A survey of 30 people is directional, not statistically significant. Either invest in a proper sample size (n>100) or be transparent about the limitations.
- Burying the recommendation. Stakeholders do not read methodology sections. Lead with the recommendation and the 3 key findings. Put the methodology in a secondary section for those who want to validate the approach.
Key Takeaways
- Define the decision the research will inform before starting. No decision, no research project
- Combine secondary research with 8-12 qualitative interviews for most product decisions
- Group findings by theme, not by participant. Lead reports with the recommendation
- Talk to non-users and competitor users, not just your existing customers
- Keep surveys under 15 questions. Every additional question reduces completion rate
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use