Rebundle
/customer-interview
Skill

Customer Interview

Procesa transcripts y extrae jobs-to-be-done, objections, signals y quotes citables.

SKILL.md
---
name: customer-interview
description: Process a customer interview transcript and extract Jobs-to-be-Done (functional, social, emotional), objections, buying signals, and quotable phrases. Categorize using the JTBD framework. Cross-reference with prior interviews to surface patterns. Output a structured brief reusable in sales decks, marketing copy, and product specs.
---

Customer Interview

Turns a 30-minute call recording into structured insight in 60 seconds. The output is reusable in landing copy, sales decks, demo scripts, and feature priority debates.

When to use this skill

  • Right after a discovery call or churn interview.
  • After a user testing session.
  • After a sales call where the customer described their pain in their own words.

Inputs

A transcript file. Accepted formats:

  • Plain text from Otter, Fathom, Granola, or pasted manually.
  • A markdown file with speaker labels.
  • A YouTube/Vimeo URL the skill will transcribe first.

The transcript must have speaker turns. If a single block of unattributed text, ask the user to label speakers before proceeding.

Framework

Use Christensen's Jobs-to-be-Done. Three layers per job:

  • Functional — the task the customer was trying to complete. ("I need to ship a report by 5pm.")
  • Social — how they want to be perceived. ("I want to look on top of things in front of my CEO.")
  • Emotional — how they want to feel. ("I want to stop feeling behind the rest of the team.")

A complete JTBD has all three layers. If the interview only surfaced one, flag the gap.

Extraction targets

Each as a distinct section in the output:

  1. Job-to-be-Done — written as "When I'm trying to [context], I want to [action], so I can [outcome]."
  2. Objections — verbatim phrases of why they didn't buy / hesitated. Categorize: pricing perception, compliance gate, switching cost, no-fit, timing, risk.
  3. Buying signals — phrases that indicate intent: budget mention, decision-maker identified, urgency, internal champion confirmed, evaluation timeline.
  4. Citable quotes — verbatim, emotional, specific. The kind of sentence that would work as a landing page header. Maximum 5.
  5. Triggers — what made them start looking for a solution.

Pattern surfacing

After 5+ processed interviews, surface patterns:

  • Recurring objections that appear in 3+ interviews.
  • Common JTBDs across personas.
  • Word frequency anomalies ("anxiety" appears in 4 of 7 interviews).

These patterns feed into positioning decisions.

Output format

Entrevista · {customer} · {date}

🎯 Job-to-be-Done principal
"Cuando intento {context}, quiero {action}, para {outcome}"

Funcional: {description}
Emocional: {description}
Social: {description}

⚠️ Objections
- {phrase} — {category}

🟢 Buying signals
- {signal}

💬 Quotes citables
- "{quote}"

🔁 Patrones (cross-interview)
{N} de las últimas {M} entrevistas mencionaron {topic}.
{Implication for positioning}.

Constraints

  • Never invent quotes. Only verbatim.
  • Never share customer names with third-party tools.
  • If the transcript is in Spanish, output in Spanish (preserving customer voice).
  • If the customer asked off-record about a specific topic, flag it and exclude from quotes.