customer-research
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit
Why we recommend it: Customer research directly serves the Customers facet and business planning.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: customer-research description: When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro. metadata: version: 2.0.2 --- # Customer Research You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context to skip questions already answered. --- ## Three Modes of Research ### Mode 1: Analyze Existing Assets You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal. ### Mode 2: Mine Existing Signal (Online) You gather intel from online sources (Reddit, G2, forums, communities, review sites) — customers speaking in public, unprompted. Your job is to know where to look and what to extract. ### Mode 3: Go Ask (Primary Research) No signal exists yet, or you need answers only the customer can give. You run interviews and surveys directly. For the full playbook — the PMF survey, 5-why laddering, outreach templates, incentives, best-customer recruiting, and the confirmation-bias guardrail — read `references/interviews-and-surveys.md`. Most engagements combine modes. Mine what's already public (Mode 2) before you ask (Mode 3) — it tells you what to ask and in whose words. Establish which mode(s) apply before proceeding. --- ## Mode 1: Analyzing Existing Research Assets ### Asset Types **Customer interview / sales call transcripts** - Extract: pains, triggers, desired outcomes, language used, objections, alternatives considered - Look for: the moment they decided to look for a solution, what they tried before, what success looks like to them **Survey results** - Segment responses by customer tier, use case, or tenure before drawing conclusions - Flag: what open-ended answers say vs. what multiple-choice answers say (they often conflict) - Identify: the 20% of responses that contain the most useful signal **Customer support conversations** - Mine for: recurring complaints, confusion points, feature requests, and "I wish it could…" language - Categorize tickets before analyzing — don't treat all tickets as equal signal - Separate bugs from confusion from missing features from expectation mismatches **Win/loss interviews and churned customer notes** - Wins: what tipped the decision? What almost made them choose a competitor? - Losses and churn: was it price, features, fit, timing, or something else? - Segment by reason — don't average across different churn causes **NPS responses** - Passives and detractors are higher signal than promoters for improvement work - Pair scores with verbatims — a 9 with a specific complaint beats a 10 with no comment ### Extraction Framework For each asset, extract: 1. **Jobs to Be Done** — what outcome is the customer trying to achiRead the full source on GitHub (opens external page)