Build vs Buy

What does it actually cost to build it yourself?

A build estimate and a vendor quote are not the same number. This prices what shows up after the decision: the maintenance, the orphaning risk, the months before anything works.

1Start from a company like yours

2Adjust anything that doesn’t match

Example figures

Pick a profile above and these become your numbers.

Build it in-house
$327,400
Buy a platformLower
$308,000

Have your AI check this. Opens your assistant with the equation and these numbers, and asks it to correct them for your company.

Shared assumptions

Applied to both
3 yrs

Build it in-house

$327,400
42%
4 mo

Buy a platform

$308,000

Where the money actually goes

  • Build
  • Buy
Upfront costC₀
Build · Upfront cost
$70,000
$70K
$0
Maintenance + licensen · (M · S + L)
Build · Maintenance + license
$176,400
$176K
Buy · Maintenance + license
$291,000
$291K
Risk-adjusted rebuildPₐ · C_r
Build · Risk-adjusted rebuild
$21,000
$21K
Buy · Risk-adjusted rebuild
$2,000
$2K
Time-to-value delayTTV · OC
Build · Time-to-value delay
$60,000
$60K
Buy · Time-to-value delay
$15,000
$15K
Differentiation credit− n · V_d
$0
$0

Directional cost, not a budget-grade forecast. Profile figures are published benchmarks for a company of that shape, not a claim about yours. Your inputs stay in this browser.

Reference

The equation behind it

Quantifying a build-or-buy decision is always part art, part science. It is easy to calculate a subscription fee; it is much harder to know whether that fee goes up in six months. Better to have a number and be slightly wrong than to never have had a number at all.

The equation

TCO = C₀ + n·(M·S + L) + Pₐ·C_r + TTV·OC − n·V_d

Worked example

A mid-size engineering org decides whether to build its own software factory in-house. Three engineers for six weeks is about $70K of loaded time; maintenance runs at 42% of one engineer; there is a real chance the person who owns it moves on.

TCO = 70,000 + (0.42 × 140,000 × 3) + (0.30 × 70,000) + (4 × 15,000) − 0

TCO = $327,400 over 3 years

Compare that to a managed platform at $90K a year over three years, with minimal time-to-value delay, and you have a defensible case for buying the point solution instead of maintaining someone’s science project.

Where to get a starting number

Var.MeaningWhere to get a starting number
C₀Initial cost — build hours × loaded cost, or the license and setup fee.An actual quote, or engineer-weeks × fully loaded salary.
MOngoing maintenance burden, as a share of engineering time: bug fixes, upgrades, migrations, and the rest of the tedium inherent to owning a project.Benchmark: ~42% of a developer's week for homegrown or unmanaged systems (Stripe); 10–20% of budget even for purchased tools carrying unresolved debt (McKinsey).
SFully loaded annual cost of one engineer — salary plus everything around it.Your own comp bands, loaded for benefits and overhead.
LAnnual license or subscription fee.The quoted list price, less whatever you actually negotiate.
nTime horizon — the years the system will realistically be in use.Usually 3–5 years for planning purposes.
PₐProbability of abandonment — the system becomes orphaned because the engineer who owned it leaves, gets promoted, or moves on.Estimate 20–40% for single-engineer DIY builds; lower for anything with documented ownership.
C_rCost to rebuild or replace it if that happens.Often ≈ C₀ again, sometimes more once dependencies have grown around it.
TTVTime-to-value delay, in months, relative to the fastest option on the table.Compare actual onboarding timelines.
OCOpportunity cost per month of delay — revenue, competitive ground, or engineering hours not spent on differentiated work.The monthly value of the capability once it is live.
V_dAnnual differentiation value. Arguably the most important term, because it assumes some value is actually derived from the decision. If what you are building is a commodity or a cost center, there is no net-new value to count.Assume $0 unless this is a core competency. You can also assume a point solution decreases this number by some percentage over time.
Run. Control.
Transform with Guild.
See what the buy column looks like in practice.