That's the gap. Build cost is visible, itemised, comparable. Operating cost isn't on the sheet. It shows up six weeks later as a support queue, a validation backlog, or a reconciliation spreadsheet nobody planned to own.
Here's the trade-off procurement rarely gets to see clearly. A platform with more built-in validation, cleaner exception handling and tighter supplier handoffs will almost always cost more upfront.
It will also lose most line-item comparisons, because none of that shows up as a number in a spreadsheet column. It shows up later — as headcount hours, as support tickets, as finance asking why reconciliation is taking three weeks instead of three days.
You can't fault procurement for optimising against what's measurable.
Build cost is measurable. Reconciliation effort isn't, until it's already happened.
Each handoff is a place where data has to move cleanly, or someone has to chase it manually. A cheap build usually means fewer of those handoffs are automated.
Which means more of them become someone's manual job, quietly, after the contract
is signed.
None of this argues for ignoring cost control. Full-cost visibility isn't the same as unlimited budget. It just means the comparison needs a second column: not just what does this cost to build, but what does this cost to run once volume arrives.