Tips for interviewing users for a B2B SaaS product focus on one core principle: your goal is to understand the user's current world, not to validate your solution — because users will tell you what you want to hear if you ask leading questions, and the most valuable insight almost always comes from understanding the problem, not from asking about your proposed fix.
B2B user interviews have specific challenges that consumer interviews don't: the person who agreed to the interview may not be the heaviest user, they may have been coached to be positive by the customer success manager who set it up, and their stated workflow may differ significantly from their actual workflow.
The Recruiter-Gatekeeper Problem
H3: Getting Past the CS Manager Filter
When customer success managers schedule interviews for you, they naturally select satisfied, articulate customers who are friendly to the company. This creates selection bias: you learn what your happiest users think, not what your median or struggling users think.
Countermeasures:
- Ask for a mix of tenures (users who've been customers for <3 months, 3–12 months, and 1+ years)
- Request interviews with users who submitted support tickets recently (they've encountered friction)
- Ask for 1–2 churned customers separately (requires a different ask, but they give the most candid feedback)
- Conduct cold outreach via LinkedIn for interviews outside the CS channel
H3: Reaching the Real User
In B2B, the interview participant is often the team lead or manager — not the individual who uses the product daily. Ask the manager who the heaviest daily user is and request that person specifically.
"The daily user's perspective is the one I most need to understand. Is there someone on your team who uses [product] most frequently who I could speak with?"
According to Lenny Rachitsky's writing on B2B user research, the manager who agreed to the interview and the individual contributor who uses the product 8 hours a day have fundamentally different views — and the individual contributor's view is almost always more valuable for product decisions.
Question Design
H3: The Problem-First Question Structure
Never start with your product. Start with the user's world:
Opening: "Tell me about your role. What does a typical [day/week] look like?"
The workflow dig: "Walk me through the last time you [target workflow]. What did you do first? What was the hardest part?"
The current tools question: "What tools or processes do you use for [target workflow]? What do you like about them? What's frustrating?"
The failure question: "Tell me about a time when [target workflow] didn't go as planned. What happened?"
The wish question: "If you could wave a magic wand and change one thing about how you do [target workflow], what would it be?"
These questions surface the actual problem space before you ever mention your product.
H3: Questions to Avoid
- "Would you use a feature that [describes your solution]?" — Leading and hypothetical
- "What features do you want?" — Asks users to be product designers; they'll give you a list, not insight
- "How do you like [product]?" — Too broad, invites generic positive feedback
- "Would you pay for [X]?" — Unreliable predictor of actual willingness to pay
H3: The "Tell Me More" Probe
The most valuable interviewing skill is knowing when to probe and how. Use these when users give surface answers:
- "Tell me more about that."
- "Can you walk me through a specific example?"
- "What happened next?"
- "Why was that frustrating/helpful?"
- "How often does that happen?"
Frequency questions are especially valuable: "Once a week? Once a month?" changes how you weight the finding.
According to Shreyas Doshi on Lenny's Podcast, the most common B2B interview failure is accepting the first answer — users give surface responses because they assume that's what you want. The interviewer's job is to be curious about the first answer in a way that makes the user go deeper, and the third or fourth response is usually where the real insight lives.
During the Interview
H3: The 80/20 Rule
You should speak for no more than 20% of the interview time. If you find yourself explaining, pitching, or defending, stop and ask a question instead.
H3: Silence as a Tool
After a user finishes an answer, wait 3–5 seconds before asking the next question. Most users will fill the silence with more context — often the most candid part of the interview.
H3: Showing the Product (When to and When Not to)
In discovery interviews, do not show the product. You are trying to understand their world before it is colored by your solution. Show the product only in evaluative or usability research where you want behavioral feedback on something specific.
If the user asks to see the product, redirect: "I'd love to show you after we finish — I want to make sure I understand your workflow first so I can point out the most relevant parts."
After the Interview
H3: The Note Structure
Write up interview notes within 2 hours while memory is fresh:
- Direct quotes (verbatim — these are your evidence)
- Observations (things you noticed about their workflow, environment, or reactions)
- Insights (your interpretation — label clearly so you remember it's inference, not data)
- Questions to follow up on
According to Gibson Biddle on Lenny's Podcast, the most valuable output of a user interview is a verbatim quote that captures a user's emotional language about the problem — these quotes become the foundation of positioning, messaging, and design decisions because they are in the user's authentic words, not a PM's paraphrase.
FAQ
Q: How do you get honest feedback in B2B user interviews? A: Recruit outside the CS-filtered channel, request churned users and heavy daily users specifically, start with the user's world not your product, and use silence and probing to get past surface answers.
Q: What questions should you ask in a B2B SaaS user interview? A: Ask about their role, their workflow for the target task, the tools they currently use and why, the last time the workflow failed, and what they would change with a magic wand. Never ask leading questions about your solution.
Q: How long should a B2B user interview take? A: 45 to 60 minutes. 45 minutes is enough for discovery interviews. 60 minutes for complex workflows or evaluative research with product demos.
Q: How many user interviews do you need for a B2B product? A: 5 to 8 interviews per user segment to reach thematic saturation. Diminishing returns typically appear after 8 interviews per segment.
Q: What do you do with user interview notes? A: Write up within 2 hours with direct quotes, observations, and clearly labeled insights. Synthesize across interviews to find themes. Convert insights to Insight plus Implication plus Recommendation format for product decisions.
HowTo: Interview Users for a B2B SaaS Product
- Recruit beyond the CS-filtered channel by requesting churned users, recent support ticket submitters, and heavy daily users who are not team leads or managers
- Open every interview with the user's world — their role, their workflow, their current tools — before mentioning your product or solution
- Use the problem-first question structure: workflow walk-through, failure question, current tools frustrations, and the magic wand question
- Probe every surface answer with tell me more, a specific example request, or a frequency question to reach the third or fourth response where real insight lives
- Speak no more than 20 percent of the time and use 3 to 5 second silences after user answers to invite the most candid follow-up
- Write up notes within 2 hours with verbatim quotes separated from observations and labeled insights, then synthesize across interviews to find recurring themes