The data anchors SignalForge runs engagements against, published in the open. Every number carries its source named inline. No gating, no email wall on the figures: cite them, link them, hold vendors to them. Where a number is derived rather than measured, the row says so. Where the data is still maturing, the row says that too.
12%
Roughly one hardware pilot in eight becomes a production contract. The other seven die, most often at the innovation-to-business-unit budget handoff, where a pilot funded from an innovation budget needs a production budget owner who was never identified. The number is a deal-design verdict, not a product verdict: conversion is decided at pilot signature, when the production path is or is not written into the deal. Pillar 04 walks the mechanism.
$48K · 124 days · 19%
The baseline shape of a manufacturing technology deal: a $48K average contract on a 124-day cycle closing at a 19 percent win rate. Serious capital equipment and committee-gated purchases run longer, commonly 9 to 18 months. The practical use of this anchor is calibration: comp plans, coverage targets, and board expectations built for a 30-day SaaS rhythm break against this clock. It is the arithmetic behind why imported software comp plans starve hardware sellers.
6.3 to 6.8
The cited Gartner and 6sense data puts a typical buying group at six to seven people. For hardware, map the technical champion, operations, finance, procurement, and any safety or compliance roles that can affect the decision. The Diagnostic checks whether the seller has covered the people who matter in the actual account.
1 ÷ win rate
Coverage is arithmetic, not folklore. The qualified pipeline required to hit a number works out to the inverse of the expected win rate on that pipeline. The table runs the math across win-rate bands; at manufacturing's 19 percent median win rate (anchor 02), required coverage implies roughly 5.3x.
| Win-rate band | Implied coverage |
|---|---|
| 10% | 10.0x |
| 19% (mfg median, Digital Bloom) | ~5.3x |
| 25% | 4.0x |
| 33% | ~3.0x |
Two honesty notes. The arithmetic assumes the win rate is measured on qualified pipeline against a written definition; an inflated pipeline makes any coverage multiple fiction. And coverage is a planning floor, not a guarantee: it sizes the funnel, it does not fix the motion.
25% vs 10%
The cited benchmark puts aftermarket and service business at roughly 25% EBIT margin against a 10% baseline on new-equipment sales. For a hardware company with lumpy equipment revenue, the installed base may support service contracts, consumables, retrofits, or uptime guarantees.
30%
The working threshold at which a channel motion is real rather than decorative: roughly 30 percent of revenue partner-sourced. Below it, partners are logos on a slide and the direct motion still carries the company. The anchor cuts both ways. It is the bar a channel strategy has to clear to justify its overhead, and a warning against booking channel projections before the direct motion is documented enough for a partner to run it.
51%
The cited research says half of vendor research now starts in an AI assistant. That makes clear, crawlable source pages more important. This benchmark page is open so a buyer can inspect the claim, definition, and source without submitting a form.
In measurement
The gap between "we have a deal" and a signed contract, banded by buyer type: enterprise capital committee, mid-market operations, government and utility procurement. SignalForge tracks this on its own engagement data. The bands publish here when the engagement base clears a reporting threshold worth standing behind; until then this row holds the construct without a number. What the anchor exists to kill: forecasting a verbal as revenue. The verbal starts the procurement clock, it does not stop it.
Eight anchors, three rules. Every measured number names its source inline. Every derived number is labeled derived and shows its arithmetic. Every internal number waits until the base behind it is worth standing behind. Material refresh runs quarterly; corrections ship as they are found.
These anchors are the data backbone of the Proof to Pipeline methodology and the scoring baseline of the Hardware Go-to-Market Diagnostic. If a vendor quotes you a benchmark without a source, ask for the source. If they quote one of these without the caveats, send them here.
Forge Friday is the hardware go-to-market newsletter, launching soon. One practical essay, plus benchmark updates as they land. Unsubscribe anytime.