B2B buying process: the six buying jobs and who really does them
How the B2B buying process works: Gartner's six buying jobs, who sits in the buying group, a hospital example, and questions that show how a customer buys.
The B2B buying process is how one company decides to buy from another, and it is messier than the funnel on your sales slide. Someone decides a problem is worth solving, a group looks at options, agrees on what it needs, picks a supplier, checks that choice and gets everyone to sign off. Then procurement, legal and security reviews turn the choice into a contract. For a seller, three facts matter most: several people are involved, they rarely move in a straight line, and much of the work happens when no salesperson is present.
Gartner describes the decision as six "buying jobs" that a buying group has to complete, often looping back to earlier ones rather than moving in order. Gartner: B2B buying journey The contract steps that follow are in our procurement process guide.
The six buying jobs, in the buyer's own words
Gartner sums up each job with the buyer's own question:
| Buying job | The buyer's question | What the seller can do | What to ask in research |
|---|---|---|---|
| Problem identification | "We need to do something." | Describe the problem in the buyer's words | "What happened that made this a priority?" |
| Solution exploration | "What's out there to solve our problem?" | Make clear public information easy to find | "What else did you consider, including doing nothing or building it yourselves?" |
| Requirements building | "What exactly do we need the purchase to do?" | Help the buyer define needs, not list features | "Who wrote the requirements, and where did they come from?" |
| Supplier selection | "Does this do what we want it to do?" | Demonstrate on the buyer's own workflow | "How did vendors get on and off the list?" |
| Validation | "We think we know the right answer, but we need to be sure." | Offer references and pilots that match the buyer | "What did you need to see before you were sure?" |
| Consensus creation | "We need to get everyone on board." | Give the champion material they can forward | "Who could have stopped this, and what did they need?" |
Gartner says buyers revisit these jobs, and that group members may have different goals and needs as they do their own research. A buyer may be checking references when a new stakeholder joins and reopens the requirements. (This stakeholder tends to appear right after you put the deal in the forecast.) So track each deal by which job it is in, not by how many meetings it has had.
The buying group is bigger than your contact
The people doing these jobs usually include a user, the owner of the workflow, an internal champion, someone who approves the spending, and reviewers such as IT, security, finance, legal and procurement. One person can hold several roles. In a small company the founder may hold all of them. How to interview B2B users, buyers and champions covers telling who does what, and our buyer persona guide turns those roles into profiles.
A worked example: a scheduling tool for hospitals
Here is a made-up example: a startup selling software that schedules the staff who move patients between departments inside a hospital. Its founders assumed the patient transport manager was the buyer and that a sale would take three months. Then they interviewed people at five hospitals that had bought similar tools:
- Problem identification. At four of the five, the trigger was nursing leadership complaining about patients waiting for transport after discharge.
- Solution exploration. The transport manager asked peers what they used. IT asked early whether any option connected to the electronic health record.
- Requirements building. IT and security wrote most of the requirements, starting from their standard vendor security questionnaire.
- Supplier selection. Two or three vendors demonstrated to a small group, which scored them.
- Validation. Buyers called references at similar hospitals while the security review ran.
- Consensus creation. A purchase review committee and finance approved, and the contract went through supply chain.
So the transport manager is the champion, a vice president of operations approves, and security review is the longest step. The founders moved their forecast from three months to six to nine, started the security questionnaire in the first meeting, and wrote a one-page summary the transport manager could send to nursing leadership.
The real process isn't published, so ask people who bought
The details that decide a deal, such as who approves spending above a threshold, are seldom published. Interviews with people who took part are the fastest way to learn them.
- Ask about a recent purchase, not the general process. "Walk me through the last time you bought something like this" gets facts. "How do you usually buy software?" gets the version in the policy document.
- Talk to more than one role at the same company. Each remembers a different part of the deal.
- Cover several companies. Five buying stories of the same kind show the pattern and the exceptions. Count companies, not people.
- Include buyers who chose someone else or nothing. Win-loss analysis and interviews with customers who chose another product cover how.
- Record dates and documents for each job, such as when the security questionnaire arrived.
Besides the questions in the table, ask who joined the conversation later, how long security, legal and procurement took, and what they would do differently if they bought again tomorrow. Sales discovery questions adapts these for live deals.
Turn the map into a sales process
With five or more buying stories, write down what the buyer must have done in each job before a deal moves on, and forecast with it. For the hospital example: no close date until the security review has started. Then find the job where your deals most often loop back. That is where a missing document costs the most time.
Your next step
Take your last three won deals and two lost ones. For each, write the six buying jobs, who did each one and roughly when. Mark the blanks. Those are the questions for your interviews.
If you have no contacts at the companies you sell to, describe the person, such as "IT security reviewers at mid-size hospitals," and Instant Expert finds people who match. Start with the directory pages for experts in selling to hospitals and enterprise SaaS procurement experts.
Invite one person per buying job rather than several people with the same title. A 30-minute call with a security reviewer and another with someone from finance fill more blanks on your map than two calls with the same kind of buyer. Each person comes with a suggested price and you set each offer separately. The offer is what they receive and our fee is added on top (a $100 offer costs you $125), charged per person and only when they book.
Each person you invite sees your note, the call length and what they would receive, and has 7 days to book a time, decline, or reply with the price they want. They don't need an account to book.