How Should-Cost Analysis Is Rewriting the Rules of Supplier Negotiation
How Should-Cost Analysis Is Rewriting the Rules of Supplier Negotiation
Every procurement team has been there: a supplier sends a quote, you push back 5–10%, they agree, and everyone shakes hands. It feels like a win.
It usually isn't.
Without should-cost analysis, you have no way to know whether that final price reflects actual manufacturing economics or just how far the supplier was willing to move on the day. In defence, aerospace, and precision manufacturing, where a single machined component can carry $2,500–$25,000 of hidden margin, that gap matters enormously.
This article explains what should-cost analysis is, how it works in practice, and why forward-thinking OEMs and Tier-1 suppliers in India are treating it as a core procurement discipline rather than an optional finance exercise.
What Is Should-Cost Analysis?
Should-cost analysis is a structured method for estimating what a part or assembly ought to cost based on its actual design, materials, manufacturing processes, overhead, and reasonable profit. The result is an independently derived target cost built from engineering logic, not vendor pricing.
A proper should-cost model breaks cost down into its real components:
- Raw material cost: grade, form factor, weight, buy-to-fly ratio
- Process cost: machining time, setup, tooling, number of operations
- Labour cost: operator grade, cycle time, regional wage rate
- Overhead: machine depreciation, facility cost, utilities
- Scrap and rework allowance: based on process capability and complexity
- Supplier margin: reasonable profit for the process type and volume
When you build this bottom-up, you get a defensible number. Not a wish. Not a benchmark from a catalogue. A cost that reflects what it should actually take to make that part.
Why Conventional Supplier Negotiation Falls Short
Traditional procurement negotiation relies on three weak levers:
- Competitive quoting: works only if you have enough qualified suppliers and time to run a proper RFQ process
- Year-on-year price reduction targets: often arbitrary, and resisted hard by suppliers who have already tightened margins
- Benchmarking against similar parts: useful directionally, but rarely specific enough to hold up in a negotiation
None of these give you a cost floor. Without knowing what a part should cost, you're negotiating from a position of informational asymmetry. The supplier knows their cost structure. You don't.
This problem is especially acute in:
- Defence manufacturing: parts often have single or dual qualified sources, making competitive tension low
- Aerospace and space: tight tolerances and stringent material certifications limit the supplier pool
- Precision machining: process complexity makes it easy for suppliers to hide margin inside cycle-time estimates
How Should-Cost Analysis Shifts the Negotiation Dynamic
When you arrive at a negotiation with a well-built should-cost model, the conversation changes completely.
Instead of "your quote is too high, can you do better?", you're saying: "Based on our analysis, the material cost for this Inconel 718 forging is approximately $X, 5-axis machining at your setup time should run $Y, and your overhead at this volume is likely $Z. Our target price is $[Total]. Walk us through where our assumptions differ."
That's a different meeting. The supplier can't simply say "that's our price." They have to engage with your numbers.
This does three things:
- It exposes genuinely inflated margins you'd never have caught otherwise
- It creates a collaborative frame: you are analysing costs together, not making accusations
- It builds long-term supplier trust, because data-driven conversations are less adversarial than percentage haggling
Real-World Example: Titanium Structural Bracket for a Space Programme
Consider a supplier quoting ~$5,000 per unit for a titanium bracket used in a satellite structural assembly. A should-cost model built from the drawing and process route might reveal:
- Material: Ti-6Al-4V billet at current LME-linked prices: $1,000
- Machining (5-axis, 3 setups, 14-hour cycle): $1,300
- Inspection and certification (AS9100 compliance, CMM, FAI): $500
- Overhead at standard absorption rate: $650
- Reasonable margin (15%): $525
Should-cost total: ~$4,000.
That's a ~$1,100 gap per unit. At a programme quantity of 200 units, you have just found ~$220,000 in recoverable savings, with data to back every dollar of it.
Should-Cost Analysis in Defence and Aerospace: Why It's Different
Commercial procurement can often lean on market forces to keep pricing honest. Defence and aerospace manufacturing in India operates differently:
- Limited qualified sources. DRDO, ISRO, HAL, and private defence OEMs often have 2–3 qualified suppliers for critical components. Competition alone won't give you fair pricing.
- Long-term contracts. A component priced 15% above should-cost on a 5-year contract compounds badly.
- Offset and indigenisation pressures. As India pushes deeper into self-reliance under Atmanirbhar Bharat, OEMs are qualifying new domestic suppliers who may not have mature cost structures. Should-cost analysis helps you price development partnerships correctly from the start.
- DPSU audit expectations. Defence public sector units and their Tier-1 partners are increasingly required to justify procurement costs. A should-cost model is an auditable artefact, not just a negotiating tool.
Example: Qualifying a New Domestic Supplier for a Defence Sub-Assembly
An OEM qualifying a new MSME for a hydraulic manifold block used in an armoured vehicle programme has no historical pricing to reference. Should-cost analysis using the supplier's proposed process route, local material sourcing, and labour rates gives the OEM a fair cost target, ensuring the supplier earns a viable margin without embedding excess cost into the programme baseline.
This isn't just about saving money. It's about building a supplier relationship on a shared understanding of economics.
The Manufacturing Cost Breakdown: What to Model and How
A rigorous should-cost model for a precision-manufactured part typically includes these layers:
1. Design-Driven Cost Inputs
- Part geometry complexity (derived from CAD/drawing)
- Tolerances, GD&T callouts, surface finish requirements
- Material specification and grade
- Part weight and buy-to-fly ratio
Modern CAD to Cost tooling can pull most of these inputs directly from the 3D model, turning a multi-day modelling exercise into a same-day estimate.
2. Process Cost Modelling
- Operation sequence (turning, milling, grinding, EDM, etc.)
- Machine type and hourly rate by process
- Setup time and changeover
- Tooling cost allocation
3. Overhead and Burden
- Machine absorption rate (depreciation, maintenance, utilities)
- Factory overhead (floor space, supervision, quality systems)
- Volume-adjusted burden: costs that shift as quantities change
4. Supplier-Side Variables
- Location-based labour rates (Tier-2 city MSME vs. large precision shop)
- Certifications held (AS9100, NADCAP), which carry real overhead costs
- Capacity utilisation: a supplier running at 60% has different economics than one at 90%
Where Should-Cost Software Changes the Game
Building a should-cost model manually in Excel works for one part. It doesn't scale to a programme with 300 unique part numbers, or to a sourcing cycle that needs to move in weeks, not months.
Should-cost software that integrates with CAD, PLM, and supplier data can:
- Auto-extract geometry parameters and material specs from 3D models
- Apply current material prices (LME, domestic market indices)
- Run process simulations to estimate machining time
- Generate a cost breakdown automatically, ready for review and refinement
- Track cost variance across revision cycles, so you know when a design change shifts should-cost materially
For cost engineering teams at OEMs managing multiple simultaneous programmes across space, defence, and commercial work, this shift from manual modelling to AI cost estimation is the difference between should-cost as a project and should-cost as a standard practice.
Common Mistakes in Should-Cost Analysis
Even well-intentioned teams get this wrong. Here's what to avoid:
1. Using catalogue or index prices for everything. Material prices vary by supplier, form, certification level, and lot size. A should-cost model that uses LME spot price for aerospace-grade aluminium without accounting for certified billet premium is going to be off.
2. Ignoring supplier overhead realities. An MSME with NADCAP certification for special processes carries real overhead that a non-certified shop doesn't. Your model needs to reflect the right overhead tier for that supplier, not the cheapest option available.
3. Treating should-cost as a one-time exercise. Parts evolve. Designs change. Material prices move. A should-cost model that isn't updated through the product lifecycle becomes stale and unreliable fast.
4. Using it as a hammer, not a conversation. Should-cost is most effective when shared with suppliers as a collaborative tool. Presenting it as a take-it-or-leave-it demand tends to damage relationships and doesn't surface the real cost levers.
5. Not tying it to supplier intelligence. The most accurate should-cost model still needs to be calibrated against what you know about a specific supplier's actual capabilities and cost structure. General assumptions won't reflect the economics of a specific shop floor.
Building a Should-Cost-Based Supplier Negotiation Strategy
Here's a practical approach for OEM procurement and cost engineering teams:
- Select target parts: prioritise high-spend, single-source, or high-complexity components
- Build the should-cost model bottom-up, using design data and current market inputs
- Run a sanity check: compare against historical actuals and similar part families
- Identify the gap: quantify the difference between should-cost and current or quoted price
- Prepare the negotiation brief: document your assumptions, sources, and reasoning, and be ready to show your work
- Engage the supplier: share your model, invite challenge, and focus on cost drivers rather than just final numbers
- Close with a documented agreement: price adjustments should trace back to specific cost elements, not just a percentage move
- Revisit at design freeze and production transitions: update should-cost whenever design or volume assumptions change
Frequently Asked Questions
What is should-cost analysis and why does it matter for OEMs?
Should-cost analysis is the process of estimating what a manufactured part should cost based on its materials, processes, overhead, and a reasonable supplier margin, independently of what a supplier actually quotes. For OEMs in defence, aerospace, and precision manufacturing, it removes the informational asymmetry in supplier negotiations and enables cost decisions grounded in engineering logic rather than market positioning.
How is should-cost analysis different from cost benchmarking?
Benchmarking compares a price against historical or market data for similar parts. Should-cost analysis builds cost from the bottom up, covering geometry, process, material, and labour, for the specific part in question. Benchmarking tells you if a price looks unusual. Should-cost analysis tells you exactly where it's unusual and why.
What data do you need to build a should-cost model?
At minimum: part drawing or 3D model, material specification, process route (or an assumed process route based on features), machine hourly rates for the relevant processes, current material prices, and a reasonable overhead and margin assumption. More accurate models also incorporate supplier-specific data like location, certifications, and capacity.
Can should-cost analysis be applied to defence and space manufacturing components?
Yes, and it is particularly valuable there. Defence and space components often have small supplier pools and long contract durations, which limits competitive pressure. A bottom-up should-cost model gives procurement teams an objective cost floor that holds up under audit and supports fair-pricing discussions even in single-source situations.
How does should-cost analysis support supplier negotiation strategy?
It gives buyers a data-backed target price and a detailed cost breakdown they can table in negotiations. Instead of bargaining by percentage, both parties can discuss specific cost drivers: material grade, cycle time, and overhead assumptions. This tends to surface real savings opportunities and produce more durable pricing agreements.
What role does AI cost estimation play in should-cost analysis?
Manual should-cost modelling is time-intensive and doesn't scale well across large part catalogues. AI cost estimation tools can auto-extract geometric and material parameters from CAD files, apply live market pricing, and generate should-cost breakdowns in a fraction of the time. For OEMs running multiple concurrent programmes, this makes should-cost analysis practical as a standard workflow rather than a periodic project.
How often should should-cost models be updated?
Should-cost models should be updated at major design milestones, when material prices shift significantly, when production volumes change, and before any contract renewal or re-negotiation. Treating should-cost as a living document rather than a point-in-time estimate keeps it useful across the full product lifecycle.
Conclusion
Should-cost analysis closes the knowledge gap that makes supplier negotiations feel like guesswork. When you know what a part should cost, not just what a supplier is asking, you negotiate from facts, not from hope. For India's defence, aerospace, and space OEMs, where supplier pools are limited and contract durations are long, that difference directly affects programme economics and long-term competitiveness.
The discipline isn't complicated in principle. What makes it hard at scale is the data work: keeping material prices current, modelling process routes accurately, and doing this across hundreds of part numbers without burning out your cost engineering team. That's the problem modern tooling is built to solve.
