Skip to content
Cloud

Haven Systems saved 36% on AWS with Savings Plans and reserved databases

A 24-person healthcare software firm ran a stable AWS workload entirely on on-demand pricing. Right-sizing first, then covering the baseline with Savings Plans and reserved instances, cut the bill from ₹2.5L to ₹1.6L a month.

  • Healthcare software development
  • 24 people · Small
  • Vadodara
  • 3 weeks

Monthly spend

₹2.5L₹1.6L
Saved / month
₹90k
Reduction
36%
Payback
2 weeks

−36%

AWS spend

₹10.8L

Annual saving

85%

Savings Plan coverage

₹0

Upfront payment

The challenge

Haven's workload had barely changed in two years, yet it paid full on-demand rates for everything. The team worried that commitments would lock them into the wrong sizes.

Compliance requirements meant changes had to be carefully planned and documented.

What we reviewed

  • AWS Cost Explorer and Savings Plans recommendations
  • EC2, RDS, ElastiCache and OpenSearch utilization
  • Workload growth plans for the next 18 months
  • Compliance and change-management requirements

The approach

  1. 1

    Right-size before committing

    Six instances were downsized first, so commitments would cover only what was truly needed.

  2. 2

    Compute Savings Plan

    A one-year, no-upfront Compute Savings Plan covers 85% of steady compute and flexes across instance families.

  3. 3

    Reserve the databases

    RDS and ElastiCache moved to one-year reserved instances matched to the right-sized classes.

  4. 4

    Document for compliance

    Every change came with an impact note and rollback step for the client's audit trail.

Before and after

Monthly cost by line item, in Indian rupees.

Haven Systems — monthly cloud spend

Line itemBeforeAfterSaving
EC2 on-demand compute₹1,30,000—−₹1,30,000
EC2 under Compute Savings Plan—₹74,000+₹74,000
RDS (on-demand → reserved)₹58,000₹38,000−₹20,000
ElastiCache and OpenSearch₹32,000₹22,000−₹10,000
S3, EBS and data transfer₹30,000₹26,000−₹4,000
Total₹2,50,000₹1,60,000₹90,000 (36%)

Monthly spend over time

₹10.8L saved per year

Two months before the engagement, then six months after the plan was delivered.

Timeline

  1. Week 1

    Analysis

    Utilization and commitment options modelled.

  2. Week 2

    Right-sizing

    Downsizing validated and applied in maintenance windows.

  3. Week 3

    Commitments

    Savings Plan and reservations purchased; plan delivered.

“We had avoided Savings Plans for two years because we were afraid of getting it wrong. They right-sized first, then committed. It was simple once someone did the maths properly.”
RBRajesh BhattFounder & CEO, Haven Systems

Find out what your agency could save

Book a 20-minute call. We'll show you where the quickest wins usually are for a team like yours, with no data required and no obligation.

  • Free 20-minute assessment
  • NDA before any data is shared
  • Fixed-scope quote, 30/70 payment terms
  • 7 days of post-delivery support
Chat with us