Best practices for conducting user research for a B2B SaaS product: recruit across the full buying committee not just end users, structure interviews around job-to-be-done rather than product feedback, always capture the organizational context — who the user reports to, how they are measured — and connect every research session directly to a specific roadmap or prioritization decision.
B2B SaaS user research fails in a specific way: PMs interview the enthusiastic early adopters who gave them their email, ask what features they want, and walk away with a list of requests that validates their existing roadmap. Real B2B user research surfaces the problems customers have, the organizational constraints that shape them, and the success criteria that determine renewal.
This guide covers the practices that produce B2B research that changes roadmap decisions.
The B2B Research Challenge
B2B user research is harder than consumer research for four reasons:
- Access: Enterprise users require scheduling through procurement or CS; consumer users can be recruited in a day
- Multiple stakeholders: The end user's needs differ from the economic buyer's needs — you need both
- Organizational complexity: What the user needs is shaped by their role, their manager, and their company's priorities
- Answer bias: B2B users give diplomatic answers that protect their vendor relationship — direct questions produce misleading responses
Best Practice 1 — Recruit Across the Buying Committee
For every B2B research initiative, recruit participants from each role:
H3: Research Participant Types
- End users: Day-to-day product users; surface usability and workflow pain
- Champions/power users: Internal advocates; surface what they need to justify the product internally
- Economic buyers: Contract owners; surface renewal criteria and competitive threats
- Churned customers: Former customers; surface what failure looked like (most honest feedback)
Split your research sessions: 50% end users, 25% champions, 25% economic buyers or churned customers.
According to Lenny Rachitsky's writing on B2B product research, the churned customer interview is the most valuable and most avoided research session in B2B SaaS — churned customers are honest in a way that retained customers aren't because they have no vendor relationship left to protect.
Best Practice 2 — Structure Around Jobs, Not Features
H3: The Jobs-to-Be-Done Interview Script
Opening question: "Walk me through the last time you had to [job the product is supposed to do]. What prompted it?"
Follow-up: "What were you doing right before that?"
Digging into friction: "Where did things get complicated? What did you try?"
Outcome question: "What did good look like? How did you know it worked?"
The workaround question: "Is there anything you do outside of [product] to get this job done that you wish you could do inside it?"
Never ask: "What features do you want?" or "How would you rate this feature?" Feature requests and ratings are lagging output. Job-to-be-done interviews surface the upstream need.
H3: Capturing Organizational Context
For every B2B interview, capture:
- Who does this person report to?
- How are they measured (their KPIs)?
- Who else is involved when they complete the job you're studying?
- What would happen if the product didn't exist for a week?
This context transforms a feature request into a problem definition. "I need better export" becomes "I need to export because I report to a VP who only looks at Excel and the export format doesn't match the template she uses."
Best Practice 3 — Separate Discovery From Validation
H3: Discovery Research vs. Validation Research
- Discovery research: Understanding the problem space. Use open-ended JTBD interviews. No mockups or prototypes.
- Validation research: Testing a specific solution hypothesis. Use prototypes or usability tests. Pre-defined pass/fail criteria.
Mixing these produces the most common B2B research failure: showing a mockup in a discovery session. The mockup anchors the user to your solution frame and prevents them from describing the problem in their own terms.
According to Shreyas Doshi on Lenny's Podcast, the most valuable discovery research insight never comes from the question you planned to ask — it comes from the follow-up to an unexpected answer. B2B research sessions that are too scripted miss the most important signals.
Best Practice 4 — Connect Research to Specific Decisions
Every research project should start with a research question that maps to a specific decision:
H3: Research Question Template
"We need to decide [roadmap decision]. We don't know [the specific unknown that's blocking the decision]. We need to research [who to talk to] to learn [what we need to know] so we can [make the decision with confidence]."
Without this connection, research produces interesting findings that don't change anything. With it, research produces decisions.
H3: The Research-Roadmap Connection
After every research cycle:
- Present findings mapped to the original decision question
- Name the specific roadmap items that are affected
- State what changed vs. what was expected
- Document the updated hypothesis
According to Gibson Biddle on Lenny's Podcast discussing research impact, the most common reason user research doesn't change product decisions is that it was conducted without a specific decision it was designed to inform — insights without a decision they apply to are interesting but not actionable.
FAQ
Q: What are the best practices for conducting user research for B2B SaaS? A: Recruit across the buying committee including end users, champions, and economic buyers. Structure interviews around jobs-to-be-done. Capture organizational context. Separate discovery from validation research. Connect every research session to a specific roadmap decision.
Q: How do you recruit participants for B2B SaaS user research? A: Mix retained customers, churned customers, and prospects. Split sessions across end users, champions, and economic buyers. Prioritize churned customers for the most honest feedback and prospects for unbiased problem discovery.
Q: What questions should you ask in a B2B SaaS user research interview? A: Start with the last time they completed the job you're studying. Follow with what prompted it, where friction occurred, what they tried, and how they knew it worked. Never start with feature requests or ratings.
Q: How is B2B user research different from consumer user research? A: B2B research requires recruiting across multiple organizational roles, capturing organizational context that shapes user needs, managing answer bias from vendor relationship protection, and connecting findings to multi-stakeholder buying decisions.
Q: How do you connect user research to roadmap decisions in B2B SaaS? A: Define a specific decision the research is designed to inform before starting. After each cycle, present findings mapped to that decision, name the affected roadmap items, and document what changed versus what was expected.
HowTo: Conduct User Research for B2B SaaS
- Define the specific roadmap decision the research is designed to inform before recruiting a single participant
- Recruit across the buying committee — end users, champions, and economic buyers — with at least 20 percent of sessions dedicated to churned customers
- Structure interviews around jobs-to-be-done using open-ended questions about the last time they completed the relevant job rather than feature preferences
- Capture organizational context in every session: who they report to, how they are measured, and who else is involved in the job you are studying
- Keep discovery research and validation research separate — never show mockups in discovery sessions as they anchor users to your solution frame
- Present findings after each cycle mapped to the specific decision question and document which roadmap items changed and why