What a listing shows you
| Field | What it tells you |
|---|---|
| The analyst | Who published it, with their SEBI registration |
| Index | Whether it trades NIFTY or SENSEX |
| Backtested win rate | Share of profitable trades in the published test |
| Risk and reward | Average win against average loss |
| Minimum margin | What your account needs to run one lot |
| Strategy details | The legs, strike rules, timings and risk settings |
Why the minimum margin field is the one to read first
The multi-leg complication
How to review one properly
Check the index and margin first
Read the strategy details
Look at the drawdown, not the win rate
Convert the worst stretch to rupees
Paper trade it
Then deploy live at minimum size
Deploy as-is, or clone and modify
| Deploy as published | Clone into My Strategies | |
|---|---|---|
| What you run | The analyst's rules exactly | Your modified version |
| Updates from the analyst | You see them | Your copy is independent |
| Can you change the rules? | No | Yes — legs, strikes, timings, risk settings |
| Whose strategy is it | The analyst's | Yours, from that point |
When an analyst updates a strategy
The stale-backtest flag
Comparing several strategies sensibly
| Rank on | Why it misleads or helps |
|---|---|
| Win rate | Misleads. A high rate with large losses is worse than a moderate one with small losses |
| Total return | Misleads. Says nothing about what was risked to earn it |
| Max drawdown in rupees at your size | Helps. This is the constraint that decides whether you can run it |
| Return over max drawdown | Helps. Profit per unit of worst pain, comparable across strategies |
| Minimum margin | Helps as a filter. Removes what you cannot fund before anything else |
| Number of trades in the backtest | Helps. A small sample makes every other figure unreliable |
What to do during a losing stretch
- Check the drawdown against the published backtest. If the current stretch is within what the backtest already showed, the strategy is behaving normally.
- Check the execution logs. Confirm the losses came from trades rather than from rejections or missed starts, which are different problems with different fixes.
- Check whether the analyst has updated the rules. A pending-backtest flag means what you are running may differ from what the figures describe.
- Compare against your written stop condition. The one you decided before deploying, in rupees.
What RA strategies are not
- 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.
What it costs
How analysts get published
If you are an analyst
A sensible way to use them
- 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 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.

