FinOps for Ukrainian business: How to control cloud costs

What is FinOps and why is it important for Ukrainian business?

FinOps is an operational model and cultural practice that brings together people, processes, and tools for managing cloud costs [1]. In a context of economic instability and growing dependence on cloud solutions, Ukrainian companies need FinOps to control expenses and maximize value from cloud investments. FinOps is not just financial management; it's a cultural shift that fosters collaboration among financial, IT, and business teams [2]. Its primary goal is to maximize business value from every cloud investment by ensuring transparency, accountability, and efficient resource utilization. This not only helps control budgets but also enables informed decisions regarding the future development of cloud infrastructure.

Key principles and phases of the FinOps framework: See, Optimize, Operate

The FinOps framework is based on three core phases that form a continuous cycle of cloud cost management: See, Optimize, and Operate [3].

See

At this stage, the main task is to ensure full transparency of cloud costs. This involves collecting, analyzing, and visualizing data on resource consumption and associated expenses. Monitoring and reporting tools allow IT directors and financial managers to understand where money is going, who is spending it, and on which projects. Effective resource tagging is critical for accurate cost attribution and allocation across teams, projects, or business units. Without clear visibility, it's impossible to make informed optimization decisions.

Optimize

Once a complete picture of costs is obtained, the optimization phase begins. This involves active measures to reduce unnecessary spending and improve the efficiency of cloud resource utilization. This may include:

Rightsizing: Reducing the size of instances or services to the actually required level.
Reserved Instances/Savings Plans: Utilizing long-term commitments with the cloud provider to obtain significant discounts.
Deleting unused resources: Identifying and removing idle virtual machines, storage, or other services.
Using Spot Instances: For non-critical workloads that can be interrupted, allowing for substantial savings.

These strategies require continuous analysis and interaction among developers, operations teams, and financial professionals.

Operate

The "Operate" phase focuses on continuous improvement and automation of FinOps practices. This includes integrating FinOps into daily operations, setting budgets, forecasting mechanisms, and automating cost management processes. At this stage, teams work to make FinOps an integral part of the corporate culture, where every participant understands their impact on cloud costs and actively contributes to their optimization.

FinOps organizational structure: Roles and responsibilities

Effective FinOps implementation requires a clear allocation of roles and responsibilities that extend beyond traditional IT teams. FinOps is a team effort that unites various company departments [4].

FinOps Practitioner: A central role responsible for implementing and supporting the FinOps framework, analyzing costs, developing optimization policies, and coordinating across teams. They act as a bridge between IT, finance, and business.
Cloud Engineers / Developers: Responsible for the technical implementation of optimization measures, such as rightsizing resources, using efficient architectures, and automation.
Finance Business Partner: Financial professionals who collaborate with IT teams to understand cloud costs, budgeting, forecasting, and ensuring financial accountability.
Product Owner / Business Owner: Responsible for the business value generated by cloud resources. They make decisions regarding cloud investments, considering the balance between costs and benefits.

The success of FinOps depends on how well these roles interact, share information, and collaboratively work towards financial and business goals. In smaller companies, these roles may be combined; for example, a FinOps Practitioner might also perform the functions of a Finance Business Partner for cloud expenses.

Tools for FinOps implementation: Monitoring, analysis, and automation

Effective FinOps implementation requires a set of tools that ensure transparency, control, and automation of cloud cost management.

Built-in cloud provider tools: Every major cloud provider offers its own tools for monitoring and managing costs. For example, Azure Cost Management and Billing provides detailed cost reports, the ability to set budgets, alerts, and analyze resource usage [5]. Similar tools are available in AWS (Cost Explorer) [6] and Google Cloud (Cloud Billing reports) [7]. These serve as a starting point for most companies.
Third-party FinOps platforms: Specialized platforms (e.g., CloudHealth [8], Apptio Cloudability [9]) exist that aggregate data from various cloud providers, offering advanced capabilities for analysis, optimization, and automation.
Automation tools: To implement the "Operate" principles, automation tools are needed that can shut down unused resources, resize them, or apply reservation policies based on defined rules.

