The public website for a school, built around what parents and students actually arrive looking for, and kept consistent with the same institution's operations system.
The site's job is orientation, not persuasion: admissions, calendar, staff and contact are first-level destinations rather than items inside a submenu. It was built alongside the school's operations system, so the public pages and the internal records use the same names for the same things instead of drifting apart over time.
The operations system a school actually runs on — students, teachers, classes, fees, reports — put online and then hardened: scheduled jobs, backups, an audit log and a documented way to update it.
A multi-tenant restaurant platform: an installable POS on the floor, a kitchen display that updates as orders change, and a NestJS backend holding the order state machine behind both.
A point-of-sale platform built as a multi-tenant SaaS: organisations, branches and users on one schema, a till that keeps up with a USB scanner, and a versioned public API with scoped keys.
Tell us your goals and current setup — we'll come back with a clear, honest plan.