An admissions CRM is usually quoted per seat, per applicant or per branch. Those units matter, but they are not the whole cost. The expense that surprises a coaching centre or school is the work of cleaning years of enquiry data, agreeing what counts as a qualified applicant, and getting counsellors to record the follow-up they currently keep in a personal notebook.
This guide is for an institute in Bangladesh that has outgrown a shared spreadsheet and wants a realistic budget for admissions software. It separates one-time implementation from recurring cost and shows the quantities to put in a calculator. It does not quote prices, because the right scope depends on intake size, branch structure and the systems the CRM must connect to.
What the budget is buying
Admissions is a pipeline, not a contact list. The system must capture enquiries from Facebook, WhatsApp, phone, walk-in, referral and the website; merge duplicates; assign a counsellor; schedule follow-ups; store documents and eligibility notes; manage tests and interviews; issue offers; and hand the enrolled student to fees without re-entry.
It also needs reporting by source, programme, branch and counsellor, plus consent and access controls for student and guardian data. If a product cannot show the next action for every applicant, it is a database with a login screen, not an admissions CRM.
What drives the cost
- Applicant volume and peak season. Intake months concentrate work. The system must handle the peak without a temporary spreadsheet.
- Counsellor seats and roles. Admissions, branch managers, accounts and leadership need different views and permissions.
- Branch count. Each branch adds users, reporting rules, data visibility and sometimes a separate intake calendar.
- Channels and integrations. WhatsApp, Facebook lead forms, telephony, SMS, email and the website each need a capture path and a consent rule.
- Document and test management. Scanned certificates, transcripts, test scores, interview notes and offer letters consume storage and workflow design.
- Data migration. Old spreadsheets, duplicate phone numbers and inconsistent programme names are remediation work before import.
- Customisation. A programme-specific eligibility rule or a multi-step offer approval may be configuration or custom code; the difference should be explicit.
- Training and adoption. Counsellors need practice with real scenarios, not a two-hour tour of the menus.
Seven cost lines to compare
1. Process design. Define the stages, the entry and exit criteria, the follow-up rules and the owner of each stage.
2. Data cleanup and migration. Deduplicate applicants, normalise programme names, map sources and decide what history to keep.
3. Subscription or licence. Seats, applicant blocks, branches, storage and support tier. Ask which unit triggers an overage.
4. Implementation and configuration. Pipeline stages, forms, notifications, permissions, templates and reports.
5. Integrations. Website forms, WhatsApp, telephony, SMS, email and the fee or accounting system.
6. Training and change support. Role-based sessions, a written playbook and a first-intake support period.
7. Ongoing operations. Administration, template updates, message charges, data quality review and vendor support.
A formula for the first year
first year = implementation + migration + annual subscription + messaging + internal time
implementation = base configuration + integrations + training
subscription = seats × seat rate + applicant blocks × block rate + branch fees
Ask the vendor to quote each unit separately. A low seat price with a high applicant-block price can invert the comparison for a large intake. Messaging is usually pass-through, so model the number of outbound messages and the channel's current rate rather than accepting a single bundled figure.
Calculator logic
Use applicant volume, peak-month volume, counsellor seats, branches, channels and integrations as inputs. Score complexity from one to three for each. A single-branch institute with one intake and two channels is a different project from a multi-branch group with seven programmes and four approval levels.
Then add the migration quantity: number of historical records, duplicate rate from a sample, and the number of documents to upload. This is often the line that turns an affordable subscription into a difficult first year.
Budget worksheet
Create one row per line with unit, quantity, rate source, one-off cost, monthly cost, owner and evidence. Include internal time for workshops, data cleanup, testing and training. Add a contingency for the first intake, when counsellors discover edge cases the design did not cover.
Where institutes overspend and underspend
Custom-building an admissions system before the process is stable is an expensive way to automate confusion. Buying an enterprise suite for a few hundred applicants can add configuration work that no one uses. Underinvesting in data cleanup produces duplicate applicants and unreliable source reporting. Underinvesting in training produces a system that counsellors update after the phone call, if at all.
Also budget the less visible work: consent language, retention rules, access reviews and the reports leadership will ask for in week two. A CRM that cannot produce a clean applicant count by source and branch will not survive the first management meeting.
Data protection and adoption
Student and guardian records include contact details, identity documents, academic history and sometimes financial information. Limit access by role, record who viewed or exported a record, set retention rules and agree how consent is captured across channels. Bangladesh's data protection framework and the NIST Privacy Framework both point to the same disciplines: know what you collect, why, where it goes and when it should be deleted.
Our education operations team configures admissions around existing batches, fee structures and parent communication, and the pricing page explains how implementation and support are scoped. For the buying options, read the comparison of education CRM approaches.
Sources
- DataGuidance, Bangladesh data protection overview, accessed 17 November 2026.
- NIST, Privacy Framework, accessed 17 November 2026.
- OWASP Application Security Verification Standard, accessed 17 November 2026.
- Meta, WhatsApp Business Platform documentation, 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 *.