Your personal learning hub for managing Jira, Salesforce, Zoom, OpenAI, Anthropic, and more — with financial discipline and data-driven decision making.
Start Here
Four steps, in order. Do these before anything else — they map directly to your NYS ITS role managing Salesforce, Jira, Zoom, and AI tools under an ELA.
Your Learning Sprint
14 weeks. Timed to the September 1st EA renewal — so your studying and your real work reinforce each other. 30 min a day is enough. The renewal IS the exam.
Foundation
The short version: FinOps = Finance + DevOps. It's a cultural practice that brings engineering, finance, and product teams together to maximize the business value of technology spend.
"An operational framework and cultural practice which maximizes the business value of technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams."— FinOps Foundation (2026 Framework)
FinOps is about getting maximum value from every dollar — sometimes that means spending more strategically, not less.
Finance, Engineering, Procurement, and Product all participate. As a product owner, you're a core persona.
FinOps now officially covers SaaS, AI, Licensing, and Data Centers — not just cloud infrastructure. This is exactly your world.
Core Knowledge
These are the terms and practices that come up constantly in FinOps conversations. Learn these first.
A living catalog of every tool in use — including vendor name, contract owner, renewal date, license count, and cost. This is your foundation. Without it, you're flying blind.
Matching license tier to actual usage. Downgrading inactive Zoom seats, removing unused Salesforce users, or switching Jira tiers. Typically your fastest savings lever.
Showback = reporting which teams use what (no money moves). Chargeback = billing teams for their actual usage. Showback is typically where orgs start; chargeback drives accountability.
The full cost picture: license fees + implementation + training + support + integration + maintenance. Used in Build vs. Buy decisions — especially critical for AI tool evaluation.
How OpenAI, Anthropic, and other AI APIs bill — pay per token/call. Unlike per-seat SaaS, usage can spike unexpectedly. Needs monitoring alerts and budgets, just like cloud.
Should you use OpenAI's API directly, Anthropic Claude, or build your own? FinOps informs this with TCO comparisons, not just sticker price. Includes data privacy considerations.
Segments of tech spend you apply FinOps to. Your scopes: SaaS (Jira, Salesforce, Zoom), AI (OpenAI, Anthropic), and Licensing. Each scope has different personas, KPIs, and strategies.
Cost per user, cost per transaction, or cost per outcome. This is the language of leadership — showing that $X in Salesforce licensing drives $Y in productivity or revenue.
Tools purchased outside of official procurement (often on personal credit cards). A major challenge in SaaS FinOps. Governance policies and SSO discovery tools help surface these.
Jira, Salesforce, Zoom = per-seat (license-based). OpenAI, Anthropic = per-token (usage-based). These require completely different optimization strategies.
Contracts with renewal clauses, auto-renewals, and true-up requirements need tracking 90–180 days out. Negotiating mid-cycle is much harder than at renewal. FinOps builds this discipline.
FinOps Open Cost & Usage Specification. A new (2025) unified data schema folding SaaS and cloud billing into one format. Enables apples-to-apples comparisons across all your tools.
Applied FinOps
Each product you manage has a different pricing model. Here's how FinOps applies to each one.
License-based SaaS. Biggest levers are inactive users and tier selection (Free → Standard → Premium → Enterprise).
One of the most expensive enterprise SaaS tools. License tier mismatches and unused features are common cost drivers.
Hybrid pricing — base seats plus add-ons (webinars, phone, rooms) that compound quickly.
Consumption-based. Usage can spike unpredictably. Treat this like a cloud workload — needs budget alerts, usage dashboards, and model optimization.
Two pricing dimensions: Claude.ai seats (Pro/Team/Enterprise) and API token consumption. Enterprise pricing unlocks volume discounts and data privacy controls.
Manage all tools together using a unified SaaS inventory. Work with Procurement and Finance to build chargeback models that show each team's spend.
Audio Learning
These are the specific episodes most relevant to your SaaS Product Owner role at NYS ITS. Ranked in order — listen to #1 first. All free on Apple Podcasts.
This is your episode. Adrian Tatsch comes from the business side — not engineering, not finance — and shares exactly how she found FinOps and made it work for her role. Described as "a must listen for anyone navigating their career." Her story maps almost exactly to yours as a SaaS PO in a large organization.
Directly covers FinOps principles applied to AI usage — including SaaS-hosted AI (like Claude.ai and ChatGPT) and self-hosted API models. Covers tracking AI costs, guardrails for usage, understanding tokens as a billing unit, and how to have cost conversations with leadership about AI. Essential for managing your OpenAI and Anthropic spend.
Tammy Burnitt shares how she established a FinOps practice inside a large global organization — exactly the government/enterprise context you are in at NYS ITS. Covers how to spread the FinOps message, gain collaborators (not just budget approvers), and build cross-team buy-in without authority.
Great orientation episode — covers how FinOps expanded beyond cloud to officially include SaaS, AI, and licensing in 2024. This is the context for why your role as a SaaS PO is now squarely inside FinOps territory. Good for understanding the big picture before going deep on any one topic.
Once you have the foundations from FinOpsPod, this show fills the leadership communication gap. Interviews with FinOps leaders on how they got executive buy-in, built cost-aware cultures, and communicated SaaS spend in business terms. Very relevant for presenting FinOps findings to NYS leadership. Listen to any recent episode — all are strong.
Learning Resources
Everything here is free. No paywalls, no credit cards required.
Official Framework
FinOps for SaaS — FinOps Foundation
The official SaaS-specific framework docs. Covers SaaS pricing models, inventory management, governance, and the product owner persona.
finops.org/framework/scope/saas →Free Course
Product Owner Training — learn.finops.org
FinOps Foundation's free Product Owner training path. Specifically designed for your persona — covers how to collaborate with finance and engineering teams on tech spend decisions.
learn.finops.org →Free Module
Get Started with FinOps — Microsoft Learn
Free Azure FinOps module. Excellent intro covering the CapEx → OpEx shift, FinOps principles, stakeholder roles, and scopes.
Microsoft Learn →YouTube
FinOps Certified Practitioner — Joe Holbrook
Comprehensive video crash course for the FOCP certification. Covers SaaS billing models, cloud service types, chargeback, and the full FinOps lifecycle.
Search YouTube →Community
FinOps Foundation — finops.org
Main hub. Access papers, playbooks, working groups, and the State of FinOps annual report. The community is active and practitioner-led.
finops.org →Upcoming Certification
FinOps for SaaS Certification
The FinOps Foundation has a SaaS-specific certification in development. Sign up for early access — directly relevant to your product owner role.
Get notified →Quick Reference
Key terms to know when talking to finance, procurement, or leadership.
CapEx vs. OpEx
Capital Expenditure (buy once, depreciate) vs. Operating Expenditure (pay-as-you-go). Cloud and SaaS shifted IT from CapEx to OpEx — this is why FinOps exists.
Chargeback
Billing internal teams for their actual technology usage. Creates real financial accountability and incentivizes cost-conscious behavior.
Showback
Reporting tech costs to teams without actually charging them. A common starting point before moving to full chargeback.
TCO (Total Cost of Ownership)
All costs associated with a technology over its lifetime — license, implementation, support, training, and maintenance. Essential for Build vs. Buy decisions.
Rightsizing
Matching the license tier or resource allocation to actual usage. Downgrading unused seats or switching to a cheaper tier that still meets needs.
License Harvesting
Reclaiming and reassigning licenses from inactive or departed users. Often the fastest cost-saving action for per-seat SaaS like Jira and Salesforce.
FOCUS
FinOps Open Cost & Usage Specification. A 2025 standard that unifies how SaaS and cloud billing data is formatted, enabling consistent reporting across all tools.
Shadow IT
Software purchased or used outside of official procurement. Common when teams use personal credit cards for SaaS tools. Creates cost, security, and compliance risks.
Unit Economics
Cost expressed per meaningful business outcome — cost per user, cost per transaction, cost per feature delivered. The language leadership understands.
True-up
A contract reconciliation where you pay for actual usage above your committed amount. Common in Salesforce and large enterprise contracts. Track carefully.
Personas
The different roles involved in FinOps: Product Owner, Finance, Engineering, Procurement. Each has different responsibilities. You are a core persona.
FinOps Scopes
The segments of tech spend you're managing: SaaS, AI, Licensing, Cloud, Data Center. Each scope has distinct pricing models, personas, and optimization strategies.
Fast Track
A realistic plan to build working FinOps knowledge fast — designed around your actual workload as a product owner.
Week 1
Build the Foundation
Week 2
SaaS-Specific Deep Dive
Week 3
AI + Consumption Costs
Week 4
Put It Into Practice
🎥 Watch List
Curated from the FinOps Foundation channel — prioritized for your role. All free on YouTube.