What Can Investment Firms Do to Control Cloud Costs While Preserving Resilience?

Connect proposed savings to business requirements, assign clear approval responsibilities, and verify that changes preserve performance and recovery capabilities.

Investment firms can control cloud costs by identifying what their resources support, assessing the operational effects of proposed reductions, and verifying the results. Finance, business, and technology leaders need to agree on the performance and recovery requirements each change must preserve. This coordination forms part of FinOps, the practice through which these teams manage technology spending together.

Consider a hypothetical investment firm reviewing the cloud resources behind its investor-reporting process. The technology lead proposes three changes: reduce production capacity, switch off a test environment outside working hours, and reduce resources maintained for recovery.

Each proposal could lower spending. Evaluating them requires an understanding of reporting deadlines, peak demand, and the team’s ability to resume work after an interruption.

Establish the requirements behind the spending

Start with the reporting team’s obligations. When must staff complete reports? How much does processing demand increase at the end of a quarter? How much time do employees need to investigate discrepancies and rerun their work?

The reporting owner can define these requirements, while the technology lead identifies the computing capacity, storage, and supporting services involved. Include dependencies such as data transfers and access services that a proposed reduction could affect.

Finance staff then need a spending baseline: which charges relate to reporting, how they vary across reporting cycles, and which would actually decrease under each proposal. Shared resources may require input from other business owners.

The reporting owner and technology lead should also agree on what the team needs to recover from an interruption. They should establish:

• How long the reporting process can remain unavailable.
• How much recent data the team could afford to lose and reconstruct.
• How those limits change as a reporting deadline approaches.

Document the answers alongside the spending baseline. They give reviewers a common basis for evaluating savings and operational consequences.

Investigate low utilization before reducing capacity

When a cloud resource shows little activity, the technology lead should check who uses it, when demand increases, and whether staff keep it available for testing or recovery. That review helps establish whether the firm can reduce its capacity, limit its operating hours, or remove it.

The FinOps Foundation’s Usage Optimization guidance recommends checking for monthly and quarterly increases in demand before reducing capacity. It also advises teams to weigh potential savings against the work, risk, and disruption involved in making the change.

At the hypothetical investment firm introduced above, the reporting team may process relatively little data between quarterly deadlines. The technology lead should examine how the production environment performs during end-of-quarter reporting before recommending a smaller configuration. Processing must finish early enough for staff to investigate discrepancies, rerun reports, and meet the deadline.

Before scheduling shutdowns for the test environment, the technology lead should ask:

• Who uses it, and during which hours?
• Do automated jobs run overnight?
• Does the team need access during late reporting cycles?
• Does it support recovery exercises?

If employees and automated processes do not need the environment outside agreed hours, the administrator can schedule shutdowns to reduce spending. Employees also need a way to request access for late reporting work or recovery exercises, and the technology lead should assign someone to manage those exceptions.

The technology lead should investigate resources without a clear owner. For example, a resource that records little activity may support an occasional report or a recovery procedure that staff have not needed recently. Before arranging its removal, the technology lead should confirm who depends on it and whether the firm still needs it.

Make the recovery consequences explicit

An investment firm may pay to keep additional computing capacity available so administrators can restore an application if its primary environment fails. That capacity may receive little use during normal operations, making it a potential target when finance and technology leaders review spending. Before proposing a reduction, the technology lead should establish how it would affect restoration time, data recovery, and the reporting team’s ability to meet its deadline.

The FinOps Foundation’s FinOps for Resiliency analysis recommends considering the business value at risk during a service disruption. Finance staff and the reporting owner can use that approach to estimate the financial consequences of missing a reporting deadline. They should also identify applicable obligations and explain where their estimates remain uncertain.

The technology lead should explain how administrators would restore reporting with fewer recovery resources available:

• Would administrators need to add computing capacity during an incident?
• How long would it take to make that capacity available and restore the reporting application?
• Which supporting services would administrators need to restore the application and its data?
• Would the reporting team have enough time afterward to check and complete the reports?

The reporting owner should assess those recovery times against the reporting calendar. An interruption early in the cycle may leave enough time to restore access, check the data, and complete reports before the deadline. The same interruption shortly before reports are due could leave staff unable to finish those checks.

The reporting owner and technology lead should also test any backup way of completing the work. If employees plan to use approved data exports while the application is unavailable, they need to confirm that those files contain sufficiently current information and that staff can prepare and check the reports using them.

The technology lead should document untested assumptions, such as how quickly administrators could add capacity during an outage or whether the reporting team could finish its work from exported data. Leaders can then decide what testing they need before approving the reduction.

Approve a specific change with clear ownership

