This Will Commoditize Us

The fear

A shop spends years earning the right to charge more. It buys the CMM, trains inspectors who can read a difficult print, builds fixture discipline into the traveler, keeps outside processing under control, and learns the expensive lessons that keep NCRs low and cert packets clean. Then a portal lands in the estimator's inbox asking for two fields — price and lead time — with a PDF drawing attached and nowhere serious to explain an assumption, flag a risky tolerance, or say why this job is not the same job as the cheaper quote that will appear one row below. That is the commoditization fear in plain language. All the discipline stored in the inspection plan, the quality record, and the delivery history gets erased, and what survives is a number in a spreadsheet.

I hear this objection more than almost any other, and the people making it are usually the best operators in the room.

The broader promise of this series is that American manufacturing gets stronger when coordination gets better, because better coordination lets buyers send the right package, reach the right suppliers, and measure the right behavior. My claim here is bounded and falsifiable: when a coordination system preserves technical context, records execution history, and routes work by risk and complexity, it makes good shops less interchangeable, not more, because the evidence that separates them survives into source selection and repeat award decisions. Everything turns on the difference between a marketplace that reduces a job to a price contest and a coordination layer that preserves the work package, the supplier record, and the consequences of bad execution.

Why a smart shop believes this

The objection is strong because most digital sourcing systems have trained suppliers to expect the worst. A shop owner has seen the portals where the buyer is hidden, the RFQ packet is thin, and the award disappears into silence with no clue whether the job was lost on price, on lead time, on a cert requirement, or on somebody simply misreading the drawing set. In that environment, the estimator who studies the rev block, catches the missing finish note, and asks whether a first article is required looks slower and more expensive than the bidder who throws out a low number and sorts out the damage after the PO.

That is not paranoia. It is a rational read of the incentives inside a badly designed system. If the only structured fields on the quote sheet are price and days, those two fields will dominate the decision even when the real job depends on tolerance competence, inspection maturity, outside process control, and schedule discipline. A portal that strips the RFQ down to a price box and a promised date does something worse than fail to show supplier quality. It actively suppresses the evidence that would let a buyer tell a safe quote from an optimistic one.

When the objection is correct

Under weak design, the objection is correct. A system that treats suppliers as interchangeable, hides their operating history, and compares quotes as though every bidder is describing the same work will commoditize good shops. A complex part with a difficult datum scheme, special process notes, and a meaningful first-article requirement becomes falsely equivalent to something much simpler, because the comparison threw away the inspection plan, the cert burden, and the actual consequences of getting the job wrong.

That is how bad sourcing systems manufacture false competition. The cheap quote looks attractive precisely because the system discarded the context needed to judge whether the quote is grounded in reality. The buyer sees a spreadsheet row. What the buyer does not see is that one supplier noticed the print calls for tighter process control, accounted for the cert packet, and built real inspection time into the route, while another priced the job as if none of that existed. In that design, commoditization is not a fear anyone should have to argue about. It is the operating model.

How the bad version fails

Price is the easiest field to sort, and that is the whole problem. Once a buyer has twenty responses on a quote sheet, the temptation is obvious: start at the cheapest line, glance at lead time, and assume the attached drawing PDF means everyone quoted the same job. Drawing packets rarely speak for themselves. The differences that matter usually live in the gaps between the files, the notes, and the assumptions nobody wrote down.

A supplier who underestimates a tolerance stack, ignores what a surface finish implies, or fails to account for outside processing can look competitive at quote time and turn expensive right after award. The cost comes back in an uglier form — a late ship date on the schedule board, a missing cert in the packet, a nonconformance that triggers containment, an argument over scope when the traveler finally reaches the floor. A price-led system pays suppliers to hide uncertainty until it becomes someone else's problem, which is exactly the behavior a serious buyer is trying to avoid.

The damage is measurable. You see it in late quote conversions, higher clarification count after award, more revision churn, more expedite requests, dirtier cert packets, more NCRs, and lower repeat award rates on the jobs that looked cheapest on day one. If the platform cannot connect any of that back to the original RFQ record and the assumptions in the winning quote, the buyer learns nothing and the same thing happens again next quarter.

What buyers actually do when the work matters

