Claude Opus 4.7 / GPT-4oYou just finished a 45-minute user interview. The transcript is sitting in a Notion doc. Your product launch is three weeks out, your homepage copy still reads like every other SaaS company, and your copywriter needs a brief by tomorrow morning.marketing

Turn a customer interview transcript into a complete product messaging framework

May 27, 2026

Why this prompt matters

Most teams run user interviews for discovery but lose 80% of the messaging value by the time they write copy — customer language gets paraphrased, emotional nuance evaporates, and the final copy sounds like it was written by committee. A single well-analyzed interview consistently outperforms six rounds of A/B testing, because it uses the exact words customers already use when they describe the problem to their colleagues.

What we use it for

You just finished a 45-minute user interview. The transcript is sitting in a Notion doc. Your product launch is three weeks out, your homepage copy still reads like every other SaaS company, and your copywriter needs a brief by tomorrow morning.

Prompt

Act as a senior product marketer with deep expertise in the Jobs-to-be-Done framework, narrative-driven positioning, and customer language research.

**Context:**
You have been given a raw user interview transcript below. Real customers describe their problems through stories, workarounds, and emotions — not in marketing language. Your job is to extract the strategic signal buried in their words.

**Transcript:**
[PASTE FULL INTERVIEW TRANSCRIPT HERE — include both interviewer questions and customer responses]

**Your role at [COMPANY NAME]:** [e.g., Head of Product Marketing, Founder, Growth Lead]
**Product being positioned:** [DESCRIBE YOUR PRODUCT IN 1-2 SENTENCES]
**Target customer segment:** [e.g., "B2B SaaS founders under $5M ARR", "freelance designers", "HR managers at 200–500 person companies"]

**Task:**
Analyze the transcript and produce a complete product messaging framework with these six sections:

**1. Core Message (one sentence)**
The single most important transformation this customer wants. Not a feature — a before/after state. Write it as: "[Customer type] can finally [desired outcome] without [previous frustration]."

**2. Three Value Pillars**
The three distinct jobs this customer is trying to get done. For each:
(a) The job in their exact words (quote where possible)
(b) The current friction — what makes this hard today
(c) Success looks like — what "done" means to them

**3. Pain/Gain Pairs (5 pairs)**
Direct mappings from specific pains mentioned to the gains they are seeking. Use the customer's language. Format:
— Pain: "[quote or close paraphrase]"
→ Gain: "[what they actually want instead]"

**4. Before/After Narrative (3 sentences each)**
BEFORE: The customer's working life before your product. Use second-person, past tense, emotional register from the interview.
AFTER: The same person's life with the problem solved. Make it specific, not generic.

**5. Five Headline Variants**
Write five different homepage or ad headlines using these structures, one each:
(a) Benefit-led: leads with the main outcome
(b) Specific outcome: includes a number, timeframe, or metric
(c) Fear-of-loss: what they risk by not solving this
(d) Social proof hook: implies others like them already solved it
(e) Question: one the customer is already asking themselves

**6. Red Flags (3–5 items)**
Language or assumptions in the interview that your current product messaging might be contradicting. Format: "You say '[your current phrasing]' — they mean '[what they actually said]'."

**Constraints:**
- Pull specific quotes from the transcript to support at least half your claims
- Do not invent pain points not mentioned in the transcript
- Avoid marketing buzzwords: no "seamless", "robust", "holistic", "game-changing", "next-level"
- If the transcript is too short to fill a section with evidence, say so explicitly rather than padding

Result

CORE MESSAGE Founders can finally see exactly how customers talk about their problem — and use those words directly in their copy — without spending a week synthesizing interview notes.

THREE VALUE PILLARS

<ol>

<li>Getting the actual words right (a) Customer said: "I keep writing copy that sounds great to me, but our customers don't recognize themselves in it." (b) Friction: Translating customer stories into marketing language strips away specificity. (c) Success: Homepage headline contains a phrase lifted directly from a customer's mouth.</li>

<li>Moving from insight to action fast (a) Customer said: "The problem isn't that we don't know what our customers want — it's that I can't turn those Zoom calls into anything I can actually use." (b) Friction: User research generates transcripts that sit unread. Converting them requires skills most founders don't have time to develop. (c) Success: A usable messaging brief within an hour of finishing the interview.</li>

<li>Team alignment on the product story (a) Customer said: "Our sales rep describes the product completely differently than our website does." (b) Friction: Without a documented framework, everyone defaults to their own interpretation of what the product does. (c) Success: A single source of truth for core message, pillars, and language that every team member references.</li>

</ol>

PAIN/GAIN PAIRS — Pain: "I can write for days and it still doesn't feel like it's for them." → Gain: Copy that customers read and immediately think "this is exactly my problem." — Pain: "I don't know what to emphasize because everyone seems to care about something different." → Gain: Clarity on the three things that actually matter most to the target segment. — Pain: "Our sales calls go well but our website doesn't convert." → Gain: Website language that speaks to the same person the sales team is already winning. — Pain: "We have 20 pages of interview notes and no idea what to do with them." → Gain: A one-page messaging framework that distills the most important signal. — Pain: "Every time we rewrite the homepage, we go in circles." → Gain: A grounded framework that ends the revision loop.

