Data & Platform

    Warehouse Cost Optimization

    Warehouse bills grow in a particular way: a warehouse sized for one heavy job stays that size all month, queries nobody reads run on a schedule, and a table nobody clusters gets scanned in full every time.

    Start with the audit

    No sales layer, no juniors. You meet the engineer before anything begins.

    // What is included

    What you get

    • Idle warehouses downsized automatically instead of billing at full size
    • Scheduled queries reviewed against whether anybody reads the output
    • Table and materialisation design revisited where scan volume drives the bill
    • Spend attributed per team or workload so ownership is possible

    // How it runs

    The sequence

    1. 01

      Attribute

      Where the compute actually goes, by workload rather than in total.

    2. 02

      Trim

      Sizing, schedules and retention adjusted with the owners.

    3. 03

      Hold

      Guardrails so the bill does not drift straight back.

    // Stack

    • Snowflake
    • ClickHouse
    • AWS
    • Terraform

    // Related work

    Where this has been done before

    Client names under NDA. The numbers are not.

    Analytics warehouses under control, PII isolated (NDA)

    • Single owner for schema and migrations across both warehouses
    • Managed replication with personal data isolated from the analytics path
    • Idle warehouses downsized automatically

    Warehouse compute brought under control

    AWS bill down 46% for a data governance SaaS (NDA)

    • EC2 and ECS rightsized against real utilization
    • Eligible workloads moved to Graviton
    • S3 storage classes and ECR lifecycle policies applied

    AWS bill down 46%

    All case studies

    // Questions

    Before you ask

    Talk to the engineer who would do the work

    A 20 minute call. You describe your setup, you get an honest read on whether this helps, and the top risks worth looking at first.

    See pricing