ETL Cost Benchmarks SME

An ETL cost audit cut a small team’s bill by roughly a third. Same 4 patterns I always find.

ETL spend has a property that makes it grow unwatched: it’s everyone’s tooling and nobody’s budget line. The bill rises a few percent a month, always explainable, never anyone’s fault.

The 4 patterns, in the order of usual savings:

1. Full reloads where increments would do. The job was written in week one, the table was small then. It reloads 2 years of history nightly now.
2. Compute running between jobs. Clusters and warehouses idling on generous auto-suspend settings, or none.
3. The same source ingested twice. Two teams, two connectors, one API, double the cost, and eventually two versions of the truth.
4. Retry storms. An orchestrator retrying a failing job every 10 minutes all weekend does real damage on scan-priced systems.

The whole audit is one afternoon with the billing export and the job logs you already have. All 4 patterns show up there.

A useful habit afterwards: the ETL line gets an owner and a monthly glance. Growth needs a reason.

When did someone last read the ETL line of your cloud bill with intent to change it?