Data architecture audit
Diagnose the DWH and the data platform: workarounds, risks, growth stalls.
I come into a company where the DWH or platform is already running, but something is off. Slow reports, a growing engineering backlog, regulator questions, migration talk. I look at the architecture with the eyes of someone who has built it inside several banks.
I walk the layers: raw, core, mart. Ingestion, orchestration, governance, metrics. I record gaps between what the documentation claims and what actually runs. I put a price and a timeline on the technical debt.
The output is a report: AS-IS diagrams, a prioritized issue list, and three 12–24 month scenarios. Each scenario carries a cost and risk estimate. The decision stays with you.
- For whom
- CTOs, Heads of Data, VPs of Engineering in banks and fintech with an existing DWH they don't want to rewrite from scratch.
- We solve
- Regulator reports get assembled by hand and slip deadlines. Data engineers complain about legacy. Migration is on the table with no clear target. Prior consultants left a deck, not a plan.
- Deliverables
- A 30–50 page report: AS-IS architecture and data flow diagrams, a prioritized issue list, three 12–24 month development scenarios with time and budget estimates, and an executive summary for the CTO and CFO.
- Format
- Remote, plus 3–5 days on-site for team interviews.
- Duration
- 3–4 weeks.