Adopting FinOps (Financial Operations) provides a structured approach to manage, optimize, and forecast cloud spending, ensuring that cloud investments deliver maximum value to the business.

Adopting FinOps (Financial Operations) provides a structured approach to manage, optimize, and forecast cloud spending, ensuring that cloud investments deliver maximum value to the business.

1. Adopting FinOps Proposal

2. License Attribution / Use This work is licensed under a [Creative Commons Attribution 4.0 International License][cc-by]. Use or Adaption of this work requires attribution to the FinOps Foundation under the CC BY 4.0 license . You are free to: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material for any purpose, even commercially. Under the following terms: Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. More details can be found at https://www.finops.org/introduction/how-to-use/ Copyright 2019-2024 FinOps Foundation – All rights reserved

3. How to use this deck These slides are designed as a template tool for individuals to use when pitching FinOps adoption. Included herein are a mix of slides - some ready for use, others ready for you to put on the final touches, and others reference use and to be removed prior to presenting your pitch. When an organization is first considering adopting FinOps, it is common for executives to ask for a very short summary of what FinOps is, what it will require, and the value it will bring to the organization. Often this needs to be delivered in 10 minutes on a crowded agenda. Review the Contents slide to learn more about which slides are ready for use, which require your input, and which should not be presented as part of your pitch Read all the speaker notes on all slides for a sample talking track and additional instruction Keep an eye out for the spotlight — it indicates that you should customize the content or provide additional inputs

4. Contents Introduction to FinOps Ready to use slides to be incorporated into your pitch presentation if/as needed Proposal to Adopt FinOps Template slides which require your inputs and customization Personas Reference slide for leverage as you build your pitch, remove before final presentation Appendix A collection of additional content which you can use, not use, and customize as needed

5. Introduction to FinOps

6. Cloud is critical to every business but is a fundamentally different consumption model... Decentralized Engineers siloed from Finance (and Procurement) are empowered to commit the company to spend Variable Variable cloud spend replacing data center/fixed cost spend, including numerous ways to optimize rates Scalable Instant access to a variety of resources enables innovation but often results in overprovisioning

7. FinOps is an operational framework and cultural practice which enables timely data-driven decision making through collaboration between engineering, finance and business teams. maximizes the business value of cloud creates financial accountability Framework 

8. FinOps Framework FinOps is an operational framework and cultural practice which maximizes the business value of cloud , enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams. Core Personas Allied Personas Principles Teams need to collaborate Decisions are driven by business value of cloud Everyone takes ownership for their cloud usage FinOps data should be accessible and timely A centralized team drives FinOps Take advantage of the variable cost model of the cloud Phases Maturity Crawl Walk Run Procurement ITFM ITAM Security ITSM Sustainability Finance FinOps Practitioner Leadership Engineering Product FinOps Framework by FinOps Foundation Understand Cloud Usage & Cost Quantify Business Value Optimize Cloud Usage & Cost Data Ingestion Allocation Reporting & Analytics Architecting for Cloud Rate Optimization Workload Optimization Cloud Sustainability Licensing & SaaS Anomaly Management Manage the FinOps Practice FinOps Education & Enablement FinOps Practice Operations FinOps Tools & Services FinOps Assessment Cloud Policy & Governance Intersecting Disciplines Onboarding Workloads Invoicing & Chargeback Domains & Capabilities Planning & Estimating Budgeting Forecasting Unit Economics Benchmarking FinOps.org

9. Who Does FinOps? In the same way that everyone is responsible for security with a central team enabling best practices (at scale), many roles do FinOps with help from a central team. “If I do my job properly I do not need to be in the room when Finance and DevOps teams meet. They are enabled by the work I have done to normalize the cloud bill, allocate and highlight key data points. When FinOps succeeds the business is using the data of FinOps to make better decisions on its own.” Mike Fuller, CTO FinOps Foundation, Former Head of FinOps at Atlassian Copyright 2019-2024 FinOps Foundation – All rights reserved

10. Proposal to Adopt FinOps

11. Current State In the last 6 months our cloud migration has resulted in faster delivery to market yet higher than anticipated spend and a lack of clarity on cost per application. XX % Resource Utilization XX% Unused Resources

12. FinOps Adoption Roadmap Months 6 + Phased rollout Iterate on FinOps practices implemented in pilot Rollout to remaining LOBs leveraging pilot learnings Month 3 - 6 Deepen practices Improve allocation and cost visibility Select & deploy FinOps tooling Engage with CCoE on implementing FinOps policy and governance guardrails . Month 2 & 3 Pilot with top 2 LOBs Drive agreement on FinOps operating mode Define & implement processes for forecasting, budgeting, rate optimization & usage optimization in collaboration with teams Month 1 Get the ball rolling… Gain approval to adopt FinOps Start role definition & hiring Define EOY goals Adopt FinOps via a pilot with the top 2 lines of business and do a phased rollout across the rest of the organization after a period of 6 months.

