Content Strategy
Market Research: Your Buyers Already Wrote Your Copy
Research a market before you write a word of strategy.
What it does
Your buyers have already written your copy. It is sitting in forum threads, review complaints, and support conversations — the exact language they use when no one is selling to them. This skill pulls that language out and turns it into a messaging framework: the pains, gains, and objections in your buyers’ own words, organized so you can write against them.
Most research stops at a word cloud of themes. This one stops at a working framework: exact phrases, mapped to the stage of the journey they belong to, with the proof points your buyers themselves accept. It is the difference between research you file away and research you write from.
- Source identification. Points at where buyers actually talk — forums, reviews, support threads — instead of surveys people answer politely.
- Exact-language extraction. Preserves the buyer’s phrasing, which is the phrasing that converts when it appears in your copy.
- Pain / gain / objection mapping. Organizes raw language into the three forces every message must handle.
- Journey-stage tagging. Tells you which language belongs in which part of the funnel.
- Messaging framework output. A working document, not a report — structured so writers can build from it directly.
When to use it
- Entering a new market or audience: Run this before writing strategy, so the first words you publish speak the buyer’s language.
- Rewriting core pages that do not convert: Replace your vocabulary with theirs — the fastest copy fix that is not copywriting.
- Building an ICP definition: The pain/gain/objection map is the evidence an ICP needs.
- Before a content plan: The question map in content-plan is only as real as the language behind it — this is where the language comes from.
The methodology
- 1
Identify the sources
List where your buyers talk when no one is selling: product review sites, Reddit and niche forums, support tickets, community threads, competitor review complaints. Include the "bad" sources — complaints are where the language gets honest.
1 hour - 2
Collect the raw material
Export threads, reviews, and tickets. Target a few hundred genuine customer statements. The goal is depth over breadth — a hundred honest complaints beat a thousand survey answers.
2 hours - 3
Extract exact phrases
Pull the verbatim phrases customers use for their problems, their desired outcomes, and their objections. No paraphrasing — the exact wording is the asset. You are mining vocabulary, not themes.
2 hours - 4
Map to pains, gains, objections
Cluster the phrases into pains (what hurts), gains (what they want), and objections (why they hesitate). Tag each with the journey stage it belongs to. This is the raw framework.
1–2 hours - 5
Build the messaging framework
Write the final document: for each stage, the buyer’s exact language, the message that answers it, and the proof point buyers themselves accept. This becomes the copywriting reference.
1 hour
Common mistakes
- Stopping at a word cloud or theme list — Themes are summaries; they lose the exact phrasing that does the work. You end up with research and still write in your own voice.
- Paraphrasing instead of quoting — Paraphrase removes the buyer’s words — the entire point. Keep the verbatim phrases or the framework is hollow.
- Ignoring objections — Objections are where conversions die. A framework that skips them leaves your sales page guessing.
- Skipping the ICP definition — Without a defined buyer, "their language" is anyone’s language. Define the audience first or the collection has no center.
Output
A messaging framework: buyer language organized by pain, gain, and objection, tagged by journey stage, with proof points. Ready to write from.
Format
Structured markdown doc — no reports or decks.
Feeds into
Directly informs content-plan (question language), design-what-if (emotional target), and every copy deliverable.
Next steps
Hand the framework to content-plan-reasoning-lift to build the editorial roadmap from the buyer’s actual questions, or to design-what-if to ground the emotional target in real language.
Time & resources
First run
5–7 hours including collection
Iterations
2–3 hours to refresh language for a new audience
Low process, real judgment in the clustering and the ICP definition.
Take it with you
Want to run this in Claude? This page is the strategic overview. The GitHub SKILL.md is the full technical specification — import it and run the method.
Ask Claude: "Use the Market Research methodology to build a messaging framework." Provide the forum threads, reviews, and support ticket exports as source material.
