SquareOps
Get an architecture review

How SquareOps Cut a Fintech's $265K Monthly AWS Bill by 41%

Ankush Madaan November 16, 2026 Case Studies

Introduction

A fintech company cut its monthly AWS bill from about $265K to about $155K. That is about $110K a month less (about 41%), or about $1.3M a year. SquareOps worked on a success fee: we are paid a share of the savings we verify, and if there are no savings, there is no fee. The savings came from engineering work, not discounts. Our engineers set the right resource requests for its Kubernetes workloads, moved them from AWS Fargate to Graviton-based EC2 nodes managed by Karpenter, and ran most stateless workloads on Spot or a mix of Spot and On-Demand. All of this was done in about two to three months, before any Savings Plans or other commitment discounts were bought.

  • Before: about $265K a month in cloud spend.
  • After: about $155K a month.
  • Saving: about $110K a month (about 41%), or about $1.3M a year.
  • How: right-sized resource requests, a move from Fargate to Graviton EC2 nodes with Karpenter, and Spot for stateless workloads. Commitments came last.
  • Commercial model: a success fee. No savings, no fee.

Client Overview

This case study is anonymous: it does not name the client, and all figures are rounded. When the engagement began, the client, a fintech company, was spending about $265K a month on AWS. Its applications ran as containers on Amazon EKS, with the pods running on AWS Fargate.

The Challenge

A bill this size invites a quick fix, and both of the usual quick fixes leave money on the table.

  • Buying commitments first. Savings Plans bought against today's usage give a discount, but they also lock in spend on capacity that could have been removed or moved to something cheaper. The commitment is sized to the waste.
  • Relying on a dashboard alone. A FinOps tool ranks the waste, but someone still has to change each resource, test the change and prove the saving. The biggest savings come from changes that no dashboard makes on its own: what kind of capacity a workload runs on, which instance types it uses, and which processor family it is built for.
  • Keeping production safe. Every one of those changes touches running systems. Each has to be tested and rolled out carefully, with the client's team approving it.

How the Success-Fee Engagement Worked

SquareOps was paid a share of the savings it verified. If no savings were verified, there was no fee. This puts the partner on the same side as the finance team: the fee exists only if the bill actually goes down. It also points the work at the changes that save the most, not at the ones that are easiest to put in a report.

SpendZero, the cloud cost tool built by SquareOps, is included free with every success-fee engagement, so the client paid nothing extra for tooling. Our engineers used it to map the client's overall cloud usage and find where it could save, with the most detail on the Kubernetes side: which workloads asked for more CPU and memory than they used.

The full terms of the model, including how savings are verified, are on our success-fee cloud cost optimization page.

What SquareOps Did: Engineering First, Commitments Last

The order of the work mattered as much as the work itself. First our engineers reduced what the workloads cost to run. Only then did it make sense to think about discounts.

1. Set the Right Resource Requests

On Fargate, each pod is billed for the CPU and memory it requests, not for what it uses. Requests that are set high "to be safe" are paid for every hour. Our engineers mapped each workload's real usage and set its requests to match, so capacity follows what the workloads need.

2. Moved from Fargate to Graviton EC2 Nodes with Karpenter

The workloads moved off Fargate onto EC2 worker nodes managed by Karpenter, which picks node types to fit the pods that need to run and removes nodes that are no longer needed. The nodes run on AWS Graviton, AWS's Arm-based processors, which cost less than comparable x86 instances.

Moving to Graviton is more than changing an instance type: the software has to run on Arm. Our team rewrote the Dockerfiles and the CI/CD pipelines so every service builds Arm images, and tested each workload under real load before it took production traffic.

3. Ran Stateless Workloads on Spot

Spot capacity is spare AWS compute sold at a discount. AWS can take it back at short notice, so it suits workloads that can be interrupted and restarted without harm. Most of the client's stateless workloads moved to Spot, and others to a mix of Spot and On-Demand nodes, so a Spot interruption never takes a whole service down. Workloads that cannot be interrupted stayed On-Demand.

4. Every Change Through Terraform, Reviewed by the Client

All infrastructure changes were made as code in Terraform, each as a pull request that the client's leadership team reviewed before it was applied. Nothing was changed by hand in the console, so every change is recorded and the client's team can run the setup on its own.

5. Commitment Discounts Stayed with the Client

The roughly $110K a month in savings came before any Savings Plans or commitment discounts were bought. SquareOps' part was the engineering work. The client's own team buys commitments as part of its normal process, so any commitment is now sized on the lower bill, not on capacity that was about to be removed.

Results

Monthly cloud bill before and after the engineering changes (rounded)
MeasureValue
Monthly bill beforeAbout $265K
Monthly bill afterAbout $155K
Monthly savingAbout $110K (about 41%)
Yearly savingAbout $1.3M
Commitment discounts bought before the savingNone

No commitment discounts had been bought, so the saving came from changing how the workloads run, not from a discount on the same usage. The work took about two to three months, including the rewrite of the build pipelines for Graviton.

What the Client Does Now

About $155K a month is now the starting point for any further work and any commitment decision. SquareOps has handed the setup over to the client's team. Because every change lives in Terraform and went through reviewed pull requests, the team owns and runs it without us.

What Other Teams Can Take From This

  • Cut before you commit. Remove waste and move to cheaper capacity first, then size Savings Plans or other commitments on the lower bill.
  • The biggest savings are engineering changes. Spot, the right instance types and Graviton each need engineers to change, test and roll out workloads. A report can point to them but cannot make them.
  • Pay for results. A fee tied to verified savings means your partner is paid only when your bill actually drops.

To see where your own bill stands, you can run a free first scan with SpendZero. If you want engineers to make the changes and be paid only from verified savings, book a free cloud cost assessment with our success-fee team.

Frequently Asked Questions

How did SquareOps cut a $265K monthly cloud bill by 41%?

SquareOps engineers set the right resource requests for the client's Kubernetes workloads on Amazon EKS, moved them from AWS Fargate to Graviton-based EC2 nodes managed by Karpenter, and ran most stateless workloads on Spot or a Spot and On-Demand mix. The bill fell from about $265K to about $155K a month, about $110K a month or about $1.3M a year. All of this was done before any Savings Plans or commitment discounts were bought.

How does a success-fee FinOps engagement work?

In a success-fee engagement, SquareOps is paid a share of the cloud savings it verifies, not for hours or a subscription. If no savings are verified, there is no fee. Our engineers make the changes with the client's approval, and SpendZero, SquareOps' cloud cost tool, is included free for the engagement.

Why were Savings Plans bought last instead of first?

Savings Plans and other commitment discounts lock in spend for a period. Bought first, they are sized on a bill that still contains waste and capacity that could move to cheaper options. Cutting the bill first through Spot, the right instance types and Graviton means any commitment is sized on the lower bill.

What does moving workloads to AWS Graviton involve?

AWS Graviton instances use Arm-based processors and cost less than comparable x86 instances. Moving to them means the software must run on Arm: builds, container images and dependencies with native code need Arm versions, and each workload must be tested under real load before it takes production traffic.

Is SpendZero included in a success-fee engagement?

Yes. SpendZero, the cloud cost tool built by SquareOps, is included free with every success-fee engagement, so there is no separate tool subscription while the engagement runs.