Product Market Survey Template
Use this product-market survey to decide what to change next: messaging, segment focus, roadmap, packaging, or pricing. Send it to clean lifecycle groups (prospects vs users vs churned) and keep a stable core question set so you can track trends run to run.
Trusted by 5000+ Brands
How to Use This Product-Market Survey (3 Deployment Scenarios)
Scenario 1: Pre-product / pre-MVP concept validation
Goal: Decide if the concept is worth building, and which segment to build for first.
Who: Prospects (in-market); split buyer/decision-maker vs end-user.
When/Where: Send right after a concept demo, prototype walkthrough, or pricing page review (email + sales-assisted link).
Decision you can make: Commit to a segment + use case, or rewrite positioning before you write code. Do this next: add the competitor/alternative and problem-severity questions, then run 15-minute follow-up calls with 5-10 high-fit respondents.
Scenario 2: Post-MVP adoption diagnosis
Goal: Find the activation and onboarding blockers that prevent repeat usage.
Who: Trialists and new users; split by role (buyer vs end-user) and use case.
When/Where: Trigger after onboarding plus a first value moment (in-app + email).
Decision you can make: Ship the top 1-3 friction removals (setup, data import, permissions, time-to-value). Do this next: turn on the integrations module and add one open-end: "What stopped you from getting value this week?"
Scenario 3: Established product tune-up (positioning, packaging, retention)
Goal: Decide what to change to reduce churn and unlock expansion (positioning, packaging, pricing).
Who: Active users and churned/recent drop-offs; analyze separately.
When/Where: Send to active users after a meaningful workflow completes; send to churned users within days of cancellation (email + optional sales-assisted link).
Decision you can make: Pick one: adjust packaging, fix a top workflow gap, or narrow to a segment where retention is strongest. Do this next: add the churn/exit module for churned users only and schedule 10 interviews for your highest-revenue segment.
Distribution checklist (keep it simple)
- Email: Use a short invite that promises a concrete outcome ("help us pick the next 2 roadmap bets").
- In-app: Show the survey after the trigger moment (activation, success event, cancellation flow).
- Sales-assisted links: Give reps a single link per segment (prospect vs user vs churned) to avoid mixing data.
- Reminders: Send 1-2 reminders, 2-3 days apart. Incentives and follow-ups can lift participation; use them consistently across segments to avoid skewing who responds.
- Anonymous vs identified: Use identified responses when you need follow-up interviews. Use anonymous responses for sensitive topics (pricing fairness, trust/security). You can also run a confidential survey with an optional "OK to contact me" checkbox.
If response is lagging, use Dillman's Tailored Design Method as a guide to add a second channel (in-app + email, or sales link + email) without changing question meaning.
Next step: Pick one scenario above, then build three separate links: prospect, user, and churned.
Who Should Take It (and Why You Should Not Mix Segments)
Goal: Decide what to change next (messaging vs roadmap vs packaging/pricing).
Who: Split results by lifecycle (prospect vs user vs churned) and role (buyer vs end-user).
When/Where: Prospect after demo; user after first value moment; churned within days of cancellation.
Send to these three groups: (1) prospects who are actively evaluating, (2) active users/trialists, and (3) churned or recent drop-offs. You will get clearer decisions when each group has its own link or branch.
Do not mix segments in analysis. Prospects answer from expectations. Users answer from real friction. Churned users answer from broken promises and switching costs. If you average them together, you can hide onboarding pain or inflate demand.
Sampling rules that prevent bad decisions
- Ask a role question up front: "What is your role in choosing and using this product?" Keep options for buyer/decision-maker and end-user. You will see willingness-to-pay patterns by buyer role, while usability issues cluster by end-user role.
- Capture ICP fields you will actually cut by: company size, industry, job function, and primary use case. If you need help defining roles and segments, start from persona survey questions and keep only the fields you will use in charts.
- Plan minimum completes per cut: decide your required cells before launch (example: 50 prospects + 50 users + 30 churned, each split by buyer vs end-user). You can still act on smaller samples, but you should label results as directional.
Funnel-stage interpretation (avoid false comparisons)
- Top-of-funnel awareness: expect vague answers and higher "not sure" rates. Use it to pick language, not pricing.
- Mid-funnel evaluators: compare alternatives, switching blockers, and procurement constraints. Use it to decide positioning and requirements (integrations, compliance).
- Post-purchase users: focus on time-to-value, missing workflows, and reliability. Use it to pick what to ship next.
To keep perspective on participation, Pew's guidance on low response rates is a helpful reminder to focus on bias risk and who did not respond, not a single percentage.
Next step: Create three separate contact lists (prospect, user, churned) and block reporting until each is analyzed alone.
Customization Guide: Pick-Your-Path by Product Type (Keep Core Questions Stable)
| Product type | Keep constant (trend tracking) | Tailor (modules and wording) | Optional modules to turn on/off | Operator rules (keep data usable) |
|---|---|---|---|---|
| B2B SaaS | Core PMF signal, current alternative, top problem, open-ends ("biggest benefit" / "biggest blocker"). | Stakeholders (security, IT, finance), buying process, admin setup, integrations that gate activation. | Security/compliance; integrations; competitor comparison; churn/exit; pricing survey template module. | Mirror the words from sales calls and tickets. Avoid internal feature names. Collect only firmographics you will chart. |
| B2C app | Core PMF signal, usage frequency, alternatives, open-ends about value and friction. | Habit loop triggers, platform/device, notifications, onboarding steps, paid vs free experience. | Pricing; competitor comparison; churn/exit. | Keep scales consistent (same 5- or 7-point anchors each run). Add "not applicable" when a feature is not universal. |
| Marketplace | Core PMF signal, alternative, top outcomes, open-ends about trust and friction. | Two-sided roles (buyer vs seller), liquidity (availability), trust/safety, fees, dispute flow. | Pricing/fees; trust/safety; churn/exit; competitor comparison. | Do not blend both sides into one score. Keep buyer and seller branches separate from the first screen. |
| Services | Core PMF signal, alternative (agency/internal), expected outcomes, open-ends on experience gaps. | Scope definition, handoffs, communication cadence, delivery quality, success criteria. | Packaging/pricing; churn/exit; competitor comparison. | Ask about the last completed project, not "in general." You will get more accurate answers that way. |
Keep / Change / Add rules (so you can compare over time)
- Keep: the core questions stable across runs (PMF signal, alternatives, 2-3 open-ends). You need this for trending.
- Change: module wording to match the respondent's language. Do not use internal jargon.
- Add: only the modules you will analyze: pricing, security/compliance, integrations, churn/exit, competitor comparison.
If you are still unsure who you are building for, run a short market segmentation survey template before you run a full PMF diagnostic.
Next step: Pick one product type row, then lock your core question set before you add any modules.
How to Analyze Results (Turn Answers Into Decisions)
- Step 1: Clean the data before you look for patternsFlag low-quality completes (straight-lining, impossible completion times, nonsense open-ends). Remove them from charts, but keep a count. Do this next: set a minimum time threshold and review the first 20 open-ends manually.
- Step 2: Segment first, then score (ICP x lifecycle x role x use case)Cut results by ICP, lifecycle stage (prospect/user/churned), role (buyer vs end-user), and primary use case. Build a simple grid (example: SMB buyers vs SMB end-users vs enterprise buyers). Do this next: pick 3-5 segments you can actually act on this quarter.
- Step 3: Find the biggest opportunity with a 3-factor rankingRank problems and gaps by (1) severity, (2) frequency, and (3) dissatisfaction with current alternatives. The best targets show up when all three are high in the same segment. Do this next: pull the top 10 open-end themes and tag each theme with severity and frequency.
- Step 4: Prioritize fixes with Importance vs SatisfactionPlot each feature/workflow on an importance-vs-satisfaction matrix. Fix the high-importance / low-satisfaction items first. This is the classic importance-performance analysis approach in a product decision format. Do this next: choose 3 items in that quadrant and write one experiment per item.
- Step 5: Apply decision rules (message vs segment vs product vs pricing)Use clear triggers so you do not debate forever:
- Iterate messaging when buyers rate the problem as important, but your differentiation is unclear in open-ends.
- Refocus on a segment when one ICP has higher PMF signal and lower alternative satisfaction than others.
- Treat pricing as the blocker when value is clear, but buyers cite budget ownership, payback period, or package mismatch.
- Schedule interviews when one theme is a repeat driver of negative comments in a priority segment (internal starter target: about 20% of negative comments; adjust after your baseline).
- Step 6: Share results in three formats (so teams use them)Create (1) a 1-page exec summary with 3 decisions, (2) a product/design detail doc with top workflows and quotes, and (3) a sales objections library with the top 10 switching blockers by segment. Do this next: schedule a 30-minute readout and end it by choosing one roadmap bet.
Next step: Build your first dashboard cut as ICP x lifecycle stage, then re-run charts for buyer vs end-user.
Action Plan and Next Steps (2-Week and 6-Week Playbook)
2-week plan (fast fixes you can ship)
- Run a message test for your top segment: Rewrite your headline and value bullets using the exact words from open-ends. Re-test on prospects only.
- Fix one onboarding drop-off: Remove the #1 setup blocker (permissions, data import, invite flow). Validate with users and trialists.
- Remove one top friction point: Pick the highest-frequency complaint in your priority segment and ship a small change within 14 days.
6-week plan (bigger bets with clear pass/fail)
- Run one feature experiment: Build a thin version of the top high-importance / low-satisfaction gap and measure adoption in the target segment.
- Test packaging/pricing: If buyers cite budget, run a packaging test or a price fence test. Keep prospect, user, and churned reads separate.
- Ship a segment-specific landing page: Build one page per priority use case. Match proof and requirements (integrations, compliance) to that segment.
Follow-ups that make the survey actionable
- Invite interviews: Add a final checkbox: "OK to contact me for a 15-minute follow-up." Use it to validate the top 2 themes per segment.
- Pulse after changes: Re-run a short survey after shipping, but keep your core trend questions unchanged. Add only one module tied to the change.
- Retest cadence: Run quarterly, or after a major release that changes onboarding, pricing, or a core workflow.
- Response lift tactics: Use simple incentives and 1-2 reminders. A BMC review on incentives and follow-up for survey participation summarizes practical tactics that can increase participation.
- Go deeper on features: After you ship changes, switch to a product feedback survey template to collect feature-level input from the same segment.
Next step: Put three dates on the calendar now: launch day, reminder day, and the readout meeting.
Frequently Asked Questions
Should I run one survey for prospects, users, and churned users?
Run separate distributions (or at least separate branches) and analyze each group on its own. Lifecycle stage changes intent, expectations, and willingness to pay, so one blended score will mislead you. Keep the same core questions across groups, then add group-specific modules (onboarding for users, switching friction for prospects, exit reasons for churned).
When is the best time to send a product-market survey?
Send to prospects right after a clear concept demo or pricing page review. Send to users after onboarding plus a first value moment, so answers reflect real usage. Send to churned users within days of cancellation; too early gives opinions, and too late creates recall blur.
How many responses do I need for useful product decisions?
As an internal starter target for directional decisions, aim for 30-50 completes per lifecycle group (prospect, user, churned) and adjust after your baseline. For more confident comparisons, target 75-150 per key segment cell (example: SMB buyers vs enterprise buyers), then revise based on how stable your results look by segment. Decide your minimum completes per cell before you launch, or you will end up with unusable cuts.
Should responses be anonymous or identified?
Use identified responses when you need account context or follow-up interviews tied to firmographics. Use anonymous responses when feedback is sensitive (pricing fairness, trust/security concerns, dissatisfaction with an internal tool). A practical default is confidential responses plus an optional follow-up consent checkbox.
How do I avoid biased or leading PMF questions?
Write neutral prompts, use balanced answer choices, and avoid double-barreled items (two ideas in one question). Keep a stable core question set so you can trend results without moving the goalposts. Order the survey as: experience/context first, diagnostics next, overall fit/intent after, then open-ends.
What should I do if my PMF signal looks weak?
Diagnose before you pivot: if the problem is severe and frequent but differentiation is unclear, fix positioning and proof first. If importance is high but satisfaction is low, prioritize the top workflow gaps and onboarding friction. If willingness to pay is low, revisit packaging and target buyer, then run follow-up interviews in your highest-fit segment.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED