What a Monthly Voice-of-Customer Brief Should Include
The brief should show what changed in customer evidence, where the evidence is limited, and which marketing decisions now deserve action.
A monthly voice-of-customer brief should not be a folder of quotes with an executive summary attached. It should tell the company what changed in customer evidence, how sure the team is, and which marketing decision now deserves attention.
The month is a review window. It is not the subject of the brief. A strong brief carries forward persistent evidence, marks what is new or declining, and closes the loop on decisions from the prior review.
Open With the Decisions the Evidence May Change
Lead with the few findings that can change current work. Name the affected decision, page, campaign, proof asset, or sales material. State whether the brief recommends a change, a test, more research, or no action.
Do not lead with source volume. The company does not need a count of calls before it knows why the evidence matters. Coverage belongs immediately after the decision summary so readers can judge how much confidence the brief has earned.
The executive section should still make sense if a reader stops there. Each finding links to the exact evidence and the detailed section below.
Declare the Evidence Window and Source Coverage
State the start and end of the review window, the sources expected, what was actually available, and any lag or missing periods. Separate new evidence from older records carried forward for comparison.
A brief built from discovery calls alone cannot speak for support experience or churn. A brief missing one segment cannot silently generalize to it. Coverage is part of the finding, not a footnote.
Keep record counts and independent account counts separate. Report known duplication or dependence across calls, tickets, renewal notes, and churn records.
Show What Changed Since the Prior Brief
The most useful section is the delta. Mark signals as new, strengthening, stable, declining, contradicted, or reclassified. Explain whether the evidence changed, the product changed, or the classification rule changed.
A lifetime total hides movement. A concern can remain common while its language shifts. A competitor can appear more often because the company entered a new segment. A proof request can decline after sales starts using a new asset without proving the asset caused the change.
Keep the prior state and the reason for the update. The reader should be able to distinguish market movement from a rewritten taxonomy.
Summarize Objections as Current Decision Barriers
Use the objection feed as the source, then select only the objection changes that matter to marketing now.
For each included objection, state the buyer decision blocked, current state, segment and time boundary, independent account count, exact language, counter-signals, response used, and affected asset. Link back to the underlying passages.
A monthly brief should not repeat the entire feed. It explains why one objection now deserves a page change while another remains under observation.
Keep Churn Evidence Separate From Churn Risk
Confirmed churn reasons come from attributable exit evidence. Churn risk may come from support friction, adoption behavior, renewal language, or an unresolved expectation. They are not interchangeable.
Label the evidence state. State whether the record describes a completed churn event, a customer concern, an internal prediction, or a hypothesis under review. Include segment, tenure or lifecycle stage where relevant, and contrary evidence from customers who stayed.
Marketing may need to correct expectation-setting, strengthen onboarding proof, narrow a claim, or leave the message alone because the issue belongs to product delivery. The brief should make that boundary visible.
Preserve Buyer Language That Changed Meaning
Do not fill this section with memorable quotes. Choose passages that reveal a new frame, a material wording shift, or a condition that changes how the company should describe the problem.
Keep the exact passage and surrounding context. Explain how current language differs from the website, campaign, sales response, or prior brief. Link to the original evidence so the interpretation can be checked.
Separate language worth testing from a claim that the market has changed. The first can come from a smaller evidence set. The second needs broader support.
Report Competitor Mentions by Decision Context
A competitor leaderboard tells marketing who appeared. It does not explain why the buyer brought them into the decision.
Group mentions by role: incumbent, shortlist option, internal benchmark, pricing anchor, feature comparison, or perceived category leader. Preserve the buyer's reason and the stage where the comparison mattered.
Distinguish prompted mentions from unprompted ones. Record whether the competitor changed the evaluation or merely appeared in background context. Recommend work only when the comparison exposes a decision the company can influence.
Connect Proof Requests to the Claim They Challenge
"Send a case study" is incomplete. Record which claim the buyer could not accept without proof.
The request may concern implementation time, security, economic value, integration depth, or adoption. Name the live claim, proof available, proof used, and gap. A missing proof asset and a hard-to-find proof asset require different action.
Keep public proof separate from restricted customer evidence. Internal support may justify a recommendation without giving marketing permission to publish the source.
Write Every Finding as Evidence Plus Consequence
A finding needs a clear statement, essential facts, scope, counterevidence, and the consequence for a real decision. Quotes illustrate the evidence. They do not replace the finding.
GOV.UK's research analysis guidance separates exact observations from interpretation, then turns agreed findings into actions. That sequence is useful here. The monthly brief should preserve the observation, state what the team believes it means, and show the decision that follows.
Keep confidence language tied to evidence. Do not use a score that hides missing sources, dependence, or disagreement.
Recommend Work With an Owner and Review State
A recommendation should name the affected object, proposed change, owner, evidence, and review state. State what would happen next if the recommendation is approved.
Separate factual corrections from message tests. A verified product fact may justify an immediate correction. A broader positioning interpretation may deserve a focused test or another evidence window.
Use the signal-to-action record to carry the reason through execution and return the result.
Include Open Questions and Coverage Gaps
A credible brief says what it could not determine.
List missing sources, thin segments, unresolved contradictions, stale product facts, and research questions that block a broader conclusion. Name the owner of the missing input where one exists.
Do not turn uncertainty into a generic disclaimer. Tie each gap to the decision it limits and the evidence that would resolve it.
Close the Loop on the Prior Brief
Start a decision log when the brief is reviewed. Keep the finding, decision, owner, affected work, status, and returned result. If the company chose no action, record why.
The next brief begins with this log. It can show which recommendations changed work, which remained blocked, and which interpretations weakened after new evidence arrived.
GOV.UK's guidance on sharing research findings says findings should help teams make design decisions and prioritize work. It recommends a clear headline, essential facts, importance or consequences, and relevant evidence. The monthly brief should meet that standard and add the operating record needed to follow the decision afterward.
Use a Fixed Skeleton and Variable Findings
Keep the structure stable so changes become easier to spot. Keep the findings selective so the brief does not become an archive.
Northstar's Listening Engine maintains the source-linked evidence, current classifications, and changes over time. The Glass Dashboard assembles the decision summary, coverage, findings, actions, and prior outcomes into one review surface.
The brief succeeds when the company can decide what to change and explain exactly why. Everything else belongs in the evidence system behind it.
Frequently asked questions
What is a monthly voice-of-customer brief?
A monthly voice-of-customer brief is a source-linked decision document that explains what changed in customer evidence during a defined period, what remains uncertain, and which marketing decisions or assets should be reviewed.
What sections should a voice-of-customer brief include?
Include the evidence window and source coverage, changes since the prior brief, objections, churn evidence, buyer language shifts, competitor mentions, proof requests, recommended actions, open questions, and the status of prior decisions.
How long should a monthly voice-of-customer brief be?
Use the shortest format that preserves the decision-grade findings and their evidence. The brief should exclude raw material that does not change a decision and link readers to the full source records.
Should every customer quote appear in the brief?
No. Include exact passages that help a reviewer understand a material finding or counter-signal. Keep the full evidence in the source record and provide stable links from the brief.
How should churn signals be presented?
Separate confirmed churn reasons from risk indicators, support friction, and hypotheses. State the source, affected segment, time window, contrary evidence, and the decision the signal may change.
Should the brief recommend marketing actions?
Yes, when the evidence supports a specific next step. Name the affected asset or decision, owner, proposed change, review state, and evidence that would confirm or reject the recommendation.
How does Northstar Stack produce a voice-of-customer brief?
The Listening Engine maintains source-linked evidence across customer and company records. The Glass Dashboard assembles current changes, evidence limits, recommendations, owners, and prior outcomes into a reviewable brief.
Work with Northstar Stack
Start with the Marketing Information Flow Diagnostic. Leave a work email and we will follow up with the right next step.