Before approving a reduction in cloud costs, leaders need to understand the financial case, assign responsibility for implementation, and agree on how the team will respond if problems arise.

Define the savings and operating impact

The technology lead should prepare a proposal with input from finance staff and the reporting owner. The proposal should explain what will change, how much the firm expects to save, and how employees will continue meeting their obligations. Finance staff should include implementation costs and ongoing administrative work, such as maintaining schedules and handling access requests, in the financial assessment.

For the test environment, the proposal should specify operating hours, anticipated savings, and how employees can request additional access. The reporting owner can then assess whether the schedule accommodates the team’s work.

Give people authority and time to implement

The technology lead should assign an administrator to configure and test an approved change. A designated senior leader should approve any material reduction in recovery capability or change in the level of business risk the firm accepts.

McKinsey’s research on implementing FinOps describes how competing priorities and limited authority can prevent engineers from acting on opportunities for reducing cloud costs. The technology lead should confirm that the assigned administrator has permission to make the change and enough time to complete the work.

Plan for problems and changing needs

Before reducing the reporting application’s production capacity, the technology lead should document when administrators would restore its previous capacity settings. For example, the team may need to reverse the reduction if processing takes so long that reporting staff cannot complete their checks before the deadline. The implementation plan should identify who can authorize that reversal.

After confirming that scheduled shutdowns will not interrupt automated jobs or other processes that use the test environment, the assigned administrator can automate its approved shutdown and restart schedule. This reduces the administrator’s need to switch the environment off and on manually. The same administrator should update the schedule when the reporting owner approves changes to the team’s access hours.

Verify savings, performance, and recovery

After implementation, finance staff should compare actual charges with the spending baseline and determine how much the change saved. They should account for differences in demand, pricing, and other factors so leaders can distinguish savings from unrelated changes in the bill.

The technology lead and reporting owner should also check whether employees can complete their work under the revised arrangement:

• Test environment scheduling: Confirm that shutdowns and restarts occur as planned. Ask whether employees experienced delays, requested frequent exceptions, or needed additional support.
• Production resizing: Test representative demand before implementation and monitor processing afterward. Confirm that staff retain enough time to investigate discrepancies and complete reports.
• Recovery changes: Run the revised recovery procedure, record restoration time, and check that the recovered data allows employees to resume the reporting task.

Finance staff and the technology lead should keep the proposal, approval, financial results, and operational checks together. Leaders can then see what the firm saved and whether employees continued to meet reporting and recovery requirements. If the revised arrangement falls short, the responsible leaders should decide whether to adjust or reverse the change.

With that evidence, leaders can retain changes that lower spending while preserving the team’s ability to complete reports and recover from an interruption. The findings also give them a stronger basis for evaluating the next proposed reduction.

Revisit decisions as reporting needs change

As investment firms take on new commitments, process larger data volumes, or change workflows, business and technology leaders should revisit the assumptions behind earlier spending decisions. The reporting owner should communicate changes in deadlines, workload, or working hours early enough for the technology lead to reassess capacity and recovery needs.

Finance and technology leaders should schedule reviews around the firm’s spending and reporting cycles. Each review can draw on employees’ experiences and the results of earlier changes. For example:

• If reporting staff repeatedly request access outside the test environment’s scheduled hours, the reporting owner and technology lead should reconsider the schedule.
• If reports take longer to process, the technology lead should check whether the team needs additional capacity.
• If administrators take too long to restore an application during a recovery test, they should investigate the delay and test the revised procedure again.

Regular reviews help leaders keep cloud spending aligned with the work the firm needs to complete. They can maintain savings that continue to meet business requirements and adjust arrangements as those requirements change.

How Option One Technologies can help

Option One Technologies can support investment firms with cloud, managed IT, and backup and disaster recovery services as they review infrastructure spending and operational requirements. Contact our team to discuss your firm’s cloud spending, as well as the performance and recovery capabilities on which your employees depend.

Executive FAQs

Should we retire or resize a cloud resource if it has low utilization?

Not necessarily. Review demand across relevant business cycles and establish whether the resource supports recovery, testing, or infrequent processing before deciding whether to resize, schedule, or retire it.

Who should approve cloud investment changes at an investment firm?

Finance staff validate the financial case, business owners confirm operating requirements, and technology staff assess and implement the configuration. A designated senior leader should approve material changes to recovery capability or accepted business risk.

How can a firm confirm that cloud cost reductions don’t hurt resilience?

Administrators should test how quickly they can restore the application and its data. The reporting owner should confirm that employees can use the recovered data to meet reporting deadlines, while finance staff members verify the savings against the spending baseline.