Overview
Industry: Heavy Vehicle Manufacturing
Geography: Japan & India
Technologies: Microsoft Azure, Reserved Instances, Azure Hybrid Benefit
The Situation
A global heavy vehicle manufacturer was running a USD 4 million annual Azure bill and leadership knew a significant portion of it was waste. Cloud adoption had moved fast, and the environment had grown organically: old test environments left running, resources provisioned for projects that had ended, compute sized for peak loads that rarely occurred.
With no clear line of sight into what was truly necessary, and no governance model to prevent overspend from accumulating again, the organisation needed a partner who could find the waste quickly, eliminate it safely, and leave a cost management discipline in place.
What Codincity Did
Codincity deployed a FinOps team across six focused Agile sprints, starting with a full discovery of Azure resources mapped against actual business need and utilisation data.
Rightsized virtual machines and PaaS services scaling down oversized resources to match real workload requirements without impacting performance.
Decommissioned idle test environments, unattached storage disks, orphaned network cards, and redundant backup jobs that were generating cost with no business value.
Applied Reserved Instances selectively to steady-state workloads, locking in lower pricing on resources the business was consistently using.
Implemented auto-shutdown policies for non-production environments, preventing idle resources from running and billing outside working hours.
Applied Azure Hybrid Benefit to eligible workloads, converting existing software licences into immediate cloud savings.
Established cost alerts, budget thresholds, tagging standards, and a regular review cadence ensuring savings are maintained as the environment evolves.
Business Impact
USD 510,000 saved within the first six weeks of engagement.
USD 768,000 in annualised savings nearly 20% of the organisation's total Azure spend.
28% in total optimisation opportunities identified, with a clear roadmap for capturing remaining savings as part of business-as-usual operations.
A FinOps operating model established cost accountability embedded across teams, with governance in place to prevent overspend from re-accumulating.
What It Means Going Forward
Cost savings are only part of the outcome. What Codincity left behind was a FinOps practice a way of thinking about cloud spend that connects costs to business outcomes, creates team-level accountability, and catches overspend before it becomes a problem.
The client no longer has a cloud cost problem. They have a cloud cost practice.
Conclusion
Cloud cost optimization delivers the greatest value when it becomes an ongoing business discipline rather than a one-time initiative. By combining rapid savings with a structured FinOps approach, Codincity helped the organization reduce Azure spend, improve cost visibility, and establish governance practices that support long-term financial accountability. The result is a more efficient cloud environment that enables the business to scale with confidence while maintaining control over its technology investments.
