Scaling a Research Analyst Practice: What Breaks at 25, 100 and 500 Clients
Most RA practices do not stall on getting clients. They stall because the process that worked for 20 people quietly breaks at 100. Here is where, and what to fix first.
Note: This is a practice-management guide built from the regulatory duties of a Research Analyst, not a case study. Figures in the worked example are simple arithmetic, not results achieved by any named practice.
Everyone wants the story of the analyst who reached 500 clients. We do not have a customer to put in that story, and we will not invent one. What we can do is walk through the stages a practice passes through and the specific duties that stop scaling at each. It is less exciting and more useful.
Some arithmetic first
At an illustrative fee of โน30,000 a year, 25 clients is โน7.5 lakh, 100 clients is โน30 lakh and 500 clients is โน1.5 crore in annual fees before costs. Those numbers are not a forecast, and your fee has to sit inside the cap for individual and HUF clients (โน1,51,000 per family per year under SEBI's January 2025 circular) and inside your own research capacity. They show why the question matters: the work that is trivial at 25 clients is a full-time job at 500.
Around 25 clients: the spreadsheet stage
You know every client. Onboarding is a handful of documents sent by hand, research goes out over WhatsApp, and records live in folders. It works because you are the system.
- Start now: a standard onboarding pack (agreement, MITC, KYC, disclosures). See client onboarding.
- Start now: one logged channel for research delivery, so your archive is a by-product of sending. SEBI's guidelines require records of client interactions from the first contact, kept for five years.
- Risk: ad hoc messages with no archive. See communication scripts.
Around 100 clients: the consistency stage
You no longer remember who was told what. Clients are on different service tiers, some on different renewal dates, and some have raised grievances you must answer to a clock.
- What breaks: who received which recommendation, and when. A client disputing a call needs an answer from records, not memory.
- What breaks: renewals. Expiring clients keep receiving research or lapsing clients are lost silently.
- What breaks: grievance handling. Complaints need an owner, a log and a response, not a chat thread.
- Fix: structured recommendations with timestamps, tiered delivery lists and a complaints register. See recommendation tracking.
Around 500 clients: the audit stage
At this size you are a target for inspection by volume alone, and the regulator will assume a process, not heroics. You also have staff, which brings role boundaries, access control and training.
- What breaks: one person sending research. Delivery needs a queue, retries and a record that every client in the tier got every note.
- What breaks: evidence. You need to show, quickly, the agreement, MITC, KYC and communications for any client. See inspection preparation.
- What breaks: performance claims. At scale, marketing a track record without verification is a larger exposure. See what PaRRVA is.
- What breaks: churn. A 10% annual loss at 500 clients is 50 people to replace. See why clients leave.
The pattern across all three stages
Where software fits
Software is useful where a duty repeats per client: structured onboarding, logged delivery, timestamped recommendations, an archive you can search. It does not replace the analyst's judgement or responsibility. The Research Analyst remains the regulated entity. Compare options on how they handle records first, using how RA software options compare.
FAQ
What is the hardest part of scaling a Research Analyst practice?
Keeping records and delivery consistent as the client list grows. Duties that are manageable by hand at 25 clients, such as logging who received which recommendation, break around 100 and become an audit exposure at larger sizes.
How many clients can a solo Research Analyst handle?
It depends on research output, service tiers and how much of onboarding, delivery and record-keeping is standardised. The honest limit is set by process, not by hours alone.
Do I need software to run a Research Analyst practice?
Not at the start. Past roughly 100 clients, a spreadsheet and chat threads usually stop being a reliable record, and structured tooling for onboarding, delivery and archive becomes the safer route.
Does Aktai have case studies of analysts scaling?
Not yet. We publish case studies only from real customers who agree to be named, so this guide is built from regulatory duties and not from invented outcomes.