We don't start with software.
We start with your school.
It begins with a conversation, not a contract. We learn how your week really runs, build around it in stages, and hand you something you own.
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 school's 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 hand you the keys.
You own what we built. Outright. From there you choose: we run it for a flat monthly fee, or we train your team to run it themselves. Either way it is yours, and it keeps working whether we are in the room or not.
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 schools ask
Because off-the-shelf software was built for the average of ten thousand schools, so it fits none of them exactly, and your teachers end up working around its gaps. Bespoke software fits your school, so there are no gaps to work around. And you own it, instead of renting it forever.
Every build is bespoke, so there is no fixed price list. The cost depends on what your school actually needs, which we work out together before anything is built. You pay once and own the software outright. After that, you choose: we manage it for a modest, flat monthly fee per student, or we train your own staff to run it. You get a clear, fixed quote before you commit to anything.
Less than you might fear. The heaviest part is early: a conversation with your teachers about how the week really works. After that, we do the building. We check in at the right moments, but we do not tie up your staff for weeks.
Faster than a full IT project, because we are not building for ten thousand schools, only for yours. We start by understanding how your school works, 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 your school 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 it. Outright. Most school software is rented: you pay every month, forever, and own nothing. With us, you pay once and the software is yours. An asset, not a subscription.
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.