Voice of the customer for a small team

Voice of the customer is what your customers tell you about what they expect, prefer and dislike. ¹ For a team of one to five people, using it means three small routines and one person who owns them, with no platform needed.

This guide explains what the term covers, whether you need a "program" at all, and a four-week plan to start. It includes a worked example of reading 60 comments.

What voice of the customer means

The term has two halves: customers' words, and a way to use them. One common description says voice of the customer summarizes customers' expectations, preferences and dislikes. ¹ The collecting and acting is what makes it a habit.

One simple way to group where the words come from (this grouping is ours, not a standard):

The direct and indirect rows are where a small team gets the most for the least work. Inferred data tells you what happened, but rarely why. Cancellations are one example, and the customer churn guide shows how to count them.

A program, or just a habit?

Large companies run voice of the customer programs with analysts, dashboards and a budget. If you have a few hundred customers, you do not need that. You need a habit that survives a busy month.

A habit is enough when one person can read every comment. A program starts to make sense when nobody can read them all, or when several teams need the same data. Until then, a tool you do not have time to use is worse than a spreadsheet you open every Friday.

The minimum program: score, moment, review, owner

The plan below has four parts. Each is small on purpose.

1. One score. Pick one relationship survey and send it on a schedule, for example an NPS survey once a quarter. It gives you a trend and a comment from each person who answers. Leave the cadence alone once you choose it.
2. One moment. Pick one event that is worth a question, such as a solved support ticket or a first paid invoice, and send a short survey a little after it. Rules for timing and wording are in how to ask for feedback without annoying people, so this post does not repeat them. Wording for each moment is in customer satisfaction survey questions to ask.
3. One review. Block 30 minutes every week. Read the new comments, add support tickets and replies that mention the same thing, and tag each one with a theme.
4. One owner. Name one person. If the review belongs to everyone, it will not happen.

A four-week plan to start:

1. Week 1. Choose the owner. Write down the one score and the one moment. Make a sheet with columns for date, person, source, comment and theme.
2. Week 2. Send the first event survey. Add the last 30 days of support tickets to the sheet by hand.
3. Week 3. Hold your first 30-minute review. Pick the one theme to act on and write down who will do what.
4. Week 4. Send the first relationship survey. At the second review, check whether the theme from week 3 appears less often.

If you use Pulseri, the event survey can start when Stripe or Zendesk sends an event, and relationship surveys wait a set number of days per person, 90 by default. You can read more on the customer feedback surveys page. If you are a SaaS founder, the same steps are laid out for your setup on the SaaS founders page.

A worked example: 60 comments

Made-up example: after six weeks, a ten-person software company has 60 comments from surveys and support tickets. The owner reads each one and gives it one theme. The counts:

Setup is the biggest theme by a wide margin. The team picks setup for the next four weeks and leaves the export request on a list.

The counts are not a measure of how much each problem costs you. Twenty-one setup comments may come from new customers who stayed, and three export comments may come from your largest account. Counts tell you what to look at first. They do not decide for you.

Reading small numbers: pattern or anecdote?

With 60 comments, one or two mentions can feel like a trend. This is a rule of thumb, not a statistic:

• A theme is a pattern when it appears in at least five comments from at least three different people, and it has come up in more than one week.
• A theme is an anecdote when it comes from one person, however loudly, or from one moment such as an outage.
• Anything in between goes on a "watch" list for next month.

Read the comments in their original words before you count them. Two comments on the same theme can describe different problems. Questions that draw out more useful answers are in open-ended survey questions with examples.

Close the loop with the person who answered

Reply to people who left a comment, even if the reply is two lines. Say what you heard, whether you will change it, and when. If you will not change it, say that too, with the reason.

Replying shows people that the survey leads somewhere. It also gives you a chance to ask one follow-up question. For a low score that needs an answer the same day, see turning detractors into a Slack alert.

When to move to a tool

A spreadsheet works until the weekly review takes more than 30 minutes or you cannot tag comments consistently. At that point a tool helps with three jobs: sending surveys at the right moment, alerting someone when a score is low, and tagging comments.

Pulseri can send low-score alerts to Slack or Microsoft Teams. Its AI tags comment sentiment and themes and writes a weekly digest. The owner and the weekly review stay. The tool gets you the same list faster. Pricing depends on how many people you track, not on how many answer; see the pricing page.

For next steps and more guides, see the resources hub.