voice-of-customer-loop

$npx mdskill add Significant-Gravitas/skills-catalog/voice-of-customer-loop

Use this when field feedback needs to reach product. Start from the feedback with its source (call quote, lost-deal note, support thread, QBR), the account and deal behind it, and how often it has come up.

SKILL.md

.github/skills/voice-of-customer-loopView on GitHub ↗
---
name: "voice-of-customer-loop"
description: "Use when field feedback needs to reach product: feature asks, churn reasons, competitive losses, and deal-blocker patterns."
triggers: ["voice of customer", "feature request", "win-loss", "churn reason", "product feedback", "lost deal", "feedback log"]
version: "1"
---

# Voice of customer loop

Use this when field feedback needs to reach product. Start from the
feedback with its source (call quote, lost-deal note, support thread,
QBR), the account and deal behind it, and how often it has come up.

## Log once

Log each item once: what the customer said (quoted, never paraphrased into
more), who said it and where, the revenue attached with its source, and
how many accounts have said it. Dedupe on the underlying ask, not the
wording.

## Grade the pattern

Grade the pattern weekly: frequency, revenue weight, and whether it blocks
deals, churns accounts, or just annoys. A pattern needs three-plus
accounts or one named churn risk before it goes to product.

## Product brief

Write the product brief in one page: the pattern, the three best quotes,
the revenue math with sources, the competitive angle when one exists, and
the ask (roadmap, workaround, or positioning). Close the loop back to the
field: what product said, and what the rep tells the account.

## Win-loss program

Run the win-loss interview program on closed deals: a neutral interviewer
(never the owning rep), 15-20 minutes, open-ended what and why questions
across product, sales experience, pricing and packaging, competition,
committee, implementation, and timeline, sampled half wins and half losses.
A win-loss pattern needs triangulated buyer-plus-seller-plus-CRM evidence
across 3-plus deals before it changes a playbook, battlecard, or roadmap
call.

## What you hand back

The deduped feedback log plus the one-page product brief, saved to file.
Put the brief in chat first, fold in one round of their changes, and then
write it to the feedback log.

## Fallbacks

A single-account ask with no pattern means you log it and say it stays in
the log until it repeats. Feedback with no source means UNKNOWN until
someone names the call or thread. The brief to product and any promise
back to the account wait for your yes.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.