[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E2WTC56EXE86GDQBA8FVX0":3,"skill-same:01M7E2WTC56EXE86GDQBA8FVX0":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7E2WTC56EXE86GDQBA8FVX0","customer-research",null,"Use this skill when conducting, analyzing, or synthesizing customer research. Trigger phrases include: \"research our customers,\" \"build a persona,\" \"analyze customer interviews,\" \"mine reviews,\" \"voice of customer,\" \"jobs to be done,\" \"ICP research,\" \"survey our users,\" \"analyze support tickets,\" \"find where our customers hang out,\" \"turn research into messaging.\"","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fadvertising\u002Fcustomer-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customer-research\ndescription: >\n  Use this skill when conducting, analyzing, or synthesizing customer research. Trigger phrases include: \"research our customers,\" \"build a persona,\" \"analyze customer interviews,\" \"mine reviews,\" \"voice of customer,\" \"jobs to be done,\" \"ICP research,\" \"survey our users,\" \"analyze support tickets,\" \"find where our customers hang out,\" \"turn research into messaging.\"\nsource: \"https:\u002F\u002Fgithub.com\u002Fscayver\u002Fmarketing-skills\"\nsource_repository: \"scayver\u002Fmarketing-skills\"\nsource_path: \"skills\u002Fcustomer-research\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# Customer Research Skill\n\n## Mandatory Content Standards\n\n- Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.\n- Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.\n- Use short sentences. One idea per sentence. One focus per paragraph.\n- Use active voice. Never passive constructions.\n- Address the reader directly using \"you\" and \"your.\"\n- Use bullet points only when they genuinely improve readability.\n- Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.\n- End every sentence with a period.\n- No hashtags, emojis, or asterisks.\n- No introductory or closing filler phrases such as \"in conclusion,\" \"in summary,\" or \"in a world where.\"\n- No warnings, notes, or disclaimers. Stick to requested output.\n- No AI cliches: no \"game-changer,\" \"unlock,\" \"leverage,\" \"dive into,\" \"delve,\" \"cutting-edge,\" \"transformative,\" \"revolutionize.\"\n- No excessive adjectives or adverbs. Let specifics do the work.\n- No broad generalizations. Every claim tied to specific context.\n- Use specific examples, data, and scenarios.\n- Pose at least one thought-provoking question per skill.\n- Mobile-friendly: short paragraphs, clear headers, scannable.\n- Practical and actionable. Every section connects to a next step.\n\n---\n\n## What This Skill Does\n\nThis skill helps you plan, execute, and synthesize customer research. It covers the full research process, from identifying what you need to know, to collecting data across multiple sources, to turning raw input into messaging your customers will recognize as their own words.\n\nGood customer research is the foundation of every marketing decision that works. Without it, you write copy that sounds like you, not like your customer. You build features people don't use. You target the wrong channels. You miss the language that actually triggers a purchase.\n\nThe question worth sitting with before starting: what decision are you trying to make, and what would you need to believe to make it confidently?\n\n---\n\n## Part 1: Define the Research Question\n\nBefore collecting any data, get specific about what you need to learn.\n\nVague research produces vague insights. \"Understand our customers better\" is not a research question. These are:\n\n- Why do customers choose us over [specific competitor]?\n- What does a customer's workflow look like before they start using our product?\n- What outcome does a customer expect within the first 30 days?\n- What makes a customer cancel, even when they liked the product?\n\nWrite your research question down before you collect anything. Every data source and interview question you use should connect back to it.\n\n### Types of Research by Decision Stage\n\nDifferent decisions require different research methods.\n\n**Early-stage (pre-product or pre-messaging):** You need exploratory research. Open-ended interviews. Watering hole observation. No surveys yet. You don't know enough to write good survey questions.\n\n**Mid-stage (you have users, refining positioning):** You need both qualitative and quantitative. Interviews plus surveys. Review mining. Support ticket analysis.\n\n**Late-stage (optimizing existing channels):** You need specific, targeted data. Conversion surveys. Exit surveys. Cohort analysis of behavior.\n\nMatch your method to your stage.\n\n---\n\n## Part 2: Ideal Customer Profile (ICP) Research\n\nYour ICP is not a demographic profile. It is a description of the specific type of company or person who gets the most value from your product and is the easiest to retain.\n\nStart with your existing customers, not hypothetical ones.\n\n### Step 1: Pull Your Best Customers\n\nDefine \"best\" concretely:\n- Highest lifetime value.\n- Lowest churn rate.\n- Fastest time to activation.\n- Most likely to refer others.\n\nPull 10 to 20 of these customers and look for patterns. What industry are they in? What size is their team? What job title holds the budget? What triggered them to buy?\n\n### Step 2: Interview Your Best Customers\n\nTalk to five to eight of your best customers directly. You will find more useful signal in five conversations than in 500 survey responses.\n\nUse this as a starting framework for ICP interviews:\n\n- \"Walk me through what was happening in your work right before you started looking for a solution like ours.\"\n- \"What had you tried before finding us, and what wasn't working about those options?\"\n- \"What made you decide to try our product specifically?\"\n- \"What does success look like for you, and how would you know if we failed you?\"\n- \"Who else on your team uses this, and how would you describe what we do to them?\"\n\nListen for specific situations, not abstract opinions. \"I needed a way to send reports to clients without giving them access to our internal tools\" is far more useful than \"I needed something efficient.\"\n\n### Step 3: Document the ICP Profile\n\nAfter interviews, write a structured ICP document:\n\n**Firmographic profile:** Industry, company size (revenue or headcount), geography, business model (SaaS, agency, e-commerce, etc.).\n\n**Role profile:** Job title, seniority level, team structure, who they report to, who reports to them.\n\n**Trigger events:** What happened in their business that made them start looking? Common triggers include a team size crossing a threshold, a new hire in a specific role, a failed audit, losing a major client, or hitting a capacity wall.\n\n**Alternatives considered:** Which competitors or substitutes did they evaluate? What made those fall short?\n\n**Success definition:** In their own words, what does \"working\" look like?\n\n---\n\n## Part 3: Customer Interview Frameworks\n\nInterviews are your most direct access to customer language. The goal is not to validate your ideas. The goal is to understand their world before your product entered it.\n\n### The Jobs-to-Be-Done (JTBD) Interview Framework\n\nJTBD research asks: what progress was the customer trying to make when they hired your product?\n\nThe canonical JTBD interview focuses on the purchase moment. You reconstruct the story of how they went from \"I have a problem\" to \"I bought this specific thing.\"\n\n**JTBD Interview Structure:**\n\nStart by anchoring to the decision:\n- \"Think back to when you first signed up. What was going on that made you start looking?\"\n- \"What day of the week was it? Were you in a meeting, at your desk, somewhere else?\"\n\nExplore the struggle:\n- \"How long had this been a problem before you did something about it?\"\n- \"What had you already tried? What happened when you tried those things?\"\n\nExamine the evaluation:\n- \"When you went looking for a solution, what did you search for?\"\n- \"What options did you consider? How did you narrow it down?\"\n\nProbe the decision moment:\n- \"What was it specifically that made you choose us?\"\n- \"Was there anything that almost made you not sign up?\"\n\nUnderstand the context:\n- \"Who else was involved in the decision?\"\n- \"What did you have to convince yourself (or someone else) of before you moved forward?\"\n\n### The Switch Interview (Competing for Attention)\n\nWhen you want to understand switching behavior specifically, the switch interview maps the timeline from their old solution to yours.\n\nAsk:\n- \"What were you using before? What did a typical week look like with that tool?\"\n- \"When did you first start thinking it wasn't good enough anymore?\"\n- \"What was the first thing you did when you decided to look for something different?\"\n- \"What almost made you stay with [old solution]?\"\n\nThis interview surfaces the \"push\" (what drove them away from the old solution) and the \"pull\" (what attracted them to yours). Both are marketing gold.\n\n### Interview Logistics\n\nRecruit through email to active users, your support ticket list, or a Calendly link in your product. Aim for 30 to 45 minutes per session. Record with permission. Transcribe with Otter or Descript.\n\nOffer something specific in return: a gift card, an extended trial, or a product credit. Make the offer concrete so people show up.\n\nAfter each interview, write a one-paragraph summary immediately. Do not rely on transcripts alone. Your immediate impressions capture things transcripts miss.\n\n---\n\n## Part 4: Survey Design and Analysis\n\nSurveys work best when you know roughly what you're looking for and need to quantify it at scale.\n\n### When to Use Surveys\n\nUse surveys when:\n- You need to validate a pattern you've already seen qualitatively.\n- You want to rank options by priority among a large group.\n- You need quantitative data to make a budget or roadmap case.\n- You want to segment responses by customer tier or cohort.\n\nDo not use surveys when:\n- You don't yet know what questions to ask.\n- Your sample size will be under 50 responses (use interviews instead).\n- You need nuanced language; surveys return opinions, not stories.\n\n### Survey Design Principles\n\n**Keep it short.** Five to seven questions for external surveys. If you need more, split into two surveys at different times.\n\n**Use one question per question.** \"How useful and easy to use is our product?\" is two questions.\n\n**Avoid leading questions.** \"How much has our product improved your workflow?\" assumes it has. Ask instead: \"How has your workflow changed since using our product?\"\n\n**Use open-ended questions strategically.** Include at least one open-text question. The write-in answers are where the real insights live.\n\n**Sequence matters.** Start with behavioral questions (what they do), then attitudinal questions (what they think). End with open text.\n\n### Survey Templates by Use Case\n\n**Post-signup survey (3 questions):**\n1. What's the main thing you're trying to accomplish with [product]?\n2. What were you using before, or what's your current approach?\n3. What would make [product] a success for you in the first month?\n\n**Churn survey (4 questions):**\n1. What's your main reason for canceling?\n2. What did you use [product] for while you had it?\n3. What would have needed to be different for you to stay?\n4. What will you use instead?\n\n**NPS follow-up (for detractors and passives):**\n1. What's one thing we should fix or improve?\n2. What's the main thing holding you back from getting more value?\n\n**Feature priority survey:**\n1. Which of these [list features] would be most valuable to you?\n2. Which one would you pay more for?\n3. What's missing from this list?\n\n### Analyzing Survey Results\n\nExport to a spreadsheet. Separate quantitative and qualitative columns.\n\nFor open-text responses:\n- Read all responses before tagging anything.\n- Identify 5 to 10 recurring themes.\n- Tag each response with the relevant theme(s).\n- Count frequency. Weight by customer tier if your data allows.\n\nLook for the unexpected. The responses that don't fit your existing categories are often the most valuable.\n\n---\n\n## Part 5: Voice of Customer (VOC) Methods\n\nVoice of customer is a specific practice: capturing the exact words, phrases, and language your customers use when describing their problems and goals.\n\nVOC research feeds directly into your copywriting. The best headlines, email subject lines, and ad copy come from customers, not from your team brainstorming in a room.\n\n### VOC Data Sources\n\n**Support tickets and chat logs:** Search your helpdesk for tickets about specific topics. Look at how customers describe problems in their own words. \"I can't figure out how to get my report to show only the current month\" tells you something about the mental model and the language you should use.\n\n**Sales call recordings:** Use Gong, Chorus, or Loom recordings of sales calls. Listen for the phrases prospects use before they understand your product. The language they use to describe their problem before you explain your solution is the language your homepage should use.\n\n**Onboarding call notes:** What questions do people ask during onboarding? What confuses them? What are they excited about?\n\n**Win\u002Floss interviews:** Talk to recent wins and recent losses. Both teach you what matters in the buying decision.\n\n**Review platforms:** G2, Capterra, Trustpilot, app stores. These are structured, public VOC data. More on this in the review mining section.\n\n### Building a VOC Library\n\nCreate a living document (Notion, Airtable, or a spreadsheet) where you store customer quotes organized by:\n\n- Theme (e.g., \"pain before purchase,\" \"outcome achieved,\" \"competitor comparison,\" \"specific feature love\")\n- Customer tier (e.g., enterprise, SMB, individual)\n- Data source (interview, review, support ticket)\n\nRefer to this library every time you write copy. Pull exact phrases. Replace your assumed language with their actual language.\n\n---\n\n## Part 6: Review Mining\n\nReviews on G2, Capterra, Trustpilot, Reddit, and app stores are pre-written customer research. People write reviews unprompted, which means the language is uninfluenced by your questions.\n\n### Where to Mine Reviews\n\n**G2 and Capterra:** Search your product and every competitor. Read reviews for your product (what they love, what they hate). Read competitor reviews (what competitor customers wish were different).\n\n**Reddit:** Search \"[your category] Reddit\" or \"[competitor name] Reddit.\" Look for threads where people ask for tool recommendations. The replies describe what people actually care about. Look for threads about frustrations with current tools.\n\n**App stores:** For mobile products. Look at one-star and five-star reviews. Three-star reviews often have the most nuanced feedback.\n\n**Amazon:** If there are books in your category, read the reviews. What do people say a book helped them with? What did they wish the book covered? These are content and messaging opportunities.\n\n**Twitter and LinkedIn:** Search for your product name, competitor names, and category terms. Filter to posts with replies or engagement.\n\n### How to Structure Review Mining\n\nCreate a spreadsheet with columns:\n- Source (G2, Capterra, Reddit, etc.)\n- Review text (copy the exact words)\n- Sentiment (positive, negative, mixed)\n- Theme (pain, outcome, feature, competitor comparison, context)\n- Customer segment if identifiable\n\nAfter you've collected 50 to 100 data points, sort by theme. Look for:\n\n- The most common pain mentioned across negative reviews of competitors (your opportunity).\n- The outcome mentioned most frequently in positive reviews of your product (your positioning hook).\n- The words used repeatedly to describe the problem (your copy language).\n- The objections or hesitations mentioned in mixed reviews (your FAQ and onboarding content).\n\n### Competitor Review Analysis\n\nGo to your top three competitors on G2. Filter to three-star reviews. Read what people wished were different.\n\nThose unmet expectations are your product's positioning opportunities. If three-star reviewers of Competitor A keep saying \"it's powerful but too complex for our small team,\" and your product is simpler, that's your headline.\n\n---\n\n## Part 7: Digital Watering Holes Research\n\nWatering holes are the places your ideal customers congregate online. Finding them is an underused research method.\n\n### Finding Watering Holes\n\nStart by asking your best customers directly: \"Where do you go to learn about [your category] or talk shop with peers?\" Common answers include:\n\n- Specific Slack communities (e.g., \"Online Geniuses\" for marketers, \"Exit Five\" for B2B marketing).\n- LinkedIn groups.\n- Reddit subreddits (r\u002Fentrepreneur, r\u002Fmarketing, r\u002Fwebdev, etc.).\n- Facebook groups.\n- Newsletters with active comment sections.\n- Specific conferences or event communities.\n- Discord servers.\n- Niche forums (Hacker News for technical audiences, Indie Hackers for bootstrapped founders).\n\n### What to Do in Watering Holes\n\nDo not go in to promote. Go in to observe.\n\nRead threads where people discuss problems in your category. Note the exact language. Note what solutions they mention and what they say about those solutions. Note what questions come up repeatedly.\n\nAfter two to four weeks of observation, you will have a list of:\n- Recurring questions (content opportunities).\n- Common frustrations (positioning and messaging opportunities).\n- Language patterns (copy language).\n- Influencers and community leaders (partnership opportunities).\n\nYou can also participate authentically by answering questions, which builds brand awareness without promotion.\n\n---\n\n## Part 8: Building Customer Personas\n\nA persona is a synthesis of research, not a guess. If you build a persona before doing research, you're writing fiction.\n\n### What a Research-Based Persona Contains\n\n**Name and context:** Give the persona a name and a specific job. \"Sarah, Head of Marketing at a 50-person B2B SaaS company\" is specific. \"Marketing Manager\" is not.\n\n**Trigger event:** What specific situation triggers her to start looking for a solution like yours? \"Her team just doubled and the manual reporting process is breaking down\" is a trigger. \"She wants to be more efficient\" is not.\n\n**Current workflow:** How does she do this job today, before your product? What tools does she use? What's the manual part? What's the painful part?\n\n**Desired outcome:** What does she want to be true in 90 days? Not \"use the product more\" but \"spend four fewer hours per week on reporting and get buy-in from her VP on the new dashboard.\"\n\n**Objections and hesitations:** What might stop her from buying? Budget approval process, concern about implementation time, team adoption risk.\n\n**Exact phrases she uses:** Pull directly from interviews and reviews. \"I just need something that doesn't require me to explain it to everyone\" is a real person's words. Use them.\n\n### Persona Anti-Patterns\n\nAvoid personas that contain:\n- Demographics with no connection to buying behavior (age, gender).\n- Psychographics that could apply to anyone (\"values quality,\" \"goal-oriented\").\n- Aspirations disconnected from your product.\n- Stock photo plus a paragraph of speculation.\n\nA persona is only useful if it changes a decision. If your persona doesn't change what you write or who you target, it's decorative.\n\n---\n\n## Part 9: Turning Research Into Messaging\n\nResearch is only useful if it changes what you say and how you say it.\n\n### The Research-to-Messaging Process\n\n**Step 1: Cluster your data.**\nGroup all your qualitative data (interview quotes, VOC snippets, review excerpts) by theme. Common themes: trigger event, functional outcome, emotional outcome, competitor frustrations, specific features that matter.\n\n**Step 2: Identify the highest-frequency, highest-intensity themes.**\nFrequency means how often something came up. Intensity means how strongly people feel about it. A problem mentioned by 80% of interviewees in passing is less useful than a problem mentioned by 30% of interviewees with visible frustration.\n\n**Step 3: Match themes to messaging pillars.**\nYour homepage, email sequence, and ads should each focus on one to three core messages. Map your research themes to these pillars.\n\n**Step 4: Write in their language.**\nUse the exact phrases from your research. If three customers independently said \"I was drowning in spreadsheets,\" that's your headline, not a paraphrase.\n\n**Step 5: Test your messaging against your research.**\nRead your draft copy and ask: would the customers you interviewed recognize this as describing their problem? If not, you've drifted into your own language.\n\n### From Research to Homepage Copy\n\nYour hero section should answer three questions your customer has:\n- Is this for me?\n- What does it do?\n- Why should I believe it?\n\nPull the trigger event language for the hero headline. Pull the outcome language for the subheadline. Pull the specific feature language for the feature section. Pull review quotes for the social proof section.\n\n### From Research to Email Copy\n\nYour welcome email should reference the trigger event that brought someone to your product. Your onboarding emails should address the hesitations and confusion points you found in support tickets and interviews. Your case study emails should use the outcome language from your best customer interviews.\n\n---\n\n## Part 10: Synthesizing a Research Report\n\nAfter a round of research, write a synthesis document that the whole team can use. Keep it short and specific.\n\n**Structure:**\n\n1. Research question (one sentence).\n2. Methods used and sample size.\n3. Key findings (5 to 10 bullet points with supporting quotes).\n4. ICP profile (updated or confirmed).\n5. Messaging implications (specific copy suggestions).\n6. Open questions (what you still need to learn).\n\nShare this document in Slack or Notion. Reference it in copy reviews. Update it every quarter or after any major research project.\n\nThe goal is a living record that keeps your marketing grounded in what customers actually say, not what you assume they feel.\n\n---\n\n## Research Cadence Recommendation\n\nResearch is not a one-time project. Build a rhythm:\n\n- Weekly: Read five support tickets. Flag interesting language.\n- Monthly: Read 10 to 20 new G2 or Capterra reviews (yours and competitors).\n- Quarterly: Run three to five customer interviews focused on a specific question.\n- Annually: Full ICP review. Survey your customer base. Update personas.\n\nIf you do this consistently, you will always know more about your customers than your competitors know about theirs. That knowledge gap compounds over time.\n","# Customer Research Skill\n\n## Mandatory Content Standards\n\n- Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.\n- Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.\n- Use short sentences. One idea per sentence. One focus per paragraph.\n- Use active voice. Never passive constructions.\n- Address the reader directly using \"you\" and \"your.\"\n- Use bullet points only when they genuinely improve readability.\n- Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.\n- End every sentence with a period.\n- No hashtags, emojis, or asterisks.\n- No introductory or closing filler phrases such as \"in conclusion,\" \"in summary,\" or \"in a world where.\"\n- No warnings, notes, or disclaimers. Stick to requested output.\n- No AI cliches: no \"game-changer,\" \"unlock,\" \"leverage,\" \"dive into,\" \"delve,\" \"cutting-edge,\" \"transformative,\" \"revolutionize.\"\n- No excessive adjectives or adverbs. Let specifics do the work.\n- No broad generalizations. Every claim tied to specific context.\n- Use specific examples, data, and scenarios.\n- Pose at least one thought-provoking question per skill.\n- Mobile-friendly: short paragraphs, clear headers, scannable.\n- Practical and actionable. Every section connects to a next step.\n\n---\n\n## What This Skill Does\n\nThis skill helps you plan, execute, and synthesize customer research. It covers the full research process, from identifying what you need to know, to collecting data across multiple sources, to turning raw input into messaging your customers will recognize as their own words.\n\nGood customer research is the foundation of every marketing decision that works. Without it, you write copy that sounds like you, not like your customer. You build features people don't use. You target the wrong channels. You miss the language that actually triggers a purchase.\n\nThe question worth sitting with before starting: what decision are you trying to make, and what would you need to believe to make it confidently?\n\n---\n\n## Part 1: Define the Research Question\n\nBefore collecting any data, get specific about what you need to learn.\n\nVague research produces vague insights. \"Understand our customers better\" is not a research question. These are:\n\n- Why do customers choose us over [specific competitor]?\n- What does a customer's workflow look like before they start using our product?\n- What outcome does a customer expect within the first 30 days?\n- What makes a customer cancel, even when they liked the product?\n\nWrite your research question down before you collect anything. Every data source and interview question you use should connect back to it.\n\n### Types of Research by Decision Stage\n\nDifferent decisions require different research methods.\n\n**Early-stage (pre-product or pre-messaging):** You need exploratory research. Open-ended interviews. Watering hole observation. No surveys yet. You don't know enough to write good survey questions.\n\n**Mid-stage (you have users, refining positioning):** You need both qualitative and quantitative. Interviews plus surveys. Review mining. Support ticket analysis.\n\n**Late-stage (optimizing existing channels):** You need specific, targeted data. Conversion surveys. Exit surveys. Cohort analysis of behavior.\n\nMatch your method to your stage.\n\n---\n\n## Part 2: Ideal Customer Profile (ICP) Research\n\nYour ICP is not a demographic profile. It is a description of the specific type of company or person who gets the most value from your product and is the easiest to retain.\n\nStart with your existing customers, not hypothetical ones.\n\n### Step 1: Pull Your Best Customers\n\nDefine \"best\" concretely:\n- Highest lifetime value.\n- Lowest churn rate.\n- Fastest time to activation.\n- Most likely to refer others.\n\nPull 10 to 20 of these customers and look for patterns. What industry are they in? What size is their team? What job title holds the budget? What triggered them to buy?\n\n### Step 2: Interview Your Best Customers\n\nTalk to five to eight of your best customers directly. You will find more useful signal in five conversations than in 500 survey responses.\n\nUse this as a starting framework for ICP interviews:\n\n- \"Walk me through what was happening in your work right before you started looking for a solution like ours.\"\n- \"What had you tried before finding us, and what wasn't working about those options?\"\n- \"What made you decide to try our product specifically?\"\n- \"What does success look like for you, and how would you know if we failed you?\"\n- \"Who else on your team uses this, and how would you describe what we do to them?\"\n\nListen for specific situations, not abstract opinions. \"I needed a way to send reports to clients without giving them access to our internal tools\" is far more useful than \"I needed something efficient.\"\n\n### Step 3: Document the ICP Profile\n\nAfter interviews, write a structured ICP document:\n\n**Firmographic profile:** Industry, company size (revenue or headcount), geography, business model (SaaS, agency, e-commerce, etc.).\n\n**Role profile:** Job title, seniority level, team structure, who they report to, who reports to them.\n\n**Trigger events:** What happened in their business that made them start looking? Common triggers include a team size crossing a threshold, a new hire in a specific role, a failed audit, losing a major client, or hitting a capacity wall.\n\n**Alternatives considered:** Which competitors or substitutes did they evaluate? What made those fall short?\n\n**Success definition:** In their own words, what does \"working\" look like?\n\n---\n\n## Part 3: Customer Interview Frameworks\n\nInterviews are your most direct access to customer language. The goal is not to validate your ideas. The goal is to understand their world before your product entered it.\n\n### The Jobs-to-Be-Done (JTBD) Interview Framework\n\nJTBD research asks: what progress was the customer trying to make when they hired your product?\n\nThe canonical JTBD interview focuses on the purchase moment. You reconstruct the story of how they went from \"I have a problem\" to \"I bought this specific thing.\"\n\n**JTBD Interview Structure:**\n\nStart by anchoring to the decision:\n- \"Think back to when you first signed up. What was going on that made you start looking?\"\n- \"What day of the week was it? Were you in a meeting, at your desk, somewhere else?\"\n\nExplore the struggle:\n- \"How long had this been a problem before you did something about it?\"\n- \"What had you already tried? What happened when you tried those things?\"\n\nExamine the evaluation:\n- \"When you went looking for a solution, what did you search for?\"\n- \"What options did you consider? How did you narrow it down?\"\n\nProbe the decision moment:\n- \"What was it specifically that made you choose us?\"\n- \"Was there anything that almost made you not sign up?\"\n\nUnderstand the context:\n- \"Who else was involved in the decision?\"\n- \"What did you have to convince yourself (or someone else) of before you moved forward?\"\n\n### The Switch Interview (Competing for Attention)\n\nWhen you want to understand switching behavior specifically, the switch interview maps the timeline from their old solution to yours.\n\nAsk:\n- \"What were you using before? What did a typical week look like with that tool?\"\n- \"When did you first start thinking it wasn't good enough anymore?\"\n- \"What was the first thing you did when you decided to look for something different?\"\n- \"What almost made you stay with [old solution]?\"\n\nThis interview surfaces the \"push\" (what drove them away from the old solution) and the \"pull\" (what attracted them to yours). Both are marketing gold.\n\n### Interview Logistics\n\nRecruit through email to active users, your support ticket list, or a Calendly link in your product. Aim for 30 to 45 minutes per session. Record with permission. Transcribe with Otter or Descript.\n\nOffer something specific in return: a gift card, an extended trial, or a product credit. Make the offer concrete so people show up.\n\nAfter each interview, write a one-paragraph summary immediately. Do not rely on transcripts alone. Your immediate impressions capture things transcripts miss.\n\n---\n\n## Part 4: Survey Design and Analysis\n\nSurveys work best when you know roughly what you're looking for and need to quantify it at scale.\n\n### When to Use Surveys\n\nUse surveys when:\n- You need to validate a pattern you've already seen qualitatively.\n- You want to rank options by priority among a large group.\n- You need quantitative data to make a budget or roadmap case.\n- You want to segment responses by customer tier or cohort.\n\nDo not use surveys when:\n- You don't yet know what questions to ask.\n- Your sample size will be under 50 responses (use interviews instead).\n- You need nuanced language; surveys return opinions, not stories.\n\n### Survey Design Principles\n\n**Keep it short.** Five to seven questions for external surveys. If you need more, split into two surveys at different times.\n\n**Use one question per question.** \"How useful and easy to use is our product?\" is two questions.\n\n**Avoid leading questions.** \"How much has our product improved your workflow?\" assumes it has. Ask instead: \"How has your workflow changed since using our product?\"\n\n**Use open-ended questions strategically.** Include at least one open-text question. The write-in answers are where the real insights live.\n\n**Sequence matters.** Start with behavioral questions (what they do), then attitudinal questions (what they think). End with open text.\n\n### Survey Templates by Use Case\n\n**Post-signup survey (3 questions):**\n1. What's the main thing you're trying to accomplish with [product]?\n2. What were you using before, or what's your current approach?\n3. What would make [product] a success for you in the first month?\n\n**Churn survey (4 questions):**\n1. What's your main reason for canceling?\n2. What did you use [product] for while you had it?\n3. What would have needed to be different for you to stay?\n4. What will you use instead?\n\n**NPS follow-up (for detractors and passives):**\n1. What's one thing we should fix or improve?\n2. What's the main thing holding you back from getting more value?\n\n**Feature priority survey:**\n1. Which of these [list features] would be most valuable to you?\n2. Which one would you pay more for?\n3. What's missing from this list?\n\n### Analyzing Survey Results\n\nExport to a spreadsheet. Separate quantitative and qualitative columns.\n\nFor open-text responses:\n- Read all responses before tagging anything.\n- Identify 5 to 10 recurring themes.\n- Tag each response with the relevant theme(s).\n- Count frequency. Weight by customer tier if your data allows.\n\nLook for the unexpected. The responses that don't fit your existing categories are often the most valuable.\n\n---\n\n## Part 5: Voice of Customer (VOC) Methods\n\nVoice of customer is a specific practice: capturing the exact words, phrases, and language your customers use when describing their problems and goals.\n\nVOC research feeds directly into your copywriting. The best headlines, email subject lines, and ad copy come from customers, not from your team brainstorming in a room.\n\n### VOC Data Sources\n\n**Support tickets and chat logs:** Search your helpdesk for tickets about specific topics. Look at how customers describe problems in their own words. \"I can't figure out how to get my report to show only the current month\" tells you something about the mental model and the language you should use.\n\n**Sales call recordings:** Use Gong, Chorus, or Loom recordings of sales calls. Listen for the phrases prospects use before they understand your product. The language they use to describe their problem before you explain your solution is the language your homepage should use.\n\n**Onboarding call notes:** What questions do people ask during onboarding? What confuses them? What are they excited about?\n\n**Win\u002Floss interviews:** Talk to recent wins and recent losses. Both teach you what matters in the buying decision.\n\n**Review platforms:** G2, Capterra, Trustpilot, app stores. These are structured, public VOC data. More on this in the review mining section.\n\n### Building a VOC Library\n\nCreate a living document (Notion, Airtable, or a spreadsheet) where you store customer quotes organized by:\n\n- Theme (e.g., \"pain before purchase,\" \"outcome achieved,\" \"competitor comparison,\" \"specific feature love\")\n- Customer tier (e.g., enterprise, SMB, individual)\n- Data source (interview, review, support ticket)\n\nRefer to this library every time you write copy. Pull exact phrases. Replace your assumed language with their actual language.\n\n---\n\n## Part 6: Review Mining\n\nReviews on G2, Capterra, Trustpilot, Reddit, and app stores are pre-written customer research. People write reviews unprompted, which means the language is uninfluenced by your questions.\n\n### Where to Mine Reviews\n\n**G2 and Capterra:** Search your product and every competitor. Read reviews for your product (what they love, what they hate). Read competitor reviews (what competitor customers wish were different).\n\n**Reddit:** Search \"[your category] Reddit\" or \"[competitor name] Reddit.\" Look for threads where people ask for tool recommendations. The replies describe what people actually care about. Look for threads about frustrations with current tools.\n\n**App stores:** For mobile products. Look at one-star and five-star reviews. Three-star reviews often have the most nuanced feedback.\n\n**Amazon:** If there are books in your category, read the reviews. What do people say a book helped them with? What did they wish the book covered? These are content and messaging opportunities.\n\n**Twitter and LinkedIn:** Search for your product name, competitor names, and category terms. Filter to posts with replies or engagement.\n\n### How to Structure Review Mining\n\nCreate a spreadsheet with columns:\n- Source (G2, Capterra, Reddit, etc.)\n- Review text (copy the exact words)\n- Sentiment (positive, negative, mixed)\n- Theme (pain, outcome, feature, competitor comparison, context)\n- Customer segment if identifiable\n\nAfter you've collected 50 to 100 data points, sort by theme. Look for:\n\n- The most common pain mentioned across negative reviews of competitors (your opportunity).\n- The outcome mentioned most frequently in positive reviews of your product (your positioning hook).\n- The words used repeatedly to describe the problem (your copy language).\n- The objections or hesitations mentioned in mixed reviews (your FAQ and onboarding content).\n\n### Competitor Review Analysis\n\nGo to your top three competitors on G2. Filter to three-star reviews. Read what people wished were different.\n\nThose unmet expectations are your product's positioning opportunities. If three-star reviewers of Competitor A keep saying \"it's powerful but too complex for our small team,\" and your product is simpler, that's your headline.\n\n---\n\n## Part 7: Digital Watering Holes Research\n\nWatering holes are the places your ideal customers congregate online. Finding them is an underused research method.\n\n### Finding Watering Holes\n\nStart by asking your best customers directly: \"Where do you go to learn about [your category] or talk shop with peers?\" Common answers include:\n\n- Specific Slack communities (e.g., \"Online Geniuses\" for marketers, \"Exit Five\" for B2B marketing).\n- LinkedIn groups.\n- Reddit subreddits (r\u002Fentrepreneur, r\u002Fmarketing, r\u002Fwebdev, etc.).\n- Facebook groups.\n- Newsletters with active comment sections.\n- Specific conferences or event communities.\n- Discord servers.\n- Niche forums (Hacker News for technical audiences, Indie Hackers for bootstrapped founders).\n\n### What to Do in Watering Holes\n\nDo not go in to promote. Go in to observe.\n\nRead threads where people discuss problems in your category. Note the exact language. Note what solutions they mention and what they say about those solutions. Note what questions come up repeatedly.\n\nAfter two to four weeks of observation, you will have a list of:\n- Recurring questions (content opportunities).\n- Common frustrations (positioning and messaging opportunities).\n- Language patterns (copy language).\n- Influencers and community leaders (partnership opportunities).\n\nYou can also participate authentically by answering questions, which builds brand awareness without promotion.\n\n---\n\n## Part 8: Building Customer Personas\n\nA persona is a synthesis of research, not a guess. If you build a persona before doing research, you're writing fiction.\n\n### What a Research-Based Persona Contains\n\n**Name and context:** Give the persona a name and a specific job. \"Sarah, Head of Marketing at a 50-person B2B SaaS company\" is specific. \"Marketing Manager\" is not.\n\n**Trigger event:** What specific situation triggers her to start looking for a solution like yours? \"Her team just doubled and the manual reporting process is breaking down\" is a trigger. \"She wants to be more efficient\" is not.\n\n**Current workflow:** How does she do this job today, before your product? What tools does she use? What's the manual part? What's the painful part?\n\n**Desired outcome:** What does she want to be true in 90 days? Not \"use the product more\" but \"spend four fewer hours per week on reporting and get buy-in from her VP on the new dashboard.\"\n\n**Objections and hesitations:** What might stop her from buying? Budget approval process, concern about implementation time, team adoption risk.\n\n**Exact phrases she uses:** Pull directly from interviews and reviews. \"I just need something that doesn't require me to explain it to everyone\" is a real person's words. Use them.\n\n### Persona Anti-Patterns\n\nAvoid personas that contain:\n- Demographics with no connection to buying behavior (age, gender).\n- Psychographics that could apply to anyone (\"values quality,\" \"goal-oriented\").\n- Aspirations disconnected from your product.\n- Stock photo plus a paragraph of speculation.\n\nA persona is only useful if it changes a decision. If your persona doesn't change what you write or who you target, it's decorative.\n\n---\n\n## Part 9: Turning Research Into Messaging\n\nResearch is only useful if it changes what you say and how you say it.\n\n### The Research-to-Messaging Process\n\n**Step 1: Cluster your data.**\nGroup all your qualitative data (interview quotes, VOC snippets, review excerpts) by theme. Common themes: trigger event, functional outcome, emotional outcome, competitor frustrations, specific features that matter.\n\n**Step 2: Identify the highest-frequency, highest-intensity themes.**\nFrequency means how often something came up. Intensity means how strongly people feel about it. A problem mentioned by 80% of interviewees in passing is less useful than a problem mentioned by 30% of interviewees with visible frustration.\n\n**Step 3: Match themes to messaging pillars.**\nYour homepage, email sequence, and ads should each focus on one to three core messages. Map your research themes to these pillars.\n\n**Step 4: Write in their language.**\nUse the exact phrases from your research. If three customers independently said \"I was drowning in spreadsheets,\" that's your headline, not a paraphrase.\n\n**Step 5: Test your messaging against your research.**\nRead your draft copy and ask: would the customers you interviewed recognize this as describing their problem? If not, you've drifted into your own language.\n\n### From Research to Homepage Copy\n\nYour hero section should answer three questions your customer has:\n- Is this for me?\n- What does it do?\n- Why should I believe it?\n\nPull the trigger event language for the hero headline. Pull the outcome language for the subheadline. Pull the specific feature language for the feature section. Pull review quotes for the social proof section.\n\n### From Research to Email Copy\n\nYour welcome email should reference the trigger event that brought someone to your product. Your onboarding emails should address the hesitations and confusion points you found in support tickets and interviews. Your case study emails should use the outcome language from your best customer interviews.\n\n---\n\n## Part 10: Synthesizing a Research Report\n\nAfter a round of research, write a synthesis document that the whole team can use. Keep it short and specific.\n\n**Structure:**\n\n1. Research question (one sentence).\n2. Methods used and sample size.\n3. Key findings (5 to 10 bullet points with supporting quotes).\n4. ICP profile (updated or confirmed).\n5. Messaging implications (specific copy suggestions).\n6. Open questions (what you still need to learn).\n\nShare this document in Slack or Notion. Reference it in copy reviews. Update it every quarter or after any major research project.\n\nThe goal is a living record that keeps your marketing grounded in what customers actually say, not what you assume they feel.\n\n---\n\n## Research Cadence Recommendation\n\nResearch is not a one-time project. Build a rhythm:\n\n- Weekly: Read five support tickets. Flag interesting language.\n- Monthly: Read 10 to 20 new G2 or Capterra reviews (yours and competitors).\n- Quarterly: Run three to five customer interviews focused on a specific question.\n- Annually: Full ICP review. Survey your customer base. Update personas.\n\nIf you do this consistently, you will always know more about your customers than your competitors know about theirs. That knowledge gap compounds over time.\n",{"name":5,"source":24,"license":15,"description":25,"imported_at":26,"source_path":27,"source_repository":28},"https:\u002F\u002Fgithub.com\u002Fscayver\u002Fmarketing-skills","Use this skill when conducting, analyzing, or synthesizing customer research. Trigger phrases include: \"research our customers,\" \"build a persona,\" \"analyze customer interviews,\" \"mine reviews,\" \"voice of customer,\" \"jobs to be done,\" \"ICP research,\" \"survey our users,\" \"analyze support tickets,\" \"find where our customers hang out,\" \"turn research into messaging.\"\n","2026-09-20","skills\u002Fcustomer-research\u002FSKILL.md","scayver\u002Fmarketing-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fadvertising\u002Fcustomer-research","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill customer-research",{"tool":41,"command":42},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill customer-research",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill customer-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fadvertising\u002Fcustomer-research\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]