Make-or-buy analysis in project management is defined as the analytical process used to determine whether a particular deliverable, service, or result can be produced internally by the performing organization or should be acquired from an external supplier. The evaluation weighs internal production costs and capabilities against the price, quality, risk, and strategic value of purchasing from outside. It sits at the intersection of project planning and procurement strategy, shaping how resources are allocated and how contracts are structured. In many projects the decision appears straightforward on the surface, but a rigorous analysis reveals layers of trade-offs that are easy to miss.
Make-or-Buy Analysis: Summary of Key Topics
| Key Concept | Summary |
|---|---|
| Make-or-Buy Analysis | Make-or-buy analysis is a structured evaluation used to determine whether a deliverable, service, or result should be produced in-house or sourced from an external supplier. |
| Core Decision Question | It assesses whether the project team and organization hold a measurable advantage in skills, tooling, capacity, and cost, or whether an external supplier is better positioned to deliver the component. |
| Hidden Trade-offs | Seemingly straightforward choices often conceal multiple layers of trade-offs that become visible only through rigorous, structured analysis. |
| Supplier Risks | External sourcing can introduce quality control gaps, intellectual property exposure, and supply chain fragility that are invisible in a simple direct cost comparison. |
| Scope of Application | The analysis applies to a continuum of items, from a single machined component to an entire software module, a training program, a testing service, or a facility expansion. |
| Evaluation Factors | It weighs technical complexity, proprietary knowledge, regulatory constraints, staffing availability, and the strategic value of preserving a capability within the organization. |
| Indirect Cost Drivers | Supervision, quality assurance, rework, training, and scarce management attention often alter the balance more than direct unit costs. |
| Total Cost Perspective | A complete cost view extends beyond the initial transaction to include maintenance, support, upgrades, disposal, and ongoing supplier relationship management. |
What Is Make-or-Buy Analysis in Project Management?
The question behind make-or-buy analysis in project management is deceptively simple, but the evaluation it demands touches almost every part of project planning. At its core, the analysis answers whether the project team and the wider organization possess the skills, tools, time, and cost advantage to deliver a component themselves, or whether an outside party is better positioned to supply it. That single decision can ripple through budget, schedule, quality, risk, and even long-term organizational capability.
Make-or-buy analysis is not merely a procurement exercise. It is a strategic evaluation that forces the project team to think about opportunity costs and hidden dependencies. A component that looks cheap to produce internally may consume scarce engineering hours that are needed for higher-value work. Conversely, buying from a supplier may introduce quality control concerns, intellectual property exposure, or supply chain fragility that never shows up on a direct cost comparison.
The Core Meaning and Scope of Make-or-Buy Analysis
The scope of make-or-buy analysis can range from a single machined part in a manufacturing project to an entire software module, a training program, a testing service, or a facilities expansion. It applies whenever a project has a defined scope element that could be delivered either by the performing organization or by an external entity. The analysis compares more than money. It weighs technical complexity, proprietary knowledge, regulatory constraints, staffing availability, and the strategic importance of retaining a capability in-house.
In practice, the analysis often happens iteratively. An initial screening may eliminate obviously unsuitable options, then a more detailed evaluation compares the remaining alternatives. The goal is not to produce a perfect answer but to surface the trade-offs clearly enough for a defensible decision.
Core Insights on Make-or-Buy Analysis
- A Deceptively Simple Decision
- Make-or-buy analysis clarifies whether the project team and organization possess the skills, tooling, capacity, and cost advantage to produce a component in-house, or whether an external supplier is better positioned to deliver it at acceptable quality and risk.
- Ripple Effects Across the Project
- The choice extends well beyond immediate cost, shaping budget, schedule, quality, risk exposure, and long-term organizational capability, which is why it merits strategic planning attention instead of a narrow price comparison.
- Hidden Costs and Opportunity Costs
- Internal production that appears inexpensive on paper can drain scarce engineering hours from higher-value initiatives, while external procurement may bring quality control gaps, intellectual property exposure, or supply chain vulnerabilities.
- Broad Scope of Application
- Its reach extends across procurement categories, from a single machined part to an entire software module, training program, testing service, or facilities expansion, making it relevant whenever a deliverable component could be sourced either internally or externally.
- Screening Before Detailed Evaluation
- A preliminary screening filters out clearly unsuitable alternatives before a more rigorous evaluation weighs the remaining options against technical complexity, proprietary knowledge, regulatory constraints, staffing capacity, and strategic alignment.
Key Components of Make-or-Buy Analysis
The key components of make-or-buy analysis include cost structures, internal capability, capacity constraints, risk exposure, and strategic alignment. Each component interacts with the others, which is why treating the analysis as a pure cost comparison almost always produces a distorted picture. A decision that appears inexpensive on a unit basis can become costly when the full lifecycle and organizational impacts are considered.
Direct costs are the most visible part of the equation. For the buy option these include purchase price, shipping, taxes, and supplier management effort. For the make option they include labor, materials, equipment, utilities, and any incremental overhead. But direct costs rarely tell the whole story. Indirect costs such as supervision, quality assurance, rework, training, and the use of scarce management attention can shift the balance significantly.
Total Cost of Ownership and Hidden Costs
Total cost of ownership is a central concept in make-or-buy analysis. It extends the cost view beyond the initial transaction to include maintenance, support, upgrades, disposal, and the cost of managing the supplier relationship over time. A component that is inexpensive to buy but expensive to integrate or maintain may have a higher total cost than an internal alternative that initially looks more expensive. Hidden costs are particularly dangerous because they surface late, often after the decision has already been locked into contracts or resource plans.
Capability, Capacity, and Core Competence
Internal capability refers to whether the organization has the technical skills and processes to deliver the work at an acceptable level of quality. Capacity is a separate question. A team may be highly capable but fully allocated to other priority work. Core competence adds a strategic filter. Activities that differentiate the organization in its market are often strong candidates for a make decision, even when the direct cost comparison favors buying, because losing that internal competence could weaken the company over time. Commodity or generic activities, by contrast, are frequent buy candidates unless there are compelling reasons to keep them internal.
Risk is another component that deserves explicit treatment. The buy option transfers certain execution risks to the supplier but introduces supplier performance risk, schedule dependency, and possible loss of control over proprietary information. The make option retains control but concentrates execution risk inside the organization. A balanced make-or-buy analysis does not ignore either side of this risk equation.
Make-or-Buy Analysis in PMBOK and Project Management Frameworks
In PMBOK terminology, make-or-buy analysis PMBOK is positioned as a planning technique within the Project Procurement Management knowledge area. The PMBOK framework places the technique in the Plan Procurement Management process, which belongs to the Planning Process Group. Its outputs include the procurement management plan, procurement strategy, and the documented make-or-buy decisions for individual deliverables or work packages. The analysis uses inputs such as the project scope statement, work breakdown structure, resource requirements, market conditions, and organizational process assets.
PMBOK does not prescribe a rigid formula for the analysis. It treats make-or-buy analysis as a structured evaluation that may include financial modeling, risk assessment, and expert judgment. The emphasis is on documenting the reasoning behind the procurement approach so that later decisions remain traceable. In PMBOK, the make-or-buy decision often feeds directly into source selection criteria and contract type selection, because an external purchase requires a different set of controls than internally produced work.
PRINCE2 and Agile Perspectives
PRINCE2 does not name make-or-buy analysis as a separate technique, but the same decisions appear in its Plans and Business Case themes. When a PRINCE2 project evaluates delivery options, it considers whether work will be done by internal teams or external suppliers, and that decision influences the plan, the risk register, and the business justification. The supplier aspect of PRINCE2 is woven into the Organization theme, where the project team must understand who is accountable for delivering each part of the plan. Make-or-buy thinking is therefore present, even if it is not labeled as a distinct process.
In Agile environments, make-or-buy decisions often happen at a more granular level and may be revisited sprint by sprint. A team might decide to build a small utility internally one week and then switch to a commercial library the next when the cost of maintaining the internal version becomes visible. Agile teams tend to favor buying commodity components and services so they can focus internal effort on product features that create direct user value. The analysis remains relevant, but the documentation is typically lighter and the decision cycle shorter.
BVOP Perspective on Make-or-Buy Analysis
From a BVOPM standpoint, the decision is influenced by the principle that employee-created tools and open-source software count as formal products, which can shift the internal capability calculation. A make decision may support value delivery when it builds reusable internal assets, while a buy decision aligns with waste reduction when external suppliers offer proven quality at lower total effort.
Core Insights on Make-or-Buy Across Frameworks
- Planning Technique in Procurement Management
- PMBOK treats make-or-buy analysis as a structured planning technique within Plan Procurement Management, supporting decisions about internal production versus external acquisition before commitments are made in the Planning Process Group of the Project Procurement Management knowledge area.
- Inputs and Structured Evaluation Methods
- This evaluation draws on the project scope statement, work breakdown structure, resource requirements, market conditions, and organizational process assets, and typically integrates financial modeling, risk assessment, and expert judgment to compare internal capabilities with external supply options.
- Link to Source Selection and Contracts
- In PMBOK, make-or-buy decisions directly shape source selection criteria and contract type selection because externally procured work requires distinct governance, performance, and risk controls compared with work completed by the project team.
- Framework and Value Perspectives Compared
- PRINCE2 links delivery option choices to the project plan, risk register, and business justification, while agile teams typically buy commodity components to keep focus on user value, and the BVOP perspective weighs reusable internal assets against the waste reduction gained through proven suppliers.
Purpose and Importance of Make-or-Buy Analysis in Projects
The purpose and importance of make-or-buy analysis in projects lies in its ability to prevent costly misallocations of scarce resources and to align procurement decisions with organizational strategy. Without a structured analysis, project teams often default to familiar patterns, either always building internally out of habit or always buying externally for speed. Both defaults can waste money, delay delivery, or erode capabilities that the organization actually needs to protect.
A disciplined make-or-buy analysis forces the project manager and sponsor to articulate why an approach is being chosen. That clarity matters when stakeholders later question a budget line or a schedule assumption. It also helps the organization avoid the trap of investing heavily in non-core activities that could be purchased more efficiently, or outsourcing a critical function that later becomes a source of competitive disadvantage.
The importance extends beyond individual projects. Repeated make-or-buy choices shape the organization's structural cost base, its supplier ecosystem, and its technical depth. A pattern of buying every non-core service may look efficient in project accounting but can hollow out internal knowledge over time. Conversely, a pattern of making everything internally can leave the organization slow and expensive. The analysis provides the evidence base for making those trade-offs deliberately rather than by drift.
How Make-or-Buy Analysis Is Applied in Practice
Make-or-buy analysis in practice rarely follows a clean linear path. It involves iterative discussions with technical teams, procurement, legal, and finance, and the outcome is often a recommendation rather than a hard numerical answer. In real projects the decision emerges from a mix of cost modeling, capability assessment, market research, and sponsor judgment about strategic direction.
A typical scenario involves a project manager reviewing the work breakdown structure with the team. For each major deliverable, someone asks whether the organization should produce it internally or buy it. The project manager may gather quick estimates from engineering, request a rough quote from a known supplier, and then compare not only the numbers but also the schedule impact and the team's current workload. The result is documented in the procurement management plan, with a clear notation of which items are make, which are buy, and which require further analysis.
Scenarios and Decision Timing
Make-or-buy analysis is most commonly applied during project planning, before major contracts are signed or internal resources are committed. It can also reappear during execution if a supplier fails, a technical assumption changes, or the team realizes that an internal build is taking far longer than expected. In software projects, the decision might involve building a custom module versus licensing a commercial package or adopting an open-source component. In construction, it might involve using an internal crew for site preparation versus hiring a subcontractor. The timing matters because switching direction later is almost always more expensive than making a considered choice early.
Key Insights on Practical Make-or-Buy Decisions
- Iterative, Cross-Functional Process
- In practice, make-or-buy analysis is an iterative, cross-functional process in which technical, procurement, legal, and finance teams jointly shape a recommendation through cost modeling, capability assessment, market research, and sponsor judgment, rather than a single definitive calculation.
- Deliverable-by-Deliverable Evaluation
- Project managers typically evaluate each major deliverable in the work breakdown structure by comparing internal cost and effort estimates with supplier quotes, while also weighing schedule impact, resource availability, and current team workload before recommending a sourcing path.
- Timing and Revisiting the Decision
- The analysis normally takes place during project planning before contracts are signed or internal resources are committed, but it can resurface during execution if a supplier underperforms, an underlying assumption changes, or an internal build takes substantially longer than planned.
Common Challenges, Pitfalls, and Misconceptions in Make-or-Buy Analysis
Common misconceptions about make-or-buy analysis often lead project teams to treat the decision as a one-time cost comparison rather than a dynamic evaluation of trade-offs. One of the most persistent myths is that the lowest quoted price should automatically win. That view ignores quality differences, integration costs, supplier responsiveness, and the long-term value of retaining internal knowledge.
Another frequent pitfall is underestimating internal costs. Teams tend to overlook the time spent on meetings, rework, tooling, and management oversight when they estimate the cost of making something themselves. The internal option looks artificially cheap because the organization already pays salaries, so the incremental labor seems free. In reality those hours have an opportunity cost, and assigning them to one project means they are unavailable for another.
Political pressure can also distort the analysis. A sponsor may prefer a buy decision to avoid hiring staff, or a technical manager may insist on building internally to protect the team's role. When the analysis becomes a justification exercise rather than an honest evaluation, the result is often a procurement approach that satisfies the loudest voice but does not serve the project's actual objectives.
Why the Decision Goes Wrong
Analysis paralysis is a less visible but real problem. Some organizations demand such detailed financial justification that the decision stalls for weeks, delaying the project. In other cases the analysis is based on outdated market data, and the buy option is either overpriced or underpriced relative to current conditions. Supplier risk is another blind spot. A buy decision that looks rational on paper can unravel when the supplier has hidden financial problems, long lead times, or weak quality controls. The make-or-buy analysis should therefore be treated as a living input to project planning, not a static document frozen at the start.
Make-or-Buy Analysis vs Other Procurement and Strategic Tools
A common point of confusion is the relationship between make-or-buy analysis vs procurement planning, since the analysis feeds into the procurement strategy but does not replace the broader planning process. Procurement planning encompasses many activities beyond the make-or-buy choice, including market research, contract type selection, source selection criteria, and risk allocation. Make-or-buy analysis is one input that helps shape those decisions.
The analysis is also sometimes confused with total cost of ownership modeling, but the two are not identical. Total cost of ownership is a financial evaluation method that can be used within a make-or-buy analysis, but make-or-buy analysis also includes non-financial factors such as strategic alignment, internal capability development, and risk appetite. Source selection criteria, by contrast, apply only after the buy decision has been made. They define how potential suppliers will be evaluated, not whether the work should be purchased at all.
Related Concepts and Boundaries
Make-or-buy analysis relates closely to outsourcing decisions, but outsourcing usually implies moving an existing internal function to an external provider, whereas make-or-buy analysis applies to new project work that has not yet been allocated. It also connects to core competence theory, which suggests that organizations should focus internal resources on what they do best and buy everything else unless there is a strong strategic reason not to. The boundary between these concepts is not always crisp, but keeping them distinct helps prevent scope creep in the analysis itself.
Key Distinctions for Make-or-Buy Analysis
- Input to procurement planning
- Make-or-buy analysis establishes the initial procurement direction but must be supplemented by market research, contract type selection, and explicit risk allocation to form a complete sourcing strategy.
- Broader than total cost
- Total cost of ownership provides the financial foundation for the decision, while make-or-buy analysis also evaluates strategic alignment, long-term capability development, and the organization's risk appetite.
- Source criteria come later
- Source selection criteria are applied only after the decision to buy has been made; they guide supplier evaluation and do not determine whether work should be purchased or performed internally.
- Outsourcing and core competence
- Outsourcing typically transfers an existing internal function to an external provider, whereas make-or-buy analysis addresses new project work and draws on core competence theory to concentrate investment on activities that strengthen internal capabilities.
Evolution and Current Thinking on Make-or-Buy Analysis
The evolution of make-or-buy analysis reflects a broader shift from simple cost accounting to strategic sourcing and capability management. Early approaches to the make-or-buy question were heavily influenced by manufacturing economics, where the decision often came down to comparing production costs with purchase prices. Transaction cost economics later added a crucial dimension by emphasizing the costs of negotiating, monitoring, and enforcing contracts, not just the price of the goods themselves.
Ronald Coase and Oliver Williamson are widely associated with the transaction cost perspective, which explains why firms sometimes choose to do things internally even when a supplier's quoted price is lower. The answer lies in the hidden costs of using the market. Later work on core competencies by C.K. Prahalad and Gary Hamel reinforced the idea that some activities should remain internal because they are central to the organization's long-term identity and competitive advantage. These ideas have filtered into project management practice, where make-or-buy analysis now routinely includes strategic and risk considerations.
From Cost Accounting to Strategic Sourcing
Current thinking treats make-or-buy analysis as a dynamic capability rather than a static calculation. Cloud computing, open-source software, and global supply chains have changed the economics of both options. A project team can now buy infrastructure capacity by the hour, adopt a mature open-source component at near-zero acquisition cost, or contract with a specialized vendor on the other side of the world. At the same time, concerns about data security, intellectual property, and supply chain resilience have pushed some organizations back toward internal capability for critical functions.
Debate continues over how much weight to give to non-financial factors. Some practitioners argue that cost should dominate because projects are temporary and strategic benefits are hard to quantify. Others maintain that project decisions have lasting organizational consequences that a narrow cost view misses. The most defensible position is context-dependent. A make-or-buy analysis that serves a small, short-duration project may appropriately emphasize cost and schedule, while a decision affecting a core product line or a critical technology platform must weigh strategic factors far more heavily. The analysis has evolved not into a formula but into a structured conversation about value, risk, and capability, and that conversation remains one of the most consequential parts of project procurement planning.
