{"site":{"name":"Koji","description":"AI-native customer research platform that helps teams conduct, analyze, and synthesize customer interviews at scale.","url":"https://www.koji.so","contentTypes":["blog","documentation"],"lastUpdated":"2026-05-18T13:37:59.640Z"},"content":[{"type":"documentation","id":"91067506-74eb-4d60-9d72-23d85b6a11b9","slug":"mcp-workflow-founders-gtm","title":"MCP Workflow Guide for Founders & GTM Teams","url":"https://www.koji.so/docs/mcp-workflow-founders-gtm","summary":"Workflow guide for founders and GTM teams using Koji MCP with Claude for market validation, lead qualification, competitive intelligence, and positioning validation. Includes structured question workflows for pain scoring, feature ranking, solution segmentation, and quantitative analysis alongside qualitative research. Features a weekly playbook and tips for non-researchers.","content":"## Research Without a Research Team\n\nMost startups and GTM teams do not have dedicated researchers. Customer understanding falls to founders, product leads, and marketing managers who are already stretched thin.\n\nKoji MCP changes the equation. Instead of scheduling, conducting, transcribing, and analyzing interviews yourself, you tell Claude what you need to learn and it handles the research infrastructure.\n\n---\n\n## Use Case 1: Market Validation\n\nBefore investing months into building something, validate the problem:\n\n> \"Create a customer discovery study about whether small business owners struggle with managing multiple social media accounts. Use the Mom Test methodology so we avoid leading questions.\"\n\nClaude creates a study with:\n- Problem statement focused on the pain, not your solution\n- Questions that explore current behavior (not hypotheticals)\n- Guardrails preventing you from pitching during research\n\n### Adding Quantitative Validation\n\nGo beyond qualitative themes by adding structured questions:\n\n> \"Add a scale question asking how painful this problem is (1-10, with 1 labeled 'Not a problem' and 10 labeled 'Extremely painful'), and a single-choice question asking how they currently manage social media (options: one platform at a time, scheduling tool, virtual assistant, agency, do not manage it).\"\n\nAfter 10-15 interviews, you get both qualitative depth and quantitative data:\n\n> \"Analyze the interviews. What is the average pain score? What percentage use scheduling tools versus doing it manually? Do people with higher pain scores use different workarounds?\"\n\nClaude synthesizes the findings with per-question aggregations — averages, distributions, and frequency counts — alongside qualitative themes.\n\n---\n\n## Use Case 2: Lead Qualification Through Research\n\nThe Lead Magnet methodology turns research into a sales channel:\n\n> \"Create a lead magnet study about how marketing teams measure content ROI. Configure a lead form asking for name, email, company, and marketing team size. Add a scale question asking satisfaction with current ROI measurement (1-5) and a multiple-choice question about which metrics they track.\"\n\nUse `koji_configure_study` to set up the lead form and branding in one call:\n\n> \"Set the headline to 'How Do Marketing Teams Measure Content ROI?' with accent color #2563EB, enable the lead form, and set the URL slug to 'content-roi-research'.\"\n\nAfter collecting interviews:\n\n> \"Show me respondents from companies with 50+ marketing team members. What are their biggest content ROI challenges? What was their average satisfaction score with current measurement?\"\n\nYou now have qualified leads with rich context and quantitative benchmarks for your sales team.\n\n---\n\n## Use Case 3: Competitive Intelligence\n\nUnderstand why customers choose (or leave) competitors:\n\n> \"Create a JTBD study about what triggers companies to switch from [Competitor] to a new solution. Target the switching moment — what was happening when they decided to look for alternatives? Add a ranking question asking them to order these switching factors: price, features, support, reliability, integrations.\"\n\nJTBD is perfect for competitive research because it focuses on the trigger events and decision criteria that drive switching behavior. The ranking question gives you quantitative data on which factors matter most.\n\n---\n\n## Use Case 4: Positioning Validation\n\nTest your positioning with real prospects:\n\n> \"Create an exploratory study to understand how developers describe their ideal CI/CD workflow. I want to hear their language, not ours. Add a scale question asking how satisfied they are with their current CI/CD setup (1-7, with anchor probing so we understand what would improve it).\"\n\nThe AI interviewer captures the exact words your audience uses to describe their problems. The anchor probing on the satisfaction scale reveals what improvements they actually want. Export the transcripts and use their language in your copy:\n\n> \"Export all transcripts. Pull out the exact phrases respondents used when describing their frustrations. Also show me the satisfaction score distribution.\"\n\n---\n\n## The Founder's Weekly Playbook\n\n### Week 1-2: Problem Validation\n1. Create a discovery or Mom Test study with structured questions (pain scale + current solution choice)\n2. Share the link in communities, LinkedIn, email outreach\n3. Target 15 interviews\n\n### Week 3: Analysis\n4. Review themes, sentiment, and per-question metrics via Claude\n5. Generate a research report with charts showing pain distributions and solution breakdowns\n6. Decide: build, pivot, or dig deeper?\n\n### Week 4+: Ongoing Discovery\n7. Keep the study active for continuous feedback\n8. Import new contacts as you meet prospects\n9. Update reports monthly with latest quantitative trends\n\n---\n\n## Tips for Non-Researchers\n\n### Do Not Lead the Witness\n\nThe worst mistake founders make in research: describing their solution and asking \"would you use this?\"\n\nKoji's methodology frameworks prevent this automatically. The Mom Test methodology ensures the AI asks about past behavior, not hypothetical future use.\n\n### Five Interviews Is Enough to Start\n\nYou do not need statistical significance for early-stage validation. Five solid interviews often reveal clear patterns about whether a problem exists and how people currently solve it. Structured questions like pain scales give you quantitative signal even with small samples.\n\n### Use Voice Interviews for Deeper Insights\n\nFounders often get richer data from voice interviews because respondents share more freely in spoken conversation. Enable voice as the default mode:\n\n> \"Configure my study to enable voice interviews as the default mode\"\n\n### Use Structured Questions to Make Data Actionable\n\nAs a founder, you need data that drives decisions. Structured questions bridge the gap between qualitative research and actionable metrics:\n\n- **Pain scale (1-10)**: Is this problem painful enough to pay for a solution?\n- **Willingness to pay scale**: How much would they pay for a solution?\n- **Feature ranking**: Which capabilities matter most to your target market?\n- **Current solution choice**: What is your competitive landscape?\n\nEach of these captures a number you can track over time while the AI interviewer still captures the qualitative reasoning behind each answer.\n\n---\n\n## Next Steps\n\n- **[Quick Start Guide](/docs/quick-start-guide)** — Get your first interview running\n- **[MCP Setup](/docs/mcp-setup-claude)** — Connect Koji to Claude\n- **[Structured Questions Guide](/docs/structured-questions-guide)** — Configure question types and probing\n- **[MCP Overview](/docs/mcp-overview)** — Full integration overview\n- **[PM Workflow Guide](/docs/mcp-workflow-product-managers)** — For product-focused teams\n\n## Further reading on the blog\n\n- [B2B Customer Research: The Complete Guide for Product Teams (2026)](/blog/b2b-customer-research-guide-2026) — B2B customer research is harder than B2C — you are navigating buying groups of 10+ stakeholders, gatekeepers, and enterprise procurement cyc\n- [Concept Testing: The Complete Guide for Product Teams (2026)](/blog/concept-testing-guide-2026) — Concept testing validates whether your idea is worth building before you build it. This guide covers methods, question templates, analysis a\n- [Customer Research Done Right: A Complete Guide for Product Teams](/blog/customer-research-done-right-a-complete-guide-for-product-teams) — Customer research is the foundation of every successful product decision. Learn the types, methods, and best practices that help product tea\n\n<!-- further-reading:blog -->\n","category":"Claude & MCP Integration","lastModified":"2026-05-13T00:26:36.807295+00:00","metaTitle":"MCP Workflow for Founders & GTM Teams — Validate Markets with AI | Koji","metaDescription":"How founders and GTM teams use Koji MCP with Claude for market validation, lead qualification, competitive intelligence, and positioning research — without hiring a dedicated researcher.","keywords":["founder customer discovery AI","GTM research tools","market validation AI","startup customer interviews","lead qualification AI interviews","competitive intelligence AI","positioning validation research","founder research workflow"],"aiSummary":"Workflow guide for founders and GTM teams using Koji MCP with Claude for market validation, lead qualification, competitive intelligence, and positioning validation. Includes structured question workflows for pain scoring, feature ranking, solution segmentation, and quantitative analysis alongside qualitative research. Features a weekly playbook and tips for non-researchers.","aiPrerequisites":["Koji MCP connected to Claude"],"aiLearningOutcomes":["Validate market problems through AI interviews","Qualify leads through research conversations","Gather competitive intelligence using JTBD methodology","Extract positioning language from customer conversations","Run a weekly research cadence as a founder"],"aiDifficulty":"beginner","aiEstimatedTime":"8 minutes"}],"pagination":{"total":1,"returned":1,"offset":0}}