School software in Pakistan is priced in three incompatible ways, which makes comparing vendors unusually painful. One quotes per student per month, one quotes a one-time licence per campus, and one quotes a project. Before comparing numbers, convert everything to the same unit: total cost over three years for your actual student count.
The three pricing models
| Model | Typical price in Pakistan | Watch for |
|---|---|---|
| Per student, per month | Roughly PKR 50 – 250 per student per month | Cost rises every time you grow; check the price at double your current roll |
| One-time licence per campus | Roughly PKR 150,000 – 800,000, plus annual support | What the annual support actually covers, and what a version upgrade costs |
| Custom build | Project-quoted | Only worth it when your academic or fee structure genuinely does not fit a product |
These are market ranges, not our price list. A 400-student single campus and a 4,000-student group with three branches are not the same purchase, and any vendor quoting both the same way has not asked enough questions.
Modules you will be upsold, and which ones matter
- Admissions and student records — the base, always included.
- Fee management with vouchers, instalments, discounts, siblings and arrears. This is the module schools actually buy the system for, and the one worth testing hardest.
- Attendance, whether manual, biometric or RFID. Biometric adds hardware cost per gate.
- Examination, grading and report cards in your board's format. If it cannot produce your exact result card, it will be rebuilt by hand every term.
- Parent portal or app with SMS and WhatsApp notifications. SMS is billed per message and is a recurring cost, not a feature.
- Payroll and HR for staff, often sold separately.
- Transport, library and hostel, which only some schools need.
Local requirements that rule products out
Fee collection through local rails matters more than any feature list: bank challan or voucher printing, and JazzCash or Easypaisa if you want parents to pay from a phone. Urdu support, multi-campus consolidation under one owner login, and report cards in the format your board requires are the other three that quietly disqualify otherwise-good international products.
If the school is a registered business for sales tax purposes, note that digital invoicing obligations are a separate question from academic software — see FBR digital invoicing — and your tax adviser should confirm what applies to you.
Costs that follow the purchase
- 1Data migration from your existing registers or spreadsheets, often quoted separately and often the most painful week of the project.
- 2Staff training, with a refresher at the start of each academic year as staff change.
- 3SMS and WhatsApp message credits, billed per message and growing with your roll.
- 4Biometric or RFID hardware per gate, if you take attendance that way.
- 5Annual support and version upgrades on a one-time licence.
- 6The cost of switching later if the vendor will not export your full data.
Buy the product, unless
For most single-campus schools, an established product is the right purchase and a custom build is a waste of money — our note on custom versus ready-made software sets out when each wins. Custom becomes defensible for multi-campus groups with consolidated reporting, for institutions with a fee or academic structure no product models, or where a system has to integrate with something you already run and cannot replace.
If you want this costed against your own roll, campuses and fee structure, send us those three numbers and we will tell you honestly whether to buy a product or build one.
Need help applying this?
WordbitX turns guidance like this into delivered work — scoped, built and supported. Email info@wordbitxtech.com or send your brief through the contact form.
