Which Comes First: Should Cost Accuracy Or The Supplier’s Quote? Three Myths About Your Cost Accuracy Debunked

Key Takeaways:

• Most procurement teams evaluate should cost by how closely it matches the supplier’s quote, but that inverts the process. The right should cost estimate measures the supplier’s accuracy, not the other way around
• Precision expectations must match design maturity. Early-stage estimates are directional signals; late-stage estimates are negotiation anchors. Conflating the two erodes trust in a tool that’s actually performing as designed
• aPriori doesn’t just close the gap. It changes the conversation. By providing an independent, defensible cost baseline, it shifts procurement from reacting to supplier pricing to interrogating it by material, region, margin, labor, and more

The Full Article

These are all quotes taken directly from real conversations with manufacturers:

“I should be able to get a precise should cost that matches the supplier quote for negotiations.”

“Our organization has no consensus on how to define “should cost”.”

“Supplier quotes are good enough to obtain directional cost information. It doesn’t have to be exact, but we would like estimates within 10–15% of actual supplier quotes to be actionable for strategic sourcing decisions.”

“We only need aPriori for comparing percent differences between scaling methods and pattern recognition, since it’s impossible to get accurate costs. Our costs are “so far off” that it would be “a dream state” to achieve “15–20% accuracy to challenge suppliers”.”

Read those four quotes again. At first glance, they sound reasonable, even pragmatic. But look closer, and you’ll find four different organizations, each wrestling with should cost precision in their own way. Moreover, each is making the same fundamental mistake: they’re evaluating their should cost tool by the wrong standard.

They are not the outliers. They represent a near-universal misconception that has quietly undermined procurement’s negotiating power for years.

Everyone agrees should cost is useful. The myth surrounding it concerns what precision actually means, and what it should be measured against.

The Myth of the Matching Number

The most persistent myth in should cost is also the most seductive: that a good should cost estimate is one that closely matches the supplier’s quote.

It sounds logical. You run your analysis, the supplier sends their number, and you compare the two. If they’re close, the tool works. If they’re far apart, the tool is wrong, and the supplier must be right. This logic is flawed, and in fact, the exact opposite is true.

Suppliers can alter the margin they add to the quote based on how much they want the business. If they are busy, or the job seems complex or high-risk, they can charge more. aPriori’s should cost is a precise, consistent number, based on the inputs. During design, accuracy may be lacking because some things are not fully defined. But aPriori’s should cost can be cultivated as the designs develop, with the controls and additions available to be included along the way.

When procurement teams treat the supplier’s quote as the benchmark for should cost accuracy, they’ve already conceded the negotiation before it starts.

They’ve handed the supplier the role of arbiter. And they’ve turned a powerful analytical tool into little more than a validation exercise for someone else’s pricing.

The four quotes above each reflect a different stage of this same trap.

One team envisions a 15–20% accuracy threshold; a number they openly call a “dream state.” Another can’t even agree internally on what “should cost” means. A third leans on supplier quotes for directional guidance. And finally, a fourth has reduced aPriori’s role to pattern recognition because they’ve given up on accuracy altogether.

None of these teams is asking the right question. It is not: “Does my cost match the supplier’s quote?” It’s: “Does the supplier’s quote reflect what the part should actually cost to produce?”

The Problem with Accuracy: It’s Defined the Wrong Way

Should cost accuracy isn’t a fixed bar. It shifts depending on where you are in the product lifecycle, and conflating the two is where most procurement teams lose their footing.

In early design stages, a should cost estimate functions as a directional signal. It tells engineers and sourcing teams whether a design is heading toward a commercially viable cost before tooling is cut and commitments are made.

At this seminal point in product development, one customer found aPriori estimates within 9–10% of final supplier quotes, an outcome they correctly described as a high-value “early predictor.” Another company took it further: A sheet metal team achieved estimates within a dollar of actual cost. Not a percentage range. One dollar.

These are not failures of precision. These are exactly what a well-calibrated should cost tool delivers.

But a different expectation takes over in late-stage procurement, when designs are locked in, and suppliers begin quoting. Now, the same estimate, generated by the same tool and using the same methodology, is held to a different, often tacit standard.

Suddenly, “directional” becomes “wrong”. Preliminary becomes unacceptable. And the supplier’s quote, with all its opaque assumptions baked in, gets treated as truth.

The issue isn’t whether aPriori is accurate. It’s a product cost clarity gap. Customers want two different things: an early-stage directional signal and a late-stage defensible should cost.

However, they don’t always recognize that commingling them actually distorts both. When teams use early-stage estimates to make late-stage supplier challenges without adjusting their expectations, they undermine trust in a tool that was performing exactly as designed.

What Actually Drives the Gap Between Estimates and Quotes

Before dismissing a should cost estimate that doesn’t align with a supplier’s number, procurement teams need to ask a harder question: “Why is the supplier quoting that pricing in the first place?”

