A coaching centre runs on a dense set of small operations: enquiries, admissions, batch scheduling, attendance, fees, tests, results, parent communication and teacher payments. When those operations live in notebooks and spreadsheets, the owner spends the evening reconciling them instead of improving teaching.
Software can help, but the market is crowded and the pricing models are hard to compare. Some vendors charge per branch, some per student, some per message, and some bundle everything into an annual contract. This guide sets out the requirements worth paying for and a cost model you can apply to any quote.
What the software must do
Start with the operating flow. A coaching centre typically needs:
- Enquiry and admission: capture leads, follow up, convert to a student record and assign a batch.
- Batch and timetable: subjects, teachers, rooms, start and end dates, holidays and make-up classes.
- Attendance: manual, QR or biometric, with a way to correct mistakes and notify parents.
- Fees and dues: invoices, partial payments, discounts, waivers, due dates and receipts.
- Exams and results: marks entry, grade rules, publish dates and student or parent access.
- Communication: SMS, WhatsApp or in-app messages for attendance, dues, results and notices.
- Teacher management: class allocation, availability and payment calculation.
- Reporting: collection, outstanding dues, enrolment, attendance and batch profitability.
If a vendor cannot show a clean flow from admission to fee collection to results, the rest of the feature list does not matter.
Requirements by priority
Must have
- Student and guardian records with a unique student ID.
- Batch assignment and a timetable that handles multiple subjects and teachers.
- Fee invoices, partial payments, receipts and an outstanding balance per student.
- Attendance with a correction log.
- Role-based access for owner, accountant, teacher and front desk.
- Data export in a usable format.
Should have
- SMS or WhatsApp templates with delivery reports.
- Exam marks and configurable grade rules.
- Multi-branch reporting and consolidated collections.
- Bangla and English interfaces, or at least Bangla message templates.
- Mobile-friendly screens for teachers and front-desk staff.
- Payment gateway or mobile financial services integration for fee collection.
Nice to have
- Biometric or QR attendance.
- Parent portal or app.
- Library, transport and inventory modules.
- Automated follow-up sequences for enquiries.
- Custom report builder.
The cost model
Do not compare headline monthly prices. Compare the annual total across these lines:
- Subscription: per branch, per student, per user or a flat plan. Ask what counts as an active student and what happens in a month with fewer students.
- Implementation and setup: configuration, branch setup, user roles, templates and initial training.
- Data migration: importing students, guardians, batches and outstanding dues. Messy data makes this line larger.
- Messaging: SMS or WhatsApp credits are usually separate and scale with attendance and due reminders.
- Payment collection fees: gateway or mobile financial services charges per transaction, plus settlement timing.
- Customisation: reports, receipt formats, grade rules or approval flows that are not in the standard product.
- Training and change support: front-desk and teacher onboarding, plus refresher sessions after staff turnover.
- Support and hosting: response times, backup, uptime commitments and whether hosting is included.
- Internal time: the owner or accountant's hours spent cleaning data, checking reports and chasing exceptions.
A low subscription with expensive messaging and no data export is not cheap. A higher subscription that removes two hours of daily reconciliation may be the better buy.
A simple annual cost calculator
Build the comparison in a spreadsheet with these inputs:
annual cost = (plan fee x branches x 12) + (per-student fee x active students x 12) + (messages per month x 12 x message rate) + (payment volume x gateway rate) + implementation + customisation + internal hours x hourly cost
Use your own numbers and include only the charging lines your shortlisted vendors actually apply. The purpose is to make visible the lines that vendors quote separately, not to produce a universal price.
Bangladesh-specific questions
- Does the system handle Bangla names, addresses and message templates correctly?
- Can it send SMS through a local provider, and what is the delivery reporting like?
- Does it support the mobile financial services and payment methods your guardians actually use?
- Will it work on low-end Android phones and intermittent connections?
- Can it produce the receipts and reports your accountant needs?
- Is support available during the hours your front desk operates, including exam periods?
Questions to ask a vendor
- What exactly is included in the plan, and what is billed separately?
- How is a student counted, and what happens when a student pauses or leaves?
- Can we export all student, payment and attendance data at any time?
- What is the uptime commitment, and what happens when the system is down during admission season?
- Who owns the data, and where is it hosted?
- How are custom reports priced?
- What training is included, and what does refresher training cost?
- Can we start with one branch and add others later without re-implementation?
A 90-day rollout plan
- Days 1-10: document the current process, fee rules, batch structure and reporting needs.
- Days 11-20: clean the student and dues data. Agree the fields and the unique student ID.
- Days 21-35: configure one branch, import data and run a parallel test with a small batch.
- Days 36-50: train the front desk and teachers. Test fee collection, receipts and messages end to end.
- Days 51-65: go live for one branch. Keep a manual backup for the first two weeks.
- Days 66-80: review collection, attendance and message delivery. Fix data and workflow issues.
- Days 81-90: roll out to remaining branches and agree the support rhythm.
Metrics to track
- Fee collection rate and average days to collect.
- Outstanding dues by batch and by branch.
- Attendance capture rate and correction rate.
- Message delivery rate and parent response rate.
- Administrative hours per week before and after rollout.
- Time to produce a consolidated monthly report.
Where this fits in our work
If you need a system that matches how your centre actually runs, start with Education Operations. The pricing page explains how we scope configuration and rollout. For the data protection side, read how student data privacy obligations mature.
Sources
- Bangladesh Bureau of Educational Information and Statistics (BANBEIS), accessed 17 November 2026.
- DataGuidance, Bangladesh jurisdiction overview, accessed 17 November 2026.
- NIST Privacy Framework, accessed 17 November 2026.
- ISO/IEC 27701:2025, Privacy Information Management Systems: Requirements and Guidance, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.