Build, Buy, or Partner

Executive summary#

• Build-Buy-Partner decisions answer: "How do we source talent for this capability?" — balancing speed, cost, and risk
• Three sourcing options: Build (hire + develop), Buy (hire experienced), Partner (contractors/agencies)
• Decision inputs: Capability classification (Core/Strategic/Contextual) + Time horizon (Immediate/Short/Chronic) + Risk tolerance
• Most firms hire when they should partner, and fail to build when demand has been chronic for 12 months. Both hurt margin.
• Use this framework to make sourcing decisions explicit, repeatable, and aligned with business strategy

Definitions#

Build: Invest in hiring and developing talent internally, typically for capabilities where long-term ownership creates competitive advantage.

Buy: Hire experienced external talent, typically when immediate capability is needed and internal development takes too long.

Partner: Engage contractors, agencies, or service providers for temporary or non-core capabilities, typically when flexibility matters more than ownership.

What this includes: Explicit decision rules based on capability classification, demand patterns, and risk tolerance.

What this does NOT include: One-off hiring decisions based on "gut feel" or reactive responses to immediate staffing pressure.

Key distinction: Sourcing strategy is proactive and rule-based, not reactive and ad hoc. The same inputs should produce the same decision.

Why this matters#

Business impact#

Correct sourcing strategy:

• Optimizes cash flow — fixed costs (build) only where justified, variable costs (partner) elsewhere
• Reduces risk — core capabilities buffered, contextual capabilities flexible
• Improves speed — partner for immediate needs, build for chronic needs
• Increases margin — avoid over-hiring (fixed cost bloat) and under-capacity (lost revenue)

Incorrect sourcing strategy:

• Over-building: Hiring for short-term need: the project ships, the headcount stays. You've converted a variable cost into a fixed one.
• Under-partnering: Bottlenecks from insufficient capacity, lost revenue from declined opportunities
• Random decisions: Inconsistent sourcing creates confusion, slow decisions, missed opportunities

Cost reality#

Example: Demand signal for 8 cloud engineers, 3-month horizon

• Bad decision: Hire 8 FTEs → 1M€/year fixed cost rate, 6 become bench when project ends → 750k€/year waste
• Good decision: Partner for 6, hire 2 core → 250k€/year fixed + 486k€ project cost → 736k€ first-year total, no bench waste
• Savings: 750k€/year ongoing bench waste eliminated

The Framework#

canonical_block: decision_loop
version: 1.0.0
concept_id: strategy.build_buy_partner
updated_date: 2026-02-16

decision_name: "Build-Buy-Partner Sourcing"
description: "Framework for deciding how to source talent based on capability classification and time horizon"

decision_inputs:
  - input: "Capability Classification"
    values: ["Core", "Strategic", "Contextual"]
    source: "core-vs-contextual-capabilities.mdx"

  - input: "Time Horizon"
    values: ["Immediate (0-3m)", "Short-term (3-6m)", "Chronic (ongoing)"]
    source: "demand planning"

  - input: "Risk Tolerance"
    values: ["Low (must deliver)", "Medium (can absorb delays)", "High (exploratory)"]
    source: "business context"

sourcing_matrix:
  core_immediate:
    recommendation: "Partner + activate stash"
    reasoning: "Can't hire fast enough. Use partners while activating pipeline."
    competency_requirement: "Partner must be Technical 3-4, Agency 4-5"

  core_short_term:
    recommendation: "Activate stash + selective partner"
    reasoning: "Draw from talent stash (K3-K4). Partner only for overflow."
    competency_requirement: "Stash candidates: Technical 3-4, vetted for culture fit"

  core_chronic:
    recommendation: "Build + hire + buffer"
    reasoning: "Long-term demand justifies fixed cost + 20-30% buffer."
    competency_requirement: "Hire for Technical 3-4, Business 2-3, Agency 4-5"

  strategic_immediate:
    recommendation: "Partner"
    reasoning: "Not worth disrupting core hiring process. Partner for now."
    competency_requirement: "Partner: Technical 2-3, Agency 3-4 acceptable"

  strategic_short_term:
    recommendation: "Partner + consider build"
    reasoning: "If demand looks chronic, start hiring process. Otherwise partner."
    competency_requirement: "Evaluate demand pattern before committing"

  strategic_chronic:
    recommendation: "Selective build"
    reasoning: "Build small team, use partners for spikes."
    competency_requirement: "Hire 2-3 core, partner for 2x surge capacity"

  contextual_any:
    recommendation: "Partner always"
    reasoning: "Never build. Maintain partner bench for all horizons."
    competency_requirement: "Partner: Technical 2, Agency 2-3 sufficient"

Visual decision flow#

How it works#

Decision process#

Step 1: Classify the capability (Core / Strategic / Contextual)

Use the Core vs Contextual framework.

Step 2: Determine time horizon

Step 3: Apply sourcing logic

Step 4: Execute sourcing

• Build: Post job, run hiring process, onboard (8-12 weeks minimum)
• Buy: Activate stash (candidates at K3-K4), fast-track hiring (4-6 weeks)
• Partner: Engage existing partners or source new ones (1-2 weeks)

The matrix gives direction; you still need to argue the decision in words. Core + Chronic → Build is clear. Contextual → Partner is clear. The ambiguous cell — Strategic + Short-term — is where judgment does the real work. The right call depends on whether demand is stabilising, whether a development track is ready, and whether being wrong in either direction carries symmetric risk. That's a conversation, not a lookup.

When documenting a sourcing decision, the test is: can you explain the choice in two sentences without referencing the matrix? "We're hiring because data engineering demand has been chronic for 9 months and we've declined two projects for lack of capacity" is a good justification. "We're hiring because the matrix says Core + Chronic" is not.

Example: CaseCo Mid#

Key insight: Sourcing strategy varies by capability and horizon, not by "we need people now."

Action: Sourcing Decision Matrix#

Use this matrix for sourcing decisions:

Quick Reference#

Decision Checklist#

Before making a sourcing decision, answer:

1. What is the capability classification? (Core / Strategic / Contextual)
2. What is the time horizon? (Immediate / Short-term / Chronic)
3. What is the risk tolerance? (Low / Medium / High)
4. Do we have stash candidates for this capability? (Yes / No / Partial)
5. Do we have trusted partners for this capability? (Yes / No)

Decision output:

• If Core + Chronic: Build (hire FTEs, add buffer)
• If Core + Immediate: Partner + activate stash
• If Strategic: Hybrid (partner now, build if demand stabilizes)
• If Contextual: Always partner

Pitfalls#

Next#

• Core vs Contextual — Classify capabilities before sourcing decisions
• Staffing Gate — Apply Build-Buy-Partner in weekly staffing decisions
• Talent Readiness — Assess readiness of build vs. buy vs. partner options
• Competency Matrix — Track sourcing mix at portfolio scale

What decisions this enables#

• Whether a new demand signal should trigger a hire, partner engagement, or stash activation
• When to convert a contractor relationship into a permanent hire based on demand horizon
• How to staff a project that starts in 6 weeks when hiring takes 10-12 weeks
• Whether the current partner bench is sufficient for anticipated Core + Immediate demand
• How to present a sourcing decision to the board — with cost comparison between build and partner options

FAQs#