Why OEMs and suppliers may need to begin the cost conversation before the RFQ.
Are we sometimes optimizing the cost of an individual part while adding cost and complexity to the overall system?
Cost pressure is real. OEMs and suppliers are both being asked to find savings while protecting quality, launch timing, and production continuity. Piece price matters because it is visible, comparable, and measurable. But it is not the entire cost equation.
A component can appear less expensive on a quote and become more expensive once it enters the operating system. The difference may show up in transportation, inventory, handling, labor, floor space, sequencing, assembly, coordination, or added exposure during launch and production changes.
The cheapest part and the lowest-cost solution are not always the same thing.
Piece price is the amount paid for each unit. Total cost considers what the organization must spend, manage, and absorb to move that unit through the supply chain and into production.
This broader view is often described as total cost of ownership (TCO). In manufacturing, TCO reaches beyond the purchase order to include the work and resources required around the part.
The distinction sounds simple. In practice, the costs are distributed across different teams and budgets. Purchasing sees the quote. Logistics sees transportation. The plant sees handling, labor, equipment, and space. The program team sees launch timing and coordination risk. Each function may be managing a reasonable target while no one decision captures the full operating impact.
A fuller cost view: Part price → logistics → inventory → handling → labor → assembly → floor space → risk → total cost
An RFQ is designed to price a defined requirement. It is not always designed to challenge the operating system behind that requirement.
By the time an RFQ is complete, many consequential decisions may already be set: product architecture, part design, packaging, assembly location, supplier boundaries, logistics flows, and inventory assumptions. Suppliers can compete on the requirement in front of them, but the range of possible system-level improvements has narrowed.
This is not a criticism of sourcing teams. OEM purchasing organizations need clear specifications, comparable bids, firm schedules, and disciplined governance. Suppliers need enough definition to price work responsibly. The issue is timing.
If the first substantive supplier conversation begins after the broader system is locked, alternatives that could remove touches, handoffs, inventory, or plant-side complexity may never enter the evaluation. The organization can negotiate the price of the defined solution, but it may spend the life of the program managing cost that was designed into the process earlier.
Earlier supplier engagement changes the opening question.
Instead of beginning with, "Here is the part. What is your price?" the conversation can begin with, "Here is what we are trying to accomplish. How might we design the system differently?"
That creates room to examine the work surrounding the part, not only the part itself:
Could multiple components be assembled or sequenced as a module closer to the plant?
Could packaging or presentation reduce touches, damage exposure, or line-side handling?
Could a different material-flow model reduce buffer inventory or floor-space demand?
Could shifting an assembly boundary simplify labor or equipment requirements inside the OEM facility?
Could one partner own adjacent steps and remove handoffs or duplicated coordination?
What launch risks could be reduced before start of production?
These questions do not guarantee savings. They create the conditions to find savings that a conventional quote may not reveal.
If cost exists across the operating system, evaluating it requires a cross-functional view. Sourcing, product engineering, manufacturing engineering, plant operations, logistics, finance, and suppliers may each hold a different part of the answer.
A lower number in one column that adds work in three others is not optimization. It is cost transfer.
Before a requirement is finalized, teams can pressure-test the proposed solution with four questions:
What outcome are we optimizing? Is the target piece price, landed cost, plant cost, launch stability, or total program cost?
Where does the work move? Does lowering the part price add transportation, inventory, handling, labor, equipment, space, or coordination elsewhere?
Which decisions are still reversible? Can packaging, assembly responsibility, sequencing, or material flow still be changed?
What are we asking the supplier to contribute? Are we asking only for a quote, or are we using the supplier's operating experience to help shape the solution?
The earlier these questions are asked, the more options remain available.
Some of the most productive commercial vehicle conversations we are having at Emotiv Mobility are happening further upstream, while options are still open.
When Emotiv Mobility is involved early, we can examine assembly, sequencing, material support, logistics, and floor-space realities as connected decisions. The objective is not to give Emotiv Mobility more scope for its own sake. It is to determine whether a different operating model can reduce the total burden on the program.
The objective is not to move cost from one box to another. It is to determine whether cost and complexity can be eliminated altogether.
Sometimes the existing design and supply model will still be the right answer. But the alternative deserves to be evaluated while choices remain reversible.
We are not asking sourcing teams to give up price discipline. We are asking organizations to apply that same discipline to the full system.
The cheapest part may be the lowest-cost solution. It just should not be assumed.
When cost pressure rises, the natural response is to push harder on the most visible number. The more durable opportunity may be one step upstream, before the architecture, operating model, and supplier responsibilities are fixed.
Before the next RFQ becomes final, ask a broader question:
Are we optimizing the part, or are we optimizing the system?
That question may reveal costs that the quote cannot.