Industrialist Paper No. 15

Protocols Create Markets

One buyer experience: upload a DXF and a STEP, picks a material and finish, and gets a price that is usable immediately. A different buyer experience: email a PDF drawing and a STEP, the rev letter is unclear, the tolerance block is generic, and the message says “same as last time.” In both cases the part might be simple, but only one of those paths turns the request into something a shop can accept without a phone call. This series is about rebuilding industrial coordination by tightening interfaces, so the work becomes legible to strangers before it becomes expensive. Claim (falsifiable): in a side by side trial on comparable custom part RFQs, a lightweight intake protocol that enforces revision lock, acknowledgement states, and explicit acceptance criteria will reduce median clarification cycles per RFQ by at least 30% and increase on time quote rate by at least 15% within 90 days, measured from the RFQ record, the quote PDF, and the acknowledgement receipt.

A “protocol” here means a shared request shape plus a shared state machine, with receipts tied to artifacts like the drawing, the STEP, and the inspection plan. It is not a committee standard and it is not a demand for perfect inputs. It is a small set of fields that forces ambiguity into named buckets, plus a small set of states that forces silence to become visible. The control point is the RFQ packet, with a revision lock that points to the exact files that were quoted, then follows the work into the PO and traveler.

This is why verticalized shops can deliver instant pricing and fast parts. It’s why shops and buyers think they want instant quoting. What they’re all really saying is “let’s be clear and stick with a protocol so I get what I want fast.” The are pros and cons to every approach. Scaling it to work across many disparate shops is something we believe to be possible, but not easy. When done right, we have a functional market for US manufacturing. 

Enforcing Protocols

The mechanism is translation cost, expressed as calendar latency. In custom work, the first expensive step is the estimator translating a drawing and STEP into a quoteable job, deciding precedence, reading the tolerance block, and inferring the inspection plan. Every missing fact becomes a negotiation with risk, and each shop negotiates it differently, which makes the quotes non comparable even when the price looks comparable. When a request arrives in prose and attachments, the market is really a collection of private interpretations, and the only “protocol” is the email thread. The control point is a completeness check on the RFQ record that names what is missing, instead of burying it in the estimator’s head.

Verticalized shops are the cleanest proof that protocols create markets, because they make protocol unavoidable by owning the intake loop. A platform that instant quotes sheet and plate work does not accept a PDF drawing and hope a human can figure it out later, it forces the request into a constrained shape up front. SendCutSend, for example, publishes accepted file formats for quoting and explicitly says it does not accept PDFs or raster images for instant quoting, pushing buyers toward DXF and STEP, which are more machine checkable inputs.  The artifacts matter because they are the protocol surface, the uploaded file becomes the unit of truth that pricing and production reference.

OSH Cut makes the same point from a different angle and says it can upload parts, set units, materials, finishing options, and quantities, then provide instant pricing and design feedback through an online app.  That flow is not marketing polish, it is enforcement. It turns common failure modes into deterministic checks, wrong units, missing bends, impossible features, and it turns “what did you mean” into an explicit selection that ends up on a cut sheet and order record. The control point is the ordered configuration, because it binds the buyer’s intent to a specific set of manufacturing choices before the job hits a schedule board.

What makes these verticals scale is not that they found nicer customers, it is that they converted translation into validation. The quote is bound to an uploaded DXF or STEP, the option set is explicit, and the platform can reject, flag, or price the risk before a human reviews anything. A buyer can be a stranger because the request is checkable, the acceptance criteria are implied by the published rules, and the order can become a PO without a bespoke phone call. That is exactly what “market” means in practice, strangers can transact with low friction because the request has a shared structure. The control point is the quote record that points back to the file and option set, then flows into a traveler without re interpretation.

The transferable lesson is not “everyone should become a vertical.” A general market spans processes, materials, and exceptions, so it cannot enforce one rigid upload template the way a sheet metal or machining platform can. It can still enforce a lightweight protocol that captures the minimum facts needed to quote, and it can do that without demanding perfect inputs. In practice that protocol has hard gates and soft fields, where hard gates include revision lock for the drawing and STEP, a precedence field, and an identity bound to a real buyer role, while soft fields allow “unknown” for finish, inspection plan, or cert packet with a priced assumption flag. The control point is a state transition log, submitted, acknowledged, clarification requested, clarified, quoted, awarded, closed, each state tied to an artifact like the quote PDF or NCR record. In addition, the truth in US manufacturing is that buyers don’t always know their requirements, and they look to the shop to help connect the dots of manufacturability. This is where AI can assist in reducing that cost for US shops, rather than forcing rigid uploads (see Paper No. 14). 

Scaling Markets

