How do you run a customer interview that actually works?

THE SHORT ANSWER

Interview technique has not changed, but everything around it has. Before the call, a prep agent pulls the customer's support history, usage patterns, and NPS score so you walk in already past the surface. During the call, real-time transcription frees you to listen fully instead of taking notes. After, a synthesis agent compares the transcript against hundreds of other data points in minutes. Use the prototype interview format: 30 minutes to confirm the signal, go deep on the customer's workaround, and show a working prototype to get a concrete reaction. Three to five interviews done this way outproduce ten done the old way.

You might think AI signal processing replaces customer interviews. It does not. Agents give you breadth, what customers say at scale. Interviews give you depth, why they feel that way and the workaround they built. What changed is that you no longer walk in blind. You show up knowing exactly what this customer has been struggling with, carrying a prototype that might solve it.

Before, during, after

Before the call, your prep agent pulls everything relevant: support history, usage patterns, features they use and ignore, NPS score and comments. That changes your opening from "tell me about your experience" to "I noticed your team has been running into export issues, walk me through what happened last time." You are in the problem from the first minute.

During the call, real-time transcription runs so you do not take notes. You listen, fully present, instead of splitting attention between listening and writing.

After the call, your synthesis agent processes the transcript within minutes. It extracts the key problems, the emotional intensity, the workarounds, and compares them against your signal patterns. You spend five minutes reviewing the synthesis instead of 30 minutes creating it.

The prototype interview format

Thirty minutes, not 45, because you already have a hypothesis about the problem.

  • Minutes 1 to 3: context and connection. One personal question, nothing about the product yet.
  • Minutes 3 to 10: confirm the signal. "Walk me through what happens when you need to get data out." Do not lead. Do not mention the support tickets. Let them tell the story.
  • Minutes 10 to 15: go deep on the workaround. Workarounds are prototypes your customers built for themselves. They show the shape of the solution. "We export in batches of 500 because anything bigger crashes" tells you the limit and the cost.
  • Minutes 15 to 22: show the prototype. "It is rough, but I would love your reaction." Do not explain. Watch where they click and whether they lean forward.
  • Minutes 22 to 27: get the honest reaction, then ask what is missing. This question, asked about a real prototype, produces 10x better answers than "what features would you want" asked about a hypothetical.
  • Minutes 27 to 30: close with severity. Is this a nice to have or a we need this to stay?

Interview surgically, not randomly

Your signal data tells you who to talk to. For validating an opportunity, talk to the customers whose signals match it. For testing a prototype, talk to the target segment. For churn risk, talk to accounts the churn predictor flagged. Every conversation is aimed at a specific learning goal with a customer who has demonstrated relevant behavior.

Interviews are not the bottleneck anymore. They are the force multiplier. This week, pick one opportunity, identify three to five customers who match it, build a rough prototype, and run two 30-minute calls using the format above.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-07-31 · 3 min read