Field notes
I visited 50 coaching institutes in Chandigarh. I never got past the front desk.
I'm Uday Doda. I founded DeskFlux, and over the past months I walked into more than fifty coaching institutes across Chandigarh to sell it to them.
I can't tell you what fifty coaching institute owners in Chandigarh think about software. I visited fifty institutes, but I did not meet fifty owners. Most of the time I met a front desk, and the front desk is where it ended.
I sold nothing. Not one institute bought anything. That is worth saying plainly at the top, because everything below is written by someone the market said no to, repeatedly, in person — and I think what happened at those desks is more useful than another article about features.
What I expected to find
I expected paper. Registers, a fee diary, a cupboard of admission forms, and an owner who had never been shown an alternative. I had run the front desk of an institute myself, so I thought I knew the shape of the problem: these places were behind, and someone had to bring them forward.
That was wrong on almost every count, and it was wrong in an interesting way.
They were already computerised, and already fed up
Nearly every institute I walked into had a computer on the front desk. Most had two to five hundred students. And most were already paying for software — not one system, but several: something for admissions, something else for fees, a separate thing for messaging parents.
None of it talked to each other. So the person at the desk typed the same student's details into one system, then another, then a WhatsApp message. They had bought software and kept the work. What they were doing with three tools was, in practice, what they would have been doing with a spreadsheet — only now it cost money.
This is the thing outsiders get wrong about Indian coaching institutes. The problem is not that they refuse technology. Many of them bought it years ago. The problem is that they bought four things, and nobody joined them up.
I had arrived to solve a problem they had already tried to solve. That changes the conversation completely, and I did not adjust to it fast enough.
The person who decides is not the person who benefits
Here is the pattern I did not see coming, and the reason I think most of those visits ended before they started.
The person who evaluates the software is the receptionist or the front-desk administrator. The person who gains from it is the owner. Those are two different people, and their interests do not point the same way.
The owner gains from an institute that runs on less admin. The salaried employee at the desk gains nothing from that. Their pay does not move if fee collection improves. What does move is their workload — a new system to learn in the middle of admission season — and, if the software does what I was promising it did, the amount of work their job consists of.
I was walking in and saying this automates the work you spend your day doing. I thought I was describing a benefit. From the other side of that desk it is not a benefit. It is a threat, delivered by a stranger, in the middle of a working afternoon.
I was not unlucky fifty times. I was correctly identified as a risk fifty times, by people behaving completely rationally given what they had to gain and lose.
I want to be careful here, because there is a lazy version of this observation that blames staff for not caring about the business. That is not what I saw. I saw an incentive gap that the person at the desk did not create and is not responsible for closing. It is the vendor's job to make the case to the person whose work actually changes — and I did not make it.
“We'll think about it” was never a maybe
The most common way a conversation ended was: we'll think about it, leave your card. For a long time I logged those as warm. They were not. Nobody thought about it, and nobody was ever going to.
What took me too long to understand is that a soft no from someone who cannot say yes is just a polite way to end a conversation without a confrontation. It is only a real maybe when it comes from a person with the authority to buy. I had a pipeline full of maybes from people who were never going to be the ones deciding.
The real objection nobody says out loud
On the few occasions the conversation did go further, the resistance was never about features and rarely about price. It was about the switch.
An institute with three hundred students has three hundred fee records, part-paid instalments, discount arrangements agreed verbally with particular parents, and an admission season it cannot afford to have go wrong. Moving all of that into a new system in exchange for a promise from someone who walked in that morning is a genuinely bad risk-reward.
Nobody says I am afraid of losing three hundred fee records mid-session. They say we'll think about it. Those are the same sentence. It took me a long time and a lot of visits to hear it that way. If you sell to small businesses that already run on something, the switching risk is the objection, and every conversation that does not address it is a conversation about the wrong thing.
What I would do differently
This is the part I actually want to write down, because the rest is just what happened.
- Stop pitching automation to the person automation threatens. The honest pitch to a front-desk administrator is not that the software does their job. It is that it deletes the part of their day spent typing the same thing into three systems. Same product, opposite reception. I led with the version that closes the gate.
- Stop counting gatekeeper conversations as market feedback. Fifty visits told me a great deal about how front desks behave and almost nothing about what owners think. I had been treating the first as an answer to the second, which produces a very comfortable and very wrong conclusion: that the market is not interested.
- Lead with migration, not features. If the real fear is the switch, then the thing worth saying first is what happens to those three hundred records — who moves them, how long it takes, and what happens if it goes wrong. Everything else is a conversation you have after that one.
- Go when the owner is there, or don't go. Walking in at a time that suits me and hoping is not a sales process. It is fifty polite rejections wearing the costume of one.
I am still selling in this city, and I am still often wrong about it. But I would rather publish what fifty closed doors taught me than another list of features — and if you are selling anything into small businesses in India, I suspect the person blocking you is not the person you think, and is not being unreasonable.
If you run an institute and any of this reads wrong from where you are sitting, I would genuinely like to hear it — tell me here, or read why I started building this in the first place.
Field notes from more than fifty in-person visits to coaching institutes in Chandigarh and fifty to sixty calls to institutes elsewhere in India, made by Uday Doda, founder of DeskFlux, during 2026. No institute is named in this piece and none is identifiable from it. Everyone I met let me in on goodwill, and the observations here are about my own selling, not about them.