Build, buy, or partner: entering a market when the cheapest path isn't the fastest

1. Before you start

When a company needs a capability it does not yet have, it has three ways to get it. Build it in-house from scratch. Buy it — acquire a company or licence a finished product that already does the job. Or partner — integrate someone else’s service and pay to use it, without ever owning it. A tiny example: to add a payments feature, you could hire engineers to build one over a year, acquire a small payments startup next quarter, or wire in a payments provider’s service next month. Same destination, three very different costs, timelines, and amounts of control.

Three honest statements before you start:

This is a Decide course. You read a situation, learn the idea, and make a call. You do not write or run any code.
The companies below, Northwind Systems and Vellum Freight, are composite — invented firms built from ordinary figures so the arithmetic is clean. No number is a claim about any real company.
This is not a certification. It proves, to you, that you can defend an entry decision and say what each rejected path would have cost.

You need arithmetic and the willingness to look past a sticker price. The hard part is judgment.

2. The Situation

Northwind Systems sells workforce-scheduling software to mid-size employers, and its biggest customers keep asking for one thing it does not have: an embedded analytics dashboard so they can see their own staffing data without exporting to a spreadsheet. The head of product wants to build it — “it’s our data, we should own the experience.” The CFO wants to partner — “there are dashboard vendors we can wire in next month for a fraction of the cost.” You have to make the call, and both of them are pointing at only half the picture.

The trap is that the option with the smallest price tag can be the most expensive once you count the months it takes to arrive — and the option that looks pricey per month can be the one that wins the market, or the one that quietly hands a rival control of your product.

3. What you’ll be able to do

After this course you will be able to:

Lay out a build / buy / partner entry decision on the four things that actually decide it: cost, time-to-market, control, and risk.
Compute each path’s total cost — including a partner’s ongoing fees, not just its setup price — and its time-adjusted cost once the value lost to delay is counted.
Say when speed or a missing capability should override the cheapest-looking build, and name the number that flips the recommendation.
Judge when strategic control and integration risk should overrule a cost calculation, and say what you would need to believe to go the other way.

4. Prerequisites & time box

Prerequisites: arithmetic, and comfort reading a small table of costs. Helpful but not required: the idea of opportunity cost — the value you give up by not having something sooner (covered in section 6). No spreadsheet, no strategy background.

Time box: about 21 minutes of reading (measured), plus your own thinking time on the call. That is under the 25-minute cap for a concept course.

Difficulty: 6 / 8 — a manager-level decision: three paths and several levers moving at once (cost, time, ongoing fees, control, risk), where the cheapest-looking option is usually the trap, so you have to reason past the sticker price rather than read it off.

5. The case & where the numbers come from

Northwind Systems is a composite software company: its cost, timeline, and value figures are in-course assumptions chosen for clean arithmetic, not drawn from or claimed about any real firm. The methods — build vs buy analysis, time-to-market, total cost of ownership, opportunity cost, vendor lock-in — are standard and cited in section 11. Every figure below is an assumption; every total cost and time-adjusted cost is computed from these figures inside the course, so you can reproduce each one.

Northwind is weighing the analytics dashboard across a 36-month planning horizon, and it has estimated that once the dashboard is live it will add about $60,000 a month in retained and upsold revenue. The three paths:

Path	Up-front cost	Ongoing fee	Time to launch
Build in-house	$1,200,000	—	12 months
Buy (acquire a small analytics vendor)	$2,000,000	—	4 months
Partner (integrate a dashboard provider)	$150,000 setup	$40,000 / month	2 months

Two simplifying assumptions, stated up front so the model is honest. First, we fold each owned path’s run-cost into its up-front figure and treat build-and-buy maintenance as roughly comparable, so the one ongoing line that matters in the comparison is the partner’s monthly fee — because renting, not owning, is the defining feature of the partner path. Second, we add every dollar at face value and do not discount for the time value of money — a payment in month 35 counts the same as one in month 3. That keeps the arithmetic doing-able by hand; a real finance team would discount the future cash, which would modestly favour the paths that spend later. Section 6 returns to what this model leaves out.

6. The Concepts

The three entry paths

Every entry decision trades off the same four things, and each path sits differently on them:

Build — highest control and the cleanest fit to your product, but the slowest and often the most engineering-heavy. You own everything, including the maintenance forever.
Buy — you acquire a finished capability, so it is faster than building and you still own it, but you pay a premium for someone else’s finished work and you inherit integration risk: the acquired thing has to be bolted onto your product and its team absorbed.
Partner — the fastest and cheapest to start, because you are using something that already runs, but you do not own it: you pay for as long as you use it, and you hand some control of your own product’s experience — and roadmap — to an outside vendor.

