Build a buyer pain map from Reddit, G2 reviews, and community threads

Write one focused research question. Examples: why do RevOps teams switch enrichment tools, what frustrates marketers about webinar platforms, or what makes buyers choose one CRM implementation partner over another. Define ICP, category, competitors, and the business decision this research should support.

Use GummySearch to find threads where your ICP complains, asks for recommendations, compares tools, explains failed attempts, or describes workarounds. Save thread URL, title, original wording, subreddit, engagement, buyer role if known, and the pain or trigger being discussed. Focus on high-signal discussions, not keyword volume.

Collect review snippets from G2 for your product category and key competitors. Capture what users praise, what they dislike, what alternatives they mention, and which phrases repeat. Add each snippet to Airtable with source, competitor, sentiment, product area, and buyer role when available.

Use Perplexity to identify common alternatives buyers consider, category trends, adjacent tools, and emerging substitutes. This helps the pain map include the real competitive set, not only the vendors you already track. Add sources and notes to Airtable.

Use Claude to cluster the collected conversations and reviews into pain themes. For each theme, ask for representative language, urgency level, buyer trigger, current workaround, emotional tone, alternatives mentioned, and likely funnel stage. Keep raw examples attached so the map does not become abstract.

Cluster this buyer conversation and review data into a pain map.

Research question:
{{research_question}}

Raw evidence:
{{raw_reddit_review_community_data}}

For each theme, output:
1. Theme name
2. Plain-English pain description
3. Representative buyer phrases
4. Trigger event
5. Current workaround
6. Alternatives mentioned
7. Emotional tone
8. Funnel stage
9. Evidence strength: low, medium, high
10. Notes for messaging or content

Preserve real buyer language. Do not over-polish.

Turn the clustered output into an Airtable view with one row per pain theme. Add columns for persona, pain, trigger, quote snippets, alternatives, buying stage, content ideas, campaign angle, sales objection, and product feedback. This becomes the reusable market map your team can browse.

Use Claude to turn the pain map into practical outputs: landing page angles, ad hooks, blog topics, sales discovery questions, objection responses, and campaign themes. Do not generate full assets yet. First create a menu of options so the team can choose which pain themes are worth activating.

Turn this buyer pain map into GTM applications.

Pain map:
{{buyer_pain_map}}

Our product POV:
{{product_pov}}

Output a table with:
1. Pain theme
2. Landing page angle
3. Ad hook
4. Blog topic
5. Sales discovery question
6. Objection response angle
7. Product feedback note
8. Priority score

Do not invent claims. Use only the evidence in the pain map.

Share the pain map with sales, CS, or support and ask which themes they hear in live conversations. Mark themes as validated, questionable, or new-to-us. Capture corrections and missing language. This human review keeps public-community research from becoming detached from your actual buyers.