Mondelez International — Cadbury, Oreo, Milka — announced in May 2026 that it is bringing more manufacturing and packaging in-house specifically to "save quite a bit of money." The decision was driven by cost, but the broader context is hard to miss: tariff volatility, the Hormuz shipping disruption, and a general re-evaluation of how much operational control belongs inside the company's own walls.
Mondelez is not an outlier. ASCM's 2026 supply chain survey found that 83% of business leaders are prioritising operational control over outsourcing. McKinsey's research shows companies with strong supply chain operational control run 15–25% higher margins than those without. The structural case for vertical integration is as strong as it has been in a generation.
Here is the part of the conversation that gets less attention: what happens to operations when you actually do it.
Concept definition
The operational execution gap is the period — typically 6–18 months — between when a manufacturer brings production in-house and when the new operation reaches stability. Existing frameworks address financial viability and digital maturity but leave the execution challenges of this period unaddressed: SOP coverage, decision ownership, knowledge transfer, and cross-plant coordination.
From the work
Written from 5+ manufacturing and distribution engagements, 2022–2026, including operational readiness assessments during insourcing and vertical integration transitions.
The operational readiness gap in vertical integration
The financial logic of vertical integration is well-documented. Control your inputs, reduce supplier dependency, capture margin that currently flows to a third party. In a world of tariff volatility and geopolitical route disruptions, the risk-reduction case is now equally compelling alongside the cost case.
What is less documented — and what we observe being under-estimated — is the operational infrastructure that vertical integration requires to realise those benefits. Logistics Viewpoints, writing in April 2026 about lessons from Tesla and other vertically integrated manufacturers, put it plainly: "vertical integration can expose weak process discipline more quickly." That is worth pausing on.
When you outsource a manufacturing or packaging process, your supplier's internal coordination complexity is invisible to you. You see the output: the component, the packaged good, the delivered service. When you bring that process in-house, all of that coordination complexity becomes yours. New SOPs have to be written. New decision owners have to be named. Cross-plant coordination that your supplier managed invisibly now needs to be governed internally. Institutional knowledge that lived in your supplier's organisation now needs to be built inside yours.
This is not an argument against vertical integration. It is an argument for taking the operational infrastructure question as seriously as the financial one.
What existing readiness frameworks address — and where they stop
Several established frameworks exist for assessing manufacturing operational maturity. They are worth knowing — and worth understanding where they fall short of the specific vertical integration question.
None of these frameworks specifically address operational execution during the 6–18 month transition period — the gap this article examines.
What none of these frameworks specifically address is the governance and coordination infrastructure for the transition period: the 6–18 months during which newly insourced processes are being stood up, SOPs are being written, decision ownership is being assigned, and institutional knowledge is being built. That is precisely the period when operational failures are most likely — and most expensive.
Why the 6–18 month transition period breaks manufacturing ops
A May 2025 paper from the UK Productivity Institute on vertical integration and performance in modern manufacturing firms found that the performance benefits of vertical integration are real — but they typically materialise after a period of operational disruption that the financial models tend to underestimate. The disruption is not from the insourcing decision itself; it is from the coordination complexity that becomes visible once the third-party buffer is removed.
The specific operational failure modes we observe in this transition period are consistent:
What an operational readiness assessment might look like
Given that no single vertical integration operational readiness framework appears to address the transition period specifically, we want to open a discussion about what one should assess. Based on the failure modes above and the existing frameworks reviewed, the dimensions we think matter most are:
- SOP coverage — what percentage of the newly insourced process steps are documented before go-live, with a sign-off protocol
- Decision ownership mapping — for each new decision category the insourcing creates, is there a named owner and a defined approval path
- Knowledge capture timeline — structured transfer completed before the supplier relationship ends, not running in parallel
- Cross-plant coordination infrastructure — formal governance for exceptions that span plant boundaries, not defaulting to whoever is reachable
- Quality exception response protocol — trigger condition, named owner, and response SLA for quality exceptions in the first 90 days
This is a proposed set of dimensions — not a validated score. We would genuinely like to know whether this matches what operations leaders in the middle of vertical integration transitions are actually experiencing.
If your organisation is in the middle of an insourcing or vertical integration initiative — or has recently completed one — we would like to hear from you. Specifically:
- What was the hardest operational infrastructure problem you did not anticipate?
- Did you use a formal readiness assessment before go-live, and if so, what did it cover?
- What would a useful operational readiness score for vertical integration actually measure?
The answers will shape how we think about this problem — and, practically, how OpsGrid's roadmap develops. At the time of writing (May 2026), we are adding a vertical integration operational readiness assessment to OpsGrid's product roadmap. We want to build it around what operations teams actually encounter, not what looks good in a framework document.
Share what you're seeing →Frequently asked questions
How long does vertical integration take for a mid-market manufacturer?
Manufacturers should model for 18–24 months of integration costs (McKinsey Make-vs-Buy framework). The UK Productivity Institute's research indicates performance benefits typically materialise after an operational disruption period of 6–18 months — during which newly insourced processes are being stood up, SOPs written, and decision ownership assigned. This transition period is when failures are most likely and most expensive; the margin improvement is real, but the timeline is consistently underestimated in financial models.
What operational risks are most common when bringing manufacturing in-house?
Three failure modes are consistently observed: (1) no SOP coverage for newly insourced processes — institutional knowledge lived in the supplier organisation and was never formally transferred; (2) decision ownership gaps at cross-plant boundaries — decisions that were implicitly the supplier's now need explicit named owners inside your organisation; (3) knowledge loss during the handover window — the most knowledgeable people are the supplier's staff, who are not joining your company.
What is an operational readiness assessment for vertical integration?
An operational readiness assessment for vertical integration evaluates the governance and coordination infrastructure needed before a newly insourced process goes live. Key dimensions include: SOP coverage for new process steps, decision ownership mapping for all new decision categories created by insourcing, a structured knowledge capture timeline completed before the supplier relationship ends, cross-plant coordination infrastructure, and a quality exception response protocol for the first 90 days. Existing frameworks — PwC Digital Manufacturing Maturity Model, Industry 4.0 Maturity Index, McKinsey Make-vs-Buy — assess digital maturity and financial viability but do not specifically address this transition period governance gap.
When does vertical integration hurt margins before it helps them?
Vertical integration typically creates margin pressure before it delivers the promised improvement. The 6–18 month transition period is when costs peak: SOP gaps generate quality exceptions in the first 90 days; decision ownership voids route all cross-plant exceptions to the COO, adding latency; and knowledge loss during handover requires rebuilding institutional knowledge under production pressure. McKinsey's research shows supply-chain-controlling companies run 15–25% higher margins — but that premium materialises after the transition period, not before it.
How decision infrastructure supports vertical integration execution
The failure modes above — SOP gaps, decision ownership voids, knowledge loss, coordination breakdowns — are all versions of the same underlying problem: the governance model that made an outsourced process work was external, and it did not transfer with the process.
This is the operational execution gap. It is not a strategy problem. It is an infrastructure problem: the SOPs, decision ownership structures, knowledge capture systems, and cross-plant coordination workflows that need to exist before the newly insourced process can run at the quality and speed the financial model assumed. For more on why this is a decision infrastructure question as much as an operational one, see our decision infrastructure vs. decision intelligence article.
The strategic case for vertical integration is real. McKinsey's 15–25% margin premium is real. The 83% of business leaders moving in this direction are responding to real structural pressures. The operational infrastructure question needs the same rigour as the financial one — and right now, the frameworks that address it are incomplete.
We think that gap is worth closing. This article is the start of that conversation.