Cost culture doesn't require a program or a process

It requires habits. Small, consistent, not dramatic

Here are the ones that actually make a difference in small teams

Weekly bill review: 15 minutes, once a week, someone looks at the cost dashboard. Not to analyze deeply. Just to notice. Did anything spike? Is anything trending in a direction that needs attention? The value is the regular attention, not the length of the review

Tagging before deploying: before any new resource goes into production, it has a tag. Team. Service. Environment. Created date. This takes 30 seconds and it means that six months from now when someone looks at that resource they have context instead of mystery

Shutdown schedules on non-production: dev and staging environments run when people are working. They don't run at 3am. They don't run on weekends. This is a one-time configuration that saves real money every month forever

Cost check in architecture reviews: when a team is designing a new service or a significant change to an existing one, cost is on the checklist. Not the only thing. Not even the most important thing. Just on the list. "What will this cost to run at our current scale and at 10x scale?"

These habits don't require a platform. They don't require a dedicated tool. They don't require a dedicated role

They require someone to decide that this is how the team works now

The hardest part of building cost culture is not the technical implementation

It's the first few weeks when the habit isn't automatic yet. When the weekly review gets skipped because there's a crisis. When the tagging gets forgotten because the deploy was rushed

The habits that stick are the ones connected to existing workflows. Add the cost check to the architecture review that already exists. Add the tag requirement to the deployment checklist that already exists. Add the weekly bill review to the Monday planning meeting that already exists

Attach the new behavior to something that already happens

The behavior becomes automatic faster when it doesn't require a new trigger