FinOps & ITAM: Collaborating to Optimize Cost, Risk, and Value
Summary: FinOps and ITAM practitioners continue to collaborate to manage blended pricing and licensing models. Practitioners can align these disciplines by establishing shared governance forums and connecting systems of record, such as CMDBs and cloud billing platforms, to create a unified view of technology asset data. Map real-time usage telemetry against contractual entitlements, supporting accurate forecasting for BYOL, vendor renewals, and marketplace purchases. Combine FinOps utilization metrics with ITAM compliance tracking establishes a comprehensive framework for managing technology value, allocation, and risk across the organization.
The alignment of FinOps and ITAM is becoming essential for managing today’s hybrid and interconnected technology landscape. As organizations adopt a mix of public cloud, SaaS, licensing, data center, and emerging AI platforms, vendors are increasingly blending entitlement based models with usage-based pricing. This shift is creating new operational challenges and expanding the set of decisions that require input from both FinOps and ITAM skill sets.
According to the State of FinOps 2026 analysis, the collaboration between FinOps and ITAM continues to climb annually, up 20% compared to 2025. This will only increase with the growing need to manage SaaS and Hybrid Licensing spend and determine its value back to the organization.
FinOps and ITAM can work jointly toward a shared goal of maximizing the value that technology delivers to the business, with maximum cost efficiency, that enables reinvestment of savings into strategic priorities and innovation.
Understanding FinOps and ITAM
FinOps drives value creation through financial accountability, informed decision-making, and continuous innovation of technology investments.
By translating cost and usage data into actionable intelligence, FinOps enables prioritization and investment choices that directly support business outcomes, product strategy, and customer experience.
See What is FinOps for further information or take the free Intro to FinOps Training if new to this space.
ITAM brings governance, compliance, and contractual accountability.
ITAM brings governance, compliance, and contractual accountability to the entire technology estate. It ensures that every asset; software, hardware, cloud, or service, is properly acquired, licensed, configured, tracked, supported, and retired in line with business strategy, vendor terms, and regulatory obligations. This safeguards the organisation against contractual, regulatory, and legal risk, enforces commercial discipline, and maintains the integrity of the IT environment.
A mature ITAM practice delivers measurable benefits across five dimensions:
- Financial optimisation: Reduces waste and total cost of ownership by applying the “four Rs”: removing unused assets, reusing licences and devices, reconfiguring capacity of software licenses to align with actual need, and supporting renegotiating contracts based on accurate usage and configuration data.
- Risk reduction: Manages contractual, regulatory, and legal exposure by ensuring assets are used only within agreed terms, meet sector-specific regulatory expectations, and are disposed of or retired in accordance with data protection and environmental requirements.
- Operational efficiency: Provides high-quality asset data that improves support, change, and project delivery, and that can be shared with functions such as CMDB, procurement, HR, and enterprise architecture to enable faster, better-informed decisions.
- Information security: Gives security teams a reliable view of “what exists, where, and how it is configured,” forming a foundational layer for effective cyber and information security controls.
- Sustainability: Supports greener IT by enabling informed choices about hardware, software, and cloud consumption, helping to minimise energy use, extend asset lifecycles, and reduce environmental impact.
Traditionally ITAM operates as a discipline composed of three interdependent components:
- Software Asset Management (SAM): Oversees software licensing, renewals, and audit readiness.
- Hardware Asset Management (HAM): Tracks and governs physical and virtual infrastructure assets.
- Service and Cloud Asset Management: Manages SaaS, PaaS, and hybrid assets through discovery and configuration management databases (CMDBs).
Why FinOps and ITAM Collaboration Is Essential
Across teams, we are seeing that collaboration strengthens execution in several high value scenarios where neither discipline is fully effective in isolation. During Vendor and Platform Selection, joint modeling of pricing structures, commitment strategies, and adoption forecasts brings earlier financial and contractual insight into pre-purchase discussions. This helps organizations avoid costly lock-in, understand hybrid billing patterns such as monthly SaaS overages, and select platforms with a clearer view of long term cost and value.
Also hybrid and BYOL models for platforms like Microsoft SQL, ServiceNow, Adobe require entitlement accuracy from ITAM paired with FinOps usage telemetry to maintain compliance, prevent unexpected spend, and eliminate “shelfware”.
Marketplace Purchasing is another area where collaboration is already proving essential, since ITAM relies on FinOps billing data to validate entitlements, maintain inventory accuracy, and manage compliance risks introduced by decentralized buying channels.
For more information on why FinOps and ITAM collaboration is essential see: Unifying FinOps and ITAM: Realize Tech Value, Reduce Risk, and Increase Efficiency
FinOps and ITAM, Intersection Foundations
Practitioners working across FinOps and ITAM increasingly observe that meaningful progress happens when teams shift from protecting remit to pursuing shared outcomes. Structural silos, rigid RACIs, and skills gaps when working independently remain common barriers, but organizations that address these early report clearer financial visibility, stronger governance, and better optimization outcomes across the whole technology landscape.
The guidance below reflects the actions practitioners are taking and the value they are realizing.
Organizational and Governance Alignment
| Action | Value |
| Create shared forums or routines for FinOps and ITAM teams to work through cross dependent scenarios together. | Reduces duplicated analysis, inconsistent decision making and aligns priorities around the same business outcomes. |
| Use RACI matrixes (responsible, accountable, consulted, informed) with caution and encourage collaborative ownership where responsibilities naturally overlap. | Avoids reinforcing boundaries and supports joint problem solving. |
| Explore unified leadership with a shared vision or closely aligned reporting lines where organizational conditions allow. | Creates a shared vision (where we are heading, and why) and reduces competing objectives and accelerates decision making across cost, risk, and efficiency. |
| Bring both disciplines into architectural reviews and strategic planning early | Ensures cost awareness and licensing considerations influence decisions before budget and procurement commitments are made. |
| Collaborate with Procurement, IT Finance, and Legal proactively during renewals and complex commercial negotiations. | Strengthens positions by combining entitlement knowledge, consumption patterns, and financial insight. |
Data, Technology, and Assets
| Action | Value |
| Build a shared view of contractual, asset, financial and usage data by agreeing and linking the key systems of record across FinOps, ITAM and Procurement (for example CMDBs, SAM and contract tools, procurement systems, and technology cost platforms). | A unified data picture reduces conflicting interpretations on reporting, simplifies reconciliation, and makes optimization opportunities easier to identify. |
| Map procurement channels together, including vendor contracts, resellers, credit card purchases, and marketplace purchases/ self-serve SaaS. | Eliminates blind spots that commonly lead to compliance gaps or missed optimization opportunities. |
| Review blended pricing models jointly, combining entitlement and usage insights (see tier 1 vendor Measurement examples below). | Improves interpretation of total cost through improved estimation and forecasting and helps identify the most effective optimization levers pre and post plan and procure. |
Tier 1 Vendor Measurement – Blended Pricing Models Requiring FinOps and ITAM Collaboration
| Vendor | Flagship enterprise products | Measurement |
|---|---|---|
| Microsoft | Microsoft 365, Azure | Seats & cloud usage |
| AWS | EC2, S3, RDS | Cloud usage/consumption |
| GCP, Google Workspace | Workspace seats & GCP usage | |
| Oracle | Oracle DB, Fusion Cloud Apps, OCI | Core DB & app subs, OCI usage |
| Salesforce | Sales/Service Cloud, Data Cloud, Tableau, Slack | CRM seats, data/AI credits |
| SAP | S/4HANA, BTP, Business Network | ERP subs, indirect access |
| Adobe | Creative Cloud, Experience Cloud, Acrobat Sign | Seat subs, e-sign transactions, AI credits |
| IBM | Red Hat OpenShift, watsonx, IBM Cloud | SW subs, platform capacity |
| ServiceNow | Now Platform, ITSM, ITOM/FinOps | Subscription entitlements |
| Broadcom | VMware Cloud Foundation, vSphere, NSX | Core/CPU subs, VCF bundles |
Skillset, Education, and Core Value
| Action | Value |
| Pair the complementary strengths of both disciplines deliberately. | Combining entitlement governance with real time utilization insights produces clearer accountability and more informed purchasing and optimization decisions. |
| Use bi-directional training to close skills gaps (FinOps education for ITAM teams and ITAM awareness for FinOps teams). | Practitioners consistently report material cost avoidance and reduced risk in these areas. |
| Review blended pricing models jointly, combining entitlement and usage insights (see tier 1 vendor Measurement examples below). | Builds a shared language, reduces friction, and increases confidence working across hybrid cost models. |
| Treat hybrid cost cases as learning opportunities rather than boundary lines. | Helps practitioners understand how entitlements, usage, and consumption based billing interact, strengthening decision making across the whole technology landscape. |
FinOps & ITAM Collaboration by Capability
FinOps and ITAM not only intersect, but can collaborate to strengthen FinOps Capabilities. The following sections outline examples of this collaboration and its organizational value.
Allocation
- FinOps and ITAM might share allocation responsibilities
- There are overlaps with shared costs like BYOL, cloud service provider (CSP) marketplace, and support costs (CSP or software)
- Both can build a shared understanding and usage of naming standards, especially under a unified data schema
- Both can collaborate with application owners to determine how to split and allocate shared costs not only for the entire technology landscape
- SaaS products that are prepaid in a lump sum, but draw down monthly based on consumption, will need to be handled differently based on whether or not the shared costs are shown back or charged back
Reporting & Analytics
- FinOps and ITAM might approach reporting differently based on their respective practices
- Both are mindful of overlaps in reporting billing data from public cloud (i.e. BYOL, marketplace)
- Both can work together and access existing vendor dashboards (if available) or create new dashboards to track consumption-based technologies
Anomaly Management
- FinOps and ITAM both monitor for SaaS and License overages
- Consumption-based technologies like SaaS can correlate with cloud usage anomalies and action may need to be taken to get costs back in line with what the estimated usage for the contract is
- Both monitor and report on unauthorized/unsupported use of services/products (blacklisted products); may be automatically removed
- Both can take action on right-sizing licensing in response to both overages/underages
Forecasting
- FinOps might cover technology forecasting for cloud that might be out of scope for some ITAM teams
- Overlaps with BYOL, CSP marketplace and standalone SaaS
- Consumption-based SaaS: Both work with Engineering to determine the usage forecasted based on trends and planned changes, then FinOps should work with ITAM to determine the best method for acquiring/renewing that is the most cost effective
Budgeting
- FinOps collaborates with ITAM to ensure that licenses or consumption-based usage is as expected month over month, and make adjustments where necessary to course-correct if budget is in jeopardy
- Establish regular communication channels between FinOps and ITAM teams to ensure alignment on financial goals, asset management strategies, and budget planning
- Exchange data and insights between FinOps and ITAM teams, providing FinOps with detailed asset information and ITAM with financial and technology value context
- Collaborate on budget planning processes, including financial forecasts and insights into asset lifecycle costs, procurement needs, and upcoming renewals where BYOL could have benefits to budgets
Rate Optimization
- Software purchases made through CSP marketplaces (partially) counts towards overall cloud spend and could affect the amount of enterprise discount that is applied
- FinOps and ITAM should collaborate to determine the best method for licensing based on where it’s hosted, what discounts are available (and related restrictions), what kind of flexibility there is (if any), whether moving to a resource with no additional license cost is an option and whether to use commitment-based discounts
Unit Economics
- FinOps and ITAM should collaborate to identify and manage unit costs, especially when involving technologies that include a hybrid of fixed license and variable cloud operating costs
- Both can collaborate during cloud migrations as they may involve a shift of expenditure but a short term duplication of costs due to the length of the migration process and existing depreciation/maintenance schedules
- Both collaborate to ensure all teams build a full inventory and clear understanding of BYOL licenses used in the cloud to prevent overuse and to avoid audit-related penalties
Data Ingestion
- FinOps and ITAM teams should strive to create/share one source of truth for data and avoid duplicating the effort and cost of maintaining multiple repositories of the same data
- Both can collaborate to align billing data exports under a common specification, like the FinOps Open Cost and Usage Specification (FOCUS)
Invoicing & Chargeback
- FinOps and ITAM should collaborate on including licensing costs that are part of chargeback
- These costs could be 100% of licensing used or a percentage of licensing they share
Usage Optimization
- FinOps and ITAM should jointly be consulted when new workloads are being planned so that the new workload has licensing it needs and the best procurement method is selected
Governance, Policy & Risk
- FinOps and ITAM could jointly review whether or not users have the ability to procure software/licensing via CSP marketplace and establish policies/guardrails around it to prevent it and force users to use an established process
- Both can help shape an internal process where the requester must meet certain criteria (i.e. within a budget) and get approvals if there is an exception in order for their resources to be created
- On-premises/data center/private cloud resource tagging policy and governance should be unified across the organization and closely align with public cloud resources to improve allocation across various logical/business divisions, and support chargeback and showback
- Both can help create policies/guidelines around how/where resources are created (i.e. what region or technology) and whether or not they are leveraging existing discounts/licensing
- Both can collaborate on assessing total technology vendor spend for contract negotiations
FinOps Education & Enablement
- FinOps and ITAM can share educational resources to build a shared understanding, common taxonomy, process, etc.
- Both can conduct joint education sessions for stakeholders, focusing on topics like technology value management, software licensing, compliance, and asset optimization
- Both can collaborate to establish a common language and definitions to improve communication and understanding across both teams
Workload Optimization
- Constant knowledge sharing will enable organizations to take advantage of a wide range of optimization opportunities
- FinOps and ITAM can collaborate to continually review license usage and engage in optimization, right-sizing, and data hygiene activities
- When an application is designed, ensure elasticity and scaling that involves licensed assets considers the license rights and entitlements
FinOps Practice Operations
- FinOps and ITAM should have a decision and accountability structure so that each understands its obligation, roles, and responsibilities in relation to the other
- Both can support one another to ensure visibility and exposure to leadership and executive sponsorship
- Both can collaborate with common stakeholders, sharing a unified perspective, data, and insights
Licensing & SaaS
- FinOps and ITAM building and sharing a holistic view of software usage across licensing and SaaS is key to true technology value management and unit economics
- Both can collaborate and share data to achieve full visibility of what is owned, what is being used, and the terms and conditions of the licenses
- Work together ensuring compliance, risk mitigation, optimal purchase method, favorable licensing terms and licensing is optimized for the usage required by the business
- Collaboration to ensure that the cost, usage, and decision making on how SaaS is selected, used, and ultimately governed in the organization are well understood
Sustainability
- FinOps and ITAM can work together to support the creation of a holistic view of emissions data for the organization
Automation, Tools & Services
- FinOps and ITAM teams can audit and identify where their respective tools overlap in value and reporting so that they improve coordination and collaboration
- Within organizations with closely aligned teams, there will likely be overlap with 3rd-party services, particularly around BYOL implementation and management
- Sharing and combining data between separate tools may be necessary, and this process should be assigned a clear owner and automated as much as possible, under a unified billing schema if possible
Planning & Estimating
- FinOps and ITAM can support the planning and estimation processes will enable more accurate estimates and de-risk licensing challenges as part of the planned projects/programs
Architecting & Workload Placement
- FinOps and ITAM can collaborate to support the architecting for cloud processes will enable more license-conscious architectures and de-risk licensing challenges as part of the planned projects/programs
KPIs & Benchmarking
- FinOps and ITAM should provide the business with available KPIs and measures of unit economics to help make decisions on what benchmarks can be set both internally and externally
- Both should work together to help facilitate making the benchmark data accessible and visible and provide guidance on what good, better and best look like
- Both should collaborate to share the information on benchmarks to stakeholders
Next Steps
Once familiar with the intersection of FinOps and ITAM, move on to key scenarios where the collaboration of these two teams can deliver increased technology value.
- Plan & Procure
- Deliver & Govern
- Optimize & Evolve (to be published)
- Realize Value & Reinvest (to be published)
Acknowledgments
We’d like to thank the following people for their help on this Paper:
Ron Brill
Anglepoint
Rich Gibbons
Synyega
George Arezina
TAKEDA
Victoria Levy
Alteryx
Lorant Kiss
Delivery Hero
Keith Hiszem
Cardinal Health
Amy Ashby
Under Armour
Colin Jack
Flexera
Robert Nieuwenhuizen
McKinsey
Salomé Keet
FNB South Africa
Savina Stoykova
TP ICAP
Kevin Wade
SHI International Corp.
Parker Nancollas
SoftwareOneLast updated: March 16, 2026
