Meridian Digital took ₹6.6L a month out of a ₹22L multi-cloud bill
A 400-person engineering services firm running workloads across AWS, Azure and GCP had no single view of spend. We built a FinOps operating model, cleaned up non-production sprawl and aligned commitments across all three clouds.
- Digital engineering services
- 400 people · Large
- Gurugram
- 8 weeks
Monthly spend
- Saved / month
- ₹6.6L
- Reduction
- 30%
- Payback
- 11 days
₹79L
Annual saving
22% → 71%
Commitment coverage
140
Environments retired
96%
Spend tagged to owner
The challenge
Meridian's delivery units each chose their own cloud based on client preference. The result was three bills, three sets of discounts and no shared accountability. Finance reconciled spend quarterly, long after it could be influenced.
Non-production environments had multiplied across every unit, and reserved capacity bought by one team sat idle while another paid on-demand rates.

What we reviewed
- Billing data from 3 clouds and 46 accounts or subscriptions
- Commitment and reservation inventory
- Non-production environment ownership
- Cost allocation and chargeback practices
- Delivery-unit budgets and client billing
The approach
- 1
One view of spend
We normalized billing from all three clouds into a single model with a common tagging standard, so every rupee mapped to a client, project and unit.
- 2
Non-production governance
Environment owners, expiry dates and schedules were introduced; 140 abandoned environments were decommissioned in the first month.
- 3
Portfolio-level commitments
Commitments were rebalanced at company level instead of team level, raising coverage of steady workloads from 22% to 71%.
- 4
Monthly FinOps rhythm
Unit leads now review a one-page cost report each month, with anomalies flagged within 24 hours rather than at quarter end.
Before and after
Monthly cost by line item, in Indian rupees.
Meridian Digital — monthly finops spend
Monthly| Line item | Before | After | Saving |
|---|---|---|---|
| AWS production workloads | ₹9,40,000 | ₹6,70,000 | −₹2,70,000 |
| Azure client-hosted applications | ₹5,60,000 | ₹4,00,000 | −₹1,60,000 |
| GCP data and analytics | ₹3,10,000 | ₹2,30,000 | −₹80,000 |
| Non-production environments | ₹2,40,000 | ₹1,30,000 | −₹1,10,000 |
| Storage, backup and snapshots | ₹1,50,000 | ₹1,10,000 | −₹40,000 |
| Total | ₹22,00,000 | ₹15,40,000 | ₹6,60,000 (30%) |
Monthly spend over time
₹79.2L saved per yearTwo months before the engagement, then six months after the plan was delivered.
Timeline
Weeks 1–2
Data consolidation
Billing exports from 46 accounts normalized into one model.
Weeks 3–4
Unit workshops
Review calls with each delivery unit to validate ownership and changes.
Weeks 5–6
Roadmap
Ninety-day plan with commitments, clean-up and governance.
Weeks 7–8
Operating model
Tagging policy, reporting cadence and anomaly alerts handed over.
“For the first time our delivery heads can see what their cloud choices cost, and they act on it. The savings were large, but the discipline it created is what will last.”
Related case studies
All case studies
FinOpsMonthly spend
₹31L → ₹22L
Summit Digital · 420 people · Bengaluru
Summit Digital built FinOps governance and sustained a 29% cloud cost cut
Read case study
CloudMonthly spend
₹6.4L → ₹3.9L
Northbridge Systems · 120 people · Bengaluru
Northbridge Systems cut its AWS bill from ₹6.4L to ₹3.9L a month
Read case study
CloudMonthly spend
₹7.2L → ₹4.2L
Sentra Cloud · 110 people · Pune
Sentra Cloud saved 41% on Google Cloud with committed-use discounts and idle clean-up
Read case studyFind 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