Analytics platforms
Real-time views for policymakers and school leaders, built on data they already collect.
We rebuilt a national education analytics platform for a Norwegian technology company after a previous supplier missed the deadline, and migrated years of sensitive data without taking the service down.
Education platforms rarely start from nothing. There is a legacy system holding years of records, a contract with real users behind it, and a deadline somebody else already missed.
Years of sensitive records have to move with nothing lost and nothing exposed. We put a dedicated team on that alone.
Splitting the system into independent modules let workstreams run in parallel.
Real-time views for policymakers and school leaders, built on data they already collect.
Analysis, mapping and structured transfer of records that cannot be lost or exposed.
Independent modules so delivery can run in parallel and a slip in one does not stop the rest.
Penetration testing, static analysis and network vulnerability assessment as part of delivery.
The platforms teachers and pupils use, and the admin systems behind them.
Monitoring and optimisation after launch, which is when most platforms are abandoned.
The data is about children, which changes what careless looks like.

A Norwegian technology company needed its national education analytics platform modernised after a previous vendor missed the deadline and budget. We split the system into modules, put a dedicated team on the data migration, and applied penetration testing, static analysis and network assessment during delivery.
Vendors with a platform to modernise and a contract that does not pause while they do it.
Where the reporting obligation is statutory and the calendar is fixed.
Administration and analytics across many sites that never quite match.
Teams whose product is the data, and whose risk is the migration.
See the full write-up in the education platform case study, or the rest of our case studies.
Yes, and it is a large part of what we do. The first step is documenting what exists so you own it again. Rewriting waits until that is done.
With a team that does nothing else. Legacy analysis, mapping and structured transfer, planned so daily operations keep running.
Part of delivery. Penetration testing, static analysis and network vulnerability assessment ran alongside the build on the platform we rebuilt.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes with the engineers on the platform you have, the data inside it and the date you are working to.