Synchronised load
Concurrency is not spread across the day. It is a spike at the top of each period, and your capacity plan has to be built for that shape.
Education & EdTech
Education platforms have the least forgiving load profile in software. Usage is not distributed. It arrives in a wall at the start of a lesson, from devices that are older than the students using them, over bandwidth the school cannot upgrade, and if it fails the failure happens to thirty children at once in front of a teacher who now has no lesson. Education software development has to start from that morning, not from an average day.
“Will it work on a school laptop, on school wifi, at the start of a lesson?”
The pressure
Concurrency is not spread across the day. It is a spike at the top of each period, and your capacity plan has to be built for that shape.
Chromebooks with four gigabytes of memory, tablets two operating systems behind, and a network shared with the whole building.
Learners and administrators want opposite things. One needs a system that gets out of the way, the other needs reporting, permissions and oversight.
The person who buys it is not the person who uses it, budgets are annual, and accessibility and data protection are gating questions rather than nice-to-haves.
The work
Four systems, all of which have to work on the worst device in the building.
Course delivery, assessment and progress that work offline-tolerant and resume cleanly when a connection drops mid-lesson.
Timed assessments that survive a dropped connection without losing a student’s work, and marking tools that give teachers time back.
Enrolment, timetabling, attendance and reporting, including the returns you are statutorily required to file.
A different audience again, on personal devices, checking one thing quickly.
This refresh effectively reflected our shift from in-person to online training services. … We saw notable increases in conversion rates and user satisfaction, and the design reflected our mission to empower educators through the highest quality digital experiences.
The device floor
Every performance budget needs a worst case that is real. This is the kind of floor we propose at the start of a project. The figures are illustrative: the real ones come from your estate, and we write them into the acceptance criteria so you can hold us to them.
| Target | What it is | Budget | Why this one |
|---|---|---|---|
| Baseline laptop | Chromebook, 4GB RAM, 2019 class silicon | < 2.5s to interactive | A common device in state schools, and the one that will still be in the cupboard in three years. |
| Baseline tablet | iPad 7th generation, two OS versions behind | < 3.0s to interactive | Shared trolley devices are rarely current and almost never charged. |
| Network | 4 Mbps shared, 120ms latency, 2% packet loss | < 400KB initial payload | A whole year group on one connection at nine in the morning. |
| Concurrency | 2,500 sessions arriving inside 20 seconds | 0 dropped sessions | The bell is the load test. There is no gradual ramp. |
| Interruption | Connection lost for 90 seconds mid-assessment | 0 lost answers | A student who loses work once will not trust the platform again, and neither will their teacher. |
| Accessibility | WCAG 2.2 AA, keyboard and screen reader | Pass before release | A procurement gate in this sector, checked rather than asserted. |
Non-negotiable
Where AI actually lands
Worth doing
Where we stop
Summative grading that affects a student’s record without a human deciding. The accuracy argument is beside the point; the accountability question is who answers to the parent, and it cannot be a model.
Evidence
We have no education case study to publish yet. The Doers Company, who sell online training to educators, have published a review of the website and platform refresh we delivered for them.

How we deliver it
Multi-tenant architecture, metering and billing designed in from the first sprint.
Fast, accessible applications that behave correctly on a bad connection.
Interface design grounded in how the work actually gets done, not how it demos.
Other sectors we work in
Next step
A senior engineer reads every enquiry and replies within one business day with an honest view of what it will take, including how the platform behaves on the oldest device in the building.
Certified, partnered and awarded









1/7
Discuss your project
Seven short questions. About 90 seconds. A senior engineer reads your answers before we reply. No sales sequence, no newsletter. Just a thoughtful response about what comes next.
Start here
Choose the one that comes closest.
The problem
A sentence or two is enough. Tell us what isn’t working today or what you want to make possible.
Where you are today
Choose everything that applies.
Timing
A real deadline changes how we approach the work. If there isn’t one yet, that’s useful to know too.
Scope
A range is enough. It helps us understand the right approach and team for the problem. It does not determine what we charge.
Your team
This helps us understand whether we should lead the engineering, work alongside your team, or advise your existing engineers.
Stay in touch
A senior engineer will read what you’ve shared and respond within one business day.
How would you prefer to continue?
Received
A senior engineer will review what you’ve shared and come back with the most useful next step.