Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Education Technology 6 min read

Student retention workflow cost in Bangladesh: a budget guide

How to budget a student retention workflow in Bangladesh: cost lines, a unit-cost formula, pilot gates and the metrics that justify phase two.

E
EncryptTechBD · 0 comments
Teacher reading Wikipedia with students in a classroom
Photo: James Rhoda / Wikimedia Commons (BY-SA)

Retention is often treated as a counselling activity, so its budget is a line for staff time and nothing else. In practice a working retention workflow combines data, rules, communication and human follow-up. Each of those has a cost, and each can fail on its own.

This guide is for a school, college or coaching centre that wants a defensible budget before committing to software. It separates one-off build costs from recurring run costs and gives a unit-cost formula you can populate with your own figures.

What the workflow includes, and what it does not

A retention workflow identifies students at risk, decides who should act, sends a message or makes a call, records the outcome and reviews whether the intervention helped. It may include attendance signals, fee status, assessment trends, assignment completion and direct contact notes. It does not include the teaching itself, and it should not be used to label a student permanently.

Be explicit about the boundary. If the workflow stops at sending an SMS, it is a communication tool, not a retention system. If it includes counselling, case notes and escalation, the staffing model becomes the largest cost and must be designed first.

Cost lines from first contact to follow-up

  • Data consolidation: connecting attendance, fees, assessments and contact records, including cleaning duplicate student identities.
  • Risk rules: defining thresholds and combinations that trigger a review, and testing them against past cohorts.
  • Workflow configuration: case creation, assignment, escalation, reminders and closure reasons.
  • Communication: SMS or messaging charges per message, templates, language variants and delivery reporting.
  • Staff time: counsellors, class teachers and administrators making calls, recording notes and following up.
  • Management and reporting: dashboards, cohort reviews and the person who owns the process.
  • Training: teaching staff on referral, counsellors on case handling, administrators on data quality.
  • Privacy and access: role-based permissions, consent records, retention rules and audit logs.
  • Contingency: allowance for data gaps and for the first term's process changes.

A unit-cost formula for planning

Build the budget from three numbers: the fixed annual platform and integration cost, the variable communication cost, and the staff hours consumed per case. The formula below makes the assumptions visible.

Annual programme cost = platform + integration amortisation + (messages × unit message cost) + (cases × average handling hours × loaded hourly cost) + training + contingency

Then calculate two ratios. The first is cost per active student per month, which tells you whether the programme is affordable at your scale. The second is cost per additional student retained, which requires a baseline retention rate and a comparison group or a before-and-after cohort. Do not publish the second ratio until you have at least one full cycle of data; a projected ratio is an assumption, not a result.

A percentage allocation for a pilot budget

Use this as a starting split for a first-phase budget. Adjust it to your data quality and staffing model, and choose values that total 100% for your own plan.

  • Platform and integration: 25–30%.
  • Data consolidation and identity cleanup: 20–25%.
  • Workflow design and configuration: 20–25%.
  • Staff time for the pilot cohort: 20–25%.
  • Training and measurement: 5–10%.
  • Contingency: 5–10%.

The split should change if you already have clean data or an existing case-management tool. It should also change if the pilot depends on counsellors who do not yet exist; in that case, staffing is not a percentage, it is a hiring decision.

Cost drivers specific to coaching centres and schools

Batch-based institutions have short cycles, so a student can be at risk within weeks rather than terms. That increases the frequency of review and the amount of staff time per student. Contactability is another driver: guardians may share one phone number, change numbers between terms, or prefer messaging over calls. A workflow that assumes a single channel will underperform and still cost the same to run.

Multi-branch operations add coordination cost. Each branch may have its own counselling habits and its own definition of attendance. Standardising the trigger rules reduces reporting effort but requires change management. A single-campus institution can start with a simpler rule set and fewer permission roles.

Vendor pricing questions

  1. Is the platform priced per student, per active case, per branch or per staff seat?
  2. Are messaging charges included, passed through at cost or marked up?
  3. Does the price change when a cohort graduates and a new one enrols?
  4. Which integrations are included, and what does a custom connector cost?
  5. How are consent, retention and deletion handled for students who leave?
  6. Can we export case notes and outcomes at the end of the contract?
  7. What support is included during the first term, when volumes are least predictable?

A 90-day plan with spend gates

Days 1–20: define retention. Agree what counts as retained, at what point in the cycle, and which cohorts are comparable. Output: a written definition and a baseline.

Days 21–40: audit the data. Check identity matching, attendance completeness and fee status. Output: a data quality report and a migration cost estimate. Gate: do not buy a platform if the data cannot support the rules.

Days 41–60: design the intervention. Map who contacts whom, within what time, with what script and what escalation. Output: a process map and a staffing estimate.

Days 61–75: pilot one cohort. Run the workflow manually or with a lightweight tool. Output: case volumes, handling time and message delivery rates.

Days 76–90: cost review. Replace estimates with observed hours and message counts, then decide whether to automate. Gate: approve phase two only if the unit cost fits the budget and the process is followed without reminders.

Metrics that justify the next phase

Track cases opened per hundred students, time from trigger to first contact, contact success rate, cases closed with a recorded reason, re-engagement after two weeks and the retention rate of the pilot cohort against a comparable group. Also track staff time per case and the share of alerts that were false positives. A high alert volume with low contact success is a process problem, not a software problem.

Building the budget with us

We build student and batch operations inside our Education division. The student and batch management service covers records, attendance and cohort reporting. The pricing page explains how pilot and rollout work are scoped. For the privacy side of student records, read how student data privacy obligations change as you grow.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes