Make or Buy Analysis: A Practical Guide for Project Managers

Every project manager eventually faces the same procurement question: should we build this in-house, or should we buy it from an outside vendor? That decision — formally called a make-or-buy analysis — sounds simple, but it has cascading effects on cost, schedule, quality, risk, and the long-term capabilities of your organization. This guide walks through what make-or-buy analysis is, when to use it, the factors that matter, and a practical worksheet you can apply today.

What Is Make-or-Buy Analysis?

Make-or-buy analysis is a structured procurement-management technique used to decide whether a specific product, component, or service should be produced internally (make) or acquired from an external supplier (buy). It is one of the foundational tools in the Project Procurement Management knowledge area of the PMI’s Guide to the Project Management Body of Knowledge (PMBOK^® Guide).

At its core, make-or-buy analysis asks three questions:

Can we do this ourselves with the people, time, and tools we have?
Should we do this ourselves, given our strategic priorities and capacity?
What is the total cost of each option — not just the obvious dollars, but the hidden costs, risks, and trade-offs?

The analysis is rarely about a single product. It is usually about whether to develop a capability versus contract for a result — and that distinction shapes the long-term direction of an organization.

When Do You Need a Make-or-Buy Analysis?

Make-or-buy analysis is most useful when:

You are planning the procurement strategy for a new project and the scope includes deliverables that could be produced internally.
An existing in-house process is consuming resources you need for higher-priority work.
A new technology, regulation, or market shift forces a re-evaluation of how work gets done.
Costs are rising and leadership is asking whether outsourcing would reduce the burn rate.
A vendor proposal lands on your desk and you need a defensible way to decide.

The analysis is usually performed during the planning phase of a project, before procurement contracts are signed — but it is worth revisiting at key milestones, especially when scope or budget changes.

The Key Factors in a Make-or-Buy Decision

A good make-or-buy analysis weighs both quantitative (cost-based) and qualitative (strategic) factors. Skipping either side leads to decisions that look right on a spreadsheet but feel wrong six months later.

Quantitative factors

Direct cost comparison. Internal cost to produce (labor + materials + overhead) versus vendor price (unit cost + shipping + integration).
Volume and scale. Fixed costs of in-house production are easier to absorb at high volumes; low-volume needs often favor buying.
Capital investment. If making it requires equipment, software, or facilities you do not yet have, the buy option may avoid significant capital expenditure.
Time to deliver. Internal teams may take longer to ramp up; vendors may deliver faster if the capability already exists.
Total cost of ownership. Maintenance, updates, support, and end-of-life costs — not just the initial price tag.

Qualitative factors

Strategic importance. Core capabilities should usually be built and owned. Commodity work is often safer to buy.
Intellectual property. Will this work create IP, trade secrets, or competitive advantage you want to control?
Quality control. How much oversight will you have? Can you achieve the quality standards you need through a vendor relationship?
Risk and dependency. Outsourcing creates vendor dependency — what happens if the supplier raises prices, exits the market, or gets acquired by a competitor?
Speed and agility. Can the buy option flex with shifting requirements, or does it lock you into a long-term contract?
Workforce impact. Outsourcing decisions affect morale, retention, and the long-term skills profile of the organization.

Make vs. Buy: A Side-by-Side Comparison

This table summarizes the typical trade-offs. Real situations will weight these differently — that is the work of the analysis.

Factor	Make (in-house)	Buy (outsource)
Control	High — you set the standards, schedule, and quality bar	Lower — defined by the vendor contract
Speed to start	Slow if capability does not yet exist	Fast if a competent vendor is available
Unit cost at volume	Lower as volume grows (fixed costs spread)	Vendor margin built in; less scale benefit
Capability building	Creates internal expertise and IP	Builds vendor expertise; you become a customer
Risk profile	Execution risk on your team	Vendor dependency and contract risk
Flexibility	High — you can change direction	Limited by contract terms
Best fit when	Strategic, high-volume, IP-sensitive, or core to your value proposition	Specialized, low-volume, time-sensitive, or outside your core competency

A Step-by-Step Make-or-Buy Analysis Process

