Case study
200 hours a year back for a nine-figure expense portfolio
Delivered by our Founder inside a large enterprise, before Pharos Lumen
Financial reporting for a nine-figure annual expense portfolio ran on manual pulls and one-off requests. Standard templates and automated data pulls saved over 200 hours a year and made forecast turnaround 40% faster.
The problem
- Every report started with a manual extract from the reporting cube, which was slow and error-prone.
- Leadership asked for one-off cuts of the data, and each request pulled analysts off planned work.
What was done
- Automated the extraction and transformation with SQL and Power Query, straight from the source cube.
- Designed standard reporting templates and dashboards, so leadership could answer its own common questions.
- Documented and tightened the reporting controls, which improved audit readiness.
The result
- More than 200 hours a year saved.
- Forecast reporting turnaround: 40% faster.
- Fewer one-off requests, and multiple company-wide recognition awards for the work.
What it shows
One-off requests are a symptom. When people keep asking for the same thing, the fix is a standard they can serve themselves.
Keep reading
Related case: reporting that took weeks, now on demand
Guide: what inefficient processes cost, with the math