Voice Of Customer Synthesis

Voice of Customer Synthesis

When to use

Use this skill when you have raw customer input and need to turn it into useful product marketing judgment.

Good inputs include:

• Customer interview notes
• Sales call transcripts
• Win/loss notes
• Support tickets or community threads
• Customer advisory board notes
• Gong/Zoom summaries
• Survey verbatims
• Founder or sales-team anecdotes that need structure

Use it before positioning, messaging, launch planning, customer stories, sales narratives, website copy, or enablement. Voice of customer is the currency for PMM. Without it you have opinion. With it you can say, "I talked to 10 customers and here's what they said."

Inputs

Ask for or infer the following:

• Product or company context
• Target audience or segment
• Buyer, decision-maker, user, and influencer if known
• Raw customer notes, transcript excerpts, survey responses, sales notes, or research
• Business model, ACV, market, or GTM motion if relevant
• The desired downstream use: positioning, messaging, launch, sales enablement, customer story, or research synthesis

If the input is thin, still synthesize it, but label conclusions by confidence:

• High confidence: directly supported by multiple customer statements
• Medium confidence: supported by one clear statement or repeated pattern in weaker notes
• Low confidence: plausible inference that needs validation

Workflow

1. Separate customer truth from PMM interpretation

Do not blend quotes, facts, and strategy into one mush.

For each finding, distinguish:

• What the customer actually said
• What behavior or business reality it points to
• What PMM should infer from it
• What still needs validation

2. Identify the audience and buying roles

Clarify who is speaking and who matters in the deal.

Look for:

• End user pain
• Decision-maker pain
• Economic buyer concerns
• Admin or implementation concerns
• Champion language
• Procurement, security, IT, finance, or legal blockers

Do not assume the loudest user is the buyer. Do not assume the buyer is the daily user.

3. Extract the problem before the product

Start with fundamentals:

• Who is the target audience?
• What problem do they have?
• How do they solve it today?
• Why is the current way painful, risky, slow, expensive, or incomplete?
• What event makes the problem urgent now?
• How does the product solve it better?
• What value is created?
• How should GTM let the market know?

Do not jump straight to features.

4. Name the status quo

The real competition is often not another vendor. It is the make-do process customers already tolerate.

Look for current alternatives such as:

• Spreadsheets
• Email threads
• Manual handoffs
• Meetings
• Internal tools
• Consultants or agencies
• Doing nothing
• Waiting until the pain becomes urgent
• A partial tool used outside its intended job

Explain why the status quo persists. Common reasons: no owner, low urgency, switching cost, habit, budget timing, fear of implementation, or the pain is invisible until something breaks.

5. Capture the buyer trigger

Find the specific event that made the customer act.

Use this pattern:

• Situation: the old make-do process
• Trigger: the specific event that made them act
• Solution: how the product made the job better
• Result: the tangible outcome

Triggers can be reactive or proactive.

Reactive buyer moments:

• A failure, missed deadline, customer escalation, audit, outage, lost deal, cost spike, compliance issue, or executive complaint

Proactive buyer moments:

• New team, new market, new regulation, growth target, platform change, strategic initiative, budget cycle, or leadership mandate

6. Translate into Jobs To Be Done

Write jobs in plain buyer language.

Format:

• When [situation/trigger], I need to [job], so I can [desired outcome].

Separate:

• Functional job: the task they need done
• Emotional job: the anxiety, confidence, control, or peace of mind they seek
• Social job: how they need to be perceived by leadership, peers, customers, or their team

7. Pull exact language

Capture short, useful phrases customers actually used.

Prioritize language that is:

• Specific
• Emotional
• Repeated
• Plain-English
• A better alternative to internal jargon
• Close to how a buyer would describe the problem to a peer

Never polish a customer quote until it becomes generic marketing copy. Preserve the edge.

8. Identify objections and proof requirements

Extract what could stop the deal or weaken belief.

Look for objections around:

• Cost or budget
• Urgency
• Implementation effort
• Trust, risk, security, or compliance
• Integration fit
• Data quality
• Change management
• Executive buy-in
• Whether the pain is big enough to solve now

Map each objection to the proof needed:

• Customer proof
• Quantified outcome
• Demo moment
• Technical validation
• Security documentation
• ROI model
• Before/after workflow
• Executive narrative

9. Synthesize messaging implications

Turn the patterns into PMM direction.

Cover:

• Primary message
• Secondary messages
• What to stop saying
• What to say instead
• Best-fit audience
• Segment or persona nuance
• Proof points to gather
• Sales discovery questions
• Content or campaign angles
• Risks if the team overclaims

Messaging should come from customer reality, not clever copy.

Output format

Return a structured synthesis with these sections:

1. Executive summary

• 3-5 bullets on the strongest customer truths

1. Audience and buying roles

• User
• Decision-maker
• Economic buyer
• Champion
• Blockers or influencers
• Confidence level

1. Pains

• Pain
• Evidence from notes
• Business impact
• Confidence

1. Triggers

• Situation
• Trigger
• Reactive or proactive
• Why now
• Evidence

1. Current workaround / status quo

• What they do today
• Why it persists
• Where it breaks
• Real competition

1. Jobs To Be Done

• Functional job
• Emotional job
• Social job
• JTBD statement

1. Exact customer language

• Quote or phrase
• Who said it, if known
• Why it matters
• Potential use in messaging or sales

1. Objections and risks

• Objection
• Who holds it
• Why it matters
• Proof needed

1. Proof and outcomes

• Stated result
• Quantified proof, if available
• Anecdotal proof
• Proof gaps

1. Messaging implications

• Recommended message
• What to avoid
• Sales discovery questions
• Content, launch, or enablement angles
• Follow-up research needed

1. Unknowns and validation plan

• Unknown
• Why it matters
• How to validate it

Quality bar

A strong synthesis:

• Uses customer evidence, not PMM opinion, as the starting point
• Names the status quo clearly
• Distinguishes decision-maker pain from user pain
• Identifies the moment that made the customer act
• Shows whether the buyer is reactive or proactive
• Pulls exact language that sounds like a real person
• States what is known, inferred, and unknown
• Connects pains to business impact
• Connects objections to proof requirements
• Produces messaging implications a sales or marketing team could use immediately
• Avoids inventing claims, outcomes, or market patterns not supported by the input

Anti-patterns

Avoid:

• Writing generic SaaS messaging from thin evidence
• Treating every feature mention as a customer pain
• Ignoring the current workaround
• Assuming the competitor is only another vendor
• Confusing user enthusiasm with budget authority
• Turning quotes into sanitized marketing language
• Claiming ROI, savings, or business impact not present in the notes
• Averaging all personas into one vague buyer
• Hiding uncertainty
• Producing a summary that is interesting but not actionable for GTM

Related skills

• positioning-messaging-framework: Use after this synthesis to define positioning, messaging pillars, and reasons to believe.
• sales-narrative-deck: Use after positioning to turn customer truth into a first-call sales story.
• customer-story-engine: Planned future skill for turning strong before/after stories into reusable proof assets.
• launch-tier-framework: Planned future skill for using audience, narrative, and GTM priority to size launches.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: adam-lagerhausen
• Source: adam-lagerhausen/b2b-marketing-skills
• License: MIT

Install and usage instructions live in the source repository linked above.