
Thank you for registering
June 2026
Most make-or-buy decisions get anchored on a single supplier quote or an in-house gut estimate. A disciplined, component-level cost approach makes the choice transparent and defensible.
Looking to subscribe to our newsletter? Click here.

Make-vs-buy is one of the highest-stakes sourcing decisions a manufacturer makes. Bring a component in-house and you commit capital, capacity, and years of operating attention to it. Outsource it and you trade control for flexibility and pay for someone else's margin. The choice shapes your cost structure long after the spreadsheet that justified it has been forgotten.
It also tends to get made on thin cost data. Most make-or-buy calls anchor on whatever number is easiest to reach: the incumbent supplier's latest quote, or an in-house estimate assembled from gut feel and a few analogous parts. Both are guesses wearing the costume of analysis, and the decision they drive can lock in millions of dollars of cost structure.
The first discipline is knowing when the question deserves a full cost workup. Make-vs-buy earns the effort when a component is strategic, the spend is material, there is a real capability or capacity question, or supply risk is concentrated. It is a distraction when the part is a low-spend commodity served by a competitive supply base. There, the answer is almost always buy, and the modeling effort belongs on the parts where the decision is genuinely live.
One clarification keeps this analysis honest. Make-vs-buy is a different question from choosing between two suppliers. Comparing one vendor against another is a make-vs-make problem with its own playbook, which we have covered separately. Make-vs-buy asks something harder: whether the work should sit inside your four walls at all. That reframing changes which costs matter, because your own capacity, capital, and overhead now sit on the table next to a supplier's price — and they rarely get modeled with the same rigor as the quote does.
When teams estimate the cost to make a component in-house, they tend to model the obvious inputs (material and direct labor) and skip the ones that decide the outcome:
A thin make-side model quietly mis-prices the decision, and the cost of that error is not the hours someone spent in Excel. It is the capital committed to a line that should never have been built, or the savings forgone when a sound in-house case got waved off because the estimate looked worse than it was.
A supplier quote is a price, not a cost. It tells you what the supplier wants to charge, with their margin, their overhead, and their assumptions folded invisibly inside. Treating that quote as the buy-side truth is where most make-vs-buy analyses go wrong.
A disciplined buy-side view starts from a should-cost basis — a bottom-up estimate of what the component should cost from materials, process, labor, and overhead — and compares it to the quoted will-cost. The gap between them is the supplier's margin and the room you have to negotiate. The buy case also has to account for the lead-time premium, scale tiers that change unit price at different commitments, and the switching cost of moving away from an incumbent later. A quote shows none of that on its own. The should-cost basis is what turns a single number into a decision you can defend.
The make-or-buy answer is rarely a single number. It moves with the assumptions behind it, and the assumptions that move it most are not the ones teams usually test.
Upstream supply is the first. A buy decision that looks clean at tier-1 can hide a sole-source material or a geographically concentrated input two tiers up — exposure that belongs in the cost case, not just the risk register. Geography is the second: where a part is made changes labor rates, logistics, and duty exposure enough to flip the decision. Process is the third, and it is the one teams skip — on the make side, choosing between stamping and machining, or between casting and billet, can swing the in-house cost more than the make-or-buy framing itself.
This is where modeling at speed earns its keep. When you can vary process, geography, and supplier across a single component and see each result side by side, make-vs-buy stops being one fragile estimate and becomes a transparent comparison. Volume sits underneath all of it as an assumption the model holds — typically a high-volume basis you then refine for overhead and labor — rather than the only lever anyone touches.
Take a machined aluminum bracket currently bought from a single supplier. The buy path looks simple: take the quote, apply the annual volume, done. A should-cost view reframes it. Modeled from material, machining time, and overhead, the part's should-cost comes in below the quote, which means the standing decision to buy is really a decision to fund supplier margin that was never examined.
The make path is where process choice decides everything. Machining each bracket from solid billet is tooling-light but slow and material-heavy. Switching to a near-net casting with a light finishing pass cuts material and cycle time but adds tooling capex that only pays back above a certain volume. Modeled as one number, the make case looks unattractive. Modeled across both processes, a credible in-house path appears that the single estimate would have buried.
Seeing both paths transparently is the point. With a platform like Muir, a cost engineering team builds the component-level model straight from the Bill of Material (BoM) — Muir's BoM comprehension structures the incoming file, and a product twin fills the gaps where supplier detail is missing — then varies process, geography, and supplier to see where each path wins. What used to take a quarter of back-and-forth becomes a working model in minutes, which is what makes testing the make-or-buy question across real alternatives practical instead of theoretical.
If your make-vs-buy calls are still anchored on one supplier quote and an in-house gut estimate, the gap between those two numbers is margin you cannot see and capital you might be misallocating. Component-level should-cost modeling closes that gap and makes the decision defensible to finance, engineering, and procurement at the same time. Book a Muir demo to see how it works on your own components.
A make-vs-buy analysis compares the total cost of producing a component in-house against the cost of sourcing it from an external supplier. A disciplined version models both paths from the bottom up so the two numbers are truly comparable, rather than weighing a real quote against a rough internal guess.
On the make side, teams underestimate capex and tooling amortization, capacity opportunity cost, and overhead absorption. On the buy side, they overtrust a single supplier quote and miss supplier margin, lead-time premiums, scale tiers, and the cost of switching away from an incumbent later.
Should-cost modeling replaces the incumbent quote with a bottom-up estimate of what a component should cost from materials, process, labor, and overhead. That gives the buy path a defensible basis and lets it be compared directly with a bottom-up make estimate, instead of setting a real quote against an internal guess.
Revisit when volumes change materially, when a supplier contract is up for renewal, when input costs move, or when a design change alters the process or material. A make-vs-buy decision rests on assumptions that age, so it is worth re-testing rather than treating as permanent.