Product Management· 7 min read · April 9, 2026

How to Conduct Customer Interviews for a B2B SaaS Product: A PM's Complete Guide

How to conduct customer interviews for a B2B SaaS product, covering recruiting, interview structure, question techniques, synthesis, and how to turn insights into roadmap decisions.

To conduct customer interviews for a B2B SaaS product, recruit a mix of new, retained, and churned customers within each key segment, use the jobs-to-be-done interview structure that uncovers behavior before probing opinions, and synthesize findings into specific product decisions rather than vague themes — because B2B SaaS customer interviews fail when they confirm what the product team already believes rather than revealing what they don't know.

B2B SaaS customer interviews have specific requirements that consumer product interviews don't: B2B buyers are time-constrained professionals, the buying committee includes multiple stakeholders with different jobs-to-be-done, and the distinction between economic buyer, technical buyer, and end user is critical to interpreting what you hear.

Step 1: Define What You're Trying to Learn

Before recruiting a single participant, define the specific decision the interviews need to inform.

Good interview objective: "We need to understand why mid-market accounts (100–500 employees) are churning at 90 days, so we can decide whether to invest in onboarding redesign or CS coverage expansion."

Bad interview objective: "We want to learn what customers think about the product."

The objective determines who you recruit, what you ask, and what a successful interview looks like.

Step 2: Recruit the Right Mix

B2B SaaS interview recruit mix should include:

| Participant type | What they tell you | |----------------|-------------------| | New customers (0–30 days) | What triggered purchase, what they expected | | Activated retained customers | What value they're getting, what's working | | Unactivated retained customers | Where onboarding is failing | | 90-day churned customers | What disappointed, what the real reason was | | Lost deals (evaluation only) | Why you lost, what competitor won, on what dimension |

For the specific objective above (mid-market 90-day churn): Recruit 3 retained + 5 churned mid-market accounts, and 2 lost deals in the same segment.

Recruitment logistics for B2B:

  • Offer a $75–$150 incentive or a charitable donation in their name
  • Target the economic buyer AND the primary end user separately when they're different people
  • Keep the calendar invite short: 30 minutes. B2B buyers will cancel 60-minute interviews.

According to Lenny Rachitsky on his podcast discussing B2B product research, the interview participation rate in B2B SaaS improves dramatically when the request comes from the CEO or CPO rather than from a researcher — B2B customers respond to authority signals, and a 2-line email from the CEO asking for 30 minutes gets accepted at 3x the rate of a research team outreach.

Step 3: Use the Jobs-to-be-Done Interview Structure

The JTBD interview structure uncovers actual behavior before asking for opinions — this is the single most important technique for getting useful B2B SaaS interview data.

JTBD interview flow (60-minute version):

Opening (5 min): Set expectations. "I'm not here to pitch you on anything. I want to understand your job and your workflow, not sell you features."

Context (10 min):

  • "Walk me through a typical day in your role."
  • "What tools do you use most? What does your workflow look like?"

The purchase timeline (15 min) [for new/churned customers]:

  • "Walk me through the moment you decided you needed to solve [the problem your product addresses]."
  • "What were you doing when you realized this was a problem?"
  • "What did you try first? How did that go?"
  • "Walk me through the day you signed up for [product] / the day you decided not to renew."

The usage deep-dive (20 min) [for retained customers]:

  • "Show me how you use [product] for [their primary use case]." (Screen share if remote)
  • "Where do you get stuck? What takes longer than it should?"
  • "Is there something you wish you could do that you currently can't?"

Wrap-up (10 min):

  • "If [product] disappeared tomorrow, what would you do instead?"
  • "Who else in your organization uses this? What's their experience?"
  • "What's the one thing we should change?"

Step 4: Common B2B SaaS Interview Mistakes

| Mistake | Why it's wrong | Correct approach | |---------|---------------|-----------------| | Asking "what features would you like?" | Customers describe solutions, not problems; solutions they describe are rarely the best solutions | Ask about current workflow and where it breaks | | Interviewing only champions | Champions are fans; churned customers and skeptics have the most useful friction data | Mix fan interviews with churn interviews | | Treating "I would use that" as validation | B2B buyers frequently say yes to features in interviews that they never use in practice | Ask "have you ever done this with any tool?" | | Asking about hypothetical futures | "Would you use X?" is weakly predictive; "did you ever need X?" is stronger | Probe actual past behavior | | Taking first answer at face value | "Too expensive" usually means "I didn't see the value" | Probe with "If the price were cut in half, would you have renewed?" |

Step 5: Synthesize Into Product Decisions

After 8–10 interviews, synthesize findings into specific product decisions — not a theme report.

Theme report (weak output): "Several customers mentioned onboarding was confusing."

Product decision (strong output): "6 of 8 churned customers in the 90-day cohort stopped using the product before completing the integration setup in Week 2. The block was consistently the API key configuration step. Recommendation: build a guided API setup wizard and add a CS touchpoint at Day 7 if integration is not complete. Expected impact: reduce 90-day churn by 2–3pp."

The synthesis should produce an action item with an expected outcome — not a list of observations.

FAQ

Q: How do you conduct customer interviews for a B2B SaaS product? A: Define a specific decision the interviews must inform, recruit a mix of new, retained, and churned customers with economic buyers and end users represented separately, use the JTBD structure to uncover behavior before probing opinions, and synthesize into specific product decisions with expected outcomes.

Q: Who should you interview for B2B SaaS customer research? A: New customers who just purchased, activated retained customers, unactivated retained customers who haven't adopted core features, 90-day churned customers, and lost deal evaluators. Each group provides different and non-overlapping signal.

Q: What questions should you ask in a B2B SaaS customer interview? A: Ask about actual past behavior rather than hypothetical futures — walk me through the day you decided to solve this problem, show me how you use the product, what did you try before this. Avoid asking what features would you like.

Q: How do you get B2B customers to agree to a 30-minute interview? A: Send the request from the CEO or CPO, offer a $75–$150 incentive or charitable donation, keep the ask to 30 minutes rather than 60, and make the subject line about their success rather than your research.

Q: How do you synthesize B2B SaaS customer interview findings? A: Convert themes into specific product decisions with expected outcomes — not a report of observations but a specific recommendation with the evidence supporting it and the metric you expect to move.

HowTo: Conduct Customer Interviews for a B2B SaaS Product

  1. Define the specific product decision the interviews must inform before recruiting — this determines who you interview and what a useful interview looks like
  2. Recruit a mix of new customers, activated retained customers, unactivated retained customers, 90-day churned customers, and lost deal evaluators with the request coming from the CEO or CPO
  3. Use the JTBD interview structure — context, purchase timeline, usage deep-dive, wrap-up — spending the majority of time on actual past behavior rather than hypothetical opinions
  4. Probe initial answers especially for churn and pricing objections — too expensive usually means I did not see the value, and the follow-up questions reveal the real reason
  5. Take notes focused on specific behaviors and exact language customers use, not paraphrased summaries, because the language is the data for positioning and messaging
  6. Synthesize after 8 to 10 interviews into specific product decisions with expected outcomes rather than theme reports — each insight should end with a recommendation and a metric it should move
lenny-podcast-insights

Practice what you just learned

PM Streak gives you daily 3-minute lessons with streaks, XP, and a leaderboard.

Start your streak — it's free

Related Articles