Zhivko Todorov
ALL CASE STUDIES

CASE 31 · PIVOT · 2024

TAG POLICIESCOST ALLOCATIONORGANIZATIONSSCP

Cost allocation that finance trusts because tags actually exist.

A retail e-commerce company had been promising the finance team a per-team cost report for two years. The blocker was always the same: tag coverage hovered around 60% and what existed wasn’t consistent. We rolled out org-level Tag Policies plus SCP enforcement, with a six-week amnesty for backfill.

INDUSTRY

Retail e-commerce

DOMAIN

LANDING ZONE

DELIVERED

2024

STACK

AWS ORGANIZATIONS·TAG POLICIES·SCP·COST CATEGORIES·CUR·CONFIG

RESULTS

What changed, by the numbers.

TAG COVERAGE

99.6%

WAS 58%

FINANCE REPORT

SHIPPED

AFTER 2 YEARS OF PROMISES

POLICY CASES

7 → 0

DEVIATIONS RESOLVED

BACKFILL TIME

6w

WITH AMNESTY

HOW IT WENT

The first finance meeting confirmed what we already knew: every previous attempt to enforce tags had failed because the cost of doing it correctly was front-loaded onto teams and the benefit accrued to finance. We restructured the incentive — finance ran the amnesty programme themselves, with a dashboard each team could fix without ticket overhead.

Tag Policies defined the canonical key/value shapes. SCP enforced creation only when the required tags were present (after the amnesty). Cost Categories rolled the tags into the finance-team-friendly hierarchy. Config alerted on drift.

The finance report shipped in week seven. Two of the cost categories were genuinely surprising — one product line was 4x more expensive than the team had assumed. Conversations followed. Architecture changes followed those.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →