All articles
RA Strategies

What Are Research Analyst (RA) Strategies and How Do They Work?

RA strategies are option strategies published on Arthalab by SEBI-registered Research Analysts. What each listing shows, what is included in your plan, how to review one properly, and what they are not.

Arthalab11 min read
RA strategies are option strategies published on Arthalab by SEBI-registered Research Analysts. Instead of building the rules yourself, you review a strategy an analyst has published, check its backtest, and deploy it to your own broker account — or clone it and change the rules first.
They are included in the plan with no extra charge, no per-strategy fee and no profit sharing. This page covers what each listing shows, how to review one properly, and what they are not.

What a listing shows you

FieldWhat it tells you
The analystWho published it, with their SEBI registration
IndexWhether it trades NIFTY or SENSEX
Backtested win rateShare of profitable trades in the published test
Risk and rewardAverage win against average loss
Minimum marginWhat your account needs to run one lot
Strategy detailsThe legs, strike rules, timings and risk settings
The last row matters more than the first five. An RA strategy is not a black box — you can see exactly what it does before deploying it, which is the main thing distinguishing this from following a tip.

Why the minimum margin field is the one to read first

A strategy you cannot fund is not a strategy you can run, and this is the most common reason a deployment fails on the first day.
Option-selling strategies need substantially more margin than the premium they collect, and the requirement rises with volatility. The published figure is a starting point, not a ceiling — keep headroom above it rather than matching it exactly.

The multi-leg complication

For multi-leg strategies there is a further wrinkle: the margin needed partway through assembly can exceed what the finished position requires, because the hedging legs are not in place yet.

How to review one properly

The temptation is to sort by win rate and deploy the top result. That is the worst available method, for the same reason it is the worst way to read any backtest.
1

Check the index and margin first

If you cannot fund it, nothing else matters. This eliminates most of the list quickly.
2

Read the strategy details

The legs, strike rules, entry and exit times, and risk settings. You are checking whether you understand what it does.
3

Look at the drawdown, not the win rate

A high win rate with large losses is a worse strategy than a moderate one with small losses.
4

Convert the worst stretch to rupees

At the size you would actually deploy. If that number is uncomfortable, stop here.
5

Paper trade it

For at least two expiry cycles. This tells you how it behaves now, which the published backtest cannot.
6

Then deploy live at minimum size

One lot for a few weeks before scaling.
Steps three and four are where most of the value is. Reading a backtest from the risk end applies identically here, and an analyst's published figures deserve the same scrutiny as your own.

Deploy as-is, or clone and modify

Two routes, with a meaningful difference between them.
Deploy as publishedClone into My Strategies
What you runThe analyst's rules exactlyYour modified version
Updates from the analystYou see themYour copy is independent
Can you change the rules?NoYes — legs, strikes, timings, risk settings
Whose strategy is itThe analyst'sYours, from that point
Cloning is the right move if you want to change the size, tighten a stop loss, or adjust the exit time to suit your own risk appetite. It is also the right move if you want to study how the strategy is built by taking it apart.

When an analyst updates a strategy

Published strategies are not frozen. An analyst can revise the rules, and when they do, two things happen that are worth knowing about.
First, if you have the strategy deployed, you are notified that it has been updated. You can dismiss that notice once you have read it.

The stale-backtest flag

Second, a strategy whose rules have changed since its last backtest is flagged as having a pending backtest. That flag exists so you are not reading an out-of-date performance claim against a changed rule set — which is exactly the sort of mismatch that is easy to miss and hard to detect afterwards.

Comparing several strategies sensibly

With a list in front of you, the instinct is to rank. The question is what to rank on, because the obvious choice is the worst one.
Rank onWhy it misleads or helps
Win rateMisleads. A high rate with large losses is worse than a moderate one with small losses
Total returnMisleads. Says nothing about what was risked to earn it
Max drawdown in rupees at your sizeHelps. This is the constraint that decides whether you can run it
Return over max drawdownHelps. Profit per unit of worst pain, comparable across strategies
Minimum marginHelps as a filter. Removes what you cannot fund before anything else
Number of trades in the backtestHelps. A small sample makes every other figure unreliable
A workable method: filter by margin, then by whether the drawdown is acceptable in rupees, then compare what is left on return over drawdown. Win rate is the last thing to look at, not the first.

What to do during a losing stretch

