Industrialist Paper No. 20
Constraint Beats Capacity
People talk about manufacturing as if the answer is always more capacity. More shops in the directory, more machine hours on the floor, more labor on the payroll. But a drawing packet can still sit untouched if the RFQ record is incomplete, the vendor master is stale, or the request lands with suppliers who were never a real fit. The machine may be available, yet the work still does not move.
The series promise is to rebuild American manufacturing coordination by turning soft failure modes into hard control points that both generalists and builders can execute. The claim in this paper is simple and testable: when quoting, qualification, and routing are the real bottlenecks, improving RFQ completeness, triage speed, and supplier verification will raise quote response rate and quote to award rate more than adding more suppliers will, because the system is constrained before production starts. By constraint, I mean the step that most severely limits output. In many networks, that step is not the spindle, press brake, or welding cell. It is the front-end work required to understand the job, judge the risk, and route it cleanly. Sometimes it is the will to do the work.
That is the plain lesson of Theory of Constraints. First identify the bottleneck, then get more from it, then make the rest of the system serve it, and only then add capacity. The American Society for Quality (ASQ) makes the point directly: gross capacity analysis can mislead when the real queue is elsewhere. A full schedule board and an open machining cell can exist at the same time if a broken process is the actual bottleneck.
A manufacturing network makes this mistake constantly. Buyers assume that a bigger supplier list means a stronger system, but a bigger list also creates more screening work, more false positives, and more places to send a bad drawing packet. Choi and Krause (2006 Journal of Operations Management paper) describe supply base complexity in terms of supplier count, supplier differentiation, and interrelationships among suppliers, and they tie that complexity to transaction costs, risk, responsiveness, and innovation. Put that into an RFQ workflow and the practical point is obvious: if the supplier profile, quote history, and routing record are weak, scale produces chatter before it produces throughput.
The quoting data points in the same direction. The Center for Automotive Research (CAR) in a 2025 update found that automotive suppliers now process about 800 RFQs a year on average, up from 495 in 2002, while labor per RFQ rose from about 134 hours to 157 hours. The same report says cost data, BOMs, pre-RFQ tracking, resource availability, and supporting documentation are still fragmented across systems, which forces manual reconciliation inside the quote package. That is a front-end constraint. A shop can be willing and able to do the physical work, yet still lose the job because too much effort is consumed before the quote is even ready to send.
Buyer-side evidence says the same thing from the other direction. In the IndustryWeek and aPriori survey, only 4% said the average sourcing and procurement process (from specs to quote accept) takes a week or less, while most placed it at a month or more; 60% said complex bid packages are the top reason for sourcing delays. Meanwhile, 79% said the ideal window is 24 hours to two weeks. This is a massive gap. Speed matters because the first serious quote often wins the work, but the bid package often arrives in a form that is too messy to move quickly.
On the ground, the failure is usually boring. A drawing block omits the material temper, the STEP file reflects a newer revision than the print, the inspection plan calls for a CMM report that was never priced, or the cert packet requirement is buried in the PO notes. Each gap sends the RFQ back into clarification, and each clarification burns time before a traveler exists. NIST argued that efficient supply chain management reduces costs and delays that can add thousands of dollars to end product prices, and later supplier involvement research points in the same direction: earlier and better supplier integration improves quality, lowers cost, and cuts time to market. We’ve spoken about this before; offshore and ambiguous / opaque marketplaces often eat this ambiguity in a way that yields more rework and expense even though it is appealing up-front.
The implication is straightforward. Labor and energy matter, but they are inputs, and they are not always the binding constraint. When the quote queue, qualification gate, and routing logic are the limiting step, more suppliers create more noise, more idle comparisons, and more late quotes. Throughput rises when the RFQ record is cleaner, the vendor master is verified, and the first routing decision is disciplined.
This does not mean supplier count is irrelevant. A broader network can improve resilience, coverage, and surge response once the request is structured well enough that each drawing packet reaches a plausible fit. But capacity added before coordination is relieved mostly inflates the inbox, because the system still cannot tell the difference between a good option and a bad one fast enough. The control point is not the size of the directory. It is the quality of the route from RFQ record to serious quote.
That distinction matters for sovereignty. A country can have real machine capacity, real shops, and real workers, yet still lose work if buyers cannot turn a drawing packet into a fast, trustworthy domestic quote. The practical failure mode is latency, because latency makes available capacity look unavailable. The next question is allocation: once the front end is clean, how should the network decide who sees what work, in what order, and with what consequences when attention is scarce?
Implications
If the bottleneck is at the quote desk, every extra supplier profile is a new demand on scarce attention. That shows up as higher clarification count, higher no response rate, and more time spent sorting weak fits from real ones inside the RFQ record. The network looks larger, but the usable capacity does not increase at the same rate. The system gets louder before it gets faster.
If the bottleneck is relieved at the front end, the opposite happens. A cleaner drawing packet, a verified vendor master, and a narrower first route mean fewer dead ends and faster commitment. That does not eliminate the need for more labor, more energy, or more machine hours later. It just puts those inputs behind a request that is actually ready to move.
Questions to Ask
- Where in the RFQ record do we declare that a drawing packet is complete enough to quote?
- How many clarification loops does a typical request generate before a quote is sent, and which missing fields in the quote package cause most of them?
- How often do we route work to a supplier who later turns out to be a poor fit on process, commercial risk, or quality requirements, and how is that failure coded in the closure record?
- Which facts still live only in inboxes, spreadsheets, or estimator memory instead of in the vendor master, quote sheet, or RFQ history?
- Before asking for more suppliers, can we show that the current bottleneck is machine time rather than qualification time, routing time, or quote preparation time?