I learned this one the hard way, and at my own expense. Over the past months I visited more than fifty coaching institutes in Chandigarh to sell them software. I sold nothing. In most of those visits I never reached the owner at all — the conversation ended at the front desk.

For a while I told myself that was bad luck. It was not. It happened for a reason that is worth understanding whether you are selling software or buying it.

The person who evaluates it is not the person who benefits

In almost every institute I walked into, the first and often only person I spoke to was a receptionist or front-desk administrator. They decide whether a vendor gets five minutes with the owner. And their interests are not the owner's interests.

You gain from an institute that runs on less admin: better collection, fewer mistakes, more visibility. The salaried person at the desk gains none of that. Their pay does not move when fee collection improves. What does move is:

Their workload, upward, immediately. A new system to learn on top of the job they already have, often during the busiest weeks of the year.
Their visibility. Work that was previously known only to them becomes a dashboard. Not everyone is doing anything wrong — but nobody enjoys being measured for the first time.
Their job security, at least in their own mind. When a vendor stands at the counter saying “this automates the work you spend your day doing”, that sentence has an obvious second meaning.

I was pitching automation to the person automation threatens. I thought I was describing a benefit. From the other side of the desk it was a stranger explaining, in the middle of a working afternoon, why less of their job might be needed. Blocking me was the rational move. It happened about fifty times.

Why this matters to you, not just to vendors

You might read that and think it is my problem to solve. It is — but the same dynamic is why the software you eventually buy quietly fails to get used.

Most institute software does not fail in the demo. It fails four months later, when the front desk has drifted back to the register for attendance because it is faster, and started keeping a private spreadsheet of fees because they trust it more. The licence is still being paid. The system is half-empty. And the owner concludes the software was bad, when what actually happened was that nobody at the desk ever had a reason to want it to work.

What actually changes it

None of these are clever. They are just things almost nobody does before signing.

Put the front desk in the demo. Not to approve the purchase — to be seen as the person whose day it affects. The cost is thirty minutes. The alternative is a system imposed on the one person who has to live in it.
Lead with the drudgery, not the automation. The honest pitch to an administrator is not that the software does their job. It is that it deletes the part of their day spent typing the same student's phone number into three places. That is a real benefit to them, it is true, and it is the version I should have been leading with.
Say out loud what happens to their role. If nobody is being replaced, say so plainly, early, and to their face. Silence gets filled with the worst assumption, and you will never hear the assumption stated — you will just find the system unused.
Give them something that is theirs. Whoever is going to use it daily should be the one who sets up the batches and the fee reminders. People defend what they built and abandon what was handed to them.
Don't make the first month a measurement exercise. If the visible output of new software is a report on who is behind on data entry, you have confirmed the fear rather than removed it.

The uncomfortable version. If your front desk genuinely has nothing to gain from the institute running better, that is not a software problem and no system will fix it. It is worth asking why the answer is nothing — and whether that is also why other things do not improve.

What I got wrong

I spent fifty visits treating the front desk as an obstacle between me and a decision-maker. They were not the obstacle. They were the first honest signal that I was selling the wrong thing to the wrong person, and I was too slow to hear it.

If you are choosing software this year, the question worth asking is not which product has the most features. It is which one the person at your front desk would still be using in March — and whether anyone has asked them.

The full account of those visits is in my field notes from fifty institutes, and if you are weighing a change, how to migrate without breaking admission season is the practical companion to this one.

Your staff aren't resisting the software. They're resisting what it does to them.