When I registered as a mutual fund distributor, I expected the hard part to be understanding products, regulations, and client relationships. It was all of those things. But the part I did not expect to consume so much of my time was the operational plumbing. The paperwork loops, the reconciliation checks, the follow-ups, the small repetitive tasks that individually take five minutes but collectively eat your week. That friction is what eventually pushed me to start building.
What the Day-to-Day Actually Looks Like
Most people picture a mutual fund distributor as someone who recommends funds and collects a trail commission. That picture is not wrong, but it leaves out a lot. Behind every client account there are KYC records to track, nomination updates, SIP mandates, transaction confirmations, portfolio statements, and periodic reviews. Multiply that by dozens of clients and the admin load becomes real very quickly.
The platforms that serve distributors have improved a lot over the years. BSE Star MF, MFU, and the AMC portals have made transaction execution far easier than it was a decade ago. But the connective tissue between those platforms and a distributor's own client records is still largely manual. You pull a report from one place, cross-check it against your own sheet, send a summary to the client, and then log the interaction somewhere. Each step is small. Together they are a significant time sink.
I started keeping a list of every task I did more than twice a week. Within a month, the list had about twenty items on it. That list became the first version of my automation backlog.
The First Thing I Built (and Why It Was Ugly)
The first tool was not impressive. It was a Python script that pulled transaction data from a downloaded CSV, matched it against a client master sheet in Google Sheets, and flagged any SIP that had not come through in the expected window. No UI. No error handling worth speaking of. It broke whenever the CSV column headers changed.
But it worked well enough to save me about forty minutes every Monday morning. That was the proof of concept I needed. Not that the technology was good, but that the problem was real and solvable.
I rebuilt it properly over the next few months. Added a basic web interface, proper error logging, and a way to push alerts to WhatsApp via an API. The core logic stayed the same. What changed was that it stopped being fragile and started being something I could actually rely on.
The lesson there was something every founder eventually learns: the first version exists to confirm the problem, not to impress anyone.
Where Fintech Infrastructure Helps and Where It Falls Short
Building these internal tools gave me a very different perspective on the fintech ecosystem than I had before. When you are a user of a platform, you see the interface. When you start building on top of data from those platforms, you start to see the gaps.
The gaps are not always about missing features. Sometimes they are about data formats that are inconsistent across AMCs. Sometimes they are about reports that are available but not in a machine-readable form. Sometimes they are about workflows that assume a human will always be in the loop, even for steps where that adds no value.
This is not a criticism of the platforms. They are serving a large, diverse distributor base with very different levels of technical sophistication. Building for the median user means the more technical edge of the market has to roll its own solutions. That is fine. It is actually where a lot of interesting fintech infrastructure gets built, by people who got frustrated enough to fix their own problem and then realised others had the same one.
Account aggregators, the SEBI-regulated framework that allows consented data sharing across financial institutions, are probably the most interesting structural development in this space. The potential for a distributor to pull a complete financial picture of a client's holdings across institutions, with the client's consent, changes what advisory and review conversations can look like. We are still early in that adoption curve, but the direction is clear.
What Building Internally Taught Me About Product Thinking
The most useful thing about building tools for your own business is that you are the customer. There is no product manager between you and the problem. You feel the friction directly, you build the fix, and you know immediately whether it worked.
That tight feedback loop is something that is very hard to replicate when you are building for external users you have never met. It also makes you ruthless about scope. I did not build features because they were interesting. I built them because I needed them on Tuesday morning.
That mindset, build only what removes a real cost, is one I have tried to carry into everything since. It sounds obvious. In practice, most product development drifts away from it fairly quickly once a team gets comfortable and starts building for hypothetical users instead of real ones.
There is also something specific to financial services worth noting here. Compliance and auditability are not optional features you add later. When you are handling client transactions, even indirectly, you need a record of what happened and when. Building that in from the start is much cheaper than retrofitting it. I learned that the slightly painful way.
The Broader Pattern in Indian Fintech
What I went through is not unique to mutual fund distribution. Across insurance distribution, loan origination, wealth management, and payments, there is a large population of small and mid-sized financial intermediaries who are technically underserved. The large platforms are built for volume and the largest players. The smallest operators are using spreadsheets and WhatsApp. The middle is where interesting automation and tooling opportunities sit.
A lot of the most promising B2B fintech companies in India right now are essentially selling what someone like me built for themselves, packaged properly and made available as a service. The insight usually comes from someone who lived the problem first.
That is the part of the fintech story that does not get told as often as the consumer apps. The back-office, the compliance stack, the reconciliation layer. It is less glamorous than a consumer payments app. It is also where a significant amount of real value gets created.
Running a distribution business and building on top of it at the same time is a strange position to be in. But it is one that gives you a ground-level view of how financial services actually operate, not how the pitch decks say they operate. That view is worth a lot.