Six hours to one, at global scale
A reporting-and-billing backend redesign that turned a six-hour bottleneck into one hour — and lifted data accuracy across every market.
The challenge
As Director, the reporting-and-billing backend was a bottleneck. Processing windows were long and accuracy issues surfaced across global markets — exactly the kind of problems that erode trust in the numbers customers are billed on.
What I did
I led a redesign of the reporting-and-billing backend architecture — rethinking how data moved through ETL, normalization, and aggregation so the system could scale with the business instead of fighting it.
Six hours to one. Errors cut 4×. Across every market.
The outcome
The redesign cut the daily processing window from six hours to one — at the same data volume — and cut the data-error rate roughly 4× across all markets. Client finance teams felt it directly: monthly reconciliation closed in half the time. In the same chapter I launched a net-new master data management platform (0-to-1) that turned standalone tools into a connected ecosystem — today the redesigned pipeline moves a portfolio spanning roughly 2.4 trillion rows.
Daily runtime, same data volume
Reduction in data-error rate, every market
Faster monthly client reconciliation
What it proves
Technical execution at scale, a bias for reliability and data quality, and platform thinking — turning a bottleneck into foundational infrastructure the business could build on.