13. Increased collaboration driving the increased value from our cloud investments Future State Rate Optimization Coverage between xx% and xx% Decrease in unused and underused resources Timely decision making driven by granular, accurate historical cost and usage data Clarity on what drives every dollar of the monthly cloud bill and who is responsible for those charges

14. Call to Action Program Sponsorship Approval to Execute Adoption Roadmap Pilot with top 2 LOBs LOB A LOB B Define & implement processes for forecasting, budgeting, rate optimization & usage optimization in collaboration with teams Deploy new allocation strategy Engage with CCoE on implementing FinOps policy and governance guardrails. Funding to Support Roadmap Seeking … Cloud Cost Management tooling July timeframe Estimated Cost $[X] 1 dedicated FTE to Establish FinOps processes & routines for Forecasting/Budgeting Anomaly management Allocation & Chargeback Rate & Usage Optimization Own training & maintenance of FinOps Tooling Be an advocate for FinOps Aide in expectation setting with impacted teams

15. Personas

16. Tailor your message to the audience Each FinOps Persona has different interests and motivations in FinOps. These are described on finops.org: Leadership Product Engineering Finance Procurement Leverage these general perspectives with what you already know about your audience to create a custom, engaging proposal for FinOps adoption.

17. Of other helpful slides to use in your pitch Appendix

18. FinOps Framework FinOps is an operational framework and cultural practice which maximizes the business value of cloud , enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams. Core Personas Allied Personas Principles Teams need to collaborate Decisions are driven by business value of cloud Everyone takes ownership for their cloud usage FinOps data should be accessible and timely A centralized team drives FinOps Take advantage of the variable cost model of the cloud Phases Maturity Crawl Walk Run Procurement ITFM ITAM Security ITSM Sustainability Finance FinOps Practitioner Leadership Engineering Product FinOps Framework by FinOps Foundation Understand Cloud Usage & Cost Quantify Business Value Optimize Cloud Usage & Cost Data Ingestion Allocation Reporting & Analytics Architecting for Cloud Rate Optimization Workload Optimization Cloud Sustainability Licensing & SaaS Anomaly Management Manage the FinOps Practice FinOps Education & Enablement FinOps Practice Operations FinOps Tools & Services FinOps Assessment Cloud Policy & Governance Intersecting Disciplines Onboarding Workloads Invoicing & Chargeback Domains & Capabilities Planning & Estimating Budgeting Forecasting Unit Economics Benchmarking FinOps.org

19. Understand Cloud Usage & Cost Quantify Business Value Optimize Cloud Usage & Cost Manage the FinOps Practice Allocation Benchmarking Architecting for Cloud Cloud Policy & Governance Anomaly Management Budgeting Cloud Sustainability FinOps Assessment Data Ingestion Forecasting Licensing & SaaS FinOps Education & Enablement Reporting & Analytics Planning & Estimating Rate Optimization FinOps Practice & Operations Unit Economics Workload Optimization FinOps Tools & Services Intersecting Disciplines Invoicing & Chargeback Onboarding Workloads Mapping Capabilities to Domains Each Capability is now anchored to a single Domain Understand Cloud Usage & Cost Quantify Business Value Optimize Cloud Usage & Cost Manage the FinOps Practice Allocation Anomaly Management Cloud Policy & Governance Data Ingestion FinOps Assessment FinOps Education & Enablement FinOps Practice Operations FinOps Tools & Services Intersecting Disciplines Invoicing & Chargeback Onboarding Workloads Reporting & Analytics Cloud sustainability Architecting for Cloud Licensing & SaaS Rate Optimization Workload Optimization Benchmarking Budgeting Forecasting Planning & Estimating Unit Economics Framework 

20. FinOps Core & Allied Personas Product Engineering Leadership FinOps Practitioner Finance Procurement ITFM/TBM Security ITSM/ITIL ITAM Sustainability Core Personas Allied Personas Framework 

21. FOCUS is the language of FinOps Copyright 2019-2024 FinOps Foundation – All rights reserved The FinOps Open Cost and Usage Specification (FOCUS) is an open-source specification for cloud billing data. It defines clear requirements for cloud vendors to produce consistent cost and usage datasets and reduces complexity for FinOps Practitioners so they can make data-driven decisions and maximize the business value of cloud all while making their skills more portable across clouds, FinOps tools, and organizations. Learn more at focus.finops.org . FOCUS is the language of FinOps

22. A program of the Linux Foundation, we are a membership-based trade association funded by individual training and corporate memberships. Free to join for end-user practitioners. Vendors can become members for a fee. With 25 staff (in 6 countries) dedicated to furthering the advancement of the FinOps discipline and our members who practice it. A membership-based trade association of 16,000+ practitioners (including 48 of the Fortune 50) with a mission of: Connections & Community Education & Certification Best Practices & Standards Advancing the people who manage the value of cloud

23. FinOps Certification and Training V isit: learn.finops.org Advance your knowledge of FinOps with a range of training and certification 10K+ 100+ FinOps Training

24. All slides below for design/use by WG to be removed prior to publication END OF DECK