While most suppliers are well-intentioned, there are various scenarios that can inadvertently or unduly influence their quotes:

• Volume mismatches. You may require 10,000 units, but the supplier’s minimum production run is 25,000, and that assumption is baked into the price without being stated.
• Third-party production. The part may be manufactured by a subcontractor, with a margin added at each handoff before the quote reaches you.
• Regional discrepancies. Where the part is actually made or shipped from may differ significantly from the region your estimate assumed. What’s more, it could include other unaccounted-for price variances, such as tariffs or higher fuel costs.
• Inflated profit margins. The supplier may factor in a higher margin than your model or than market conditions warrant.
• Material conflicts. The supplier’s material assumptions may differ from your specification, either by interpretation or by substitution.
• Outdated historical pricing. If you’re benchmarking against legacy data, you may be comparing costs that no longer reflect current market realities.

Given how significantly each of these variables can shift a quote, why would you take a supplier’s pricing at face value, let alone allow it to override your own analysis without further consideration?

None of this means the supplier is acting in bad faith. But it does mean their quote is not absolute. It’s an output shaped by a set of inputs that may have nothing to do with what the part should cost to make.

This is precisely the terrain where should cost precision creates value. Not by matching the quote, but by giving procurement a defensible, independent basis from which to interrogate it.

Flipping How It’s Framed: Should Cost as the Measure, Not the Measured

aPriori was not built to validate supplier quotes. It was built to replace the need to rely on them unquestioningly. The shift requires a counterintuitive but essential approach.

Instead of asking, “Is our should cost close enough to the supplier’s quote?”, procurement teams should ask, “Is the supplier’s quote consistent with what we know this part should cost?” The should cost estimate becomes a measure of the supplier’s accuracy, not the other way around.

This reframing changes everything about how supplier negotiations unfold. When a procurement team walks into a negotiation anchored in their own should cost estimate rather than scrambling to reverse-engineer the supplier’s logic, they negotiate from a position of knowledge.

They can pinpoint specific discrepancies in cost drivers, such as volume assumptions, regional cost differentials, and material choices, and address them directly. The conversation shifts from “Why is your quoted price so high?” to “Here’s what we believe this part should cost to produce and why.”

That is a fundamentally different negotiating posture. And it’s one that even a directional should cost estimate can support if the team has the discipline to use it correctly.

What aPriori Actually Enables

aPriori’s automated should cost capabilities are built around the full manufacturing cost stack: raw materials, labor costs, overhead, manufacturing processes, and regional cost factors. aPriori’s should cost models how costs behave across different production volumes, scale with design changes, and track cost evolution as a product matures from concept to production release.

This means aPriori can do several things no supplier quote can do on its own:

• It establishes an independent cost baseline. Before the first RFQ is sent, procurement and engineering teams can align on a credible cost target, and one that is grounded in manufacturing realities, not commercial assumptions. This baseline then serves as the foundation for every subsequent conversation.
• It identifies the specific drivers of cost. When a supplier’s quote comes in higher than expected, aPriori flags the gap and helps explain it. Is the difference in material cost? Cycle time assumptions? Regional labor rates? Scrap factors? Knowing the source of a discrepancy is the difference between a productive discussion and having negotiation leverage, and a stalemate.
• It creates consistency across the organization. One of the four opening quotes described an organization with no shared definition of should cost. aPriori solves that problem structurally. A central platform, shared inputs, and consistent methodology produce a standard vocabulary that engineering, procurement, and finance can all work from.
• It connects early savings identification to late-stage confirmation. For teams concerned about whether preliminary cost reductions actually materialize, aPriori provides the thread. Early-stage estimates flag where savings opportunities exist. Late-stage should cost analysis confirms whether they were captured. The tool tracks cost across the design lifecycle rather than producing a single static number.
• It calibrates expectations to design maturity. Rather than applying an identical standard to every estimate, aPriori can reflect the confidence level appropriate to the design stage. An estimate produced on a concept-phase CAD model carries different precision than one run on a finalized production design. Teams that understand this distinction use both more effectively.

The Real Dream State

The procurement team that described 15–20% accuracy as a “dream state” was not wrong to want better. However, the assumption that greater accuracy was out of reach was incorrect.

The data actually proves that aPriori users who apply the tool consistently and interpret its outputs correctly, across the full design lifecycle and with an understanding of what the estimate represents at each stage, don’t settle for 15–20% accuracy. They achieve estimates within single-digit percentages of final supplier quotes at early design stages.

They come to negotiations with a cost position that suppliers simply can’t dismiss. Finally, they develop the institutional confidence to treat their own analysis as the starting point rather than the supplier’s number.

Begin by asking what a part realistically should cost before getting the supplier’s quote. Then use that answer as the starting point in negotiations. Doing so is the difference between a should cost program that validates supplier pricing and one that challenges it.

That’s not a dream state. That’s a methodology.