This is the classic make-or-buy decision widened to three options by adding “partner” between “make it yourself” and “acquire it outright.” The discipline is the same one behind every sourcing call: decide what a capability is really worth to you, then get it the cheapest honest way — where “cheapest” has to count time and control, not just cash.

Total cost of each path

Start with the money, but count all of it. The build’s cost is its $1,200,000 of engineering. The buy’s cost is its $2,000,000 acquisition price. The partner looks cheap at $150,000 to set up — but that is not its cost, because you keep paying $40,000 every month you use it. Over Northwind’s 36-month horizon the partner is live for 34 of those months (it launches in month 2, so it is paying across live months 3–36 — 34 months), so its total cash cost is:

$150,000 + $40,000 × 34 = $150,000 + $1,360,000 = $1,510,000.

So on cash alone the ranking is build $1,200,000 < partner $1,510,000 < buy $2,000,000. The build is cheapest, the CFO’s “fraction of the cost” partner is actually second, and the buy is dearest. If cash were the whole story, you would build. It is not the whole story.

The cost of being late

A capability you do not have yet is costing you every month you wait for it. Northwind reckons the dashboard, once live, is worth $60,000 a month. So a path that takes 12 months to launch spends 12 months not earning that $60,000 — a real, if invisible, cost of $60,000 × 12 = $720,000 in forgone value. That is the opportunity cost of delay, and it is exactly what a cash-only comparison ignores.

Add each path’s delay cost (its monthly value × its months to launch) to its cash cost, and you get a time-adjusted cost:

Path	Cash cost	Delay cost ($60k × months)	Time-adjusted cost
Build (12 mo)	$1,200,000	$720,000	$1,920,000
Buy (4 mo)	$2,000,000	$240,000	$2,240,000
Partner (2 mo)	$1,510,000	$120,000	$1,630,000

Now the ranking flips: partner $1,630,000 < build $1,920,000 < buy $2,240,000. The build that was cheapest on cash is $290,000 worse than the partner once you count the three-quarters of a million dollars its slow timeline burns. Speed, priced honestly, changed the answer.

(An interactive calculator sits here — enter each path’s cost and timeline, the monthly value of the capability, and the horizon, and it returns every path’s cash cost, its time-adjusted cost, and which path is cheapest. Drag the build timeline or the partner’s monthly fee and watch the recommended path flip.)

When speed beats the cheaper build

The time-adjusted view is where most build/buy/partner arguments are really won or lost, so learn to work it in your head. Two forces pull against each other:

The cost of being late favours the fast paths. The higher the monthly value of the capability — the faster the market is moving, the more customers you would lose by waiting — the more a slow build is punished. Push Northwind’s monthly value up and the partner’s lead widens.
A partner’s ongoing fee favours the owned paths over a long horizon. The partner keeps charging every month; the build and the buy do not. Stretch the horizon and those monthly fees pile up until owning is cheaper.

You can find the exact tipping points. Hold everything else at Northwind’s figures and ask when the build overtakes the partner on time-adjusted cost. The build is fixed at $1,920,000. The partner’s time-adjusted cost at a horizon of H months is $150,000 + $40,000 × (H − 2) + $120,000. Set them equal and solve: the partner passes the build at about H = 43 months. So at Northwind’s 36-month horizon the partner wins; commit to a 4-year horizon and the build wins instead — same paths, opposite call, and the fact that flips it is how long you plan to run.

The partner’s terms flip it too. Raise the partner’s monthly fee and hold the horizon at 36 months: the partner’s time-adjusted cost passes the build’s $1,920,000 at a fee of about $48,500 a month. At $40,000 the partner wins; if the vendor quotes $55,000, building becomes the cheaper path. And of course a cheaper or faster build flips it the other way: drop the build to $800,000 and 8 months and its time-adjusted cost falls to $1,280,000 — below the partner — and the build wins outright. The lesson is that “which path is cheapest” is not a fact about the paths; it is a fact about your timeline, your horizon, and the vendor’s terms, so change those and the answer moves.

Strategic control and integration risk

The calculator prices cost and time. It cannot price the two things that most often decide a real entry call, so this is where judgment takes over from arithmetic.

Strategic control. When you partner, you rent a capability and hand an outside vendor a say in your product. If the dashboard becomes the feature customers most associate with Northwind, the partner now sits on Northwind’s critical path: it can raise its fee, change its roadmap, be acquired by a competitor, or simply fail to keep up. That exposure is vendor lock-in, and it is the reason a firm will pay real money to own a capability it could rent more cheaply. The sharper the capability is as a differentiator — the more it is the thing you win on, rather than table stakes everyone has — the more owning it (build or buy) is worth paying for.

