Guide
Buying committee management: how to track every stakeholder in a complex sale
Most B2B deals involve more than one decision-maker. Research puts the average at six to ten stakeholders for larger purchases. Here is how to map who those people are, what each of them cares about, and what happens to a deal when you lose track of any of them.
Why one-to-one selling fails for agency deals
In small deals, the person who first reaches out is also the person who signs the contract. That is clean. In a typical software agency or consulting engagement, those two people are almost never the same.
The economic buyer, whoever owns the budget, is often two or three levels above the person who initiated the conversation. The technical evaluator, whoever decides whether your team has the right capabilities, may be someone who barely appears on a call. Legal and procurement show up last, when you can least afford delays.
If you have only been talking to one person, you have been building a relationship with the person most likely to help you but least able to finalize anything on their own. That is a fine way to run a deal until you are three weeks from expected close and discover there is a steering committee you have never met.
The six stakeholder types in a complex deal
Not everyone in the buying process has the same kind of influence. A useful mental model breaks it into six roles. Any given person at a company may play more than one role at once.
Champion
The person inside the company advocating for your solution. They attend most calls, push internally, and make introductions. They are your best source of information about what is actually happening in the decision process, but they often cannot finalize anything alone.
Economic buyer
Controls or approves the budget. May only appear at proposal stage and contract stage. What they care about is ROI and risk reduction, not product features. A deal that has never involved the economic buyer is a deal that is not as far along as it looks.
Technical evaluator
Reviews whether the solution fits technically. In software agency deals, this is often the CTO, engineering lead, or IT architect. Their approval can arrive as a gate mid-process. Skipping this person early tends to create friction late.
End user
The team who will live with the output. A new system, a rebuilt process, a delivered product. Their feedback surfaces late if nobody asks for it early. When end users raise concerns at proposal stage, it usually signals that the champion oversold buy-in internally.
Legal and procurement
Reviews contracts, data handling agreements, vendor compliance, and commercial terms. Rarely visible until late in the deal, but their review timeline can add weeks. Looping them in early, even just with a heads-up, often shortens that window.
Executive sponsor
Senior leadership whose buy-in matters for budget, organizational change, or strategic alignment. They may meet you once. Their opinion still carries disproportionate weight. If they are not part of the picture, you may be building a case that nobody with real authority has endorsed.
Why most CRMs miss this
A standard CRM is built around companies and contacts. You have a record for Acme Corp and a list of people attached to it. What it does not tell you is the role each contact plays in a specific deal, who has influence over whom, or who you have not met yet but probably should.
You can end up with five contacts on a deal all labeled "Decision Maker" because that was the closest available field option, with no way to see that four of them are technical evaluators and the actual budget owner is not in your CRM at all.
The pipeline looks fine. The deal is actually stuck waiting for someone you have never spoken to.
On asking about process instead of people
Oksana spent several years working in Kyiv on international business development for a software consultancy, helping European companies evaluate Eastern European development partners. She watched buying committee mismanagement derail deals consistently.
"The Ukrainian tech firms I worked with were very good at technical conversations," she says. "What they underestimated was how different the buying process is at larger Western companies. In a small startup, the CTO can say yes and it happens. In a 200-person company, the CTO can say yes and it still takes three months."
"The champions at those larger clients often didn't tell you about the other decision-makers early on. Sometimes because they were protective of their internal relationships. Sometimes because they genuinely thought they had more authority than they did."
One thing she saw consistently work: asking about process, not people. "Not 'who else is involved' but 'how does this type of decision usually get made here?' That question treats the client as the expert on their own organization. And it almost always tells you more than asking directly about names."
How to map a buying committee in your CRM
A few practical steps that work even with basic CRM setups:
- Add a stakeholder role field at the deal level. Not on the contact generally, but specifically for this deal. A person can be a technical evaluator on one deal and an economic buyer on another. Job title and deal role are different things and should be tracked separately.
- Track last meaningful interaction per contact. Not just last activity on the account overall. A deal can look active if your champion responds regularly, while the economic buyer has not replied in six weeks. Track engagement at the contact level.
- Note the contacts you have not yet met. An unidentified economic buyer is a risk that deserves a note in the deal record, even before you know the person's name. Tracking known gaps is more useful than pretending they don't exist.
The situations that kill deals in the final stretch
- Champion exits. The person who advocated for you changes roles or leaves the company. Without them, your deal loses its internal momentum. You have to rebuild trust with whoever takes over, and that person may have their own preferences. The risk is higher than it looks because champions rarely announce their departure before it happens.
- Invisible veto. A stakeholder you did not know about reviews the proposal and raises concerns. By the time you find out, the deal has slowed and your champion is not sure how to address the objection internally. This is the outcome of not mapping the committee early enough.
- Late legal review. You get a verbal agreement, and then procurement spends several weeks reviewing the contract. Not fatal, but usually could have been shorter if legal had been looped in early with a timeline heads-up. Legal reviews that drag are often legal reviews that were surprised.
- Misread authority level. Your champion said they could make this decision. It turns out they needed sign-off they did not mention. This is not deception, usually. People genuinely overestimate their own authority until the moment they have to use it and discover a layer above them.
What to do when the committee changes mid-deal
It will happen. Someone gets promoted, someone leaves, someone new joins the evaluation. The practical response is to ask your champion directly how the change affects the process, and not assume continuity. A new stakeholder is not automatically briefed on the proposal and your previous conversations.
Re-qualify. A stakeholder change is a signal to confirm that the project is still a priority, that the scope is still agreed, and that the timeline is still realistic. The deal you thought you had may have shifted.
Add the new contact to your CRM immediately, even if you only have a name and title. You want their history to start from when they entered the process, not from whenever you eventually meet them.
How Lumenbase handles multi-contact deal management
Lumenbase is built around the reality that most deals involve several people, and that different people in a deal have different kinds of influence.
- Contact roles on deals. Assign a role to each contact within a specific deal, separate from their job title. A contact can be a technical evaluator on one deal and an end user on another. The role is deal-level context, not a contact-level field.
- Activity tracking per contact. See when each stakeholder was last contacted, not just when the account was last active. A deal can look current if the champion is responsive while the economic buyer has not replied in six weeks.
- The Feed. Flags deals where a key contact has gone quiet, even if other people on the same account are still responsive. Missing signals from one part of the buying committee should surface before they become a problem.
- Lumo. Reads the full contact and deal history and can summarize who you have spoken to, what each person raised, and who you have not yet engaged. Pre-call briefings and proposal summaries are more useful when they cover the whole committee, not just the primary contact.
Who this is for
Software development agencies, IT consulting firms, and professional services teams where deals typically involve multiple stakeholders and sales cycles run longer than two months. This is less relevant for small transactional deals where one person decides quickly. It is very relevant for any agency where a single large contract represents a significant share of quarterly revenue, because those deals are precisely the ones where losing track of the committee costs the most.