A hardware purchase is not closed by a buyer. It is closed by a committee, and the committee is larger than almost any founder plans for. The SignalForge Benchmarks composite of Gartner and 6sense data puts the modal B2B buying group at 6.3 to 6.8 people, and Gartner counts 6 to 10 stakeholders on a complex solution, each one arriving with four or five independently gathered pieces of information. Most hardware pitches are built to convince one person in that room.
The distance between a 6.8-person decision and a one-person pitch is where hardware pipeline quietly dies.
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?
Six to seven on the typical deal, and more as the deal grows. The SignalForge Benchmarks composite of Gartner and 6sense data places the modal B2B buying group at 6.3 to 6.8 stakeholders, and Gartner counts 6 to 10 decision-makers on a complex solution. Hardware sits at the upper end of that range by default, because a physical-product purchase touches more functions than a software subscription does, and once a deal clears the mid-five-figure mark the count climbs past ten. The number that matters is not the average. It is the count of people who can independently stall the deal, and in hardware that count is rarely one.
Why is the hardware committee larger than the SaaS one?
Because hardware is a capital decision with line-down risk, not a credit-card subscription. A software buyer can swipe a card on Tuesday and expense a seat. A hardware buyer is committing capital expenditure, a deployment slot on a live production line, and a multi-year dependency that operations, procurement, finance, and quality all have to underwrite before anyone signs. Every one of those functions is a seat at the table, and every seat is a separate set of questions. The manufacturing deal already runs 124 days from open to close at a 19 percent win rate on a $48K average ticket, by Digital Bloom's count, and the cycle is long precisely because the committee is wide. A SaaS motion built for a single buyer and a 30-day cycle does not fail in hardware because it is under-executed. It fails because it is addressed to one person in a room of seven.
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 SignalForge 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.
What does a 6.8-person committee do to your sales cycle?
It stretches it, and it is the quiet reason most pilots never convert. IDC put median hardware pilot-to-production conversion at 12 percent in 2025, which means roughly seven in eight pilots that clear the technical bar still fail to become a purchase order. A single unconvinced stakeholder rarely says no. They say not yet, and the deal does not die so much as stall, because the champion who ran the pilot was never authorized to clear procurement, finance, and quality on their own. The committee that was invisible during the pilot becomes visible at exactly the moment the deal needs a signature, and by then the budget cycle has often closed. The deal was never a technology problem. It was a committee that nobody mapped.
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.
The gap between a 6.8-person buying committee and a single-champion pitch is the most common and least-diagnosed pipeline leak in hardware go-to-market. It closes only when the seller equips the champion to win every seat in a room the seller is not in.
That requires knowing the committee cold, which starts with ICP clarity, the first construct, and runs through buyer mapping, the third.
Verdict.
The hardware buying decision is made by 6.3 to 6.8 people on a typical deal and by more on a large one, and most hardware pitches are built to convince one of them. The companies that priced at a billion dollars and up this month did not win on a better demo. Standard Bots won on a roster of committees that said yes, NEURA on a booked order pipeline, Iceye on repeat procurement by the largest committee there is. The move for an early-stage hardware founder is the same at any scale: map the committee, arm the champion, and give every seat the one proof it needs before the deal reaches the seat that can stall it. This is what the Proof to Pipeline methodology is built on. Not the buyer. The room.
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?