Skip to main content
Engineering teams often lack direct visibility into their cloud cost footprint. FinOps stays centralized with one person or a small team, and everyone else is in the dark. When cost-saving initiatives get launched, tracking progress is fragmented, teams can’t see the impact of their work, and ownership becomes a bottleneck. This guide shows you how to scope automated cost reports to each team using Costory’s Slack, Teams, and email reports, giving every squad direct visibility into their own cloud costs.

​
Prerequisites

  • Your cloud billing data is connected to Costory (see Quickstart).
  • You have a way to scope costs per team, either via native cloud tags, via Virtual Dimensions that map resources to teams, or via Teams with persistent cost scopes.

​
What you get

  • Per-team cost reports delivered automatically via Slack, Teams, or email.
  • Each squad sees only the data relevant to them. No noise, no manual digging.
  • A continuous feedback loop that keeps teams accountable for their cloud spend.

​
How to decentralize FinOps step by step

1

Scope a view to a team

Open any view in the Cost Explorer and filter to the scope you want to report on: a specific team, service, or environment.Reports can be scoped using:
  • CSP metadata: cloud provider attributes like service name, region, or account
  • Native labels: your existing cloud resource tags
  • Virtual Dimensions: rule-based mappings to teams, environments, features, or custom groupings via Virtual Dimensions
Decentralize FinOps
2

Schedule automated delivery

Create a scheduled report from your current view. Configure the delivery channel (Slack, Teams, or email) and set the cadence: weekly or monthly.Reports run automatically, giving teams a continuous feedback loop.
Decentralize FinOps, schedule a report
For example: your backend team gets a weekly Slack report scoped to their services, your data team gets one scoped to BigQuery and Datadog, and leadership gets a monthly summary across everything.
3

Iterate and expand coverage

Start with one or two teams, validate the report content, then roll out to all squads. Combine with budgets to add spending alerts alongside the reports.

​
Next steps

Last modified on March 18, 2026