Skip to content
Approach

Listen, build, run.

Three stages. One team that stays with you after the invoice clears.

Listen

We spend time in the school before a line is written. We sit with the registrar, the bursar and the head of year, and we map what the day actually looks like rather than what the process document claims.

  • A written map of how the school runs today
  • The list of workarounds everyone has stopped noticing
  • An honest view of what software cannot fix

Build

We build to what we found, in the open. You see working software early and often, and it changes while changing it is still cheap.

  • Fortnightly working builds
  • Your language and structures throughout
  • Migration from the systems you are leaving

Run

We stay. The system keeps moving as the school does, and there is a named person who knows your setup rather than a ticket queue.

  • A named contact who knows your school
  • Termly review of what changed
  • Full export of your data at any point