About Schoolhouse
A school system with opinions.
Schools deserve software that respects a teacher's morning, a parent's evening and a principal's attention. Schoolhouse is built around a few firm beliefs about how that should feel.
What we believe
Six principles you can see in the product.
These aren't slogans. Each one is a behaviour you can watch happen in the walkthrough.
Decisions, not a wall of numbers
Dashboards open on what needs a person today. A principal arrives with one question — what needs me? — and the first screen answers it.
Reversible things just happen
Approve a request and you can undo it. Confirmation dialogs are saved for what genuinely cannot be taken back — like finalising payroll, which asks you to type the month.
The server decides, not the interface
A parent sees their children and nothing else because the server checks every request — so the rule holds for the web app, the phone app and anything else that calls the API.
Held, not dropped
Quiet hours delay non-urgent messages until morning instead of discarding them. Emergencies ignore all of it, and the screen says so out loud.
Your school, not ours
Sign-in, the app and every email carry your name, colours and logo. A parent landing on your login page should recognise their child's school, not a software vendor.
Works when the network doesn't
Registers and bus scans queue on the device and send exactly once. The teacher never has to think about it.
Working with us
Start small. Grow at your pace.
- 1
See it on a populated school
We start with a live demo on a sample school with students, timetables, fees, buses and payroll — so you judge the product, not a slide.
- 2
Bring your data across
Import students and staff from a spreadsheet with a full preview of every problem before anything is saved, and get help migrating from your current system.
- 3
Grow module by module
Start with the essentials — registers, timetable, fees, messaging — and switch on admissions, reports, transport and more as your team is ready.
Built to be checked
The numbers behind the promise.
Software for schools should be held to a higher standard than a demo. These are the checks each release has to pass.
12
Connected modules
From admissions to payroll
6
Role workspaces
Each person sees their own school
277
End-to-end checks
Run against every release
118
Documented API operations
A published OpenAPI contract
3
Languages incl. right-to-left
More on request
See Schoolhouse running a school like yours.
Book a live walkthrough with a fully populated sample school — or tell us what you need and we'll put together a proposal.
Prefer email? aqbutt05@gmail.com