B2B Buyer Journey Interview: Questions for the Buying Committee
Use this guide with people who took part in a recent software purchase at their company. It maps who joined the decision and when, what each person needed, and where the purchase slowed down.
- Length
- 30 min
- Questions
- 14
- People
- 10 to 15
- Sections
- 5
What this guide finds out
- The event that started the purchase, and who started it.
- The roles in the buying committee, when each joined and what each needed.
- The sources each role trusted, such as peers, analysts, reviews or trials.
- The steps that slowed the purchase, such as security review, legal or budget approval.
When to use it
- Your sales cycle is long and you do not know where deals wait.
- You sell to one role, but other roles stop or change the deal.
- You plan content or sales material for each stage of the purchase.
Who to talk to
People who took part in a software purchase at their company in the last 6 months, in any role. Talk to 10 to 15 people. Each interview takes about 30 minutes.
Screener for this guideB2B Decision-Maker Screener: Questions to Find Software BuyersUse this screener to find people who chose or approved a software purchase in the last 12 months. It checks the purchase role twice, so people who inflate their title fail.The discussion guide
Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.
Warm-up
3 minLearn the role and company of the participant.
Tell me about your role and your company, for example the size and the industry.
ProbeDo not ask a follow-up. Record the answer as context.
Which software purchase will we talk about today, and what was your part in it?
ProbeConfirm it was in the last 6 months. Do not ask for the vendor name if they prefer not to say.
The trigger
5 minFind the event that started the purchase.
What happened that made your company start to look for this software?
ProbeAsk for the event and the date. If they give a general need, ask what made it urgent at that time.
Who first said that the company needed to buy something?
ProbeAsk for the role, not the name. Ask how that person got the budget or the approval to look.
The buying committee
8 minMap the roles in the decision and what each role needed.
Who else took part in the decision, and when did each person join?
ProbeList each role in order. Ask who joined late and what changed when they joined.
What did each of those people care about most?
ProbeAsk for one example of a question or a demand from each role.
Was there a moment when the group disagreed? What happened?
ProbeAsk how the disagreement was resolved and who had the final word.
Was there anyone who could stop the purchase, even if they did not choose the product?
ProbeAsk what that person checked and what they needed to say yes.
Research and evaluation
8 minLearn how the committee found and compared options.
How did you find the options you looked at?
ProbeAsk which source they trusted most: peers, review sites, analysts, search or vendors. Ask why.
How did your team compare the options? Was there a list of requirements or a trial?
ProbeAsk who wrote the requirements and which requirement removed the most options.
What did the security, legal or procurement review involve, and how long did it take?
ProbeAsk which document or question took the longest. Ask what a vendor did that made it faster or slower.
Decision and close
6 minLearn how the final decision was made, and what the participant would change.
How was the final decision made, and how was it communicated?
ProbeAsk if there was a meeting, an email or a signature. Ask what the final argument was.
Looking back, what would have made the purchase faster or easier?
ProbeAsk for one change from the vendor side and one from inside the company.
Is there anything else about this purchase that you want to tell me?
ProbeThank them and end the interview.
Example finding
In several purchases, the security questionnaire took longer than the full product evaluation.
“We chose the tool in three weeks. Then it sat with the security team for two months because the vendor had no SOC 2 report ready.”
Mistakes to avoid
- Do not talk only to the person who signed. Users, IT and finance often shaped the decision earlier and more.
- Do not ask about the purchase in general. Talk about one recent purchase, step by step.
- Do not ask for confidential prices or contract terms. Ask how the price was discussed, not the number.
- Do not mix this with a win-loss interview about your own deals. Buyers then speak to the vendor, not about the process.
Analyze the answers
Analysis templateWin-Loss Analysis Framework: Codes for Buyer InterviewsUse this framework to code interviews with B2B buyers after a deal closed, won or lost. Each decision factor gets a code and a direction, so wins and losses use the same scale.Questions
A buying committee is the group of people who take part in a business purchase. It often includes users, a budget owner, IT or security, procurement and legal.
A win-loss interview asks why a buyer chose or rejected your product in one deal. A buyer journey interview maps how the company buys, whatever product it chose.
Interview more than one role. Include a user, the budget owner and a person from IT or procurement. If you can, interview two roles from the same purchase.
Use a screener that asks about their role in a recent purchase, not only their job title. Pay a reward that is fair for a senior professional's time.
Let the AI moderator ask these questions
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.