Most 'AI' in school software is decoration. One kind isn't. One kind isn't.

Walk the aisles of any school-technology expo in India this year and you will lose count of the word 'AI'. It is on every banner — an AI chatbot bubble on the website, an AI camera at the gate, an AI-powered this and a smart that. Ask the person on the stall what it does for the school office at 10 in the morning, when a parent is on the line asking whether their fee has gone through, and the answers get vague fast. Most of it photographs well in a brochure and helps almost no one behind the front desk.

Here is the claim this guide will defend: almost all 'AI' sold to Indian schools today is decoration. There is exactly one kind that changes the working day — a school ERP your own AI assistant can read and answer questions from, in plain language, in seconds. Everything else is a mascot. This is how to tell them apart before you sign.

What 'AI-powered' usually means on a school-software stall

Strip the marketing away and most 'AI' features for schools fall into two buckets. The first is a scripted chatbot — the chat bubble in the corner of a school's website that answers admission enquiries from a fixed list of replies. Ask it something slightly off-script — "who in class 9 still owes second-term fees?" — and it hands back a link to a help page. It cannot see your school's real data, so it cannot answer your school's real questions.

The second is pattern recognition dressed up as intelligence — a camera that reads faces at the gate, or a tool that flags 'at-risk' students from attendance patterns. Some of this is genuinely useful. But none of it touches the thing a school office actually struggles with every single day: getting a straight answer out of the software it already paid for.

That is the tell. A real school-software problem is almost never a shortage of data — the fee is recorded, the admission is entered, the document is uploaded. The problem is the distance between the question in the principal's head and the answer on the screen: ten clicks, two reports and a spreadsheet stitched together by hand. A chatbot in the corner does nothing about that distance. It is a mascot, not a member of staff.

Put the two side by side and the difference stops being about the word 'AI' at all. It becomes about something concrete: what the thing can actually see, and what it can actually do with what it sees.

The shift that actually changed things

For years the assistants that can genuinely reason — the ChatGPTs and Claudes that your teachers and your own children already use every day — had no safe way to reach the one place a school's answers live: its ERP. The intelligence was in one box and the data in another, with no wire between them.

That wire now exists. AI assistants recently gained a safe, standard way to connect to trusted software — to read specific things, with permission, and answer questions about them, without ever taking a copy of the whole database. It is the same kind of quiet plumbing shift that once let fee software start accepting UPI: unglamorous, but it changes what is possible overnight.

The moment that arrived, the right move for a school ERP became obvious — stop building a worse chatbot of your own, and instead let the good assistants ask your school directly. That is what an AI-native school ERP means: not a bot bolted to the website, but software built so the AI assistant you already use can read your live records and answer plainly. A school connects its account once, and after that anyone it allows simply asks — in English, in Hindi, in the Hinglish real offices actually speak — and gets the exact list, number or amount back in seconds. No export. No report. No training.

How to tell a real one from a demo trick

Buzzwords are cheap, so judge the substance, not the banner. The good news is that separating a genuine AI-native ERP from a chatbot in fancy dress does not require you to understand any of the technology. It takes six plain questions, and you can ask every one of them in a demo without using a single technical word. A real AI-native ERP answers yes to all six; a repainted chatbot quietly fails most of them, usually by changing the subject to some feature it does have. Ask them anyway, and watch which way the vendor moves.

What it looks like in a Tier-2 school office

Strip away the technology and look at the working day, because that is where a real feature proves itself. The front-desk assistant stops being a human search engine for forty 'has my fee gone through?' calls. The accountant produces the defaulter list before the reminder calls, not by staying late to build it afterwards. The principal walks into the management-committee meeting with every number current to the minute, because she asked for them on the way in rather than promising to 'send the rest by evening'.

None of this asks the staff to learn new software — and in India that is the part that matters most. Schools rarely switch ERPs because of a shiny feature; they switch because the last one made their staff feel slow and stupid. An assistant you talk to in your own words is the opposite of that. It meets the office where it already is.

“A school that can't get a straight answer out of its own software doesn't have a data problem. It has a distance problem — ten clicks between the question and the answer. The right kind of AI deletes the ten clicks.”

The safety questions worth asking first

The first thing a serious principal asks is the right thing: can the AI change or delete anything, and where does our data go? For an ERP built correctly, the answers are reassuring by design. The assistant is read-only — it can tell you a number, but it cannot collect a fee, edit a record, remove a student or message a parent. It stays inside the same access rules your staff already work under, so a figure that is hidden on screen stays hidden in the answer. Your records never leave the ERP; the assistant only ever sees the answer to the specific question you ask, and you can disconnect it at any moment.

This is not caution for its own sake. An assistant that answers is enormously useful and carries almost no risk — the worst it can do is tell you a wrong number, which you can check. An assistant that can act on live school records without a person watching is a liability no school should take on, however slick the demo. If a vendor cannot explain these boundaries plainly, treat the 'AI' label as marketing until proven otherwise.

Where this is fair to be sceptical

Let me argue the other side, because the hype deserves it. An assistant is a mirror, not a magician — if a school's records are messy, the answers will be messy too, and no AI fixes years of half-entered data overnight. Adoption is a real hurdle: plenty of principals are rightly wary of letting any AI near school information, and that caution is healthy, not backward. And honest AI-native ERPs, Inkwelly included, have started deliberately narrow — fees and students first — rather than promising every answer and shipping a fragile everything. If you were betting against this whole idea, that is exactly where you would push: dirty data, cautious staff, and early narrowness.

What to do with all this

So when the next vendor says 'AI', do not argue about the word — ask to see it read your own school's data and answer a question you actually care about. If it can, and if it is read-only, permission-bound and hosted in India, you are looking at the one kind of school AI that earns its keep. If it cannot, you are being sold a mascot with a chat bubble. The technology to close the distance between a principal's question and her school's answer finally exists. The only real decision left is whether your next ERP was built to use it — or just to advertise it.

See what 'ask your school anything' actually looks like

Book a 20-minute demo, bring the questions your office asks every day, and watch them answered from live data in seconds.