Every strategy has them, and this is where deployed strategies are most often abandoned — frequently at the worst moment.
  1. Check the drawdown against the published backtest. If the current stretch is within what the backtest already showed, the strategy is behaving normally.
  2. Check the execution logs. Confirm the losses came from trades rather than from rejections or missed starts, which are different problems with different fixes.
  3. Check whether the analyst has updated the rules. A pending-backtest flag means what you are running may differ from what the figures describe.
  4. Compare against your written stop condition. The one you decided before deploying, in rupees.

What RA strategies are not

Being precise here matters more than almost anything else on this page.
  • Not personalised advice. A published strategy does not account for your capital, risk tolerance or circumstances.
  • Not a promise of returns. A backtest is evidence about the past, not a forecast.
  • Not managed on your behalf. You deploy it, you start it, you carry the position. The analyst does not operate your account.
  • Not a substitute for understanding it. If you cannot explain what the strategy does, you cannot judge whether to keep running it during a drawdown.
That last point is the practical one. Strategies are most often abandoned during a losing stretch, and the traders who hold through are the ones who understood the strategy well enough to know the stretch was within its normal behaviour.

What it costs

Nothing beyond the plan. There is no per-strategy subscription, no separate analyst charge, and no profit sharing — Arthalab takes no share of your trading profits.
This is worth checking when comparing platforms, because models differ. Some marketplaces charge per strategy subscribed, and some arrangements elsewhere involve a share of profits. Neither applies here.

How analysts get published

For transparency about where these strategies come from: an analyst applies with their SEBI registration number, the application is reviewed, and once approved they can publish strategies through their own dashboard.
From there they can publish, update and unlist strategies, and see how their published strategies are performing across the users who deployed them — including positions, orders and execution logs for those deployments.

If you are an analyst

If you are a registered Research Analyst interested in publishing, the RA onboarding guide covers the process and what the dashboard provides.

A sensible way to use them

RA strategies are most useful as a starting point rather than a destination.
  • Use one to learn how a well-built strategy is structured
  • Paper trade it before committing capital, as you would your own
  • Clone and modify it once you understand why each setting is there
  • Judge it on drawdown and consistency, not on the win rate
  • Decide your stop condition in rupees before deploying, not during a loss
The second item is the one worth insisting on. Paper trading needs no broker, no IP and no capital, and a month of watching a strategy behave teaches you more than any published figure.

The short version

  • Published by SEBI-registered analysts, included in the plan, no profit share
  • Each listing shows the analyst, index, backtested figures, margin and full rules
  • Read the margin first and the drawdown second — never sort by win rate
  • Clone if you want to modify; your copy then stops receiving the analyst's updates
  • A stale-backtest flag means the figures describe an earlier version of the rules
  • Not personalised advice, not a promise, not managed for you

Frequently asked questions

Filter by minimum margin first, then by whether the drawdown is acceptable in rupees at your size, then compare what remains on return over max drawdown. Win rate is the last thing to look at.

Check whether the drawdown is within what the published backtest already showed, confirm from the logs that the losses came from trades rather than rejections, and compare against the stop condition you wrote before deploying.

Yes, within the same three-simultaneous-strategy limit that applies to your own, with paper bots counting towards it.

A longer sample is generally more reliable, but composition matters more than length. A long quiet period tells you less than a shorter one that contains a volatility shock.

No. They are included in the plan with no per-strategy fee and no profit sharing.

No. A published strategy is not personalised advice and does not account for your capital or circumstances. Reviewing it before deploying remains your responsibility.

Yes, by cloning it into your own strategies first. Once cloned it is independent — the analyst's later updates do not reach your copy, and the published backtest no longer describes what you are running.

The analyst has changed the strategy's rules since its last backtest, so the published figures describe a previous version. Wait for the refreshed backtest before judging it on those numbers.

No. A high win rate paired with large losses is worse than a moderate one with small losses. Read the drawdown and convert it to rupees at your intended size first.

Yes, and it is the sensible way to form your own view before committing capital. It needs no broker, no IP and no money.

No. You deploy the strategy, you start it, and you carry the position. The analyst publishes rules; they do not operate your account.

You are notified that it has been updated, and you can dismiss the notice once you have read it. Your deployment runs the configuration it was deployed with.

They count towards the same limit as your own — three strategies running simultaneously on the Monthly Plan, with paper bots included in that count.

Start with a free 3-day trial

Build a strategy, backtest it and run it on paper — no broker, no IP and no money needed to try it.

Ask us on Telegram
What Are Research Analyst (RA) Strategies and How Do They Work? | Arthalab — Algo Trading India