Education management system modernisation

Chapter 01 · The brief

One deployment per school. Unsustainable at scale.

A decade of organic growth, ending in a product that couldn't be upgraded without touching every customer individually.

A London-based education software company had built a school management information system (MIS) and student-performance tracking platform that had grown organically over a decade. Each school customer ran on a separate deployment — making upgrades, feature rollouts, and support increasingly unmanageable.

Shipping a single bug fix meant touching every deployment individually. Onboarding a new school required standing up dedicated infrastructure. The product needed to move to a true multi-tenant SaaS model before the operational burden made growth impossible.

Per-schoolEvery deployment separate — every upgrade, every fix, every onboarding done individually.

Chapter 02 · Build

Multi-tenant architecture. Per-tenant data isolation. Shared infrastructure.

Vatsa designed the multi-tenant architecture and led the re-platforming effort, working alongside the client's product team.

The migration preserved existing school data while standardising on a shared infrastructure model with per-tenant isolation at the data layer. School data remained logically separated — no school could see another's records — while the engineering team could deploy features to all customers simultaneously from a single codebase.

◇Tenant dashboard · performance overview

Chapter 03 · Outcomes

New schools onboarded in hours. Features shipped to all customers at once.

Multi-tenantTrue SaaS — single codebase, shared infrastructure

HoursNew school onboarding (was weeks)

All at onceFeatures shipped to every school simultaneously

The platform moved to multi-tenant SaaS with no data loss in the migration. New school onboarding time was reduced from weeks to hours. The engineering team could ship features and fixes to all customers simultaneously — without the per-deployment overhead that had been consuming an increasing share of engineering capacity.

Chapter 04 · Stack

Technology stack.

ArchitectureMulti-tenant SaaS — shared infrastructure, per-tenant data isolation at the database layer
MigrationPer-school data migrated to shared platform with full record preservation
OnboardingAutomated school provisioning; new tenant live in hours from a self-service flow