EdTech & Learning Platform Solutions Solutions
Helping UK education and training providers build learner dashboards, progress engines, and apprenticeship platforms that consolidate data across VLEs, e-portfolio systems, and internal tools. Senior architecture and hands-on delivery for Ofsted-driven and compliance-driven programmes, integrating systems like OneFile, Moodle-derived VLEs, and bespoke learner records into a single coherent experience.
Challenges we solve in EdTech & Learning Platform Solutions
Multi-source data consolidation
Learner records sit across VLEs, e-portfolio platforms, internal databases, and SharePoint spreadsheets. Bringing them into a single coherent view, without forcing every consuming system to know about every source, is harder than it looks.
Ofsted and compliance readiness
Inspections move faster than software roadmaps. EdTech platforms need to surface progress, off-the-job hours, and supervisor visibility in time for inspection windows, not the next major release.
Apprenticeship progress calculation
Period-based benchmarks, off-the-job hours, e-portfolio assessments, and breaks all feed into RAG status. The calculation logic is more product than plumbing, and it has to match what tutors and clients already see in their existing reports.
Legacy VLE integration
Established VLEs were not built for deep linking, modern SSO, or partial UI takeovers. Integrations have to respect what the VLE owns and avoid forking workflows that staff already rely on.
Authentication across systems
Learners, tutors, and supervisors typically authenticate against separate identity providers. SAML, OIDC, and Auth0 have to be wired together so users do not lose context as they move between dashboards and underlying tools.
Real-time vs batch data freshness
Some data sources expose APIs, others only ship overnight CSVs. Designing the platform so the user experience does not silently suffer when a feed is a day stale is a recurring product question, not just a technical one.
EdTech & Learning Platform Solutions Case Studies
See how we've helped EdTech & Learning Platform Solutions businesses achieve their goals
From Kickoff to Working Proof of Concept in One Week with Claude Code
A UK education provider needed a greenfield learner dashboard built against three unfamiliar third-party platforms, with a predominantly junior team and an Ofsted-driven deadline. By the end of week one I had a runnable Vue.js front end and matching C# back end the team could build on for the next three months.
Read case study →Restoring F5 Development to a Multi-Service Learning Platform with .NET Aspire
A greenfield learner platform was about to inherit the usual microservice tax: a docker-compose file, mocked dependencies, and developers running half the stack on faith. .NET Aspire let me give the team a true F5 development experience across services, SQL, Blob storage and Redis from day one.
Read case study →Unifying Three Source Systems Into a Single Learner View
Tutors were flipping between three systems to answer basic questions about learner progress. I designed a backend-for-frontend, a progress engine, and a clean front-end contract that pulled Campus (PostgreSQL), Beehive (a legacy VLE) and OneFile (an external e-portfolio SaaS) into one dashboard, with mixed real-time and batch data handled honestly underneath.
Read case study →Pivoting an Integration to Source SFTP Two Weeks Before Contract End
Two weeks before contract end, the planned ingest path for the e-portfolio integration turned out to be a labelled proof of concept that nobody had taken responsibility for productionising. I rewired the OneFile integration to read directly from the source SFTP feed, contained the change inside the progress engine, and shipped on time.
Read case study →Coaching a Predominantly Junior Team Through a Greenfield Aspire Build
About two-thirds of the team were junior, including bootcamp graduates and developers new to the languages they were working in. The mentoring side of the engagement was as load-bearing as the architecture itself, and the patterns I left behind were what kept the platform shippable after I left.
Read case study →Translating a Power BI Proof of Concept into a Production Progress Engine
A partner organisation's domain expert had encoded apprenticeship progress logic, period-based benchmarks, RAG status, off-the-job hours, in a Power BI proof of concept. I designed a progress engine that honoured the same calculations in production against the consolidated learner record, kept Power BI in place for internal MI, and gave the domain expert a sign-off path that did not depend on the build.
Read case study →Our EdTech & Learning Platform Solutions Expertise
Apprenticeship learner dashboards and progress engines
I have designed and led the build of greenfield apprenticeship platforms covering learner dashboards, progress engines, and integrations with OneFile, internal LMS platforms, and legacy VLEs. The work spans architecture, data mapping across multiple sources, and the period-based progress calculations that drive RAG status for tutors, supervisors, and clients.
VLE and e-portfolio integration
Most learning platforms outlive the technology they were originally built on. I integrate with Drupal-based VLEs, OneFile, and bespoke learner record systems through SAML SSO, deep linking, and database-backed adapters, so newer dashboards can sit alongside older systems without a rip-and-replace migration.
.NET Aspire for learning platform teams
Learning platforms typically end up as a small constellation of services: dashboards, progress engines, ingestion jobs, and cached data. I use .NET Aspire to give teams a true F5 development experience across the whole ecosystem, including SQL, Blob storage, and Redis, so developers can run the platform locally as one piece rather than mocking half of it.
Claude Code-led discovery and delivery
Greenfield EdTech projects often start with several unfamiliar third-party platforms and a tight inspection deadline. I use Claude Code through discovery to reverse-engineer APIs, derive component libraries from design screenshots, and produce data mappings the team can verify before any production code is written, and continue using it through the delivery itself.