BEFORE/AFTER NARRATIVE BEFORE: You finished the user interview, took careful notes, and felt like you finally understood your customer. But when you sat down to write copy the next morning, the notes felt too raw to use directly and too vague to translate. You rewrote the headline five times and ended up with something that sounded fine — because it was your words, not theirs. AFTER: You paste the transcript and get a complete messaging framework in under five minutes. You send your copywriter a brief with actual customer quotes, a clear core message, and five headline variants ready to test. The homepage gets rewritten in one session. Two weeks later, trial signups are up 34% — because visitors are reading their own thoughts back to themselves.

FIVE HEADLINE VARIANTS (a) Benefit-led: "Turn one customer interview into your homepage copy" (b) Specific outcome: "Extract your core message, 3 value pillars, and 5 headline drafts from a single user interview" (c) Fear-of-loss: "Every week you delay rewriting your copy, your interview insights are going stale" (d) Social proof hook: "Marketers at 200+ SaaS companies use this to turn interviews into messaging briefs the same day" (e) Question: "What if your best homepage headline was already said by a customer — you just haven't found it yet?"

RED FLAGS You say "powerful integrations" — they said "I just need it to work with the tools I already use." You say "unified platform" — they said "one place where my team can find the answer without asking me." You say "save time" — they said "I want to stop feeling like I'm making it up as I go."

The most expensive mistake in product marketing is running user interviews and then summarizing them into bullet points. By the time the insights pass through three Notion docs and a product roadmap meeting, the customer's voice is gone — replaced by polished paraphrases that sound professional but convert poorly.

This prompt treats a user interview as a primary source and extracts six layers of messaging value in one pass: the core transformation, the three jobs the customer needs done, specific pain/gain pairs grounded in their own language, a before/after narrative, headline variants across different emotional registers, and a red-flag check where your current positioning contradicts how your customer actually thinks.

<h2>Why existing workflows fail</h2>

Most teams read interview transcripts and produce insight summaries — sentences like "customers struggle with onboarding complexity" or "users want better collaboration tools." These summaries lose two things that make copy effective: the customer's specific vocabulary, and the emotional texture of how they describe the problem.

When a customer says "I keep writing copy that sounds great to me, but our customers don't recognize themselves in it," that's different from "customers want personalized messaging." The first sentence is quotable. It describes the physical experience of the problem. The second is a categorization — useful for a product roadmap, useless for a homepage.

<h2>What the prompt extracts</h2>

The Jobs-to-be-Done structure in Section 2 separates what the customer does from what they want. A startup buying project management software isn't buying task lists — they're buying the feeling of being in control without micromanaging. That distinction changes every word on your homepage.

The five headline variants in Section 5 are structured to test different emotional registers simultaneously. Benefit-led headlines work for audiences already searching for a solution. Fear-of-loss headlines work for audiences who haven't yet framed their problem. Social proof hooks reduce friction for skeptical buyers. Running all five in one pass gives your copywriter a ready-made test matrix instead of a single "correct" option.

The Red Flags section in Section 6 is the one most teams skip — and often the most valuable. It surfaces the gap between how your product team describes the product and how a paying customer describes their problem. If your homepage says "powerful integrations" and your customer says "I just need it to work with Slack without breaking," that mismatch is losing you conversions every day.

<h2>How to use this prompt</h2>

<ol> <li>Complete the user interview and get a clean transcript (Rev.com, Otter.ai, or Whisper work well)</li> <li>Paste the full transcript — include the interviewer's questions, not just the customer's answers</li> <li>Fill in the three context fields: your role, your product in 1–2 sentences, and your target customer segment</li> <li>Run on Claude Opus 4.7 or GPT-4o (longer context handles hour-long transcripts better)</li> <li>Copy the output directly into your messaging brief or landing page wireframe</li> </ol>

One interview, run through this prompt, typically yields enough raw material for a homepage refresh, three email sequences, and a sales deck introduction.

<h2>Example output</h2>

Core Message: Founders can finally see exactly how customers talk about their problem — and use those words directly in their copy — without spending a week synthesizing interview notes.

Pain/Gain sample: — Pain: "I can write for days and it still doesn't feel like it's for them." → Gain: Copy that customers read and immediately think "this is exactly my problem." — Pain: "We have 20 pages of interview notes and no idea what to do with them." → Gain: A one-page messaging framework that distills the signal from the noise.

Red Flags sample: You say "powerful integrations" — they said "I just need it to talk to Slack without breaking." You say "unified platform" — they said "one place where my team finds the answer without asking me."

The constraint to pull specific quotes to support at least half of your claims is what keeps the output anchored to reality rather than drifting into generic marketing advice.

messagingproduct-marketingmarketingcopywritinguser-research