Safeguarding
No open messaging between students. No public profiles. No user-generated content visible to other students. Free-text input is limited to answer fields and is visible to the student's teachers.
For schools
The rollout is the hard part.
The rollout is the hard part.
So we made it ours.
Most edtech fails in schools not because the product is bad but because adopting it costs more time than anyone has. This page is about that, honestly.
First half-term
What the first six weeks look like.
Not a promise of transformation. A realistic account of the work involved on both sides.
1
Week 1 — Setup
We import class lists from your MIS export, create accounts and configure your curriculum mapping. Your side of this is sending one file and confirming the mapping looks right. Roughly an hour of a head of department's time.
2
Week 1 — Staff session
A forty-five minute session with the teaching team, run by us, in a department meeting slot. No INSET day required. We cover setting work, reading the class view, and what to ignore.
3
Weeks 2–3 — Baseline
Each class does the diagnostic, typically one lesson. This is the point where the picture stops being an assumption. Expect some surprises — that is the point of doing it.
4
Weeks 3–6 — Normal use
Students work through adaptive practice as homework or in lesson. Teachers use the class view for planning. We stay in contact weekly and fix what gets in the way.
5
End of half-term — Review
We sit down with you and look at what actually happened: usage, movement, and what staff found annoying. If it is not earning its place, we would rather find that out at six weeks than at renewal.
6
Ongoing — Support
A named contact who knows your setting, not a ticket queue. Term-time response targets are set out in our service agreement.
Honest requirements
What we need from you.
Suppliers tend to be vague about this until after the contract is signed. Here is the full list.
- A class list export from your MIS — names, year group, class, and a student identifier. CSV is fine.
- A signed data processing agreement — we provide the draft; your DPO reviews it.
- One department meeting slot for onboarding, plus one lesson per class for the baseline.
- Our domain allowed through your web filter, and pop-ups permitted for account setup.
- One person who owns it internally. Usually a head of department. Adoptions without a named owner do not stick.
That is genuinely all. No server, no on-site installation, no integration project.
Procurement pack
Documents we can send today
- Data processing agreement (UK GDPR Art. 28)
- Privacy notice for students and parents
- DPIA supporting information
- Sub-processor list
- Accessibility statement
- Security overview & incident response summary
- Insurance certificates and written quotation
SEND & inclusion
Reading support, adjustable pacing and per-student display settings that follow the learner across devices. The adaptive path is often the accommodation — work that meets a student where they are.
Pupil premium reporting
Filter movement and engagement by the groups you already report on, so intervention spending can be evidenced rather than asserted.
Pricing
Per student, per year. Quoted properly.
We do not publish a price list, and we would rather explain why than pretend it is a strategy. Cohort size, subject scope and agreement length move the number enough that a headline figure would be wrong for most schools that read it.
Pilot
One department, one term
A single subject area, a defined set of classes, and a written review at the end. Designed so you can stop cleanly if it is not working.
Whole school
Full cohort licence
All eligible year groups, all included subjects, leadership reporting, and onboarding for the whole teaching team.
Trust / MAT
Multi-school agreement
Central reporting across schools, one contract, one invoice, and a shared implementation plan across your settings.
We will send a fixed written quotation. No auto-renewal traps and no mid-term price changes within an agreed term.
Procurement questions
What DPOs and business managers ask.
Do we need to complete a DPIA?
For a system processing children's personal data at scale, almost certainly yes — that is your call to make, but it is the sensible default. We provide the supporting information a DPIA needs: what data we process, why, where it is held, who the sub-processors are, retention periods and the technical measures in place.
Who are your sub-processors?
The current list is provided in writing before you sign, and forms part of the processing agreement. We give notice before adding a new one, and you have the right to object. We are not going to publish a list on a marketing page that then drifts out of date — ask us and you will get the accurate current version.
What happens to our data if we leave?
You export it — that is available throughout the agreement, not just at the end. We then delete your data on an agreed schedule after termination and confirm completion in writing. Your data is not held hostage as a retention tactic.
Can parents see their child's data?
Yes. As the data controller, your school handles subject access requests, and we provide whatever we hold on that student in a usable format to support you. We aim to respond to your request quickly enough that you can meet the statutory deadline comfortably.
What if the platform goes down during a lesson?
Then a lesson is disrupted, which is a real cost to you — so we treat availability as a service commitment rather than a best effort. Our target availability and incident communication process are set out in the service agreement, along with what happens if we miss it.
You're an early-stage company. What if you fail?
A fair question, and one more suppliers should be asked. Your data is exportable at any time in a standard format, so you are never locked in. Our contract sets out what happens to your data in an insolvency scenario. We would rather answer this directly than have you find out the answer the hard way.
Start with a conversation.
Tell us about your setting and what is not working. If we are not the right fit we will say so — that is a cheaper outcome for both of us than a failed rollout.