Vertical 03 of 06
Enterprise Stack Economics
Should we build this in-house or pay a vendor?
The core problem
Build-vs-buy is usually decided on the licence price and a gut feeling about control. The honest comparison is loaded engineering time to reach parity, the maintenance tax that never appears in the business case, integration and on-call, against a vendor price that escalates every renewal.
What this vertical answers
-
01
Loaded build cost, not headcount
Person-months at a fully loaded rate, including the review, testing and migration work that a v1 estimate always omits.
-
02
The maintenance multiplier
A tool that took eight engineer-months to build consumes a permanent fraction of an engineer to keep alive. That is the line item vendors quote and internal teams do not.
-
03
Renewal escalation and exit cost
Vendor pricing escalates; so does the cost of leaving. The comparison is only fair over the same horizon, with the same discount rate.
Flagship engine
Build-vs-Buy Amortization Simulator
Compare internal tooling against a vendor on loaded engineering time, the permanent maintenance fraction, infrastructure and renewal escalation, over one discounted horizon.
Open the engine →