Voice of customer research is the most direct route to messaging that actually resonates. When you put your customers' own words into your positioning, value propositions, and sales conversations, buyers recognise themselves and believe you faster. Most B2B SaaS teams understand this in theory. In practice, many rely on intuition, support ticket patterns, and occasional informal conversations instead of a systematic research process.
This voice of customer research template gives you the structure to gather, organise, and activate customer insights in a way that changes how your team writes copy, builds messaging, and positions the product.
What Voice of Customer Research Is and Is Not
Voice of customer (VoC) research is the systematic collection of customer language, motivations, and perceptions about their problems and your product. It is distinct from product feedback (which focuses on features and bugs) and satisfaction surveys (which measure sentiment). VoC research is specifically about understanding how customers describe their situation — the language they use before, during, and after using your product.
The primary outputs of VoC research are: the phrases customers use to describe their problem in their own words, the outcomes they were trying to achieve when they chose your product, the alternatives they considered and why they rejected them, and the specific moments when they realised the product was delivering value. These outputs become the raw material for positioning, messaging, and copy across the entire customer journey.
Research Methods: Choosing the Right Approach
Find Out Where You Stand
Take the PMM Strategic Maturity Assessment to benchmark your product marketing capabilities against best practices and identify your next growth opportunities.
Start the Assessment →There are four primary methods for gathering voice of customer data in B2B SaaS. Each has different strengths and is suited to different research questions.
Customer interviews
One-to-one conversations with customers or recent buyers. This is the highest-quality method for understanding nuance, context, and the emotional dimension of customer decisions. A 30-minute interview with a recent customer typically produces more usable messaging insight than a hundred survey responses.
Target eight to twelve interviews for an initial VoC research project. Focus on recent buyers who made an active decision to choose your product over an alternative — their memory of the evaluation process is fresh, and they can articulate the decision criteria clearly. Also include two or three customers who have been using the product long enough to have experienced meaningful value — they can describe outcomes in specific terms that are useful for case study development and proof point creation.
Survey research
Structured questionnaires sent to a larger group of customers. Surveys are better for quantifying patterns — what percentage of customers describe the pain in a particular way, or rank your product highly on a specific dimension — but weaker for capturing the language and nuance that make messaging resonate.
Use surveys to validate hypotheses generated through interviews, not as a replacement for them. A well-designed survey can tell you that seven out of ten customers cite "implementation speed" as a key purchase driver. An interview tells you that what they actually mean by "implementation speed" is "not having to involve IT."
Review and community mining
Systematic review of G2, Capterra, Trustpilot, and community forums (LinkedIn groups, Slack communities, Reddit threads) where your ICP discusses their problems. This method is particularly useful for understanding the language buyers use before they even know your product exists — the words they use to describe the problem in their own natural habitat.
When mining reviews, look for patterns in: what problems buyers describe in the positive reviews (they are telling you why they bought), what problems appear in neutral or negative reviews (they are telling you where expectations were not met), and how buyers describe the alternative they replaced (they are giving you competitive positioning ammunition).
Win/loss interviews
Conversations with recent buyers — both those who chose you and those who chose a competitor. Win interviews reveal why your positioning and value proposition resonated. Loss interviews reveal where your messaging failed, where competitors had a stronger story, and what buyer needs you are not addressing. The win/loss interview framework covers this method in detail.
The VoC Research Template: Interview Guide
Use this question guide for customer interviews. The questions are designed to surface natural language, emotional context, and specific decision-making moments.
Opening (set context):
- "Can you tell me a bit about your role and what your team is responsible for?"
- "When did you start using [product] and what prompted the search?"
Problem phase (understand the before state):
- "What was happening that made you start looking for a solution?"
- "How were you handling [problem area] before?"
- "What was the impact of that approach on you personally and on the team?"
Evaluation phase (understand the decision process):
- "What did you look at besides [product]? What did you think of those alternatives?"
- "What made you decide to go with [product]?"
- "Was there anything that almost made you choose a different option?"
Value phase (capture outcomes):
- "What is different now compared to before you started using [product]?"
- "Can you give me a specific example of when the product made a real difference?"
- "How would you describe [product] to a colleague who was facing a similar problem?"
Closing (capture language and advocacy):
- "Is there anything about how we describe [product] publicly that does not match your actual experience?"
- "If you were recommending [product] to someone similar to you, what would you tell them?"
Note: the last question in the closing section is especially valuable. The words a customer uses to recommend your product to a peer are the most credible form of your value proposition — they are the real version, filtered through actual experience.
Organising and Analysing VoC Data
Raw VoC data — interview notes, survey responses, review excerpts — has no value until it is organised and analysed. Use this process to turn data into actionable insights.
Tagging and categorising responses
After each interview, tag the transcript or notes with themes. Common themes in B2B SaaS VoC research: problem description language, named alternatives, purchase triggers, perceived benefits, friction points, and advocacy language. Build a shared tagging taxonomy before you start research so that responses are comparable across interviews.
Frequency analysis
Count the frequency of specific phrases or themes across your research corpus. If seven of ten interviewed customers mention "saving time" but five of those specifically say "without involving IT," the specific phrase is more useful than the general theme. Pattern frequency tells you which insights are reliable signals versus individual noise.
Jobs-to-be-done mapping
Organise insights around the jobs customers were trying to get done when they chose your product — not the features they used, but the outcomes they were pursuing. A customer who says "I needed a way to run our quarterly business reviews without spending a week pulling reports" is describing a job-to-be-done. The job is the brief for your messaging. Use the customer research guide for the full framework on jobs-to-be-done analysis.
Activating VoC Insights Across GTM
VoC research is only complete when the insights change something about how the team works. Document the activation plan alongside the research outputs.
Messaging and copy
Take the most frequently cited problem descriptions and integrate them directly into headline copy, email subject lines, and ad creative. Buyer language is almost always more compelling than product language. "Stop spending four hours on weekly reporting" beats "Automate your analytics workflow" — if that is how customers actually describe the problem.
Sales enablement
Package the most compelling customer quotes and outcome stories into a VoC library that Sales can access during discovery calls, proposal writing, and competitive situations. A well-placed customer quote from a peer company is often more persuasive than any product capability claim.
Positioning updates
Compare your current positioning statement against the language that emerged from VoC research. If customers consistently describe the value in terms that do not appear in your positioning, update the positioning to reflect what buyers actually believe — not just what the product team wants them to believe. Connect insights to the voice of customer framework and the VoC analysis framework to build a complete research system.
Building a Continuous VoC Research Practice
One-off VoC research projects produce insights that go stale. The most effective teams build a lightweight, continuous research practice that generates fresh customer language quarterly.
A minimal continuous VoC process: four customer interviews per quarter, one win interview and one loss interview per month, and a quarterly review of new G2 reviews and relevant community discussions. This takes roughly two to three hours of PMM time per week and produces a compounding body of insight that keeps messaging current with how customers actually talk.
Schedule the interviews — do not rely on finding time organically. Block time in the calendar at the start of each quarter for four research sessions. Send the interview requests in advance. Compensate customers with a small gift card where appropriate. The insight you generate is worth many times the investment of time and resources.
Common VoC Research Mistakes in B2B SaaS
Voice of customer research is easy to do badly. These are the patterns that produce data that looks rigorous but produces insights that do not change anything.
Asking leading questions
Leading questions confirm what you already believe rather than uncovering what is true. "Do you agree that our product is easy to use?" is not VoC research — it is validation-seeking. "Can you walk me through the last time you used the product to solve a real problem?" is research. The difference is in who controls the narrative: your assumptions or the customer's experience.
In every interview, prioritise open-ended questions that begin with "tell me about," "walk me through," and "what happened when." These questions force the respondent to narrate rather than evaluate, and narration produces the specific, evocative language that makes great copy.
Only talking to happy customers
Customers who agree to interviews are disproportionately likely to be advocates. Their language is valuable — but it tells you why the product works for its best-fit buyers, not why it fails for everyone else. Balance your research sample to include at least two or three customers who churned, downgraded, or struggled to find value. Their language tells you where your messaging promises things the product does not deliver, and where the product is leaving value on the table that marketing is not communicating.
Treating VoC as a PMM-only activity
The most effective VoC programs involve Sales, Customer Success, and sometimes Product in the research process. Sales hears buyer language in discovery calls every day — systematically capturing that language and routing it to PMM is a VoC program that costs almost nothing and produces continuous signal. CS hears customer language in every QBR and support interaction — a simple process for flagging notable language creates a real-time feed of how customer perception evolves after purchase.
PMM should own the VoC research program, but they should not be the only people generating data. Embed light-touch data collection into the workflows of every customer-facing team and route the outputs to a central research repository.
The VoC Research to Messaging Pipeline
The pipeline from VoC research to live messaging has four stages, each of which is a potential failure point. Understanding the pipeline helps you build processes that prevent insights from dying between collection and activation.
Stage 1: Collection
Customer language gathered through interviews, surveys, reviews, and community mining. The quality of this stage depends on interview guide quality, sample diversity, and the discipline to ask follow-up questions when a customer says something interesting and unexpected.
Stage 2: Analysis
Tagging, categorising, and finding patterns in the raw data. The quality of this stage depends on the tagging taxonomy you use and your ability to distinguish high-signal language (specific, evocative, and repeated across multiple sources) from low-signal language (vague, polite, and individual).
Stage 3: Synthesis
Translating patterns into messaging hypotheses. This stage requires judgment: which insights are significant enough to change the positioning, which should inform specific copy improvements, and which are interesting background data that does not change anything actionable. The synthesis stage is where most VoC research goes wrong — teams either over-index on single quotes without pattern validation, or under-index on genuine insights because they conflict with existing positioning.
Stage 4: Activation
Getting the new language into the places where it has impact: homepage copy, sales talk tracks, email subject lines, ad creative, and onboarding flows. This stage requires a clear process for updating existing assets and communicating changes to the teams who use them. A messaging update that lives in a PMM document but never gets to the Sales team's discovery call script has zero commercial impact.
Build the pipeline explicitly. Define who owns each stage, what the output looks like, and how changes get communicated. Review the pipeline quarterly to identify where insights are stalling before they reach activation. The VoC analysis framework provides the analytical structure for stages two and three of this pipeline.
VoC Research Across the Customer Lifecycle
Most VoC research focuses on the purchase decision: why did buyers choose us, what were they trying to achieve, what alternatives did they consider? This is the most commercially important research question, but it is not the only one.
Research at different stages of the customer lifecycle produces different insights. Pre-purchase research reveals the language of problem recognition and solution evaluation — the most useful for acquisition messaging. Onboarding research reveals where customers struggle to reach first value — useful for product and CS decisions. Post-value research (customers who have been using the product for three to six months and are seeing results) reveals the language of outcomes and advocacy — the most useful for case study development and referral programs. Renewal and churn research reveals the conditions under which customers decide the product is or is not worth continuing — the most useful for retention messaging and product prioritisation.
A mature VoC program has research touchpoints across all four stages and connects the insights to different parts of the go-to-market function: acquisition messaging, onboarding design, expansion conversations, and renewal strategy.