The choice of tools depends on the company's scale and the number of cloud providers used. For small companies or those using a single provider, native tools may suffice. For large companies with a multi-cloud environment, third-party platforms should be considered. The main goal is to ensure a single source of truth for cloud costs and the ability to act on the data obtained.

Step-by-step plan for FinOps implementation in a Ukrainian company

Implementing FinOps is a journey, not a one-time project. Here's a step-by-step plan:

Assess current state and gain executive support: Conduct an audit of current cloud costs, identify pain points, and potential areas for optimization. Present a FinOps business case to management, highlighting potential savings and efficiency gains.
Form a FinOps team or assign responsibilities: In the initial stage, this can be a small cross-functional group of representatives from IT, finance, and business who will drive the change.
Implement a tagging system: Develop a clear tagging strategy for all cloud resources to correctly allocate costs by projects, teams, environments, etc. This is the foundation for transparency.
Set up monitoring and reporting: Use built-in cloud provider tools or third-party platforms to collect cost data and generate regular reports. Ensure these reports are accessible to all stakeholders.
Define and implement optimization policies: Based on data analysis, develop and implement policies for rightsizing resources, utilizing reservations, and identifying and removing unused resources. Start with pilot projects.
Integrate FinOps into CI/CD processes: Educate developers and DevOps engineers on FinOps principles so they consider resource costs during the design and deployment phases.
Conduct regular Cost Review Meetings: Establish regular meetings between IT, finance, and business to discuss cloud costs, analyze the effectiveness of optimization measures, and plan future actions.
Automation and continuous improvement: Gradually automate routine cost management tasks. Cultivate a culture of continuous learning and improvement of FinOps practices throughout the company.

Pros and cons of FinOps implementation

Implementing FinOps, while beneficial, has its challenges and potential drawbacks that should be considered.

Pros:

Reduced cloud costs: Resource optimization, leveraging discounts, and eliminating unused services can significantly cut operational expenses.
Increased transparency and accountability: A clear understanding of who is spending what on cloud resources ensures better control and more informed decisions.
Maximized business value: FinOps helps invest in the cloud in a way that yields maximum business returns.
Improved collaboration: Fosters interaction between IT, finance, and business, breaking down silos.
Faster innovation: Through efficient cost management, companies can allocate resources to new projects more quickly.

Cons:

Initial investment: FinOps implementation requires time, resources, and investment in training, tools, and process changes.
Resistance to change: Cultural and habitual changes may face resistance from employees, especially developers accustomed to unlimited resource access.
Integration complexity: Integrating FinOps tools and processes into existing systems can be complex.
Need for expertise: Effective implementation requires specialists with an understanding of both cloud technologies and financial management.
Need for continuous monitoring: FinOps is an ongoing process that requires constant monitoring and adaptation.

A balanced approach to these aspects will allow Ukrainian companies to successfully implement FinOps and derive maximum benefit from it.

[1] FinOps Foundation. What is FinOps? URL: ¹

[2] FinOps Foundation. FinOps Principles. URL: ²

[3] FinOps Foundation. FinOps Framework. URL: ³

[4] FinOps Foundation. FinOps Capabilities. URL: ⁴

[5] Microsoft Azure. Azure Cost Management + Billing documentation. URL: ⁵

[6] AWS. AWS Cost Explorer. URL: https://aws.amazon.com/aws-cost-management/aws-cost-explorer/

[7] Google Cloud. Cloud Billing reports. URL: https://cloud.google.com/billing/docs/how-to/reports

[8] VMware. CloudHealth by VMware. URL: https://cloudhealth.vmware.com/

[9] Apptio. Cloudability. URL: https://www.apptio.com/products/cloudability/

Softline IT helps teams plan and implement cloud and hybrid solutions, from an assessment of the current environment to an agreed change plan.