The brief, the architecture, and what shipped.

The challenge

Principals evaluate software in the gaps between two other duties. The existing material described the platform in the team's internal vocabulary — precise for engineers, a barrier for a reader whose job is running a school. It could not be sent to a prospect unaccompanied.

The solution built

Pages ordered by the questions buyers actually ask rather than by our capabilities, with feature detail placed after qualification. A plain-language rule was applied throughout: any term needing a sentence of explanation was the wrong term. One enquiry path per screen, and a mobile-first build derived phone-up rather than as a breakpoint.

Performance metrics

Enquiry path per screen

1

Enquiry path per screen

Layout derived phone-up

Mobile-first

Layout derived phone-up

SSR markup, not deferred

Crawlable

SSR markup, not deferred

The challenge

Several service lines had to sit on one site, each legible on its own, without the company reading as an unsorted list of capabilities — and the catalogue was expected to keep growing after launch.

The solution built

A component library built before any page: type scale, spacing, card and section patterns established first, so every subsequent service is assembled from existing parts rather than designed fresh. Each service line got its own route into contact carrying the reader's context, and copy was separated from layout so wording changes need no deploy.

Performance metrics

Deploys needed for a copy change

0

Deploys needed for a copy change

Component library, all services

1

Component library, all services

Contact route with context

Per-service

Contact route with context

The challenge

School administration ran across a dozen disconnected registers and spreadsheets — admissions in one, fees in a second, attendance in a third, marks on a teacher's laptop. Each was maintained carefully; none agreed with the others. The cost was not storage, it was reconciliation.

The solution built

A single-record architecture: a student exists once, and admissions, attendance, examinations, fees and communication all read the same row. Multi-campus tenancy with configuration per campus, role-based access across admin, staff and parent accounts, and existing registers imported at onboarding rather than re-keyed.

Performance metrics

Canonical record per student

1

Canonical record per student

Modules on one schema

6

Modules on one schema

Isolated configuration

Per campus

Isolated configuration

The challenge

Every school we visited lost the same twenty minutes before 8am: one person working out by hand who could cover absent teachers, from a timetable, a leave book and memory. The allocation was also quietly uneven — the same agreeable staff absorbed the load, and there was no record to prove or disprove it.

The solution built

A constraint-solving engine that reads the live timetable and derives who is genuinely free rather than nominally free, then allocates cover weighted by how much each teacher has already taken across the term. The rule is visible in the interface rather than hidden, assignments push to the teacher with class, period and room, and any human can override — with the override logged like any other allocation.

Performance metrics

Daily allocation run

< 2 min

Daily allocation run

Estimate, not yet confirmed against production

Assignment to notification

Seconds

Assignment to notification

Estimate, not yet confirmed against production

Fairness weighting basis

Per term

Fairness weighting basis