We don't start with software.
We start with how you teach.
It begins with a conversation, not a contract. We learn how your week really runs, build around it in stages, then run it for you so your teachers can simply use it.
Start with a conversationThe process
Here is exactly how a build works, from the first hello to the day it's yours.
First, we learn your week.
We come in and talk to the people who run it.
Your teachers, your office, you. No slide deck. We ask how homework gets set, how marking gets done, how reports get written, and where the hours that should belong to teaching actually go. Not the teaching itself. Everything around it.
We show you where the hours go.
Then we hand it back: a clear picture of the week we found, and exactly what we would build to win those hours back, in what order, for a fixed price. You see the whole plan, and the whole cost, before you agree to anything.
We build the part that hurts most, first.
Never everything at once. We start with the one job draining your teachers' evenings, build it, and put it in their hands in weeks, not at some far-off launch. You watch it work on real classes before we build the next piece.
We fit it to your teachers, down to their voice.
The software drafts in each teacher's own voice and your house style, so what it writes sounds like them. It sits alongside the systems you already trust, and replaces only what is holding teachers back. We train your staff until the manual is one page. And nothing reaches a student until a teacher has approved it.
Then we run it, so your staff never has to.
One flat monthly fee, and the running of it is ours: the servers, the updates, the fixes, the AI cost behind every piece of feedback. Your data is the other way round. Every record your teachers and students create sits in a database of your own and leaves with you whenever you ask. Nobody on your staff has to become the person who keeps the software alive.
Two lists. We stay off the first one.
What we never touch
- Your teaching
- A teacher's judgment on a student
- The way your teachers like to work
- The systems that already do their job
What we take off their plate
- The marking pile
- Chasing late work
- The Sunday reports
- The year-end scramble to hit the standard
We only ever take the right-hand list.We only ever take the bottom list.
Questions we get asked
Because off-the-shelf software was built for the average of ten thousand schools, so it fits none of them exactly, and your teachers spend their week working around its gaps. We start with you: how your teachers mark, how you report, what your students actually struggle with. And when something does not fit, you tell us and we change it. Try getting that from a company with ten thousand other schools to answer to.
Two parts, and you see both in writing before you commit. A one-off setup fee covers making the Engine Room yours: your branding, your classes loaded, your curriculum in it, your teachers trained. Then one flat monthly fee to run it, based on how many students use it. That fee covers everything: the marking, the feedback, the speaking practice, the servers, the support, and every update we ship. No per-teacher licences. No charge per report. And you do not have to take all six Buddies at once. Start with the one costing your teachers the most evenings.
Yes. The Engine Room covers your English department, and it is what we run for schools and centres month to month. Beyond it we take on bespoke builds: an admissions chase, a report-card system, the one job only you have. Those are scoped and quoted separately. Ask us, and we will tell you honestly whether it is worth building.
Faster than a full IT project, because we are not building for ten thousand schools, only for yours. We start by understanding how you work, then build around what we find and what you want. You get a realistic timeline before we begin, and we build in stages, so you see things working early rather than waiting for one big launch.
We work around them, not against them. Part of understanding how you work is seeing what already works and what does not. We build to sit alongside what you want to keep, and we replace only what is holding your teachers back. You decide what stays.
You own your data. We own and run the system. That split is deliberate, and it is the right way round. Every mark, every recording, every report your teachers and students create belongs to you, sits in your own database, and leaves with you if you ever go. What we keep is the running of it: the servers, the AI costs, the fixes, the updates, the 2am problems. Owning your own software sounds appealing right up to the morning it breaks and there is nobody on the payroll whose job it is to fix it. That morning is ours, not yours.
The first step costs you a conversation.
No pitch. No pressure. No contract. We come in, we listen, and we tell you honestly whether we can help. If we can't, we will say so, and point you somewhere that can.