Most founders do user interviews wrong.
Not the interview itself — the analysis after. They finish a 45-minute call, feel great about it, write some notes, and move on. Two weeks later when it's time to make a product decision, they can't remember what the user actually said.
The worst part? The most valuable insight — buying signals — almost always gets lost completely.
What is a buying signal in a user interview?
A buying signal is any moment where the user expressed willingness to pay, switch tools, or commit to a solution. It doesn't have to include a price mention. These all count:
- "I'd switch from "Z" immediately if this had X"
- "We have budget approved for something like this"
- "How much does it cost? Because this would save me hours every week"
- "I've been looking for something exactly like this for months"
- "I'd pay $50 a month for this, no question"
Most researchers focus on objections and feature requests — which are important — but completely miss these moments of purchase intent.
Why buying signals get lost
When you analyze a transcript without a structured framework, buying signals disappear. They appear briefly in the middle of a longer conversation, often sandwiched between complaints or feature requests. Without actively searching for them, they look like any other sentence.
I once found a buying signal buried on page 12 of a transcript — "honestly if the pricing was clearer I'd sign up today" — that completely changed our pricing page strategy. We nearly missed it.
The free method — 5 dedicated extraction passes
Instead of reading the transcript once and trying to capture everything, read it five times — once for each insight category:
Pass 1 — Objections only
Read looking only for concerns, hesitations and blockers. Ignore everything else.
Pass 2 — Feature requests only
Look for explicit asks ("I wish it had X") and implied needs from workarounds ("I currently do this manually every week").
Pass 3 — Emotional signals only
Note every moment of frustration, excitement, confusion or anxiety. Look for words like "honestly," "frustrated," "finally," "tired of."
Pass 4 — Buying signals only
This is the critical pass most people skip. Read only for purchase intent — price mentions, willingness to switch, urgency signals, budget mentions.
Pass 5 — Patterns
Look at everything you extracted. What appears more than once? Those recurring items are your strongest signals.
Minimum thresholds for confidence:
- 3+ interviews — worth investigating
- 5+ interviews — high confidence, prioritise this
- 7+ interviews — near certain, build around this
The result:
After five passes you have five structured lists instead of messy notes. You can now answer: what are the top objections, what features are most requested, who showed buying intent, and what patterns are strong enough to build product decisions around.
If you want to skip the manual process -
I built Genvoxa to automate all five passes simultaneously. Paste any transcript — user interview, sales call, HR session, customer success call — and it extracts all five categories in under 30 seconds. Free forever plan, no credit card needed.
But the manual process works perfectly well if you only have a few interviews. The key insight is the same either way — buying signals need a dedicated extraction pass or they disappear.
Want the full step-by-step guide including how to find patterns across multiple interviews? Read the complete article at genvoxa.com/blog/how-to-analyze-user-interview-transcripts.html
Top comments (2)
Solid framework and practical advice. I like the five dedicated passes; it forces you to treat buying signals as a first-class insight instead of noise.
The five-pass method is easy to adopt and scales across interview types. Do the buying-signals pass within 24 hours of the interview so urgency and context aren’t lost.
Use the frequency thresholds (3, 5, 7+) to prioritize what to investigate, prototype, or build.
If you can’t do manual passes regularly, automate extraction for consistency, but keep humans in the loop for interpretation.
One small addition: tag each extracted insight with participant role and company size so you can filter patterns by segment later.
Really appreciate this , the point about tagging insights with participant role and company size is excellent. That's something I hadn't included in the framework but it makes a huge difference when you're trying to separate "enterprise user pain" from "solo founder pain" , they often sound similar but require completely different solutions.
The 24-hour rule for buying signals is spot on too.
Context decay is real , what felt like strong purchase intent in the room can look ambiguous in a transcript three days later.
Going to add both of these to the full guide. Thanks for making the framework stronger!