Filter in this order
- Minimum margin. If you cannot fund it, nothing else about it matters.
- Maximum drawdown, converted to rupees at your size. If you would not sit through it, stop here.
- Trade count in the published backtest. Below roughly a hundred, every ratio is provisional.
- Whether you understand the rules. If you cannot explain it, you will abandon it during the first bad stretch.
- Return over max drawdown. Only now, and only across what survived the first four.
What each published figure tells you
| Figure | What it says | What it hides |
|---|---|---|
| Win rate | How often trades were profitable | The size of the losses |
| Risk and reward | Average win against average loss | How the two combine over time |
| Minimum margin | What the account needs for one lot | That it rises with volatility |
| Index | Which market it trades | Nothing — this one is straightforward |
| Backtest period | What conditions it was tested in | What conditions it was not |
Win rate and loss size, together
| Strategy A | Strategy B | |
|---|---|---|
| Win rate | 85% | 40% |
| Average win | Small | Large |
| Average loss | Large | Small |
| What it feels like | Frequent small wins, rare painful losses | Frequent small losses, occasional large wins |
| How people abandon it | After one bad day undoes months | After a long losing run |
Converting drawdown to rupees
Take the published maximum drawdown percentage
Multiply by what you intend to deploy
Look at the rupee number
If the answer is no, reduce size or move on
Checking the backtest is current
Before you deploy
- You can fund the margin with headroom for a volatility rise
- You have converted the drawdown to rupees and accepted it
- The trade count in the backtest is large enough to mean something
- You can explain in one sentence what the strategy does
- The backtest is current rather than flagged as pending
- You have written your stop condition, in rupees, before deploying
Running more than one
The short version
- Filter by margin first, drawdown second, trade count third
- Win rate without average loss alongside it is close to meaningless
- Convert the drawdown to rupees at your size before anything else
- A pending-backtest flag means the figures describe older rules
- Paper trade before funding, and write your stop condition first
- Three similar strategies on one index are not three independent bets
Frequently asked questions
Filter by what you can fund, then by whether the drawdown is acceptable in rupees at your size, then by whether the backtest has enough trades to mean anything. Compare performance only across what survives.
A high win rate paired with large average losses is worse than a moderate one with small losses. The win rate says nothing on its own about whether the strategy makes money.
What an account needs for one lot. It was computed at a point in time and margin rises with volatility, so treat it as a starting point and keep headroom above it.
No. It is the worst that happened in that sample. A longer or different period would very likely contain a worse one, so read it as a lower bound rather than a ceiling.
The analyst has changed the rules since the last backtest, so the published figures describe an earlier version. Wait for the refreshed numbers before judging it on them.
Three simultaneously, with paper bots counting towards the same limit. Strategies on the same index expressing similar views are correlated, so they are less diversified than they appear.
Yes. It costs nothing beyond a plan and shows how the strategy behaves now rather than how it behaved during the test period.
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.

