---
title: "cost management tooling | Skills We Assign For | Azendo"
description: "Cloud cost management — attribution, waste, commitment discipline, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/cost-management-tooling/"
---

[Skills](https://azendo.co/skills/) Cloud and infrastructure 

# cost management tooling.

Cloud cost management covers the tooling and practice of attributing spend to teams and services, forecasting it, and identifying waste. It turns an undifferentiated monthly bill into something specific people can act on.

## Where cost management tooling fits on a long engagement.

Attribution is the prerequisite for everything else. A bill that cannot be broken down by team, service or environment produces meetings about the total and no decisions, because nobody owns a number they can change. Consistent tagging, enforced at creation rather than audited later, is what makes the rest possible.

The recurring waste is consistent across estates: development environments running at night and at weekends, over-provisioned instances chosen from a guess, orphaned volumes and unattached addresses, and old snapshots nobody scheduled for deletion. None require architectural change, and together they are usually a substantial proportion of a bill.

## What an assigned team does with cost management tooling.

Cost optimisation done once produces a saving that erodes. New resources are created untagged, environments are resized upward and never back down, and a year later the estate has drifted back.

Keeping it in hand is continuous rather than a project, which is why it is part of an agreed [committed monthly capacity](https://azendo.co/pricing/) rather than a one-off exercise.

## What we use cost management tooling for.

* Spend attributable to a team Tagging enforced at creation, so every cost has an owner who can act on it.
* The standard waste removed Idle environments, orphaned volumes and oversized instances found and corrected.
* Commitments bought against real usage Reserved and savings-plan decisions made from measured baseline rather than optimism.

## How cost management tooling capacity is assigned.

Cost work is assigned under [devops as a service](https://azendo.co/services/cloud-and-devops/), treated as continuous because an optimised estate drifts back within a year.

## Roles we assign cost management tooling for

* [Cloud Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/cloud-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in cloud and infrastructure

* [Kubernetes — skill we assign for](https://azendo.co/skills/kubernetes/)
* [Docker — skill we assign for](https://azendo.co/skills/docker/)
* [Terraform — skill we assign for](https://azendo.co/skills/terraform/)
* [AWS — skill we assign for](https://azendo.co/skills/aws/)
* [Azure — skill we assign for](https://azendo.co/skills/azure/)
* [GCP — skill we assign for](https://azendo.co/skills/gcp/)
* [Terraform modules — skill we assign for](https://azendo.co/skills/terraform-modules/)
* [Pulumi — skill we assign for](https://azendo.co/skills/pulumi/)

## Tell us what your roadmap needs cost management tooling for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)