메뉴
Turn customer notes, call transcripts, sales feedback, and research into PMM-ready voice-of-customer inputs: pains, triggers, status quo, JTBD, exact language, objections, proof, and messaging implications.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".
Scrapes case studies, testimonials, and solutions pages from a target website to build structured ICP documentation. Produces TAM analysis, firmographic segments, champion and economic buyer personas, use case mapping, customer proof points, and voice-of-customer synthesis with normalized attributes. Requires website URL as primary input. Upstream: recommended company-context. Downstream: feeds positioning, product-messaging, landing-page-copy, content-strategy, and outreach-emails.
Classify product launches into defensible tiers and turn roadmap inputs into a season-of-launch plan that aligns Product, Campaigns, PR/AR, Sales, and customer-facing teams.
Create sharp B2B positioning and messaging from customer truth, segmentation choices, real alternatives, differentiated value, and proof.
Win/loss analysis for B2B SaaS. Analyzes sales call transcripts across 6 dimensions (product, messaging, GTM/sales, pricing, competition, customer context) to extract why deals are won, lost, retained, or churned. Produces aggregate patterns with verbatim-quote evidence, frequency counts, confidence levels, and strategic recommendations. Includes process steps, output template, quality checklist, extraction patterns, and a worked 5-transcript example.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
| name | voice-of-customer-synthesis |
| description | Turn customer notes, call transcripts, sales feedback, and research into PMM-ready voice-of-customer inputs: pains, triggers, status quo, JTBD, exact language, objections, proof, and messaging implications. |
Use this skill when you have raw customer input and need to turn it into useful product marketing judgment.
Good inputs include:
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."
Ask for or infer the following:
If the input is thin, still synthesize it, but label conclusions by confidence:
Do not blend quotes, facts, and strategy into one mush.
For each finding, distinguish:
Clarify who is speaking and who matters in the deal.
Look for:
Do not assume the loudest user is the buyer. Do not assume the buyer is the daily user.
Start with fundamentals:
Do not jump straight to features.
The real competition is often not another vendor. It is the make-do process customers already tolerate.
Look for current alternatives such as:
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.
Find the specific event that made the customer act.
Use this pattern:
Triggers can be reactive or proactive.
Reactive buyer moments:
Proactive buyer moments:
Write jobs in plain buyer language.
Format:
Separate:
Capture short, useful phrases customers actually used.
Prioritize language that is:
Never polish a customer quote until it becomes generic marketing copy. Preserve the edge.
Extract what could stop the deal or weaken belief.
Look for objections around:
Map each objection to the proof needed:
Turn the patterns into PMM direction.
Cover:
Messaging should come from customer reality, not clever copy.
Return a structured synthesis with these sections:
Executive summary
Audience and buying roles
Pains
Triggers
Current workaround / status quo
Jobs To Be Done
Exact customer language
Objections and risks
Proof and outcomes
Messaging implications
A strong synthesis:
Avoid:
