Why We Built IskulAI — Ending the Paper Era for Bangladeshi Schools
Attendance in khata books, fees in hand-written invoices, marksheets rebuilt in Word every term. We spent time inside Bangladeshi school offices and built the system they actually need — 24 modules, bKash-first billing, a madrasa mode, and a parent PWA that installs nothing.
The office that runs on three khata books
Spend one morning inside a Bangladeshi school office and you will see the real curriculum. An assistant transcribes yesterday's attendance from a khata into a register. A clerk writes fee receipts by hand, pausing to remember whether this family's late fine was waived last month. A teacher rebuilds a marksheet in Microsoft Word because the board changed the template again. Somewhere in a drawer is the third book — the baki list of students who owe money from two terms ago.
None of this is a discipline problem. It is a systems problem. Every actor in that office is doing rational work with irrational tools, and the cost lands on the people with the least power in the chain: parents who learn about an absence three days late, and head teachers who sign financial reports they cannot verify.
Design decisions the market forced on us
Every requirement we shipped in IskulAI traces back to something we saw fail on paper. Billing is bKash-first because that is how parents already pay — the system generates the invoice, the parent pays from their bKash app, and a webhook reconciles the ledger in seconds. The late-fine engine is configurable because every school has its own fine culture; hard-coding ours would have been imposing a policy, not shipping software.
The parent portal is a PWA, not an app-store app, because a school cannot ask five hundred guardians to manage storage space and Play Store accounts. Madrasa mode exists as a first-class mode — not a checkbox — because Hifz milestones and Arabic subjects are not electives; they are half the report card. Marksheets print on board-standard templates because a result a parent cannot read is not a result.
24 modules, one architecture
IskulAI grew to 24 modules — admissions, attendance, billing, accounting, exams, CBT, LMS, timetable, discipline, payroll, logistics, printing, governance and more. The only way that scale stays healthy is a vertical-slice architecture: each module owns its API surface, types and components, and ships independently behind a single login with role-based access. A school can adopt billing first and exams a term later without a migration project.
What comes next: adaptive learning
A system of record is the foundation, not the building. Once attendance, marks and fee history live in one place, the interesting question becomes prediction: which student is drifting before the exam makes it obvious, which fee defaulters need a reminder versus a conversation, and how a chapter can adapt to the twenty-five students actually sitting in the room. That is the roadmap IskulAI is now building toward — adaptive AI learning engines tuned to the national curriculum, trained on the school's own data.
Start with your institution
If you run a school, college or madrasa and any paragraph above described your morning, IskulAI was built for you. Itqano runs pilots with full data migration and staff training — visit iskulai.com or talk to us directly from itqano.com/contact.