The decision should follow a repeatable process. Project managers who improvise this analysis end up defending decisions that lack a clear rationale; project managers who follow a structured approach can explain the call to executives, auditors, and future-them.

Define the scope of the decision. What exactly are you deciding about? Be specific: not "should we outsource development" but "should we build the customer-portal authentication module in-house or license a vendor solution."
Identify the criteria that matter. Use the factor lists above as a starting point and trim to what is relevant for this specific decision. Five to seven weighted criteria is usually plenty.
Estimate the cost of making. Include labor at fully-loaded rates, materials, equipment, software, training, and a realistic allocation of management overhead.
Estimate the cost of buying. Include the contract price, integration cost, ongoing license or service fees, vendor management time, and exit costs (what happens if you need to switch).
Score the qualitative factors. A simple high/medium/low or 1–5 scale is enough. Document your reasoning beside each score.
Apply weights and total the scores. Some criteria matter more than others — weighting them honestly reflects what the organization actually values.
Make the call, then document it. Capture not just the decision but the reasoning, so the analysis can be re-run if conditions change.

📄

Free template: Make-or-Buy Analysis Worksheet

A ready-to-use Word document with the cost-comparison framework, qualitative scoring matrix, and decision summary — built around the steps above.

Download the worksheet template (.docx)

A Worked Example

A mid-sized engineering firm is launching a customer-facing dashboard. The project manager needs to decide whether to build the analytics charting engine in-house or license a vendor library.

Cost to make: Two senior engineers for six months at $180,000 fully-loaded each = $360,000. Plus ongoing maintenance estimated at $60,000/year.
Cost to buy: Vendor license at $48,000/year, integration estimated at $40,000 one-time, plus $10,000/year for support.
Three-year total — make: $360,000 + ($60,000 × 2) = $480,000.
Three-year total — buy: $40,000 + ($58,000 × 3) = $214,000.

On dollars alone, the buy option wins by a wide margin. But the qualitative analysis adds nuance: the company sees data visualization as a long-term differentiator and wants to own the IP. A hybrid decision emerges — license now to ship the dashboard on time, build internally over the next 18 months as a capability investment, and migrate when the in-house version is competitive.

That kind of nuanced answer is impossible without doing the analysis. The numbers alone said "buy"; the strategy said "make"; the structured process led to a phased approach that respected both.

Common Mistakes in Make-or-Buy Analysis

Comparing only the obvious costs. Internal labor and vendor invoices are easy to count; vendor management, integration, exit costs, and opportunity cost are easy to miss.
Ignoring capacity. "We can build it" is true in theory — but if the team is already at 110% utilization, building it means something else does not get built.
Treating it as a one-time decision. Conditions change. A buy decision that made sense two years ago may not make sense today.
Skipping the qualitative analysis. The cost spreadsheet is necessary but not sufficient. Strategic factors often matter more than the unit-cost delta.
Defaulting to in-house from pride or to vendor from fatigue. Both are organizational reflexes that masquerade as decisions. The structured process is the antidote.

Make-or-Buy Analysis and the PMBOK^® Guide

For PMP^®-certified project managers and those preparing for the exam, make-or-buy analysis is a named tool in the Plan Procurement Management process. The PMBOK^® Guide treats it as a foundational technique for shaping the procurement strategy of a project — the decisions it produces feed directly into procurement documents, statements of work, source selection criteria, and contract types.

If you are preparing for the PMP^® exam or stepping into a procurement-heavy role, a strong grasp of make-or-buy analysis — including the factors above and how they connect to contract type selection — is essential. CEG's project management training programs cover the technique in depth, including practice scenarios drawn from real-world projects.

Build Stronger Procurement Skills

Make-or-buy is one decision in a much broader procurement-management skill set. Project managers who can confidently navigate vendor selection, contract types, source selection criteria, and supplier performance management deliver better outcomes for their organizations — and earn the trust that comes with those outcomes.

If you want to develop these skills, explore CEG's project management courses on stakeholder management, project planning and procurement, and our PM skills assessment to identify exactly where to focus.