The Brief
Raacord was built for Taxation Consultancy Pvt. Ltd. — a platform to connect SEBI-registered research analysts with subscribers, in a space where compliance isn't optional. Research analysts in India operate under SEBI regulation, and any platform built to serve them has to be built around that constraint from day one, not bolted on afterward.
This was a real client, a real regulatory environment, and a real product that needed to work correctly the first time.
The Build
Design had already been outsourced and finalized before the build started, so the engineering work began with a clear visual direction already in place. From there:
- Frontend — built end to end in React, plus a portion of the backend handled through Appwrite
- Backend — the bulk of it built by my collaborator, Yameen, in Python
- Product work — scoping, flow decisions, and feasibility were largely a shared effort between the two of us
The platform integrated DigiLocker for identity/document verification, Razorpay for payments, and a Telegram bot as an additional channel for analysts and subscribers to interact with the platform outside the core web app.
Building for a SEBI-regulated space means the compliance layer isn't a feature — it's the foundation everything else has to sit on top of. Identity verification, payment handling, and analyst registration all had to hold up to that standard, not just work.
The Payments Problem
Payments weren't a straightforward integration. Since Raacord paid out to 30+ independent research analysts rather than one merchant, we needed a way to split incoming subscriber payments and route each analyst's share to them directly.
We started with RazorpayX's Payouts/Transfers API — Razorpay's business banking layer built for sending money out (vendor payments, payroll, bulk disbursements). It worked, but it wasn't actually the right tool for a marketplace splitting incoming payments across many recipients — it's built for outbound payouts from a business account, not for tying a split to the original transaction.
We ended up migrating to Razorpay's Route API instead — built specifically for marketplaces that need to split an incoming payment across multiple linked accounts as part of the same transaction, with each analyst onboarded as a KYC-verified Linked Account.
That migration wasn't just a code change. Route required each analyst to go through Razorpay's own compliance and KYC process as a Linked Account, which meant we were on direct calls with Razorpay's team working through onboarding requirements and compliance questions specific to a SEBI-regulated marketplace. It slowed us down at the time, but it was the right foundation — and it's the kind of problem you only really learn by hitting it mid-build, not by reading the docs beforehand.
The Scale
Raacord went on to serve 30+ registered research analysts, with a combined subscriber base of 5,000+ across those analysts — a real platform carrying real regulated financial relationships, not a demo.
What I'd Point To
Raacord sits apart from my other projects because of the regulatory weight behind it. It's one thing to build a product that works. It's another to build one that has to work correctly inside SEBI's compliance requirements, handle real payments through Razorpay, verify real identities through DigiLocker, and still feel usable for the analysts and subscribers actually relying on it day to day.
Paired with Yameen on backend and product, and owning the frontend and part of the backend myself, this is the project that best shows I can operate inside real constraints — not just ideal ones.