Tax documents and a calculator on a wooden table
AI Economics · Decision

Build, Buy and the Option Nobody Prices

The comparison is usually between an internal build costed optimistically and a product costed accurately. The third option, doing nothing differently, is rarely priced at all.

Key Takeaways
  • Build versus buy comparisons systematically understate build cost by omitting maintenance, integration ownership and staff turnover.
  • The status quo is an option with a cost, and it is almost never priced in these comparisons.
  • The right comparison is over several years, since the cost profiles differ in shape rather than only in size.
  • Reversibility has value and rarely appears in the analysis at all.
  • A published estimator can frame the range before scoping conversations begin.

Every finance function considering AI runs some version of this comparison, and most of them run it badly in the same three ways.

The build option is costed as a development project rather than as a permanently owned system. The buy option is costed accurately, because a vendor has quoted it. And the option of continuing as you are is treated as free, which it is not.

Fixing those three things does not predetermine the answer. It just makes the comparison describe reality.

Build vs Buy
Decision
Cost
Procurement
Business Case
ChatFin
01

Why build costs get understated

Not through optimism about the development, which teams are increasingly realistic about. Through omission of everything that happens afterwards.

A built system needs maintenance as ERPs change and interfaces are updated. It needs somebody who understands it, which becomes a recruitment and retention problem the moment that person leaves. It needs security patching, monitoring and someone answering questions about it at close. And it accumulates a backlog of small improvements that nobody has budgeted for.

Those costs are real, recurring and rarely in the comparison. A build costed for year one against a subscription costed for year one is comparing a project to an ongoing service.

The correction is straightforward: cost the build over the same period as the alternative, including the people who will own it in year two and year three.

02

What belongs in a complete comparison

Four cost categories that a proper comparison includes and a typical one omits.

All four apply to a build and only some apply to a purchase, which is the asymmetry that makes a naive comparison misleading rather than merely incomplete:

Ongoing ownership. The people who maintain, support and answer for the system after the project ends, in every subsequent year.
Integration maintenance. ERP upgrades, interface changes and format changes, all of which arrive whether or not you planned for them.
Key person risk. The cost of replacing understanding when the person who built it leaves, which is a probability rather than a possibility.
Opportunity cost. What the engineering capacity would otherwise have produced, which is usually the largest omitted item in a build case.
03

The third option

Build versus buy is a false binary, because continuing as you are is always available and is what happens by default when a decision stalls.

It has a cost, and pricing it changes the shape of the comparison.

The status quo

What it costs today

Hours spent on the process, contractor and overtime spend at peak, error correction, late reporting and the opportunity cost of experienced people doing assembly work. All measurable, and rarely measured.

Why it matters

It is the real baseline

Both alternatives should be compared against this rather than against each other. A change that is expensive against a build may be obviously worthwhile against the status quo.

Two professionals reading through financial documents
Development is the visible cost. Ownership is the recurring one.
04

Comparing over the right period

The cost profiles differ in shape, which is why a single year comparison misleads regardless of which option it favours.

Three years is usually the right horizon.

OptionYear oneYears two and three
BuildDevelopment effort, concentrated and visibleMaintenance, ownership, integration changes and key person risk, all recurring and easy to omit
BuySubscription plus implementationSubscription, with renewal exposure and less control over the roadmap
Status quoCurrent run cost, already in the budgetThe same, plus growth in volume without a corresponding change in cost per unit

The status quo column is the one most comparisons leave blank, which makes the other two look like a choice between two costs rather than two investments.

05

Reversibility has value

A rarely discussed dimension is how expensive each option is to exit, and the differences are substantial.

A subscription can generally be ended, with the pain being migration and process disruption. A built system is not exited so much as maintained or abandoned, and abandoning it strands the investment and leaves the process needing a replacement urgently.

That matters most where the requirement is genuinely uncertain, which is common in this category. Where you are unsure what you actually need, the reversible option carries a value that a pure cost comparison does not capture, and it is worth stating explicitly in the paper rather than leaving it as an unspoken preference.

Where the requirement is uncertain, reversibility is worth paying for. Cost comparisons do not capture it.
"

A build costed for year one against a subscription costed for year one compares a project to a service.

ChatFin
06

Running the comparison properly

Four steps, and the first one is where most of the missing information is.

Price the status quo

Hours, contractor spend, overtime, error correction and the opportunity cost of experienced staff on assembly work. It is the baseline both alternatives should be measured against.

Cost the build over three years

Including ownership, integration maintenance and key person risk. Year one development cost alone is not a comparison, it is a project estimate.

Include opportunity cost

What the engineering capacity would otherwise deliver. It is usually the largest omitted item and it is a real trade.

State the reversibility position

Explicitly, especially where the requirement is uncertain. It belongs in the paper rather than in the unspoken preferences of whoever writes it.

Hands using a calculator beside document folders
The status quo column is the one most comparisons leave blank.
07

Where ChatFin sits, stated plainly

ChatFin is the buy option, and it is worth saying that directly rather than presenting a neutral framework with a thumb on the scale.

What that means concretely: a configurable platform that connects to NetSuite, SAP Business One, JD Edwards, Acumatica, Dynamics 365 and Sage Intacct through their supported interfaces, with integration maintenance, model changes and platform upgrades handled rather than owned by your team.

It also means the trade offs that come with buying: configuration within a product's boundaries rather than unlimited freedom, a roadmap you influence rather than control, and a renewal decision every term.

For teams that want to see the range before any conversation, the published cost estimator produces a first year range and compares an internal build, a consulting build and a configurable product side by side, without recommending one.

Integration maintained, not owned. ERP changes and interface updates handled rather than becoming your backlog.
Configurable within boundaries. Which is the honest trade off of buying rather than building.
Reversible. A subscription decision each term rather than a system you are permanently responsible for.
Before you budget for it

AI Cost Estimator for the CFO Office

Four inputs, a first year cost range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

Why do build cases understate cost?

Mainly through omission of what happens after the project. Ownership, integration maintenance, key person risk and opportunity cost are all recurring and are frequently absent from a comparison that costs development against a subscription.

Should the status quo be in the comparison?

Yes, and it usually is not. It is the real baseline, it has a measurable cost in hours, contractor spend, error correction and opportunity cost, and it is what happens by default when a decision stalls.

What horizon should we use?

Three years, because the cost profiles differ in shape rather than only in size. A build front loads visible cost and back loads recurring cost, and a single year comparison misrepresents whichever option it favours.

When does building make sense?

Where the requirement is genuinely specific to your organisation, where you have durable engineering capacity to own it, and where the process is stable enough that maintenance will not consume the benefit. Those conditions are real and are less common than build cases usually assume.

General information only. It is not legal, accounting or tax advice, and rules change. Check your own position with your advisers before acting on it.

Price all three options

Compare against the status quo, not against each other.

Cost the build over three years including ownership and opportunity cost, price the status quo, and state the reversibility position. The answer follows from an honest comparison rather than from the framework.

ChatFin is the buy option and says so, with the trade offs stated. The published estimator compares all three routes without recommending one.

Book a Demo
See the platform
Take it to your own ledger

Compare the routes against your own processes.

Bring your current run cost for one process. We will show what the configurable route covers, what it does not, and how it compares against the baseline you already carry.

✓Runs on the ERP you already have, on the version you already run
✓Every posting prepared as a draft that a named person approves
✓Prompt, evidence and prepared payload logged for the audit file
Schedule a Demo
Confidential & private
Photos by Artem Podrez, Mikhail Nilov and RDNE Stock project, free to use under the Pexels License (commercial use, no attribution required). Diagrams and product imagery © ChatFin.