Serious procurement teams do not really believe suppliers are interchangeable. They will tolerate that fiction for simple repeat work and abandon it the moment risk rises. A laser-cut bracket with stable specs and no unusual inspection burden is one thing; a machined part with tight concentricity, special process control, and customer-required documentation is something else, and every buyer I have met knows the difference.

That is why real sourcing organizations segment suppliers by complexity, quality risk, criticality, and delivery consequence, formally or informally. The approved vendor list, the preferred supplier table, the private notes in the buyer's spreadsheet, the unwritten memory of who returns a clean cert packet — all of it points at the same reality. Source selection is already governed by more than price. Buyers care about supplier differentiation; their tools are what fail to preserve it in any structured way.

The governed version, and why it weakens the objection

A governed coordination system changes the comparison itself. It keeps the RFQ packet intact, preserves supplier identity, records clarifications against the drawing set, and stores what happened after award — delivery performance, dispute frequency, paperwork completeness. The buyer stops choosing among abstract numbers and starts choosing among suppliers whose actual operating behavior is visible in the record.

In that system a good shop differentiates harder, because its discipline leaves receipts. The estimator who flags a missing inspection requirement before quote submission, the quality lead who asks for the correct cert expectation, the scheduler who gives a realistic date instead of a fantasy date — every one of them improves the record the buyer sees. Those behaviors become part of the sourcing memory tied to the supplier and the work package, and that memory is what makes future awards safer and more rational.

The deciding mechanism is structured visibility. When the system can see the clarification log, quote completeness, on-time delivery against promise, NCR rate, cert packet completeness, and repeat award rate by work type, competence becomes legible. A shop that reliably handles hard jobs stops competing on its price field alone and starts competing on measured evidence that it can do the work without creating downstream damage.

Control points that keep it from drifting

None of this survives without real control points. The first is routing by complexity and risk, so that not every RFQ collapses into a flat contest. Work with real inspection burden, regulatory exposure, or special process requirements belongs in lanes that reflect those facts. A commodity lane for a complex job is bad governance wearing an efficiency costume.

The second is keeping the work package and the supplier response together. The drawing set, the revision state, the assumptions in the quote, the clarification thread, and the promised date all have to stay attached to the award record. Break that link and a later failure on the schedule board or in the cert packet can never be traced back to what the supplier actually said at quote time.

The third is consequence. A supplier that chronically quotes fast and cheap and then creates rework, misses delivery, or ships incomplete paperwork has to get throttled — through routing rules, lower trust for similar work, or reduced visibility into higher-risk RFQs. A supplier that consistently returns complete quotes, flags risk early, and performs cleanly should get repeat awards and access to better-fit work. Without consequence, the record is decoration.

What this means

So the fear of commoditization turns on design, not on the existence of structure. A bad system absolutely will flatten suppliers and drag good shops into a race toward the cheapest visible field; I would be making the same argument from the shop's side of the table. A governed system does the opposite, because it preserves the evidence buyers already reach for when the work really matters.

That matters well beyond one portal or one RFQ. A country does not rebuild industrial depth by driving its most capable suppliers into blind quote contests that ignore quality history, paperwork discipline, and delivery reliability. Depth comes from making those things visible and portable across company boundaries, so the shop that actually controls process, reads the print carefully, and delivers against the traveler gets more of the right work. Flattening is the failure mode, and it is worse than it looks: it destroys trust and pushes serious buying back into closed relationships and private memory that never scale past the people holding them.

The next objection comes straight out of that. Once a system starts preserving more context and applying more consequence, someone is going to ask who sets those rules — and who keeps them from being captured.

Questions to Ask

1. When we compare quotes, which fields actually drive the award, and which of those fields are tied to the RFQ packet, the clarification log, or the supplier's documented assumptions?
2. Do we have formal routing rules that separate simple repeat work from high-risk work, or are buyers making those distinctions ad hoc in email and spreadsheets?
3. Can we measure quote completeness, on-time delivery against promise, cert packet completeness, and NCR rate by supplier and work type, or are those judgments still anecdotal?
4. When a supplier loses work, can the system tell whether the issue was price, lead time, missing capability, weak paperwork history, or poor response behavior?
5. If a supplier repeatedly wins with aggressive pricing and then causes rework, delay, or documentation problems, what throttle or consequence actually changes its future visibility?
6. Are we building a sourcing system that reveals competence, or one that hides it behind a lowest-price sort order?