Federated Data Layer
dbt-based transformations connecting to Postgres, MS-SQL, Salesforce, and a custom REST API. Refreshes every 15 minutes.
A national tertiary institution was using six different systems for admissions, fees, attendance and academic records. Senior leadership reviewed performance with PowerPoints stitched together every Monday morning.

A 22,000-student national tertiary institution across two campuses, running on a patchwork of six systems: a custom student information system, a finance ERP, an LMS, a CRM for prospective students, an attendance system, and an HR system for academic staff. Reports for the VC every Monday were stitched together by hand.
No system was authoritative — different reports gave different numbers
Late fees were tracked weeks after the fact
Admissions team could not predict enrolment within ±15%
Parent communication was email-only and non-personalised
Monthly board reports took 3 days of dedicated effort
dbt-based transformations connecting to Postgres, MS-SQL, Salesforce, and a custom REST API. Refreshes every 15 minutes.
Live VC/Registrar/CFO view of enrolment, fees, attendance, exam results, drilldown to the student level.
Forecast intake by faculty and programme, ±4% accuracy, with the underlying features visible to admissions.
Mobile-first portal showing fee balance, payment history, statements; pays via Stripe and local mobile-money rails.
"Our Monday review used to take a team of four three days to prepare. Now it lives on a screen."
— Vice-Chancellor, national tertiary institution