R&D procurement: why 70% of product cost is locked before the first RFP

By the time procurement issues a formal RFP for a new product's components, approximately 70–80% of the product's total cost is already locked in. The design specifications, material choices, tolerances, and performance requirements have been frozen by engineering and R&D — often without supplier input. Procurement's job then becomes negotiating the price of decisions already made.

The thesis is uncomfortable but supported by a growing body of empirical evidence: most procurement teams treat product development as a downstream handoff, not an upstream partnership. And the data from a Maastricht University study of 11,000 new product development projects shows that the dimension of supplier involvement that matters most is not timing — it is intensity. Involving suppliers earlier without involving them deeply delivers marginal returns at best.

When cost is determined vs. when procurement is invited

The gap between these two timelines is the single largest source of missed savings in product procurement. The CIPS intelligence framework on early supplier involvement breaks the product development lifecycle into four phases: design, procurement, supplier, and manufacturing. The design phase — where product conceptualization, value analysis of parts, quality targets, and performance ranges are defined — is where cost structure is set. By the time the process reaches the procurement phase, specification decisions are already made (CIPS, 2025).

The procurement phase focuses on utilizing the supplier's specialist skills for price negotiation and determining safety stock levels. These are optimization activities, not structural cost decisions. The difference between designing a product that costs $100 to manufacture and designing one that costs $85 is rarely a negotiation outcome — it is a design decision made with supplier input before the specification was frozen.

The 11,000-project finding: early is not enough

The Maastricht University research, cited by Procurement Leaders, distinguishes between two dimensions of supplier involvement that are routinely conflated:

The moment (timing) of involvement is what most people mean by "early supplier involvement" — bringing suppliers into discussions during early stages of product development. This helps discover new materials, technologies, and potential design-manufacturing interface flaws earlier. It is valuable, but the research shows it is insufficient on its own.

The extent (intensity) of involvement is the delegation of specific engineering and design tasks to knowledgeable suppliers. Rather than absorbing supplier knowledge and designing internally, the buying organization provides functional specifications and lets the supplier design the component. This enables concurrent engineering — buyer and supplier develop solutions in parallel (Procurement Leaders / Maastricht University).

The finding is counterintuitive but robust: projects with extensive supplier involvement — where suppliers own significant portions of the design work — show superior returns in cost reduction, time-to-market, product quality, and market performance. Simply moving the timeline earlier without changing the depth of collaboration does not move the needle.

The automotive and EV example that makes the point concrete

Procurement Leaders provides a concrete example from the automotive industry: the development of an electric vehicle. Because an EV weighs substantially more than a vehicle with an internal combustion engine, the wheels must be redesigned. The question is how that redesign happens:

The extensive approach does not mean losing control. The buyer retains architectural control and interface design. But by delegating component-level design to suppliers with deeper specialization, both cost and development time decrease. The supplier's intellectual property remains with the supplier — the buyer does not need to pay to own knowledge that it does not need to own.

The conditions that make supplier involvement work

The 11,000-project research identifies four organizational conditions that separate companies that succeed with supplier involvement from those that invest in the concept without results:

An Oxford College of Procurement and Supply analysis frames ESI as a primary cost-reduction strategy that most organizations overlook. While negotiation, rationalization, and standardization all contribute to reducing expenses, the most impactful lever — early supplier involvement in design — is the least frequently implemented because it requires cross-functional collaboration between procurement, engineering, and suppliers that most organizations lack the governance to execute (Oxford College of Procurement and Supply, 2025).

What good looks like: the concurrent engineering operating model

Organizations that successfully operationalize supplier involvement in product development exhibit three structural characteristics that their peers lack. First, procurement has a seat at the product development table before the design review, not after. Second, strategic suppliers are identified and engaged during the concept phase, with formal scoping of which design tasks they will own. Third, the cost reduction strategy is explicitly tied to supplier input, not just negotiation leverage.

An empirical study of 80 manufacturing firms, published in Adonis & Abbey Publishers (2023), found that cost reduction strategy mediates the relationship between procurement-phase and manufacturing-phase ESI and firm performance. The same study found that firm size moderates the relationship at the design phase — larger firms are better positioned to convert design-stage supplier input into measurable cost reductions, likely because they have the process infrastructure to manage joint development. For smaller firms, the cost reduction benefits of ESI are more pronounced in the procurement and manufacturing phases (Adonis & Abbey, Vol. 18 No. 2, 2023).

BCG-owned Inverto's 2026 procurement trends analysis identifies supplier-led innovation and early supplier involvement in design as central levers of procurement-driven value creation alongside AI-driven value and resilient supply networks. Procurement's role is to identify emerging technologies, scout new materials, and shape co-development partnerships — activities that cannot happen when procurement enters the product lifecycle after the RFP stage (Inverto, a BCG Company, 2026).

What this means in practice: five actions for procurement leaders

Closing the gap between when cost is determined and when procurement is invited requires structural changes to the product development operating model. These five actions address the root cause, not the symptom:

1. Map your cost-determining vs. cost-incurring timeline. For each major product category, identify when procurement is currently engaged relative to when design specifications are frozen. The gap between these two points is your addressable savings opportunity. Expected outcome: a heat map showing which product lines have the largest timing gap. Week 1–3.
2. Redefine procurement's role in the product development process. Create a formal "R&D procurement" role that participates in design reviews and concept phase meetings. This role is not about sourcing vendors — it is about identifying which design decisions have cost implications and which suppliers should be consulted before those decisions are made. Expected outcome: procurement presence at 100% of design reviews for high-cost categories. Month 1–2.
3. Identify candidates for extensive supplier involvement. For each high-cost component or subsystem, evaluate whether a supplier has deeper design expertise than your internal team. If the supplier does, shift from absorbed-knowledge involvement (early meetings) to delegated-design involvement (functional specs, supplier owns design). Expected outcome: 3–5 components transitioned to extensive involvement model. Month 2–4.
4. Establish joint development governance. Create a framework for co-development that addresses IP ownership, task boundaries, quality gateways, and risk sharing before the project starts. The governance must be in place before the supplier starts design work. Expected outcome: zero projects blocked by unresolved IP or scope questions. Month 2–3.
5. Measure ESI program ROI separately from commodity savings. Track cost reduction attributable to design-stage supplier involvement as a distinct KPI from negotiation savings. This prevents the savings from being buried in aggregate numbers and builds the case for expanding the program. Expected outcome: a clear line item in the savings report showing "Design-stage ESI savings: X%." Month 3 onwards.