The challenge
Private schools run on paper registers, scattered spreadsheets and dozens of WhatsApp groups. Fees, attendance, results and parent messages live in different places, so the people who teach spend their evenings doing admin.
Our approach
Sit in the classroom first
We started with the people, not the features: administrators, facilitators, parents and students each have a different day, so each gets a different app built on the same records.
One source of truth
Attendance, gradebooks, fees and messages share one set of records with strict roles, so a parent sees their child, a facilitator sees their classes, and the school sees everything.
Built for real phones
Installable web apps that work on low-cost Android phones and patchy connections, with sign-in by passkey and device approval instead of shared passwords.
Ship in gated stages
The platform is split into modules that switch on as a school is ready, so nobody is handed a hundred features on day one.
What we built
- Installable web apps (PWA) for admin and facilitators
- Role-based access per school, class and family
- Passkey sign-in and device approval
- Offline-tolerant data sync
- Daily encrypted backups with tested restores
How it was drawn
Like every 12pencils project, Onimde went through our five decisions: sketch the problem with the people who have it, outline the journeys, detail every screen and word, ink it in working code, then sign it off only after testing with real users.
What we learned
Schools do not want “more features”. They want fewer places to look. Every screen we removed made the product easier to adopt.
Screens on this page are illustrative. Product details reflect the current development stage.
Flykimo
