How to Present a Make-vs-Buy Analysis

A make-vs-buy analysis is a structured decision framework, and the presentation needs to show that structure clearly. Leadership is not just approving a cost comparison — they are approving a strategic choice about where the organization builds capability and where it relies on external providers. A well-constructed deck shows both the financial analysis and the strategic reasoning.

Define the Decision and the Decision Criteria

Open by defining what exactly is being evaluated: a specific product component, a service function, a software capability, or an operational process. Then state the criteria that will be used to evaluate the options — total cost of ownership, time to capability, strategic control, quality standards, scalability, and risk — and the weight or priority of each criterion.

Defining the criteria upfront prevents the decision from being made on whichever dimension is most favorable to the preferred answer. It also signals that the analysis is structured and defensible rather than post-rationalized.

Present the "Make" Option in Full

Describe what building internally would entail: the design and development effort, the ongoing operational cost (people, tools, infrastructure, and maintenance), the time to first capability and time to full capability, and the internal capabilities and resources required. Be honest about whether the organization actually has the skills and capacity to build this well, or whether building would require significant hiring or upskilling.

Include the opportunity cost: what would the internal team not be doing if they were building this? For engineering, operations, or product teams with constrained capacity, the opportunity cost of internal development is often the most significant cost that gets omitted.

Present the "Buy" Options

If there are multiple vendors or partners available, compare them systematically. For the buy option (whether purchase, license, or outsource), present the direct cost (purchase price, license fees, implementation cost, and ongoing support), the time to capability, the quality and feature match versus requirements, the vendor's stability and support quality, and the switching cost if the relationship needs to change in the future.

Lock-in is one of the most underweighted risks in make-vs-buy decisions. A solution that is slightly cheaper but creates deep integration dependencies may cost significantly more to exit in three to five years than a slightly more expensive solution with clean boundaries.

Compare Total Cost of Ownership Over the Decision Horizon

The comparison should be a multi-year total cost of ownership (TCO), not a first-year cost comparison. Make and buy options have very different cost profiles: build costs tend to be front-loaded with ongoing maintenance; buy costs tend to be more linear but grow with usage or inflation. Show both options on a common timeline (three to five years is typical) so the crossover point, if there is one, is visible.

Include a sensitivity analysis showing how the conclusion changes if key assumptions are wrong — if development takes 50% longer than planned, or if the vendor raises prices by 20% at renewal.

Apply the Strategic Criteria

Beyond cost, address the strategic dimensions: does this capability represent a source of competitive differentiation that argues for internal ownership? Are there data privacy or security considerations that make external providers problematic? Does the vendor market offer a credible long-term option, or is the supply constrained?

A capability that is commoditized, non-differentiating, and well-served by the vendor market is almost always a buy. A capability that is genuinely differentiating and where the organization has a real build advantage is a candidate for making. Most decisions fall between these poles, which is why the structured analysis matters.

Present the Recommendation and the Decision

After presenting both options fully, make a clear recommendation with the reasoning. State the conditions under which the recommendation would change — if a critical vendor assumption proves false, or if the build timeline extends significantly — so leadership knows what to monitor after the decision is made.

Slide Deck's make-vs-buy analysis template includes pre-built layouts for criteria weighting tables, TCO comparison charts, and risk comparison matrices.