We build school software that works the way a school actually works
It started with a recurring problem: a separate system for each department, data entered twice, and guardians getting two different answers about the same child.
The problem we started from
In many schools admissions lives in a folder, attendance in a book, fees in a spreadsheet, and communication in a messaging group. Every department works hard, but information breaks at the handoff between them — and families pay the price.
That a school enters information once, and it reaches whoever needs it with a clear permission and an audit trail — with no re-keying and no conflicting copies.
An Arabic-first platform schools trust because it understands their context: compound names, a local calendar, multiple campuses, and a network that sometimes drops.
What we value
Exportable in full at any time, with no exit fee and no negotiation.
We do not publish a number, a certification or a launch date before it is verifiable.
The interface was designed RTL from the start, not translated afterwards.
Attendance and grades keep working offline and sync afterwards.
Every figure on this site is derived from the source code.
A school transition is an operational project, not an installation.
The implementation journey
Understanding departments, responsibilities and the data you hold today.
Academic structure, fees, roles and permissions.
Importing students, staff and balances with reconciliation.
Training each role on the work it actually does.
A monitored start with support close at hand.
Regular review and continuous improvement.
Frequently asked questions
Who is behind IntellSchool?
Why Arabic first?
How is the roadmap decided?
See it running against your own numbers
Show us your school's size and priorities, and we will demonstrate the platform on data shaped like yours — then hand you an implementation plan and a written quote.