Jul 31, 2026 · 40 min · 10 segments
Join Anirudha Choudhury as we explore how to align Procurement and FinOps teams to combat "silent budget killers," cure SaaS sprawl, and optimize your multi-cloud economics. Key Takeaways, The "Buy…
Uh, the, the point is first, we need to be like, uh, Basically, FinOps, basically it's a framework which is developing every year.
For example, there is no concrete points that are hardline points which we need to follow.
The ideology is that when we go ahead and negotiate, let's say, I'll hop into the procurement process a little bit and come back to your question.
In that case, when a procurement team or a commercial team, in that case, tries to buy a product, it is somewhat, they are not a tech team, basically.
There is a lack of engineering aspect to it, architectural design aspect to it.
they actually maintain basically look into the contract and do the negotiation in that case it also those information are also pushed to the commercial team when they go ahead and do a negotiation they also come up from the required product teams as well or the centralized team if it's a product which is being procured for the central visibility or resources in that case.
So procurement or commercial teams, what I understand, needs to have a collaborative effort when they want to finalize a product with the FinOps team.
FinOps plays a large part in understanding cost, your amortized cost, you have built cost and so on, which plays a big part, right? You have usage cost.
So it has to be a collaborative effort when we go ahead and purchase a new product.
It all depends on the negotiation at that time, the technical negotiation, not the contract negotiation, the technical negotiation, because There are two aspect, whether we want that product, how exactly we want that product.
There has to be a revaluation whether that product fits into the org or whether that product is a requirement for us or not.
So when we do the technical negotiation, we always try to find if we can pull up data from, export that data.
Uh, the, the point is first, we need to be like, uh, Basically, FinOps, basically it's a framework which is developing every year.
For example, there is no concrete points that are hardline points which we need to follow.
The ideology is that when we go ahead and negotiate, let's say, I'll hop into the procurement process a little bit and come back to your question.
In that case, when a procurement team or a commercial team, in that case, tries to buy a product, it is somewhat, they are not a tech team, basically.
There is a lack of engineering aspect to it, architectural design aspect to it.
they actually maintain basically look into the contract and do the negotiation in that case it also those information are also pushed to the commercial team when they go ahead and do a negotiation they also come up from the required product teams as well or the centralized team if it's a product which is being procured for the central visibility or resources in that case.
So procurement or commercial teams, what I understand, needs to have a collaborative effort when they want to finalize a product with the FinOps team.
FinOps plays a large part in understanding cost, your amortized cost, you have built cost and so on, which plays a big part, right? You have usage cost.
So it has to be a collaborative effort when we go ahead and purchase a new product.
It all depends on the negotiation at that time, the technical negotiation, not the contract negotiation, the technical negotiation, because There are two aspect, whether we want that product, how exactly we want that product.
There has to be a revaluation whether that product fits into the org or whether that product is a requirement for us or not.
So when we do the technical negotiation, we always try to find if we can pull up data from, export that data.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
