Outsourcing Decision (Make vs Buy)

Definition

The make-vs-buy decision is a strategic framework resting on three pillars: cost analysis (TCO comparison), core competency assessment (competitive advantage), and control evaluation (operational risk). Organizations with proprietary core technology see ~2x stronger revenue growth than those relying on off-the-shelf platforms. [src3]

Key Properties

Three pillars: Cost (TCO), Core competency, Control
Buy TCO: Piece price + integration + training + management + customization (150-200% of sticker)
Make TCO: CapEx, depreciation, utilities, maintenance, learning curve, opportunity cost
Shifting drivers: Cost savings dropped from 70% to 34% as primary outsourcing driver; talent access now #1 at 42%
Hybrid model: "Buy context, build core"

Constraints

Hidden outsourcing costs increase TCO 150-200% beyond contract price [src1]
Core competency assessments are subjective [src3]
Switching costs increase over time, creating vendor lock-in [src2]
Organizational knowledge loss is irreversible [src5]
Regulatory requirements may prohibit outsourcing [src2]

Framework Selection Decision Tree

START — Company evaluating make vs buy
├── Is this a core competency?
│   ├── YES (differentiates, competitive advantage) → MAKE ← DEFAULT
│   ├── NO (commodity, non-differentiating) → Consider BUYING
│   └── UNSURE → Apply core competency test
├── Core Competency Test:
│   ├── Drives customer value? → Core
│   ├── Hard to replicate? → Core
│   ├── Access to multiple markets? → Core
│   └── None of above → Non-core → BUY candidate
├── TCO for "buy" lower than "make"?
│   ├── YES → BUY (if not core) ← YOU ARE HERE
│   ├── NO → MAKE
│   └── SIMILAR → Decide on control + strategic flexibility
└── Control requirement?
    ├── HIGH → MAKE
    ├── MEDIUM → Outsource with strong SLAs
    └── LOW → BUY with standard terms

Application Checklist

Step 1: Core competency test

Inputs: Activity description, competitive analysis
Output: Core/non-core classification
Constraint: If core + hard to replicate, do not outsource [src3]

Step 2: Build TCO for both scenarios

Inputs: Make costs, Buy costs (including hidden)
Output: 3-5 year TCO comparison
Constraint: Include ALL hidden buy costs (150-200% of sticker) [src1]

Step 3: Assess control and risk

Inputs: IP sensitivity, quality needs, supplier depth
Output: Risk-adjusted decision matrix
Constraint: Fewer than 3 qualified suppliers = elevated risk [src2]

Step 4: Evaluate strategic flexibility

Inputs: Technology trajectory, optionality value
Output: Lock-in risk and switching cost assessment
Constraint: If activity might become core in 3-5 years, bias toward make [src5]

Step 5: Document and schedule review

Inputs: Steps 1-4 outputs
Output: Decision with rationale and 12-month review trigger
Constraint: Conditions change; review at 12 months [src4]

Anti-Patterns

Wrong: Outsourcing based solely on cost

Quality issues and management overhead eliminate savings within 18 months. [src1]

Correct: Use full TCO with hidden cost factors

The cheapest PO is rarely the cheapest reality. [src3]

Wrong: Outsourcing core competencies

Competitive advantage erodes when differentiation is handed to a vendor. [src4]

Correct: Apply core competency test first

Build core, buy context. [src3]

Wrong: Ignoring switching costs

Integration creates 3-year switching costs on a 1-year contract. [src2]

Correct: Model switching costs at decision time

If costs exceed 50% of annual contract value, it's a lock-in risk. Negotiate exits upfront. [src5]

Common Misconceptions

Misconception: Outsourcing always saves money.
Reality: Hidden costs reduce actual savings to 50-70% of projected. Insourcing is often cheaper fully loaded. [src1]

Misconception: Non-core should always be outsourced.
Reality: Non-core does not mean unimportant. High-control activities may be better kept in-house. [src3]

Misconception: The decision is permanent.
Reality: Every outsourcing decision should have a 12-month review trigger. [src4]

Comparison with Similar Concepts

Concept	Key Difference	When to Use
Make vs Buy	Strategic insource/outsource framework	Deciding to perform internally or externally
Procurement Strategy	Optimizes sourcing for bought items	After "buy" decision is made
Build vs Buy (Software)	Software-specific platform decisions	IT/SaaS purchasing
Vertical Integration	Acquiring capabilities across value chain	M&A for supply chain control

When This Matters

Fetch this when a company asks about make-vs-buy analysis, outsourcing decisions, TCO comparison, core competency assessment, or evaluating insourcing previously outsourced activities.