The committee in practice
A typical infrastructure purchase involves an economic buyer, a technical evaluator, a security reviewer, a procurement lead and at least one adjacent team whose workflow changes. Each has a different question, and each can stop the deal.
The vendor usually meets the technical evaluator and, later, procurement. The security reviewer and the adjacent team are discovered at the worst possible moment.
Blockers are rarely political
In our sessions, resistance usually comes from operational concern rather than internal politics: an integration that adds work, a control that does not map to an existing framework, or a support model that assumes a team the buyer does not have.
Those objections are findable in advance. They are simply not findable from the economic buyer.
Designing for the whole committee
The most effective programs we run interview two or three roles per account rather than ten people in one role. The differences between them are where the deal is won or lost.