Zhivko Todorov
ALL CASE STUDIES

CASE 174 · WHARF · 2024

COST DASHBOARDSTEAM-LEVELCURFINOPS

Engineering cost ownership, by team, by day.

A B2B platform had an aggregate AWS bill the CFO saw monthly and zero per-team visibility into who spent what. Cost decisions were centralised in a small platform team. We built per-team cost dashboards and gave the teams the data.

INDUSTRY

B2B platform

DOMAIN

PLATFORM

DELIVERED

2024

STACK

COST AND USAGE REPORT·ATHENA·GLUE CATALOG·QUICKSIGHT·BACKSTAGE EMBED·TAG ENFORCEMENT

RESULTS

What changed, by the numbers.

PER-TEAM COST VISIBILITY

DAILY

WAS QUARTERLY (NEVER)

COST-AWARE PR REVIEWS

EMERGED

TEAM CULTURE

INEFFICIENT WORKLOADS

−38%

TEAMS SELF-OPTIMISE

CENTRAL COST QUEUE

−72%

PLATFORM TEAM TICKETS

HOW IT WENT

The platform team had become accidentally responsible for cost optimisation. They’d optimise; teams would un-optimise; the cycle repeated. The teams didn’t have the data — they didn’t know what their workloads cost.

The CUR landed in S3 as Parquet, partitioned by date and team-tag. Athena queries assembled per-team rollups; QuickSight rendered team-specific dashboards embedded in Backstage. Each team’s dashboard surfaced its own top spenders, anomalies, and trend.

Per-team cost visibility went from "quarterly, on request" to "daily, on the wall." A cost-aware PR review culture emerged organically — engineers started flagging "this might be expensive" in reviews without being prompted. Inefficient workloads dropped 38% as teams self-optimised the obvious wins.

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 →