Industrialist Paper No. 25
The Flywheel
A buyer sends out a bracket package on Monday morning. The RFQ record includes the current print, the STEP file, the quantity break, and the ship date, and three suppliers actually respond in a usable way. One supplier wins the work, ships on time, includes the cert packet, and closes the job with no NCR, so the next time a similar package appears the buyer does not start from zero.
That is the flywheel. A flywheel, in this context, is a loop in which each successful cycle lowers the cost and risk of the next one. The claim of this paper: a manufacturing coordination network compounds only when trusted performance changes future visibility and future routing, and when outcomes are not written back to identity and enforced with consequences, the same loop runs backward into noise, ghosting, and bad allocation.
The mechanism is feedback. In a two sided market, value does not come from raw headcount alone; it comes from getting both sides on board in a way that increases the chance of useful interaction, and governance shapes whether those interactions actually create surplus. In industrial work, that means the vendor master, the request record, and the response state have to become more informative after every completed job, because a larger network that does not improve matching is just a larger search problem.
Trust is the first input because manufacturing work is expensive to misunderstand. A clean profile page does not matter much by itself, but a record tied to a company identity, a quote response, a delivery date, a cert packet, and an NCR history matters a great deal because it changes the buyer’s estimate of risk on the next PO. Federal procurement treats this as ordinary operating practice: FAR says past performance information is relevant to future source selection, includes conformance to requirements and adherence to schedules, and CPARS is the official source for that information; DoD goes further by using SPRS to surface on time delivery, quality classifications, and supplier risk in award decisions.
Once trust exists, it should change visibility. When a buyer opens a drawing packet for turned parts, five axis work, or a welded assembly, the system should not expose the request to everyone with a login and a pulse. It should widen access in proportion to verified capability and observed performance, because markets with quality uncertainty deteriorate when participants cannot distinguish strong counterparties from weak ones, and reputation mechanisms exist precisely to reduce that problem.
That visibility then has to produce structured requests, not just more inbox traffic. A useful request object carries the current print, the material callout, the finish requirement, the inspection expectation, the due date, the shipping constraint, and a clear response state such as quote, decline, or need clarification. When suppliers can answer against the same packet and the same response fields, the system starts learning where ambiguity lives, which packets stall, which suppliers answer quickly, and which jobs should never have been routed together in the first place.
Structured requests are what turn visibility into successful work. A buyer who sends a loose email with two attachments and a vague deadline gets back delay, phone calls, and mismatched assumptions, while a buyer who sends a complete packet gets back cleaner accept or decline decisions and more comparable quotes. Every clean cycle leaves a trace in the RFQ record: how long the supplier took to acknowledge, how many clarification turns were needed, whether the award converted, whether the shipment landed on time, and whether the parts passed inspection on the first shot.
Successful work is what produces more trust, but only if the system closes the loop. A shipped job with a passing CMM report, a matched cert packet, and a clean invoice should strengthen that supplier’s future position; a missed due date, a revision mistake, or an unresolved NCR should weaken it. This is why repeat award rate is such a powerful metric: it shows that the prior cycle changed behavior, not just sentiment, and it mirrors the broader procurement logic already used in systems like CPARS and SPRS, where performance history is carried forward into later award choices.
The failure modes are brutal. If identity is weak, bad actors can enter the vendor master and poison the pool. If visibility is indiscriminate, good suppliers spend their time sorting junk requests and eventually stop looking. If the packet is thin, clarification loops explode around the print, the rev letter, or the inspection plan. If closure is sloppy, the system forgets who ghosted, who delivered late, and who shipped perfect parts. If there are no consequences, high performers end up subsidizing low performers until the best participants either withdraw or demand side channels outside the system.
That is why governance matters so much. Governance here means who can see which RFQ board, what evidence expands a supplier’s visibility, how long poor performance lingers in the record, how disputes are closed, and which behaviors trigger throttling or removal. Rochet and Tirole’s core point was that platform outcomes depend on how the sides are brought together and governed; industrial procurement systems such as CPARS and SPRS show the concrete version of that idea, because performance only becomes useful when it is attached to an identity, written into a record, and allowed to affect the next award.
This is also where the series comes together as systems engineering. The job is to design the loop, instrument the loop, and protect the loop from corruption. A national manufacturing coordination layer should be judged by operational measures written to the request record and vendor record: median acknowledgment time, clarification count before quote, quote to award rate, on time delivery, dispute or NCR rate, and repeat award rate after first success. If those numbers improve while the request pool stays usable and the best suppliers keep participating, the flywheel is real. If membership rises but the packet quality, response discipline, and repeat awards do not improve, then there is no flywheel, only traffic.
Implications
The implication is larger than one marketplace or one quoting tool. Industrial capacity does not compound at national scale when every buyer has to rediscover who is real, who responds, who ships on time, and who can be trusted with harder work. It compounds when a successful PO, a closed cert packet, and a clean inspection result improve the next routing decision for the next buyer, because that is how isolated jobs become cumulative industrial memory.
The political implication follows from the same mechanics. A country does not regain self sufficiency by collecting more supplier profiles and hoping for the best; it regains self sufficiency by making good performance legible, portable, and consequential inside its own operating boundary. The practical failure mode is misallocation: the wrong shops see the wrong work, the right shops get buried in noise, and the nation mistakes coordination failure for lack of capacity. The next question is who gets broader access to the loop, and under what rules.
Questions to Ask
- What facts about a supplier are written back to the vendor master after every awarded PO, and which of those facts actually affect future routing?
- Does every RFQ packet force a clear response state, such as quote, decline, or need clarification, so that silence is measured rather than ignored?
- Which metrics on the request record matter most for compounding: acknowledgment time, clarification count, on time delivery, first pass acceptance, dispute rate, or repeat award rate?
- What evidence is required for a supplier to gain broader visibility to higher value or higher risk work?
- How long do missed commitments, revision mistakes, and unresolved NCRs remain consequential in the system?
- Can the system distinguish growth in useful throughput from growth in noise, using award quality and repeat business rather than profile count and page views?