Convierte una transcripción de entrevista con un cliente en un marco completo de mensajes de producto
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
- 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. - 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. - 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.
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."
El error más costoso en el marketing de productos es realizar entrevistas con usuarios y luego resumirlas en viñetas. Cuando las percepciones pasan por tres documentos de Notion y una reunión de hoja de ruta del producto, la voz del cliente se pierde — reemplazada por paráfrasis refinadas que suenan profesionales pero convierten mal.
Este prompt trata una entrevista de usuario como fuente primaria y extrae seis capas de valor de mensajería en una sola pasada: la transformación central, los tres trabajos que el cliente necesita realizar, pares específicos de dolor/ganancia basados en su propio lenguaje, una narrativa antes/después, variantes de titulares en diferentes registros emocionales, y una verificación de banderas rojas donde tu posicionamiento actual contradice cómo piensa realmente tu cliente.
Por qué fallan los flujos de trabajo existentes
La mayoría de los equipos leen transcripciones de entrevistas y producen resúmenes de percepciones — frases como "los clientes luchan con la complejidad de la incorporación" o "los usuarios quieren mejores herramientas de colaboración". Estos resúmenes pierden dos cosas que hacen efectivo un texto: el vocabulario específico del cliente y la textura emocional de cómo describen el problema.
Cuando un cliente dice "sigo escribiendo textos que me suenan geniales, pero nuestros clientes no se reconocen en ellos", eso es diferente de "los clientes quieren mensajes personalizados". La primera frase es citable. Describe la experiencia física del problema. La segunda es una categorización — útil para una hoja de ruta del producto, inútil para una página de inicio.
Qué extrae el prompt
La estructura Jobs-to-be-Done en la Sección 2 separa lo que el cliente hace de lo que quiere. Una startup que compra software de gestión de proyectos no está comprando listas de tareas — está comprando la sensación de tener control sin microgestionar. Esa distinción cambia cada palabra de tu página de inicio.
Las cinco variantes de titulares en la Sección 5 están estructuradas para probar diferentes registros emocionales simultáneamente. Los titulares basados en beneficios funcionan para audiencias que ya buscan una solución. Los titulares basados en el miedo a la pérdida funcionan para audiencias que aún no han enmarcado su problema. Los ganchos de prueba social reducen la fricción para los compradores escépticos. Ejecutar las cinco en una sola pasada le da a tu redactor una matriz de prueba lista en lugar de una única opción "correcta".
La sección de banderas rojas en la Sección 6 es la que la mayoría de los equipos omiten — y a menudo la más valiosa. Supera la brecha entre cómo el equipo de producto describe el producto y cómo un cliente que paga describe su problema. Si tu página de inicio dice "integraciones potentes" y tu cliente dice "solo necesito que funcione con Slack sin romperse", esa discrepancia te está costando conversiones todos los días.
Cómo usar este prompt
- Realiza la entrevista al usuario y obtén una transcripción limpia (Rev.com, Otter.ai o Whisper funcionan bien)
- Pega la transcripción completa — incluye las preguntas del entrevistador, no solo las respuestas del cliente
- Completa los tres campos de contexto: tu rol, tu producto en 1–2 frases, y tu segmento de clientes objetivo
- Ejecuta en Claude Opus 4.7 o GPT-4o (el contexto más largo maneja mejor transcripciones de una hora)
- Copia el resultado directamente en tu brief de mensajes o wireframe de página de aterrizaje
Una entrevista, procesada con este prompt, generalmente produce suficiente material en bruto para una renovación de la página de inicio, tres secuencias de correo electrónico y una introducción de presentación de ventas.
Ejemplo de resultado
Mensaje central: Los fundadores finalmente pueden ver exactamente cómo hablan los clientes sobre su problema — y usar esas palabras directamente en su texto — sin pasar una semana sintetizando notas de entrevistas.
Muestra dolor/ganancia:
— Dolor: "Puedo escribir durante días y todavía no parece que sea para ellos." → Ganancia: Texto que los clientes leen y piensan inmediatamente "este es exactamente mi problema."
— Dolor: "Tenemos 20 páginas de notas de entrevistas y no tenemos idea de qué hacer con ellas." → Ganancia: Un marco de mensajes de una página que destila la señal del ruido.
Muestra de banderas rojas:
Dices "integraciones potentes" — ellos dijeron "solo necesito que hable con Slack sin romperse."
Dices "plataforma unificada" — ellos dijeron "un lugar donde mi equipo encuentre la respuesta sin preguntarme."
La limitación de extraer citas específicas para respaldar al menos la mitad de tus afirmaciones es lo que mantiene el resultado anclado a la realidad en lugar de derivar hacia consejos de marketing genéricos.