What you will learn
Good funnel copy is not a clever writing trick. It is compressed customer understanding. When you know what changed for someone, what they tried, what they want, and what makes them cautious, writing becomes much easier. This lesson shows you how to collect evidence without drowning in notes, then turn it into a message brief that guides pages, ads, emails, and sales conversations.
You will create a brief that describes one buyer situation, the language customers use, their desired progress, their objections, and the proof they need before moving forward.
Why this matters
Teams often write from internal vocabulary: features, processes, category labels, and assumptions. Customers may care about a completely different outcome, describe it differently, or be worried about a risk the team rarely mentions.
A strong brief prevents each channel from inventing its own message. It gives writers and operators a shared source of truth while making assumptions visible enough to test.
From raw customer voice to a useful message
Quotes are only the beginning. Your job is to understand the situation behind the words: what happened, what the customer wants to protect or achieve, and what would make a next step feel safe.
Core concepts
Buying trigger
A trigger is the event or realization that causes someone to look for a solution now. It might be a deadline, stalled growth, a bad experience, a new responsibility, or a change in their business.
Use it when: Can you complete this sentence: ‘They started looking because…’?
Desired progress
Progress is the change a customer wants in their work or life. It is usually more useful than a feature request because it shows why the product matters and what success looks like to them.
Use it when: Does the outcome describe a better situation rather than only a product capability?
Proof need
A proof need is the answer to ‘Why should I believe this will work for me?’ It may be relevance, expertise, results, a product demonstration, transparent limits, or a safe way to try.
Use it when: Can you name the specific uncertainty this proof is meant to reduce?
The practical method
Collect evidence from places customers already speak
Start with sales calls, onboarding calls, support tickets, reviews, survey responses, lost-deal notes, search queries, and community discussions. Save context with each quote: who said it, what they were trying to do, and where they were in the journey.
Sort evidence by decision, not by channel
Create simple columns for triggers, desired outcomes, current alternatives, concerns, decision criteria, proof, and exact phrases. This lets you see patterns across sources instead of treating every interview or ticket as a separate story.
Separate facts from interpretations
A quote is evidence; your conclusion about why it matters is an interpretation. Write both. If several customers say setup is confusing, do not assume they need a video until you understand where, why, and for whom it is confusing.
Write one focused message brief
Describe the buyer situation, trigger, desired progress, current approach, anxieties, proof needed, phrases worth using, and the next reasonable action. Include a short list of claims you can support and questions that remain unanswered.
Put the brief in front of real customers
Use the brief to draft a page, sales opener, ad, or email. Ask people in the target situation what feels accurate, unclear, or overstated. Better language comes from listening to their response, not defending the draft.
Worked example: a project-management tool for small agencies
The product team initially describes its offer as ‘streamlined work management.’ Call notes reveal a sharper problem: agency owners lose time asking for project status, deadlines move without warning, and clients complain when they are surprised. Their desired progress is predictable delivery without daily chasing.
The brief records the trigger, the current spreadsheet-and-chat workaround, the fear of a difficult rollout, and the proof requirement: a quick demonstration of how client visibility and team status work together. The landing page now opens with the customer’s situation and shows the workflow rather than leading with generic efficiency language.
The team can use the same brief for search ads, the landing page, a product demo, onboarding, and sales qualification without losing the customer’s original meaning.
Make it stronger
Segmentation matters when people have different triggers, risks, vocabulary, or next actions. A first-time buyer and a switcher may need different proof. Do not segment merely because you can collect more data.
Tag evidence by theme and customer situation, then revisit it when a message underperforms. A usable library links each theme to a decision and source, so a writer can tell what is well supported and what still needs research.
Apply it to a real funnel
Use evidence you already have before scheduling new research. Twenty good pieces of evidence are enough to find a first pattern.
Collect: Gather ten customer quotes or observations and preserve the surrounding context.
Cluster: Group them into triggers, desired progress, alternatives, objections, and proof needs.
Interpret: Write one sentence explaining what each important cluster means for the customer’s decision.
Brief: Create a one-page message brief for one situation and label any remaining assumptions.
Before you move on
- Evidence includes context, not isolated quotes.
- The brief identifies a real trigger and desired progress.
- Customer language is distinguished from internal terminology.
- Objections are connected to the proof or clarity they need.
- Assumptions are visible and ready to test.
Make the next customer decision clearer.
Use the course as a guide, then put the journey to work in your own workspace.