Protocols scale markets in other industries because they replace bespoke negotiation with shared message shapes. FIX is a concrete example, it is a set of messaging specifications used for trade communications, and it standardizes message types and fields that mirror the steps of a transaction cycle.  That matters here because a manufacturing transaction also has a cycle, RFQ, quote, award, PO, shipment, dispute, and today most of those steps are carried by emails with attachments. The control point is not copying finance, it is adopting the idea that an RFQ and a quote are message types with required fields, and that the field list is how strangers transact without a bespoke relationship.

Manufacturing already has serious protocols, but they generally start too late for the small shop custom front door. X12, for example, defines and maintains transaction sets that establish the data content exchanged for specific business purposes, which is what makes structured POs and invoices flow between enterprises.  Those transaction sets assume you are already past the “what job is this” moment and into repeatable document exchange, and that usually implies stable identifiers and stable commercial relationships. For a one off RFQ anchored in a drawing and STEP, the painful part is earlier, deciding what the tolerance block applies to, what the inspection plan needs to be, and whether the quoted assumptions will survive the buyer’s expectations. The control point is an RFQ protocol that sits before the EDI layer, then hands clean outcomes into PO level protocols once the job is real.

QIF and MTConnect show the same pattern, useful, real, but downstream. QIF is positioned as an XML based, CAD agnostic standard that defines, organizes, and associates quality information like measurements, part geometry, and PMI, which is powerful once you are in the measurement workflow and producing inspection results.  MTConnect is described as an ANSI standard semantic vocabulary for manufacturing equipment data, providing structured, contextualized data without proprietary formats, which helps once the job is running and you want equipment state and telemetry.  Neither one solves the moment when an estimator is staring at a drawing and STEP and trying to determine what is quoteable, because the problem is missing intent, missing acceptance criteria, and missing revision discipline. The control point is still the RFQ packet and the quote package, not the CMM report export or the machine data feed.

Implications

If the protocol sits at the intake, you can measure the real bottleneck instead of guessing at it. Acknowledgement time becomes a metric because “acknowledged” is a state, not a feeling, and the RFQ record can distinguish no response from active rejection. Clarification cycles become countable because “clarification requested” is a state tied to a specific missing field like revision lock, cert packet requirement, or inspection plan. Quote to award improves because the buyer receives quotes that share a structure, each quote PDF names the same assumptions, and the PO can reference the same revision locked drawing and STEP. The control point is a weekly report that ties acknowledgement time and clarification count back to specific RFQ packet gaps.

Shared signals also become feasible, and that changes selection pressure in the market. If on time shipment, inspection report completeness, and NCR closure time are tied to artifacts like the traveler, the CMM report, and an NCR closure code, then performance becomes legible across strangers. That creates a predictable counter pressure, participants will try to game any signal that is cheap to fake, which is why protocols must prefer receipts over self attestation. When the closeout packet includes a cert packet, the inspection report, and any NCR with a closure artifact, the system can reward execution without asking anyone to trust a claim. The control point is the closeout packet itself, because it is where disputes either converge or metastasize.

Outro

If the United States wants manufacturing sovereignty, it has to reduce the cost of working with strangers, because domestic capacity does not matter if the interface is too expensive to use. The failure mode is ambiguity that turns into latency, then turns into distrust, then turns into silence on the next RFQ, and it shows up in the RFQ record as unanswered requests and endless clarification loops. Verticalized platforms demonstrate the core truth, markets scale when the request is machine checkable and the states are explicit, even when the buyer is imperfect. The next paper should drill into verification and receipts, because protocols only hold when identity and performance signals are anchored to artifacts like the PO, traveler, inspection report, and NCR closure.

Questions to Ask

1. When an RFQ arrives with a PDF drawing and a STEP, where is revision lock recorded, and can you prove later that the quote PDF referenced that exact rev letter. If you cannot, which part of your RFQ record or email thread is acting as the substitute.
2. Do you require an “acknowledged” state on every RFQ, and can you report median acknowledgement time from the RFQ record. If not, how many RFQs die as silence, and how often do you learn that only after a buyer calls back about the same drawing.
3. Which fields create the most clarification churn today, precedence, tolerance block interpretation, inspection plan, finish, or cert packet requirements. Can you tie each clarification to a named missing field in the RFQ packet instead of letting it live in an email thread.
4. Does every awarded job produce a closeout packet that includes the traveler, the inspection report or CMM report if required, and any NCR with a closure code. If that packet is missing, where do disputes actually originate, and how long do they stay open.
5. When you price assumptions, do you record them explicitly in the quote package, and does the PO acknowledge them by referencing the same revision locked drawing and STEP. If you do not record assumptions, are you actually pricing risk, or are you hoping the tolerance block and tribal knowledge will save you.