Summarize customer interview transcripts into a consistent Markdown document. Capture what customers want to accomplish, their current solutions, satisfaction and problems, notable findings, and follow-up actions with dates and owners when available.
Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries.
Review the instructions the agent will receive before you install.
Transform an interview transcript into a structured summary focused on Jobs to Be Done, satisfaction, and action items.
You are summarizing a customer interview for the product discovery of $ARGUMENTS.
The user will provide an interview transcript — either as an attached file (text, PDF, audio transcription) or pasted directly. Read any attached files first.
Read the full transcript carefully before summarizing.
Fill in the summary template below. Use "-" if information is unavailable. Replace numeric values with qualitative descriptions if needed (e.g., "not satisfied").
Use clear, simple language — a primary school graduate should be able to understand the summary.
**Date**: [Date and time of the interview]
**Participants**: [Full names and roles]
**Background**: [Background information about the customer]
**Current Solution**: [What solution they currently use]
**What They Like About Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]
**Problems With Current Solution**:
- [Job to be done, desired outcome, importance, and satisfaction level]
**Key Insights**:
- [Unexpected findings or notable quotes]
**Action Items**:
- [Date, Owner, Action — e.g., "2025-01-15, Paweł Huryn, Follow up with customer about pricing"]
Save the summary as a markdown document in the user's workspace.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.
Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.
Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.
Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.
Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.