Tony: Hello, I’m Tony Mangino from TC2, and this is Staying Connected—where we talk about what really matters to enterprise buyers navigating today’s technology and sourcing decisions.

Tony: Today we’re looking at a pattern we see in almost every major technology deal: the tension between “lowest cost” and “total value.” On paper, the lowest-priced proposal can look like the obvious win. But once you account for lifecycle cost, commercial flexibility, execution risk, and the impact on the broader roadmap, that apparent bargain can become a very expensive decision to live with.

To talk about how enterprise buyers can move from a “lowest cost wins” mentality to a more disciplined total-value approach, I’m joined by my TC2 colleague, Larry York. Larry, welcome back.

Larry: Thanks, Tony. Glad to be here.

Why It Matters for Enterprise IT Buyers

Tony: Let’s start with the basic tension. We still hear this all the time: “Procurement’s job is to get the lowest price.” Why does that mindset remain so persistent in large network and IT deals?

Larry: Because it is simple. Lowest price is easy to score, easy to report, and easy to explain in a leadership meeting. You can point to a percentage reduction, declare savings, and move on.

The problem is that the lowest upfront rate often has very little to do with the best long-term outcome. Enterprise buyers do not operate in a static environment. Requirements change, operating models evolve, suppliers change direction, and transformation programs move on their own timelines. If you optimize only for the headline price, you can easily sign up for a deal that is cheap at signature and expensive to operate.

Tony: So what looked like a win at signature becomes a constraint for the next three to five years.

Larry: Exactly. And that is where a lot of organizations quietly give back the “savings” they thought they had achieved.

Tony: What does a cost-biased procurement culture look like compared with a value-oriented one?

Larry: In a cost-biased culture, sourcing is judged almost entirely on price. IT and the business may help define requirements, but the scorecard is still dominated by commercials, and the headline becomes annual dollar or percent savings versus the baseline.

In a value-oriented culture, price still matters. It always will. But price is evaluated alongside the things that materially impact enterprise outcomes: performance, resilience, implementation practicality, flexibility, governance, and the ability to support the roadmap without constant renegotiation or redesign.

Tony: So the real shift is redefining success—from “did we get the lowest unit rate?” to “did we choose the technology and commercial construct that best supports where the business needs to go?”

Larry: That is exactly the shift.

Main Discussion & Analysis

Tony: One of the harder parts of this conversation is making value more tangible. Everyone agrees that agility, flexibility, and innovation matter, but they are harder to model than monthly recurring charges. How do you make that real for clients and for their finance organizations?

Larry: We usually start with scenarios rather than theory. How quickly can this solution support a new site, a new geography, or an acquisition? How hard is it to integrate a new cloud provider or SaaS platform? What happens if the business needs to change service levels, bandwidth profiles, licensing volumes, or support models midterm?

You do not need a false level of precision. What you do need is a grounded way to show the direction of impact and the size of the tradeoff. If one option slows down strategic change, forces workarounds, or creates expensive change-order behavior, that value erosion is real even if it doesn’t appear neatly on the supplier’s first-page pricing summary.

Tony: And treating that impact as if it is worth zero is usually where the business case breaks down.

Larry: Exactly. In large enterprise deals, rigidity has a cost. It just tends to show up later and in less convenient ways.

Tony: Let’s talk about lifecycle modeling. When TC2 helps a client evaluate total value, what’s included in the model beyond the headline price?

Larry: We normally look at four categories. First, the recurring charges—access, ports, licenses, subscriptions, and the obvious items everyone compares.

Second, implementation and transition costs. That includes supplier non-recurring charges, dual-running costs during migration, internal project effort, dependencies on other upgrades, and any credits or incentives that affect the real cost of getting from the current to the future state.

Third, the operating cost over the term. How many people does the enterprise need to run it? How much supplier dependency are we creating? Are we locking-in to a support or service model that becomes difficult or expensive to change?

And fourth, flexibility. This can cover a lot of ground, for example – What are the commitment mechanics? What happens if the footprint changes? What rights exist around business downturn & divestiture, renewal options, termination, technology change, or restructuring? A deal can look compelling on unit rates and still become expensive if the business changes in ways that the contract doesn’t support.

Tony: And once you put those categories into a three- to five-year lens, the lowest initial quote often stops looking like the best answer.

Larry: That happens quite often. It’s not unusual to see the supplier with the second-lowest unit price win on overall economics because the platform is easier to operate, the roadmap fit is better, or the commercial terms preserve flexibility and leverage instead of constraining it.

Key Questions & Actionable Takeaways

Tony: Let’s make this practical. If you want to avoid a lowest-cost trap, what are the key questions you should ask before a decision gets locked in?

First, what does this option really cost over the full term once implementation, support, change activity, and renewal mechanics are included?

Second, how much flexibility are we giving up if the business changes?

Third, does this solution support the roadmap we actually expect to execute, or does it simply help us hit a near-term budget number?

And fourth, what are we not pricing in because it is inconvenient to model—internal effort, delayed transformation, supplier friction, or the cost of unwinding a weak decision later? Those are the areas where false economies usually hide.

Tony: How do you position a higher-value option with finance when year-one cost is higher?

Larry: You have to do two things well. First, have a firm handle on the total cost of solution ownership over the term of the agreement.  The model should have clear, documented assumptions and a reasonable sensitivity analysis. Finance typically doesn’t expect perfection, but they do expect discipline.

Second, connect the recommendation directly to business outcomes, don’t make it an abstract argument about quality. Show how the value-oriented option better aligns with the technology and sourcing roadmap, preserves leverage at renewal, reduces execution risk, or avoids paying later to undo a structurally weak decision.

Tony: Before we close, let’s touch on one more issue: the fear of missing out. We have both seen organizations chase the money and choose the low-cost option, only to watch peers modernize faster and create a much better long-term position.

Larry: That is a very real issue, but it should be framed carefully. The question is not whether a company is merely chasing near term budget relief. The question is whether it is locking itself into a contract that will be slower, harder, and more expensive to unwind while competitors move toward more flexible technologies and better commercial constructs.

That is the real risk. It is not simply that you might have saved more. It is that you may later face a much larger bill to close the gap because you optimized for the wrong thing the first time.

Closing Remarks

Tony: Larry, this has been a great discussion.

Tony: To recap, the broader point is this: the enterprise buyers who create the most value are not the ones who simply win the lowest headline rate. They are the ones who negotiate for economics, contract flexibility, and strategic fit at the same time.

Tony: Larry, thanks again for joining me.

Larry: Thank you, Tony.

Tony: To our listeners, if you would like to discuss how to bring a total value lens into your sourcing programs, or if you would like to discuss other technology strategy, sourcing, and cost reduction needs with me or any of our TC2 colleagues, please give us a call or shoot us an email.

Tony: You can also stay current by subscribing to Staying Connected, by checking out our websites, and by following us on LinkedIn.