Built by the person who had the problem.
Main Office Works is practitioner-led in the literal sense: it started as the tools one assistant principal built to run his own building, and grew into a platform for the operational work every school office does.
The first tools weren't a product. A conduct process was living in Google Forms and email, with no statuses and no follow-through. A 1:1 device program was tracked across spreadsheets and clipboards. The work had to get done, the available tools weren't doing it, and the assistant principal responsible for it could write software.
Those tools ran a real New Jersey public high school's mornings, and then kept growing: one shared identity for districts, schools, staff, and students, with modules for the workflows that consume a main office's day — conduct, teacher coverage, devices, staff attendance.
The philosophy hasn't changed with the platform. Schools deserve systems built by people who know what the referral queue feels like at 8:05 a.m., what June device collection actually involves, and why role-based access is a requirement, not a feature.
Four rules that shape every decision.
Every module begins as a process a school already runs by hand — then replaces it faithfully, step for step, until the paper version can retire.
Conduct, coverage, and devices share the same student and the same staff member. Software shouldn't make a school re-enter the same child five times.
Who should see this — and who shouldn't — is the first design question, because that's how a school office actually works.
If a workflow isn't ready, it stays labeled pilot or roadmap. No pretending a plan is a product — a district can't run a building on a maybe.
What you see on this site is what exists: a working platform, in daily use where it was built, and a founder who answers his own email.
No invented customers, no borrowed logos, no numbers we can't stand behind. If that's the kind of vendor your district prefers, we should talk.
Talk to the person who built it.
Demo requests and questions land in the founder's inbox, and he replies by email.