INDUSTRY
Software for schools, groups and universities
Education institutions here run several curricula, several languages and a parent body that expects a phone-first experience. We build student information systems, admissions journeys, learning platforms and parent portals that hold one student record across all of it. Reporting to owners and regulators comes from the same data, not from a separate exercise.
One student record, several systems
A school group typically runs an admissions tool, a student information system, a learning platform, a finance system and a bus tracking app, none of which share an identity. The student exists five times, the parent receives five logins, and any group-level question takes a week to answer.
We establish one student and guardian identity, then integrate the rest around it with single sign-on and a defined system of record for each data domain. In some cases we replace the student information system outright; more often the higher-value work is admissions, the parent experience and the group reporting layer.
- Single student and guardian identity with sibling and household relationships
- Single sign-on across the systems teachers, students and parents actually use
- Defined system of record per domain, so no field has two owners
- Group-level reporting on enrolment, attendance, attainment and collection
Admissions is the commercial system
Admissions decides the year's revenue, and it is often the least engineered process in the institution. Enquiries arrive from campaigns, walk-ins and messaging apps into different inboxes. Assessments are scheduled by phone. Offers, deposits and document collection sit in a spreadsheet that only one person understands.
We build it as a pipeline with stages, ownership and response-time visibility: enquiry capture from every channel, assessment scheduling, offers, deposit payment, document upload and verification, then a clean hand-off into enrolment. Admissions teams get a forecast they can defend, and families get a process that feels considered.
Multilingual delivery and the parent experience
Institutions here teach across multiple curricula and serve families in Arabic, English and often a third language at home. Parent communication has to work on a phone, in the family's language, and cover attendance, behaviour, fees, transport and results without five separate apps.
We build the parent portal and app in Arabic and English with equal treatment, and structure the learning platform for content in multiple languages rather than assuming a single-language course. Where an institution follows an established interoperability standard for learning tools, we build to it so content and results move between systems properly.
- Parent app covering attendance, fees, transport, results and communication
- Arabic and English parity across portals, notifications and documents
- Accessible interfaces tested with keyboard and screen reader
- Standards-based integration for learning tools and content, where supported
Which of our services usually apply
Custom Software Development, Mobile App Development and Systems Integration cover most engagements, with Product & UX Design ahead of any parent-facing or admissions work. Data & Analytics gives group leadership enrolment and attainment views. Security & Compliance matters because this is children's data and it should be handled that way.
Kuyil AI, our own voice product, is deployed in education settings for multilingual reception, admissions enquiries and campus wayfinding, which is a separate conversation from the platform work.
What you get
- Student and guardian identity model with single sign-on across systems
- Admissions pipeline from enquiry to enrolment, with assessments and offers
- Student information functionality for attendance, timetabling and attainment
- Parent portal and mobile app in Arabic and English
- Fee, instalment and collection workflows integrated with finance
- Learning platform integration using supported interoperability standards
- Group and campus reporting on enrolment, attendance, attainment and arrears
- Data protection, access-control and retention documentation for children's data
Typical outcomes
40%
Faster response to an admissions enquiry
5
Parent logins reduced to one
25%
Less administrative time on reporting
Stack we use
Questions
Usually not. The higher-value work is normally admissions, the parent experience and group reporting, built around the system you have. We only recommend replacement when the existing system is the actual constraint.
Least-privilege access by role, no production data in test environments, full audit trails on record access, and retention rules implemented in the platform. We document all of it for your governance and your regulator.
Yes. Curriculum, assessment scheme and reporting template are configuration rather than code, so a group running different curricula across campuses uses one platform with different settings.
We plan releases around term dates and avoid changes during admissions peaks, examinations and the start of term. Migration and cut-over are scheduled into breaks wherever the timetable allows.
Related
Next step
Start with a 20-minute call.
Tell us the roles you need filled, the system you need built, or both. You will speak to someone who has done the work, and leave the call with a route forward.