Journey
Ajackus built Multiples’ automated reporting portal across four structured phases, from data audit to dynamic linking implementation.
Phase 1: Data Audit and Requirements Mapping
The Ajackus team began by conducting a thorough audit of Multiples’ existing Excel-based reporting process — documenting every data source, transformation step, report category, and output format in use. This audit mapped not just what was being produced, but why each report was structured the way it was, ensuring that the automated system would produce output that matched the analytical judgements embedded in the existing process.
Phase 2: ETL Pipeline Design and Build
Using Extract, Transform, Load (ETL) methodology, the Ajackus team designed a customised data pipeline that ingests raw data from Multiples’ source systems, applies the firm’s specific transformation logic (including filtering, categorisation, and calculation rules), and produces clean, structured data ready for reporting. Intermediate data formats were created with appropriate filters to ensure that the right data reached the right report type — without cross-contamination or duplication. The ETL pipeline was built to Multiples’ specific portfolio taxonomy and investor reporting requirements, not to a generic finance template.
Phase 3: Data Portal and Reporting Layer Build
On top of the ETL pipeline, the Ajackus team built a data portal interface that enables Multiples’ team to generate any supported report type on demand — without any technical knowledge or developer involvement. The portal supports: Profit and Loss statements, portfolio sample reports, portfolio summary views, investor performance analyses, and distribution reports. Power BI was used for the reporting and visualisation layer, providing Multiples’ team with interactive dashboards and export-ready report formats aligned with their client communication standards.
Phase 4: Dynamic Linking and Version Control Resolution
A persistent challenge with Excel-based reporting is version proliferation — multiple copies of the same report at different points in time, with no clear indication of which is current. The Ajackus team implemented dynamic linking across the data portal, ensuring that all reports always reflect the most current underlying data. When source data is updated, every connected report updates automatically — eliminating version conflicts and the need for manual reconciliation.