Systems that get out of the way of teaching

Admissions, timetabling, attendance and reporting — joined up, so staff spend their time on students rather than on spreadsheets.

Education

Education runs on deadlines that do not move: enrolment, term start, inspection. The systems around them tend to be a decade of separate decisions. We connect what exists, replace what genuinely cannot continue, and keep the academic calendar out of the risk register.

Who this is for

Schools and academy trusts

Where one team supports several sites with different histories.

Colleges

Large cohorts, funding rules and a reporting calendar that does not flex.

Universities

Departmental systems that need to look like one institution to a student.

Training providers

Commercial delivery where enrolment, attendance and invoicing have to agree.

How we work

People who have done it before

Teams that have worked in this setting, not a generic squad reading the brief for the first time.

One team, start to finish

The people who design it are the people who build it and the people who answer for it afterwards.

Working software early

Something running in weeks, so the direction is judged against a real thing rather than a document.

Sector experience, not sector slides

Sector experience, not sector slides

What we bring to the first meeting

We have worked in this sector, so the first conversation is about your constraints rather than an introduction to the domain. Where we have not done something before, we say so.

Talk to us
What we promise

What we promise

  • A named team you can reach, not an account manager relaying questions
  • A working version early, and every fortnight after that
  • Written estimates with the assumptions and the risks stated
  • Your code, your data and your accounts, yours throughout
  • A direct answer when something is late or will not work

How it runs

Understand

Two weeks with the people doing the work, mapping what actually happens rather than what the process document says.

Prove

One narrow slice built and put in front of real users, to test the approach before it is expensive to change.

Build

Delivery in fortnightly increments, each one usable, each one reviewed with you.

Run

Support, monitoring and improvement — or a handover to your team, documented.

Common questions

Usually yes. Most of what we build reads from the MIS rather than replacing it, because replacing it mid-year is rarely worth the risk.

Access is by role, actions are logged, and data leaves the system only where a lawful basis has been agreed and recorded.

That is normally the plan. The delivery is shaped around the academic calendar rather than the other way round.

Some, and we would rather design it so they need less. Screens people use every day should not require a course.

Is this the right fit?

Tell us what you are trying to do. If we are not the right people for it, we will say so.

Get in touch
Contact us