Cutting a SaaS dashboard's data footprint from gigabytes to megabytes
Confidential SaaS client
GB → ~178 MB payload
Problem
The product's core dashboard loaded raw, unaggregated datasets on every request. As customer accounts grew, load times stretched into tens of seconds and infrastructure costs climbed with them.
Challenge
The data volume itself wasn't the real constraint — the query and transport strategy was. Every view re-fetched and re-computed data that changed rarely, with no aggregation layer in between.
Solution
Redesigned the data pipeline around pre-aggregation, incremental queries, and a caching layer, and restructured the API contract so the client only ever received what a given view actually needed.
Result
Dashboard payload dropped from gigabyte-scale to roughly 178 MB per session, with load times improving from tens of seconds to near-instant.
