Mujhtaba Bhat, Co-founder · 2 min read
Ask any principal about the last ERP their institution bought, and the story is rarely about features. It is about a fee collection day when the system would not print receipts, a ticket that was raised, and an answer that came the following week from someone who had never seen their fee structure.
That is the moment an institution stops using its software. Not formally. The office just goes back to the register "for now", and for now becomes permanent.
What fourteen years taught us
Before Acado, our team spent fourteen years supporting an education ERP for nursing and paramedical colleges across Jammu, Kashmir and Ladakh. Those years were not spent in a comfortable cloud. Connectivity failed for weeks at a time. Curfews closed roads. Systems ran on servers inside campuses because nothing else was dependable.
Support, in those years, meant driving to a college to update its server. It meant sending attendance alerts to parents by hand when the internet was down, because the parents still needed to know. It meant knowing each college's fee heads and exam pattern well enough to answer a question without opening the system.
We did not think of this as a service. It was simply what it took for the software to keep being used. And it is why those colleges are still clients.
Why we built Acado around it
When we built Acado as cloud software, the temptation was to leave that behind. Cloud software is supposed to scale without people. Raise a ticket, wait for the queue.
We went the other way. Every Acado institution has a person who knows its setup. General support runs on call and remote through working hours, and there is an arrangement for genuinely urgent issues outside them. Staff raise requests and suggestions from inside their own login, so nothing is lost in a corridor conversation. And the days that matter most to an office — fee collection, results, the first week of a session — get priority, because that is when a problem costs the most.
What this means when you are choosing
If you are comparing ERPs, the feature lists will look similar. Ask instead:
- Who picks up the phone on a fee collection day, and do they know my institution?
- What happens to a problem raised at 8 pm the night before results?
- When I ask for a change to a fee head, does it take a ticket, a sales call, or a conversation?
The answers tell you more than any module list. Here is how we answer them.