Voice of customer research means collecting buyers' own words and turning them into copy. Here is the full process, run on 417 real complaints, with the codebook and the message map.
Voice of customer research is the process of collecting what buyers say in their own words, coding it into themes and using the exact phrases in your copy and product decisions. This page runs the whole process on one real dataset: 417 low-rated invoicing software reviews from the BigIdeasDB Capterra corpus, coded into nine themes and turned into a message map.
Voice of customer (VoC) research captures customers' wording about a problem, the result they want and the doubts that stop them buying. The top Google results for the head term treat it as a CX program: surveys, NPS, satisfaction scores and call-center analytics, often with Six Sigma examples. That is one meaning.
This page covers the copy and positioning meaning, which is what copywriters, CRO specialists and founders writing their own landing page need. The output is not a satisfaction score. It is a codebook of themes with counts, a bank of verbatim phrases and a message map that says which phrase goes into which headline.
It also differs from a review summary. Our customer review analysis guide covers how to count and rank themes in one review set, and the pain point analysis template covers severity and gaps. VoC for copy starts where those end: it keeps the customer's sentence intact and decides where that sentence goes on the page.
The method is not new, and practitioners say the effort pays off. One r/copywriting post describing a three-hour VoC process before writing any copy for a health brand drew 65 upvotes and 42 comments as of November 6, 2026. A separate r/copywriting thread asked what research to do beyond the obvious online sources.
The best tool stack for a founder or copywriter pairs a source of real customer wording with a place to code and count it. BigIdeasDB ranks first because it supplies the raw evidence: 1M+ complaints and reviews you can search by niche. The generalist tools below handle the analysis.
| Rank | Tool | Best for | Limit |
|---|---|---|---|
| 1 | BigIdeasDB | Hosted corpus of 1M+ complaints and reviews (Capterra, G2, Reddit, app stores) with niche scans, plus Desktop for collecting Reddit and review evidence on your own computer | Public sources only. It does not hold your support tickets or call recordings |
| 2 | ChatGPT | Coding quotes into themes and drafting message-map rows from quotes you paste in | Can paraphrase or invent quotes. Verify against the source |
| 3 | Claude | Reading long exports and labeling themes with a written codebook | Same limit: it only knows what you give it |
| 4 | A spreadsheet | Counting themes, de-duplicating, keeping source and date columns | Manual tagging is slow past a few hundred rows |
| 5 | Notion | Storing the quote bank and the message map where the team can see it | A notebook, not a collection tool |
Use at least three source types, because each one is biased differently. Public reviews are free and fast. Internal sources such as support tickets and sales calls are richer, because they come from people who already considered buying from you. In the r/copywriting research thread, one reply listed recorded sales calls, complaint emails, service tickets and staff interviews, and another said 3 or 4 solid sources were enough before laying out copy.
| Source | What you get | Bias to watch | Effort |
|---|---|---|---|
| Software and app reviews | Pros, cons, reasons for choosing, alternatives considered | Skews to the angry and the delighted. Reviewers are not all buyers | Low |
| Reddit and forums | Unprompted problem language, workarounds, price talk | Vocal minority. Thread context matters | Low to medium |
| Support tickets and complaint emails | Post-purchase friction in exact words | Only existing customers. Needs permission and redaction | Medium |
| Sales call recordings | Pre-purchase objections and the phrases that win | Rep-led wording can leak in | Medium to high |
| Customer interviews | Why, in depth. Confirms what counts suggest | Small n. Leading questions ruin it | High |
For public sources, our guides to mining Capterra reviews and finding customers on Reddit show the search moves. For interviews, start with the customer discovery questions. For the wider research frame, see market research for a startup and how to define your ideal customer profile.
The process has eight steps and fits in a day for a public-source pass. The worked example below follows steps 1 to 6 on real data.
We pulled the complaint side of one software category, Billing and Invoicing, from the BigIdeasDB Capterra data. The category holds 7,864 reviews. 897 are rated 3 stars or lower. After keeping reviews dated 2023 or later with at least 30 characters of "cons" text, 417 remained, dated January 4, 2023 to November 11, 2025.
Each review was coded with a keyword rule per theme and counted once per theme. The identical-text check removed none, so 417 stayed 417. Themes overlap: 105 reviews (25.2%) carry two or more.
Takeaway: support, reliability and learning curve together touch more reviews than any pricing or feature complaint, and the biggest single bar is not a missing feature.
| Theme | Rule (keyword family) | Reviews | Share of 417 |
|---|---|---|---|
| Support and service | customer service, support team, technical support, unresponsive, never answer | 81 | 19.4% |
| Bugs and reliability | bug, glitch, crash, freeze, lag, slow, error, not working | 68 | 16.3% |
| Learning curve | learning curve, complicated, confusing, clunky, not intuitive, hard to | 65 | 15.6% |
| Pricing and fees | expensive, costly, overpriced, fee, per user, hidden, price increase | 51 | 12.2% |
| Integrations and data | integrate, sync, QuickBooks, import, export | 40 | 9.6% |
| Payments and payouts | payment, processing, gateway, deposit, get paid | 36 | 8.6% |
| Reporting | report | 29 | 7.0% |
| Customization | customize, template, inflexible, limited, no option | 27 | 6.5% |
| Mobile | mobile, phone app, iOS, Android | 16 | 3.8% |
| Not coded | matched none of the rules above | 164 | 39.3% |
The rules are crude by design. A keyword match counts "limited features" as customization even when the reviewer meant something else. That is why step 6 says to read the leftovers and spot-check each theme before the numbers go on a slide.
We also searched our Reddit pain-point table for invoice and late-payment language. It returned 39 rows between October 2024 and October 2026, too few and too mixed (trucking logs, legal billing) to code, so the example uses review text only. A real project would add a forum and an internal source.
A message map links the customer's exact phrase to the objection behind it and to the line that answers it. Below, each of the top themes becomes a row for a hypothetical invoicing tool aimed at freelancers. The headlines are drafts to test, and each is only usable if the product genuinely does the thing.
| Theme (reviews) | Customer's words | Objection | Headline or bullet to test |
|---|---|---|---|
| Support (81) | “Terrible Customer Service and No Online Chat Support with Agents” | If it breaks on invoice day, nobody will answer | Ask a question in chat. A person replies the same day. |
| Reliability (68) | “it tends to freeze at times when using it” | It will fail when I need to send an invoice | Send the invoice once. It sends. |
| Learning curve (65) | “Steep learning curve” and “too clunky and not very user friendly” | I will lose a weekend learning it | Your first invoice is out in five minutes, no setup call. |
| Pricing (51) | “They changed their license structure in order to justify a 60% price increase” | The price jumps once I am locked in | The price you start on is the price you keep. It is on the page. |
| Payments (36) | “The slow payments. I was close to losing my place of living because the payments were so slow.” | Late money is my real problem, not the software | See when each invoice was opened and when it was paid. |
| Customization (27) | “Not being able to add a designed invoice was a deal breaker for me” | My invoices will look generic | Your logo and colors on every invoice. |
Three rules make the map useful. Keep the customer's sentence intact in the first column, because a paraphrase loses the emotional detail. Write the objection as a first-person thought, not a marketing phrase. And write the headline last, from the objection, not the quote, so it answers the doubt instead of repeating the complaint.
Not every row belongs on the page. The payments row is about money arriving late, which software alone may not fix. That tells a founder where the real product gap sits. To go from a theme to a build decision, see how to prioritize feature requests from customer reviews.
Complaint frequency is a testing list, not a roadmap. A theme with 81 mentions out of 417 tells you what some unhappy reviewers wrote. It does not tell you how many buyers weigh it, whether they would pay to fix it or whether your product avoids it.
BigIdeasDB Desktop is a local-first research app for Mac and Windows. It collects Reddit threads, app reviews and software reviews on your own machine and saves the evidence in local projects, and its Deep Research reports use counted findings and checked quotes. It uses the AI agent you already have for analysis.
Two honest limits. Desktop does not include the hosted BigIdeasDB dataset: the 1M+ complaints corpus lives in the hosted product. And when you send evidence to your own AI agent, that text leaves your device, so check that agent's data policy before you paste anything sensitive. Details are on the BigIdeasDB Desktop page, and the hosted side is covered in the complaint analysis guide and the Reddit market research guide.
If you write your own landing page, the free site teardown shows what reviewers complain about in your category. To run the same analysis on your niche, scan the invoicing software niche in BigIdeasDB and read the quotes behind each theme.
| Item | Detail | Limitation |
|---|---|---|
| Source | BigIdeasDB Capterra reviews, Billing and Invoicing category (7,864 reviews, 897 rated 3 stars or lower) | One platform. One category definition set by the source |
| Sample | 417 reviews rated 3 or lower, dated 2023-01-04 to 2025-11-11, cons text of 30+ characters | Excludes older and shorter reviews. Latest review in the data is November 2025 |
| De-duplication | One row per review ID, then one per identical cons text. No rows removed by the second rule | Near-duplicates with different wording survive |
| Coding | Keyword rules per theme, one count per review per theme, nine themes | Not hand-validated. Overlap means shares sum above 100% |
| Reddit cross-check | 39 matching rows in the Reddit pain-point table, October 2024 to October 2026 | Too few and too mixed to code |
| Queried | November 6, 2026, read-only SQL | Counts are a snapshot |
Run this on your own market. Pick a software niche and BigIdeasDB returns the complaints, feature gaps and exact customer wording behind it, so your message map starts from real sentences.
Voice of customer (VoC) research is the practice of collecting what customers say in their own words, from reviews, forums, support tickets, sales calls and interviews, then coding it into themes you can act on. For copywriters it supplies the exact phrases to use in headlines. In our worked example, 417 Capterra invoicing reviews produced 9 themes, led by support at 19.4%.
Pick one audience and one question, collect 100 to 400 raw customer quotes from three or more source types, de-duplicate them, code each quote into themes, count the themes, then write a message map from the top themes. Finish by interviewing 7 to 10 customers to confirm. The worked example above followed these steps on 417 reviews, dated November 6, 2026.
BigIdeasDB is the best starting point for founders, because it holds 1M+ real complaints and reviews from Capterra, G2, Reddit and app stores, so you can pull exact customer wording for a niche in minutes. BigIdeasDB Desktop adds local collection of Reddit and review evidence. ChatGPT, Claude and a spreadsheet then handle coding and counting.
In copywriting, voice of customer means using the words your buyers actually use to describe their problem, the outcome they want and what makes them hesitate. You collect those phrases from reviews, forums and calls, then place them in headlines, bullets and objection handling. The goal is copy that reads like the buyer's own thought, not like your product description.
Start with public reviews of the category (Capterra, G2, app stores), then Reddit and forum threads, then your own support tickets, sales call recordings and complaint emails. Public sources are free and fast. Internal sources are richer, because they come from people who already considered buying from you. A good brief uses at least three source types.
There is no fixed number, but a few hundred is a workable floor for counting themes. Our example coded 417 low-rated reviews and 39% still fell outside the nine themes, so we kept reading. Code until new quotes stop producing new themes, then interview 7 to 10 customers, the range one r/copywriting commenter suggested, to confirm what the counts imply.
Not quite. In Six Sigma, VoC turns customer requirements into measurable specifications called critical-to-quality (CTQ) targets for a process. VoC for copy and positioning is about wording and objections instead: which phrases buyers use, which problems they rank first, and which doubts stop a purchase. The collection methods overlap, but the output is a message map, not a quality spec.
The best way is a message map: customer phrase, the objection behind it, then the headline or bullet that answers it. BigIdeasDB gives the raw phrases and theme counts for a niche from 1M+ complaints, and you write one map row per top theme. Only promise what your product actually does, then test the headlines.
ChatGPT or Claude can help you code quotes into themes and draft message-map rows, but they cannot supply real customer evidence on their own, and they can paraphrase or invent quotes. Feed the model quotes you collected, keep the source and date for each, and check every quote against the original before it goes into copy.
BigIdeasDB Research. (2026). Voice of Customer Research: A Worked Example With Real Data. BigIdeasDB. Retrieved from https://bigideasdb.com/voice-of-customer-research