WE BUILT THIS AFTER
WATCHING A BURSAR CRY.
That is not a marketing line. It was a Thursday in October, week six of term, and she had been reconciling three spreadsheets against a paper ledger for eleven hours to answer one question from the school owner: how much is actually outstanding?
She got the number. It was wrong. Everybody knew it was wrong. That is the problem Skoolarz was built to remove.
WHERE WE CAME FROM.
Skoolarz grew out of a decade of building systems for organisations in the region — ministries, banks, universities — where the same pattern kept showing up. The software was never the hard part. The hard part was that nobody could agree on what a record was, so every department kept their own version of it.
Schools are that problem in miniature, and with higher stakes. A student is simultaneously an enrolment, a timetable slot, an attendance record, a set of grades, an invoice and somebody's child. Most school software picks one of those and treats the rest as an afterthought.
We started in 2024 with a single conviction: build the record properly first, and every module after that becomes a view of it rather than a separate system pretending to cooperate.
FOUR RULES WE
ACTUALLY FOLLOW.
We install it ourselves
Every person who writes Skoolarz code has sat in a school office during onboarding. Not a customer visit — a working day, watching a registrar use the thing we built. It is the fastest way to stop shipping features nobody asked for.
We say no in public
There is no visual query builder, no gamification, no AI that writes report card comments. Each of those has been requested. Each was declined for a reason we are willing to defend on the roadmap page.
Arabic is not a translation project
The platform is bilingual at the data layer, not just the interface: bilingual place taxonomies for bus stops, right-to-left printed documents, per-user language independent of the school default.
The school owns the data
Export is free, complete and available at any time — during the contract, not just on the way out. We would rather earn the renewal than rely on the cost of leaving.
WHO YOU ACTUALLY
DEAL WITH.
Skoolarz is a small team, deliberately. When you have a problem, you talk to somebody who can change the code — not to a tier-one queue whose job is to establish that you have tried turning it off and on again.
- Rana Haddad — Head of onboarding. Runs migrations and will tell you, honestly, whether your data is ready.
- Yousef Barakat — Engineering lead. Owns the platform, the deployment story and the security answers.
- Dana Sweiss — Customer success. The person who calls in week six of term to ask what is annoying you.
- Lina Qasem — Finance product. Designs the invoicing and reporting side with school bursars, not for them.
A note on the numbers elsewhere on this site. Where we quote figures like hours saved or collection speed, they come from schools running Skoolarz who agreed to share them. They are real, and they are also a small sample from a young company. Ask us for the underlying detail before you rely on any of them — we would rather hand over the caveats than have you discover them later. Ask us anything.