The buying committee and the procurement process

Module 1 established that the buyer and the user are structurally different people. This lesson names who else is in that committee, what a real RFP process looks like stage by stage, and why "the champion loves it" is necessary and nowhere near sufficient.

---

#The committee, by role

Modern B2B buying-group research is unambiguous on one point: the number of people involved in an enterprise software decision has grown substantially over the past decade. Buying-group-size research widely attributed to Gartner's own sales research (most commonly cited as its "Future of Sales" work) puts the typical enterprise technology buying group at roughly 11 stakeholders, with committees for larger or more complex purchases running into the high teens or beyond — up from roughly 5 a decade earlier. [Directional] — this specific figure is consistently and repeatedly attributed to Gartner across independent secondary reporting, but this research could not confirm it directly against Gartner's own original publication (which sits behind Gartner's client paywall); treat the number as a strong, widely-corroborated planning input rather than an independently primary-verified figure, and treat the direction — committees have grown substantially and keep growing — as very well established regardless.

Within that committee, the roles that matter are consistent across enterprise-sales methodology going back decades (vocabulary that traces to Miller Heiman's Strategic Selling and was reinforced by CEB/Gartner's later Challenger Sale research):

• Economic buyer — controls budget, ultimately signs. Evaluates ROI and risk reduction against a number they can defend upward in their own organization. Rarely present in early conversations; usually surfaces late to approve, not to be sold to from scratch.
• Technical buyer — typically IT, security, or engineering leadership. Evaluates architecture fit, integration burden, and whether the product survives their own review process (the next lesson's subject). Can kill a deal unilaterally; can rarely single-handedly approve one.
• User buyers — the people who will actually operate the tool day to day. Frequently have influence but not formal veto power; a champion usually emerges from this group.
• Champion — an internal advocate, sometimes a user buyer and sometimes not, who carries the case for the purchase through the rest of the committee when the vendor isn't in the room. A deal with no identifiable champion inside the buying organization is a deal that stalls the moment the vendor's own attention moves elsewhere.
• Procurement and legal — evaluate contract terms, vendor risk, and, often, run a formal competitive process. Frequently the last gate, and the one most sales processes underestimate in how long it takes.

[Established] as a standard, decades-old practitioner-research framework — the specific role names above are functionally consistent across the major enterprise-sales methodologies that use this vocabulary.

#The formal RFP process, stage by stage

Not every enterprise deal runs a formal Request for Proposal, but large or regulated buyers frequently do, and the shape is consistent enough across procurement-process research to describe as a real sequence rather than a vague gesture:

1. Internal discovery and requirements-gathering — the buying organization defines the problem, budget range, and technical requirements internally, often before any vendor is contacted.
2. RFP drafted and distributed — a formal document naming the requirements, evaluation criteria, and submission deadline goes to a shortlist of vendors, sometimes sourced from an open call, more often from an analyst-firm shortlist or existing vendor relationships.
3. Vendor response window — commonly several weeks; a rushed or incomplete response is one of the more avoidable ways a deal is lost before evaluation even starts.
4. Evaluation and shortlisting — the buying committee scores responses against the stated criteria; security and compliance posture is frequently the first gate applied, not the last, because a vendor that fails it is removed from consideration regardless of how well the product otherwise fits.
5. Finalist presentations and negotiation — a small number of vendors present directly, followed by contract and pricing negotiation (this module's next module covers this specifically).
6. Procurement and legal sign-off — contract terms, security addenda, and, frequently, a separate security review distinct from the technical evaluation above.

[Directional] — this sequence is consistent across multiple independent procurement-process and RFP-guide sources; the specific stage names and ordering vary slightly by organization, but the shape — internal discovery, formal solicitation, evaluation against named criteria, negotiation, and a separate legal/procurement gate — is very well corroborated. A full cycle through all six stages commonly runs 6 to 12 weeks for the RFP portion alone, on top of the internal discovery and negotiation time that sits on either side of it — consistent with the multi-month total sales-cycle figures in Module 1's contract-economics lesson.

#What this means practically

A vendor that treats "the champion is convinced" as the finish line is treating one stakeholder's enthusiasm as if it were the whole committee's decision — the single most common way an otherwise well-liked product loses an enterprise deal it should have won. The practical implication for this module's next lesson and Module 3's build-vs-integrate lesson: security and compliance readiness isn't a late-stage formality to handle once the deal is otherwise won, it's frequently the first filter applied, and failing it removes a vendor from consideration before the economic buyer ever hears a pitch. The next lesson covers exactly what that review checks for.