Netanel Shemer
The Minds · Procurement and TCO

Why can the cheapest technology bid become the most expensive decision?

By Netanel Shemer

VP Sales, YouCC Technologies ·

Because the price line covers the setup, and most of the cost comes later: integration, coordination between vendors, work that sits outside the scope, price changes during the contract and the cost of leaving. Compare bids on the same scope and the same period, calculate total cost of ownership for the full contract, and agree in advance on the business outcome and who will verify it.

What does not appear in the bid

I sit on the vendor side of technology tenders, and I can tell you where the gaps usually hide. Comparing prices is easy: three bids, a capability table, a maintenance line and a discount. What is hard to compare is what is not written: integration time, work between vendors, dependence on one key engineer, what happens during an incident, and the cost of changing direction later.

Two bids that look similar often are not the same scope. One includes 24/7 support and the other business hours. One includes onboarding of new systems and the other charges for it as a change request. Until the scope is normalized, the comparison is not a comparison.

Compare by total cost and by outcome

The way to compare alternatives is a total cost of ownership model for the full contract period: licensing, implementation, integration, training, support, internal time, transition risk and exit. In Israel, add currency exposure too. Cloud and software are often priced in dollars, so a contract signed in shekels can drift.

Next to the cost, define the outcome: which business result we expect, in what time frame and who can verify it. A vendor that agrees to be measured on outcomes is telling you something about how it will behave after the signature.

Smart procurement asks hard questions about ownership

When budgets are tight, it is tempting to cut the line that looks like overhead: project management, integration, the managed layer. That is usually the line that holds everything together. Who coordinates when cloud, security and data have to change at the same time? Who owns the fix when the problem sits between two vendors?

Sometimes a point solution is the right choice. Sometimes an integrated service reduces management load and risk. In both cases, decide on value and total cost, not on the price line alone.

What to include in a technology TCO comparison

  • Normalized scope: support hours, response times, included systems and what counts as a change request.
  • Setup: licensing, implementation and initial configuration.
  • Recurring services for the full contract period, including price update clauses and currency exposure.
  • Integration and migration: connecting to existing systems and moving off old ones.
  • Internal coordination time: hourly cost × weekly hours spent coordinating vendors × number of weeks. Over three years, every weekly hour at ILS 260 per hour adds about ILS 40,560.
  • Ownership terms: SLA, escalation path, exclusions and how risk is split in the contract.
  • Exit: data return, handover support and the cost of moving to another vendor.

Common questions

What is total cost of ownership (TCO) in technology procurement?

The full cost of a solution over the contract period: licensing, implementation, integration, training, support, operations, internal time and the cost of transition or exit, not just the purchase price.

Is an integrated service always cheaper than several point solutions?

No. Sometimes a point solution is the right choice. Compare on the same scope, the same period and the same assumptions, including internal coordination time, and decide on value and total cost.

Over what period should TCO be calculated?

Over the full expected contract or usage period, usually three years for managed services and cloud, so recurring costs and coordination time are not hidden behind a low setup price.

What should we ask every technology vendor before signing?

What exactly is excluded from the scope, how prices can change during the contract, who coordinates changes across cloud, security and data, what the SLA and escalation path are, and what leaving would cost.

More from The Minds