What I automate / Schools, colleges and coaching institutes
The front desk between batches
An institute's back office runs in the gaps between batches. Fees are chased, attendance is marked, marks are added up, report cards are typed, and the same message is sent to forty parents individually. All of it by people who are also dealing with whoever is standing at the counter.
The work is not difficult. It is repetitive, interruptible, and done under pressure — which is exactly the combination that produces mistakes that cost trust. A fee reminder sent to a parent who has already paid is worse than no reminder at all.
Everything here runs in your institute's own Google account. The data stays yours, you can remove my access whenever you like, and if you stop working with me it keeps running.
You probably know this is you if
- Fee dues are worked out by going through a register or a workbook
- Receipts are written or typed by hand
- Attendance registers are totalled at month end
- Marks are added up and report cards typed one student at a time
- The same message is sent to parents individually, forty times
- The owner finds out how the month went only when somebody prepares a report
The jobs in this area
Working out who owes fees this week
An instalment due list every morning, ordered by how late each one is, with receipts generated on payment.
Marking and totalling attendance
One tap per student, an absent-three-sessions list before it becomes a dropout, and monthly percentages ready before a parent asks.
Adding up marks and making report cards
Marks entered once; totals, ranks and a one-page report card per student come out of it.
Typing the same update to forty parents
A ready message per parent with their child's own numbers filled in, sent by your staff from your own number.
Counting teaching hours at month end
Hours logged as classes happen, totalled per teacher when it is time to pay them.
How a build like this goes
- 1
Start with fees, almost always. It is where the money is, the rules are clear, and the result is visible within days.
- 2
Keep the staff habit and change what happens behind it. Reception keeps filling the same form or register; the counting, checking and reminding stop being done by a person.
- 3
Build on Google Sheets and Apps Script where it fits, because you already have the account, there is no licence to pay for, and any developer can maintain it.
- 4
Messages to parents go from your own number, sent by your staff, one at a time — or through Meta's official platform. Never through unofficial bulk tools, which get your number blocked.
A worked example
Fee dues and receipts for a 300-student institute
- Before
- Most of a day each week going through records to work out who owes what, plus receipts typed by hand.
- After
- A dues list every morning, ordered by how late each instalment is. Receipts generated on payment. A monthly pending-fees summary for the owner.
6 hours a week × 52 is about 312 hours a year. Even at a modest ₹150/hour that is around ₹47,000 a year against a quick-win or small module build. The larger effect is usually collection: instalments chased on the day they are due rather than whenever somebody has time.
Those are illustrative figures, not a quote and not a promise. Your own numbers are the only ones that matter — the calculator does the same arithmetic on them.
What this normally costs
A job in this area is usually a quick win: ₹18,000 to ₹45,000, ready in 3 to 7 working days. The exact number comes from the audit, in writing, before anything is built.
The audit itself is ₹9,999 and comes off the first build in full. If it turns out this is not worth automating for you, that is what the report will say.
Questions about this kind of work
We already use Classplus or Teachmint. Is this a replacement?
No. Keep using them for what they do well. This is for the jobs they do not cover, or cover in a way your staff have quietly stopped using.
Will you send bulk WhatsApp messages to parents?
No. Unofficial bulk messaging gets your institute's number blocked. Messages go from your staff one at a time, or through Meta's official platform if the volume justifies it.
Where does our student data live?
In your institute's own Google account. I get access only to build and maintain it, you can remove that access at any time, and nothing is copied anywhere else.
Tell me about your version of this
Tell me the job you are tired of
One call, half an hour. You will get a straight answer about whether it is worth automating — including 'no' if that is the answer.