A hardware purchase can require agreement across several functions. Start with the actual account: who matters, what each person needs to approve, and how the group reaches a decision. The Gartner research on buyer alignment provides context for that work.
Build the case for the people who must agree to the purchase.
The capital that moved into hardware this month rewarded the companies that closed that distance. In the week ending June 12, three of the largest hardware rounds on record priced, and not one of them priced on a demo. Standard Bots raised a $200M Series C at a $1B valuation on June 9, and the proof in the release was a customer roster, not a spec sheet: Lockheed Martin, NASA, the U.S. Army, Amazon, and Sunoco (The Robot Report). Each of those names is a full buying committee that reached yes. NEURA Robotics raised a Series C of up to $1.4B at roughly a $7B valuation on June 10, the largest full-stack robotics round on record, and stated its order and deployment pipeline already exceeds $1B (Businesswire). Booked enterprise demand, not a working prototype, set that mark. Iceye raised about $520M at a valuation above $12B on June 9, with seven European governments now procuring sovereign systems and a contracted backlog above EUR 1.5B (Iceye newsroom). Government procurement is the buying committee at its largest and slowest, and Iceye turned it into a repeatable motion. Iceye sits well above the early-stage profile most hardware founders occupy, so take it as the committee in its purest extreme, not as a peer case. The lesson scales down cleanly.
How many people actually decide a hardware purchase?
Count the people who can independently approve, delay, or stop the purchase in the account you are working. Confirm their responsibilities, their requirements, and how the group reaches agreement.
Why is the hardware committee larger than the SaaS one?
A hardware purchase can involve capital expenditure, deployment on a live line, and ongoing support commitments. Ask operations, procurement, finance, and technical evaluators to define their requirements. Check the account’s own buying process rather than assuming one approval path applies to every customer.
Who actually sits on the committee?
Six roles, and a pitch that skips any of them stalls there. This is buyer mapping, the third of the twelve Quarry North constructs, and in hardware the map is consistent enough to name. The economic buyer owns the budget and wants a one-line thesis they can defend to their own boss. The technical evaluator stress-tests the product and will end the deal in the first conversation if fluency is missing. The operator who lives with the machine wants to know what changes on their floor and what breaks during integration. Procurement owns terms, vendor risk, and the question of whether a new supplier has been approved in the last three years. Finance owns the capex math and the depreciation schedule. And the skeptic, usually quality, security, or reliability, holds a seat whose entire job is to find the reason not to buy. Six people, six different questions, and a single deck written for the technical evaluator answers exactly one of them.
How does buyer alignment affect the sales cycle?
Unresolved requirements can delay the next decision. During the pilot, establish who owns the production budget and what procurement, finance, and operations need to approve. Give the champion a plan for securing those commitments before the evaluation ends.
How do you sell to a committee instead of a champion?
You stop selling to the champion and start arming them. The champion cannot be present in the three internal meetings the seller will never attend, so the work is to hand them the exact material each of those rooms needs. Map the committee before the pitch, not after the stall: name the six seats, and for each one, identify the single objection that seat is paid to raise. Then build one artifact per seat. The economic buyer gets the one-sentence thesis. Finance gets the capex and payback math as a P and L line, not a spec line. Procurement gets the vendor-risk and reference package. Quality gets the failure-mode and reliability proof. The operator gets the integration and line-down plan. The technical evaluator gets the demo they already wanted.
Equip the champion to address the questions raised in internal meetings. Map the decision roles, record the evidence each person needs, and check what remains unresolved before forecasting a close.
That requires knowing the committee cold, which starts with ICP clarity, the first construct, and runs through buyer mapping, the third.
Verdict.
Map the buying group, equip the champion, and give each decision-maker the evidence they need. Keep the account plan current as people and requirements change. The Proof to Pipeline methodology connects that work to a repeatable sales process.
So before the next pitch, answer one question honestly. If the champion walked into a procurement review tomorrow with only the deck you gave them, how many of the seven seats could they close, and which one stalls the deal?