Integration risk. Buying looks like a shortcut to ownership, but an acquisition is only as good as the integration: the acquired product has to merge into yours and its team has to stay and deliver. Many acquisitions underdeliver precisely because that merge is harder than the price tag suggests. So “buy” carries a risk “partner” does not — you have paid for something you must now make work.

Put the two lenses together and the honest rule is: use the numbers to rank the paths, then ask whether control or risk should overrule the ranking. If the capability is a commodity everyone offers, take the cheapest time-adjusted path and move on — usually partner. If it is a core differentiator you must control, be willing to pay a premium to own it, and let build or buy win even when partner is a little cheaper. The calculation narrows the choice; it does not make it.

7. Your Call

You have seen how cost, time, control, and risk decide Northwind’s dashboard call. Now a different one lands on your desk.

Vellum Freight is a composite regional trucking carrier — a different company in a different sector from Northwind’s software business — and it wants to add an AI route-optimization capability that would cut fuel and driver hours, worth about $80,000 a month once live, over a 36-month horizon. Its three paths: build for $900,000 over 15 months (it must hire a machine learning team from scratch); buy a small routing vendor for $1,600,000, live in 5 months; or partner with an established routing service — $100,000 to set up plus $50,000 a month, live in 2 months. But the partner attaches a condition the taught case did not have: a three-year exclusive lock-in on this capability, so Vellum could not switch or add another provider for the whole horizon.

How this differs from the taught case (the transfer): this is a different company and sector (a freight carrier, not Northwind’s software firm), the figures are different so the arithmetic must be redone, and it adds a constraint the taught case did not have — the partner’s exclusive lock-in, which the pure cost model cannot price. The core concept is the same: a build / buy / partner entry call decided on cost, time, control, and risk.

8. Self-check

Before you write the memo, make sure you can say each of these in one line:

Why is a partner’s setup fee the wrong number to compare against a build’s cost?
What single fact turns the cheapest-on-cash build into the most expensive path once time is counted?
When should strategic control or integration risk overrule whichever path the numbers say is cheapest?

If any is fuzzy, reread section 6 — the three paths, total cost, the cost of being late, and control-and-risk are the whole course.

9. Stretch

Push the decision further on your own:

Back at Northwind: the partner beats the build up to about a 43-month horizon. Your CEO is now planning around a five-year horizon. Rework the call — and say what non-cost reason might still keep you with the partner even past the crossover. (The genuinely harder one: at a long horizon, is build or buy the owned path you’d actually pick, and why?)
Suppose the analytics vendor Northwind could acquire is also the vendor its main competitor is circling. Does that change the buy-versus-partner call, and which of the four levers — cost, time, control, risk — did it just move?
Write the one sentence you would say to a CFO who insists “the partner is a fraction of the cost, so it’s obviously the cheapest option.”

10. Ship it — your decision memo

Write a one-page memo to Vellum’s leadership. State the call (do not take the partner despite its lowest time-adjusted cost; buy the routing vendor — it costs about $40,000 more over three years but launches in 5 months and leaves Vellum owning a core capability instead of locked to one exclusive vendor). Show the reasoning in two or three lines (time-adjusted costs: partner $1,960,000, buy $2,000,000, build $2,100,000; the buy’s tiny premium buys ownership and dodges a three-year lock-in). Name what you rejected (the partner on its lowest number; the build on its slow 15-month timeline) and why. Name the one thing that would change your mind (route optimization turning out to be a commodity many vendors offer, which would make the cheap partner the right call after all). Keep it to a single page leadership grasps in two minutes. This memo is your own argued claim — not a credential.

11. Sources

Northwind Systems and Vellum Freight, and every figure attached to them, are composite and illustrative — constructed for clean teaching arithmetic, not drawn from or claimed about any real company. The methods used to reason about them are standard; references below.

Concept / claim	Source (publisher)	URL	Accessed
Make-or-buy (build vs buy) as a sourcing decision	Wikipedia — Outsourcing	https://en.wikipedia.org/wiki/Outsourcing	2026-07-20
Time-to-market and the cost of delay	Wikipedia — Time to market	https://en.wikipedia.org/wiki/Time_to_market	2026-07-20
Total cost of ownership beyond sticker price	Wikipedia — Total cost of ownership	https://en.wikipedia.org/wiki/Total_cost_of_ownership	2026-07-20
Opportunity cost of delay	Wikipedia — Opportunity cost	https://en.wikipedia.org/wiki/Opportunity_cost	2026-07-20
Vendor lock-in and strategic control	Wikipedia — Vendor lock-in	https://en.wikipedia.org/wiki/Vendor_lock-in	2026-07-20
Partnering via strategic alliance	Wikipedia — Strategic alliance	https://en.wikipedia.org/wiki/Strategic_alliance	2026-07-20

Next up

Finished this call? Continue the Strategy track:

Double down or cut? Where the next dollar goes across business units → · Browse all courses