06 / EDUCATION
Learning platforms serve twousers at once.
Educational software has to work for the learner and for the person responsible for their progress. We build curriculum delivery, learning platforms and progress systems that serve both — a competency developed through delivered work in the sector.
THE PROBLEM
Two audiences, one system
A learning platform is used by learners who need it to be simple, and by educators and administrators who need it to be complete. Optimising for one at the expense of the other is the most common failure in the category.
Add institutional procurement cycles, accessibility obligations, and content that must be updated by non-technical staff, and the platform requirements extend well past content delivery.
SYSTEMS WE BUILD
What we build for education.
01
Curriculum platforms
Structured content delivery with sequencing, scheduling and differentiation built into the model.
02
Learning management
Enrolment, cohorts, assignment and completion tracking across programmes.
03
Progress and reporting
Reporting for educators and administrators that reflects the outcomes the institution is measured on.
04
Content authoring
Tooling that lets non-technical staff maintain and publish material without an engineering request.
05
Accessible delivery
Interfaces built to accessibility standards, because in this sector it is a requirement rather than a preference.
INTELLIGENCE
Where AI genuinely changes the outcome.
And, just as importantly, where it does not. We are direct about which problems in this sector are better solved with conventional software.
Content adaptation
Producing variants of existing material for different reading levels and contexts, with educator review before publication.
Progress insight
Surfacing where a cohort is struggling early enough for an educator to act on it.
Administrative reduction
Automating the reporting and documentation work that takes educators away from teaching.
CAPABILITIES
Recurring product requirements.
- Content delivery
- Cohort management
- Progress tracking
- Authoring tools
- Accessibility
- Reporting
- Integrations
RELEVANT WORK
Delivered in this sector.
PROCESS
From ambiguity to production.
01
Discover
Understand the business, the users, the constraints and the actual opportunity — including where software is not the answer.
02
Architect
Define the product, the AI approach, the data model and the system architecture, with the trade-offs written down rather than assumed.
03
Build
Engineer the software and the intelligence layers together, in short cycles, against criteria agreed before work started.
04
Validate
Test functionality, quality, security and — where models are involved — behaviour, against inputs that reflect real use.
05
Deploy
Launch through infrastructure and pipelines built for repeatable release, with a rollback path that has been exercised.
06
Evolve
Observe how the system behaves in production, improve it against that evidence, and scale what is working.
TECHNOLOGY
Typical stack for this work.
Product
- React
- Next.js
- TypeScript
- JavaScript
- Node.js
- Express
- ASP.NET
- Laravel
- Ruby on Rails
- Vue.js
- Nuxt
- Tailwind CSS
Cloud & DevOps
- AWS
- Azure
- Google Cloud
- Docker
- Kubernetes
- Terraform
- Jenkins
- Git
- Bitbucket
Data
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Firebase
- Power BI
- Plotly
- Seaborn
- Dash
- Scala
FAQ
Common questions.
Yes. We target WCAG AA across all work, and in education it is treated as a delivery requirement subject to testing rather than a review item at the end.
That is normally a core requirement. Authoring and publishing tooling is part of the platform, so content updates do not depend on a development cycle.
NEXT STEP
Building something in education?
Tell us the constraints — regulatory, operational or technical. Those are usually what decides the architecture.