Share this
FinOps—Lifting the Bar on the Value of Cloud
by Grant Simpson on 12 March 2025
Despite its promise of efficiency and flexibility, the variable cost model of cloud computing often results in poor financial outcomes. Unused resources, overprovisioning and a lack of cost visibility result in budget overruns and missed opportunities for value creation.
Many organisations struggle to align cloud spending with business objectives, turning what should be a competitive advantage into a financial burden. This is where FinOps comes in—a disciplined approach to managing cloud spending through work practices and behaviours.
By applying FinOps practices, businesses can regain control, reduce waste, and ensure their cloud investments deliver the value they should.
Research shows this is a widespread problem
Market research1,2 suggests that most organisations could save between 20% and 40% of their cloud spend with improvements to cloud cost management. The inefficiency can be attributed to shortfalls in a range of work practices including:
- failing to optimise workloads
- making decisions without timely, quality and relevant data
- misallocation of spending and inaccurate forecasting
- lack of architecture, policy and governance frameworks and definition
- not following a well-defined RACI structure (Responsible, Accountable, Consulted and Informed)
- neglecting investment in learning and engagement.
The research also shows cloud spending is increasing rapidly, with the use of data analytics, SaaS and AI solutions prominently driving growth. At this growth rate the problem will get significantly worse if it’s not fixed.
We need a new collaborative approach
To truly harness the value of cloud investment, we need to shift from a reactive approach to managing cost, to a proactive strategy. Central to this strategy is how we engage capabilities across the business in good operational and financial work practices.
Let's use reserving cloud resources and savings plans as an example. These pricing mechanisms are used by cloud vendors to motivate customers to make term-based resource and spending commitments. Savings can range between 30% and 70% of the pay-as-you-go (PAYG) price.
Clearly, these plans have the potential to reduce our cloud expenditure and improve value. However, if we over commit to usage, we may end up spending more than the pay as you go price. The key to getting this right, is good planning and forecasting of resource use.
Let's think about the work different people in our organisation do, to build a great forecast.
- Leadership set strategic objectives for cloud use including the value creation expected and how that shows up in budgets, forecasts and value expectations. Leaders oversee governance practices and decisions that guide people's behaviours consistent with architecture, operational and spending expectations.
- Product owners plan new products and services, features and capabilities and forecast the estimated change in user demand over time. They engage with engineers and architects to ensure these expectations are reflected in the solutions we build and maintain. Product owners are often accountable for managing variations in spending, ensuring value is realised and informing future forecasts.
- Architects are scanning the market for new technical approaches to deliver more value while meeting security and compliance mandates. They define the resource standards that allow our engineers to make good resource choices. They work with engineers to project the cost of resources to support new products and services, features and capabilities.
- Engineers configure the right resources with the appropriate tagging ensuring alignment with business use and that usage and spend can be tracked over time. They monitor resource performance and generate estimates of future use based on current trends and customer experiences.
- Operations or Finance teams analyse our usage data, identify gaps and errors in the data, remediate issues with engineers and allocate the usage of shared resources. They produce usage, trend and anomaly reports that can be compared to existing usage forecasts including assumptions for reserved instances and savings plans and updating usage forecasts as required.
- Finance also takes our usage reporting and allocates it to business unit or product budgets, providing financial reporting and trends informing product and business owners decision making and future planning.
We can see from this example, that great forecasting needs people to execute well on a wide range of capabilities and that the collaboration of people in roles across the organisation is critical to solving the puzzle of cloud forecasting.
Introducing the FinOps Framework
This proactive approach of connecting teams and capabilities around work practices has matured into the discipline of FinOps.
The FinOps Framework, developed by the FinOps Foundation has established a standardised approach for managing cloud costs and value. The Framework provides us with practices, tools and processes to manage cloud costs effectively.
Well implemented cloud resources ensure spending is intentional, well-governed and aligned with business objectives.
The Framework acknowledges that cloud cost management requires a broad range of capabilities, from data ingestion, vendor independent reporting and analysis and forecasting to automation and performance optimisation. It defines what good FinOps practices look like. It also recognises that practices and value are unique to each organisation’s cloud use.
Using the Framework as a blueprint, we can define what good FinOps culture and practice should look like for our organisation, understand where we are today, build an analysis of our gaps to get to good and iteratively implement the most valuable, sustainable change.
Rather than focussing on the impossible task of being good at everything, we focus on the change in capabilities and practices that will result in the greatest improvement in the value of cloud to our organisation. It also provides confidence to our CIO and CFO that budgets are appropritely managed and controlled.
We also understand that the culture change required is hard. It requires a mission driven engagement from leadership. The approach establishes an awareness and desire in our people to work together, building work practices towards a common outcome of successful cloud management.
Leading effective change drives a transformational improvement in cloud value
Lifting the bar on cloud value with FinOps formally recognises it as both a culture shift and an enhancement of work practices within our organisations. By following a structured approach, we create a foundation for reducing wasteful spending, improving cloud ROI, and driving better business outcomes—all while balancing innovation with financial accountability. However, embedding FinOps effectively requires the right strategy, expertise, and ongoing commitment.
The FinOps team at Equinox IT specialises in guiding organisations through this journey, improving your practices, optimising cloud investments, and supporting a sustainable FinOps culture. Partner with us to accelerate your FinOps maturity and unlock the full potential of your cloud strategy.
Grant Simpson is a Principal Consultant with Equinox IT and Certified FinOps Practitioner.
1 Stacklet Usage Optimization Survey - Stacklet
2 Unlocking value in cloud sourcing and consumption | McKinsey
Share this
- Agile Development (153)
- Software Development (126)
- Agile (76)
- Scrum (66)
- Application Lifecycle Management (50)
- Capability Development (47)
- Business Analysis (46)
- DevOps (43)
- IT Professional (42)
- Equinox IT News (41)
- Agile Transformation (38)
- IT Consulting (38)
- Knowledge Sharing (36)
- Lean Software Development (35)
- Requirements (35)
- Strategic Planning (35)
- Solution Architecture (34)
- Digital Disruption (32)
- IT Project (31)
- International Leaders (31)
- Cloud (27)
- Digital Transformation (26)
- Project Management (26)
- Azure DevOps (23)
- Coaching (23)
- IT Governance (23)
- System Performance (23)
- Innovation (21)
- Change Management (20)
- MIT Sloan CISR (15)
- Client Briefing Events (13)
- Architecture (12)
- Working from Home (12)
- IT Services (10)
- Data Visualisation (9)
- Kanban (9)
- People (9)
- Business Architecture (8)
- Communities of Practice (8)
- Continuous Integration (7)
- Business Case (4)
- Enterprise Analysis (4)
- Angular UIs (3)
- Business Rules (3)
- GitHub (3)
- Java Development (3)
- Lean Startup (3)
- Satir Change Model (3)
- AI (2)
- API (2)
- Automation (2)
- Scaling (2)
- Security (2)
- Toggles (2)
- ✨ (2)
- .Net Core (1)
- Diversity (1)
- FinOps (1)
- Microsoft Azure (1)
- Testing (1)
- March 2025 (1)
- December 2024 (1)
- August 2024 (1)
- February 2024 (3)
- January 2024 (1)
- September 2023 (2)
- July 2023 (3)
- August 2022 (4)
- August 2021 (1)
- July 2021 (1)
- June 2021 (1)
- May 2021 (1)
- March 2021 (1)
- February 2021 (2)
- November 2020 (2)
- September 2020 (1)
- July 2020 (1)
- June 2020 (3)
- May 2020 (3)
- April 2020 (2)
- March 2020 (8)
- February 2020 (1)
- November 2019 (1)
- August 2019 (1)
- July 2019 (2)
- June 2019 (2)
- April 2019 (3)
- March 2019 (2)
- February 2019 (1)
- December 2018 (3)
- November 2018 (3)
- October 2018 (3)
- September 2018 (1)
- August 2018 (4)
- July 2018 (5)
- June 2018 (1)
- May 2018 (1)
- April 2018 (5)
- March 2018 (3)
- February 2018 (2)
- January 2018 (2)
- December 2017 (2)
- November 2017 (3)
- October 2017 (4)
- September 2017 (5)
- August 2017 (3)
- July 2017 (3)
- June 2017 (1)
- May 2017 (1)
- March 2017 (1)
- February 2017 (3)
- January 2017 (1)
- November 2016 (1)
- October 2016 (6)
- September 2016 (1)
- August 2016 (5)
- July 2016 (3)
- June 2016 (4)
- May 2016 (7)
- April 2016 (13)
- March 2016 (8)
- February 2016 (8)
- January 2016 (7)
- December 2015 (9)
- November 2015 (12)
- October 2015 (4)
- September 2015 (2)
- August 2015 (3)
- July 2015 (8)
- June 2015 (7)
- April 2015 (2)
- March 2015 (3)
- February 2015 (2)
- December 2014 (4)
- September 2014 (2)
- July 2014 (1)
- June 2014 (2)
- May 2014 (9)
- April 2014 (1)
- March 2014 (2)
- February 2014 (2)
- December 2013 (1)
- November 2013 (2)
- October 2013 (3)
- September 2013 (2)
- August 2013 (6)
- July 2013 (2)
- June 2013 (1)
- May 2013 (4)
- April 2013 (5)
- March 2013 (2)
- February 2013 (2)
- January 2013 (2)
- December 2012 (1)
- November 2012 (1)
- October 2012 (2)
- September 2012 (3)
- August 2012 (3)
- July 2012 (3)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- February 2012 (1)
- December 2011 (4)
- November 2011 (2)
- October 2011 (2)
- September 2011 (4)
- August 2011 (2)
- July 2011 (3)
- June 2011 (4)
- May 2011 (2)
- April 2011 (2)
- March 2011 (3)
- February 2011 (1)
- January 2011 (4)
- December 2010 (2)
- November 2010 (3)
- October 2010 (1)
- September 2010 (1)
- May 2010 (1)
- February 2010 (1)
- July 2009 (1)
- April 2009 (1)
- October 2008 (1)