Skip to main content
← Voice of Customer (full guide)
Spoke · 90-day roadmap · 7 min read

VoC program setup — 90-day roadmap

Five phases over 90 days, with specific items per phase and the milestone that signals you\'re ready for the next one. Designed for founders and small teams without enterprise budget.

The trap most VoC programs fall into: trying to do everything in week 1. Real programs ramp progressively — foundation, then passive listening, then active research, then the first shipped action. Each phase has a milestone you can\'t fake.

Days 1–7

Foundation

  • Name the owner. One person, no shared accountability.
  • Pick the primary metric (NPS, CSAT, or CES) — just one.
  • Document the 1-page program charter: who, what, when, why.
  • Get sign-off from the leader who controls product roadmap (so feedback can drive change).

Milestone:Charter signed. One owner named. Primary metric chosen.

Days 8–21

Passive listening setup

  • Audit existing channels: support tickets, app reviews, social mentions, sales call recordings.
  • Define the tag taxonomy (10-15 tags max — start small).
  • Set up channel ownership: who reads which channel, with what cadence.
  • Stand up the action log spreadsheet (every piece of acted-on feedback gets one row).

Milestone:Every customer-touch channel has a named owner + a tag taxonomy. Action log empty but ready.

Days 22–42

First survey + first interviews

  • Send the first NPS / CSAT / CES survey (whichever you picked as primary).
  • Recruit + run first 5 customer interviews.
  • Read every response within 7 days. Tag everything.
  • Identify top 3 themes from the combined survey + interview signal.

Milestone:First themes identified from real signal. Action log starts filling with specific items.

Days 43–63

First action shipped

  • Pick ONE theme from the top 3 that has the strongest signal + lowest cost.
  • Ship the change. Even small — fixing a confusing onboarding screen counts.
  • Send loop-closure email to customers who raised the original theme.
  • Document the case study: theme → action → result → learning.

Milestone:First customer-driven change shipped. First loop-closure emails sent. First case study written.

Days 64–90

Cadence + scaling

  • Establish weekly synthesis review (30 min, output is decisions not data).
  • Run second cohort of 5 interviews to validate themes are persistent, not noise.
  • Add second survey channel (e.g., add CES on top of NPS) once first is stable.
  • Calendar quarterly executive briefing — VoC owner presents themes + actions to leadership.

Milestone:Weekly cadence sustainable. Themes validated across 2+ cohorts. Leadership engaged. Program shifts from setup to operations.

Common failure modes

❌ Skipping Days 1-7 because "we already know our customers"

Without a written charter, ownership drifts — by Day 30, no one knows who reads NPS responses. Invest the week. The discipline of writing it down filters out half the things you thought you wanted to track.

❌ Buying enterprise tools before manual program works

Qualtrics + Medallia rescue no bad programs. They accelerate good ones. Until you have a working tag taxonomy + weekly synthesis cadence on free tools, more sophisticated tools just hide the same dysfunction.

❌ Adding too many surveys at once

First survey → tag responses → close loop → THEN add second survey. Stacking 4 surveys in week 1 produces survey fatigue + low response rate before you ever see real signal.

❌ Not shipping anything in first 60 days

If the first 60 days produce no shipped customer-driven change, the program will quietly die. Even a tiny visible change (loading-state copy fixed because customers complained) signals to the team that VoC moves the product.

Start Day 1 with hypothesis clarity

Days 1-7 require knowing which customer voice matters most — that\'s where most teams stumble. We built GoNoGo as the prep — a 30-min voice session that maps your customer hypothesis + runs synthetic personas + tells you which segments to listen to first.

Map your starting point free →

30 min · No credit card

Frequently asked questions

Can a small team really set up VoC in 90 days?+
A working program, yes. A mature program (all 4 layers, full integration into operating decisions), no — that takes 12-18 months. The 90-day plan focuses on Layer 1 + Layer 2 (passive listening + active research) with enough discipline that Layer 4 (closing the loop) starts emerging organically. Layer 3 (co-creation) can wait until you have stable signal.
Who should own VoC at a startup?+
Ideally a Product Manager who controls roadmap. Marketing-owned VoC tends to optimize for brand metrics (NPS for the website). Customer-Success-owned VoC tends to over-rotate on retention complaints. Product-owned VoC drives the changes that move all the metrics. At a 5-10 person startup, the founder usually owns it directly.
How much should this cost?+
For 90-day setup at a small team: $50-300/month total tooling. Tally or Typeform (surveys) + Otter (transcription) + Notion (synthesis) covers most needs. Don't spend on Qualtrics or Medallia until you have a working manual program — enterprise platforms accelerate good programs but rescue no bad programs.

More on this topic