Five Conditions, Twelve Wishes: Designing an Option-Selling Rule Set Under a Builder Cap
Sit down to build a multi-leg option-selling strategy in a no-code builder and you will hit the same wall within the first hour. You have twelve ideas for rules. The builder gives you room for five. Some tools cap the number of entry and exit conditions per strategy, and the cap is usually small enough that you feel it before you finish the first draft.
Most people react in one of two ways. They squeeze in every rule by making each one vague, or they pick the five that feel most clever and hope for the best. Both approaches produce strategies that are hard to trust. A vague rule fires at the wrong time. A clever rule fires so rarely that it never earns its slot.
This article gives you a method for the choice. It covers how to count what you really have, how to rank rules by what they protect, which ones to drop first, which ones you can move out of the builder entirely, and how to tell when the cap is a sign that you have outgrown the tool. The examples are built around weekly-expiry index selling on NIFTY and SENSEX, but the logic holds for any multi-leg short-premium setup.
What a condition cap really limits
A cap on conditions is a cap on decisions your strategy can make by itself. It is not a cap on how good the strategy can be. That difference matters, because a short-premium strategy needs surprisingly few decisions to work, and a strategy with many decisions is often just a strategy with many ways to fail.
First, learn how your builder counts. This is the step people skip. Some builders count one condition per rule, no matter how many legs it applies to. Others count a stop-loss on each leg as a separate condition. Others count the entry time as a condition and the exit time as another. If you have four legs and each has its own stop-loss and its own target, a builder that counts per leg has used eight slots before you have written anything about entry. Read the vendor's current documentation and test with a dummy strategy. Do not rely on a forum post, because these rules change between versions.
Second, notice what a cap does to your thinking. It forces you to say which rules you would defend in front of a sceptical friend. That is useful. A strategy where you can name the job of every condition is easier to debug than a strategy with fifteen rules where nobody remembers why the ninth one exists. Treat the cap as a design constraint, the way a page limit helps a writer, and the first draft of your rule set will get shorter and better.
Take inventory before you rank anything
Write down every rule you want, in plain words, before you open the builder. Do not filter. Include the ones you think are silly. A typical wish list for a four-leg NIFTY weekly-expiry strategy (a short strangle with two bought hedges, which is an iron condor) looks like this.
- Enter at a fixed time, say 09:20.
- Skip the day if India VIX is above a set level.
- Pick the short strikes by premium (nearest to Rs 40, for instance), not by distance.
- Buy hedge legs a fixed number of points further out.
- Stop-loss on each short leg at a set percentage of its entry price.
- Stop-loss on the whole position at a set rupee loss.
- Trail the combined stop once profit passes a threshold.
- Exit everything at a fixed time, say 15:15.
- Re-enter once if the first position is stopped out.
- Skip the day if the previous session moved more than a set percentage.
- Exit everything if spot moves a set percentage from the entry level.
- Allow one trade per day only That is twelve. Now sort them into four kinds, because the kind matters more than the rule.
Look at what this table already tells you. Five of the twelve are risk rules, and they are the ones fighting for the same few slots. Structure and schedule rules often do not need slots at all, which is the subject of a later section. Filters are the easiest to cut, as you will see.
The exit-first rule: rank by what a condition protects
Here is the ranking principle that does most of the work. Rank every condition by the size of the loss it prevents on your worst day, not by how often it triggers or how elegant it is. Short-premium strategies make small gains most days and give back large amounts on a few. The rules that cap the large losses are the ones that keep the account alive long enough for the small gains to add up.
That gives a priority order that surprises some people, because entry rules come last.
Priority 1: a hard stop on the whole position
Pick one rule that ends the trade no matter what else is going on. A combined stop-loss in rupees is the usual choice because it is one condition no matter how many legs you have. If you keep only one risk rule, keep this one. Without it, a strategy depends on every other rule working perfectly on the worst day, and that is when they tend not to.
Priority 2: a time exit
An exit at a fixed clock time does two jobs. It closes the position before the last chaotic stretch of expiry day, and it removes the need to decide anything at 15:10 when you are tired. It also ends the trade if nothing else did. Many builders treat this as a setting rather than a condition. If yours does, you get it free. If not, it still earns a slot.
Priority 3: profit protection
This is where the desk data is useful. EliteAlgo's study of 163 NIFTY and SENSEX weekly expiry sessions between January 2025 and July 2026 looked at a short ATM straddle entered at 09:20. On the 159 usable days, the median give-back from the intraday peak profit to the close was 42.8% of that peak. On 86 of the 159 days (54%) the position gave back more than 30% of its peak. On 48 days (30%) a position that had been in profit at some point finished the day as a loss.
Those figures describe a plain straddle with no protection, so they are not a forecast for your strategy. They do show how common it is for a winning position to melt. Some form of profit lock, whether a trailing stop on the combined P&L or a simple target, is the second-best use of a slot after the hard stop. If you can afford only one of the two, the target is cheaper to build and the trail is usually more effective, but test both before trusting either.
Priority 4: a per-leg rule, only if the legs behave differently
Stops on each short leg feel safe. They are also the most expensive rule in the list when the builder counts per leg, and they interact badly with a combined stop. Once one leg is stopped, the remaining leg can lose money quickly while the combined rule no longer describes your position. If the structure is hedged and the combined stop exists, the per-leg stop adds little and costs several slots. Drop it first when you are short of space, then check what changes.
Priority 5: the single best filter
You get at most one filter, and it has to pass the test in the next section.
What to drop first, and why
When you must cut, cut in this order: re-entry, then secondary filters, then per-leg stops, then fancy strike-selection logic. Here is the reasoning for each.
Re-entry goes first. A rule that opens a second position after a loss doubles your exposure on exactly the days that went wrong. It also needs several conditions of its own: a trigger, a time window and a size. If you want to test re-entry later, do it as a separate strategy, not as a clause inside the first one.
Secondary filters go second. Rule 10, skipping days after a big previous-session move, and rule 2, the VIX cut-off, are both filters. Keep the one with better evidence, drop the other. Judge a filter by how many days it changes. The desk data has a useful reference here. Across the 163 sessions, only 11 had a VIX reading above 20 at the 09:20 snapshot. That is about 1 day in 15 (6.7%). A rule that says "skip if VIX is above 20" would have changed your behaviour on 11 sessions out of 163. If you use that slot on it, you spend a precious condition on a rule that is idle for more than 93% of the sessions.
Compare that to a cut-off at 14. In the same study, 35 sessions fell in the 14-17 band, 24 in 17-20 and 11 above 20, so a cut-off at 14 would have skipped 70 of 163 sessions, which is 43%. That changes the strategy a lot. It might also be the right call, but now you are really designing a different strategy, one that trades only in calm conditions, and you should test it on its own merits. The point is that how often a filter fires should drive whether it deserves a slot. A rule that triggers on 7% of days has little effect on the results, good or bad. A rule that triggers on 43% of days is a second strategy hiding inside the first.
Afternoon-only rules are weak. The same study tracked the ATM straddle premium as a share of its 09:16 level. It fell from 100% to about 88.6% by 11:16, then sat in an 88% to 93% band until the close. The strike is fixed at the 09:20 level while spot keeps moving, so decay and re-pricing roughly cancel. A rule that waits for "more afternoon decay" has little support in this data.
Fancy strike selection goes last. Choosing strikes by a target premium instead of a fixed distance sounds sensible, because premiums move with volatility. But in many builders the choice is a setting made at strategy creation and not a counted condition. Check before you cut it. If it does count, a plain rule such as "sell the strike at a fixed distance from ATM" may be good enough, because the VIX band already changes the premium you collect. The desk data shows the ATM straddle premium as a share of spot rising from a mean of 0.38% when VIX is under 12 to 0.83% when VIX is over 20. Strikes picked by distance will collect less in calm markets and more in stressed ones. Whether that is a feature or a bug depends on your risk limits, not on the builder.
Move rules out of the builder altogether
Many conditions do not need a slot because you can move them elsewhere. Four places are worth a look.
Structure. A hedge leg is a position, not a rule. Rule 4 in the list above, buying hedges a fixed distance out, becomes part of the strategy's shape and uses no condition slots in most builders. The same goes for the number of lots. Some risk rules can also be built into the structure: a bought wing defines a maximum loss per lot without any stop condition at all. That is a strong reason to hedge a strategy when you are short on conditions.
Schedule. Entry time and exit time are often fields on the strategy, not conditions. A start time of 09:20 and an end time of 15:15 might cost nothing. Check, because it changes the maths.
The calendar. "One trade per day" and "only on expiry day" can be handled by choosing the day the strategy is active. You do not need a condition to stop a strategy from running on Wednesday if you only switch it on for Thursday.
You. A filter you apply by hand costs zero slots. If your rule is "do not run the strategy on the morning of a major scheduled event," then the cheapest and most reliable implementation is that you do not switch the strategy on that morning. This is not cheating. It is a deliberate human override, with a written rule, applied before the market opens and not after the loss. The risk is that you apply it unevenly, so write the rule down and keep a log of the days you used it.
Moving rules out of the builder is also the point where people start looking at what else is on the market. If the cap is the main thing slowing you down, it makes sense to compare builders on that one dimension. One published list of Zerodha Streak alternatives is a reasonable place to see what other tools offer, though condition limits change between versions, so check each vendor's current documentation and test with a dummy strategy before you decide anything.
A worked example: from twelve wishes to five slots
Take the twelve-rule wish list and assume a builder that counts one slot per risk or filter rule, counts a per-leg stop once per leg, and treats the entry time, exit time and strike selection as settings that cost nothing. This is an illustrative counting scheme, not a description of any product.
Twelve wishes came down to four slots with one spare. The strategy has not lost its risk control. It has a hard stop, a trail, a spot-move exit, a hedge structure, a time exit and one filter. What it has lost is re-entry, the second filter and the per-leg stops, and each of those has a stated reason.
Now decide what to do with the spare slot. A good use is a second protective rule, such as a profit target that closes the position when it reaches a set rupee gain. Another good use is to leave it empty and wait until a backtest shows a clear weakness. An empty slot is not wasted. It is room for the first thing your testing teaches you.
The drop-one test: prove each condition earns its place
Once you have a five-slot design, test it by removing one condition at a time and running the same backtest over the same period. You will end up with a table like this, filled in with your own numbers.
Read the table with three questions. Did the worst day get worse when the rule was removed? A risk rule that does not improve the worst day is not doing its job. Did the rule fire often enough to matter? If it fired on four days in a year, its effect on net P&L is mostly luck, and the number of days is the thing to look at, not the rupee figure. Did removing it change net P&L a lot but the worst day not at all? Then it is an optimisation rule, not a protection rule, and it ranks below the others.
Be careful with the result. A backtest is a record of what a rule would have done in the past data, with the costs and fill assumptions you gave it. Slippage, brokerage, taxes and the gap between a backtest fill and a live fill all matter. A rule that looks useful by a thin margin on a backtest often vanishes after costs. When two versions are close, choose the simpler one.
Signs you have outgrown a no-code builder
A cap on conditions is a normal limit of a product designed for fast setup. Hitting it once is not a reason to change tools. These are the signs that the cap has become a real problem.
Your best design needs more than seven or eight conditions, and each one passes the drop-one test. If every rule is earning its keep and you still have to cut, the tool is limiting you and not your thinking.
You keep splitting one idea into several strategies to get around the cap. Running two linked strategies that must act together, with nothing coordinating their stops, creates risk that neither strategy shows on its own screen.
Your key rule depends on something the builder cannot read. Examples include a rule that depends on your total exposure across several strategies, or on option-chain data the builder does not expose.
You are applying manual overrides every day. A few overrides are fine. If you are intervening most days, the strategy as built does not match the strategy as traded, and your backtest is describing something you do not run.
Your risk limit is at the account level, not the strategy level. A cap on total daily loss across strategies is a different kind of rule from a strategy stop, and many builders do not offer it.
If two or more of those are true, the useful question is no longer how to fit within five conditions. It is what you will move to, and how you will check that the new setup behaves the same as the old one. Write down the rules before you move, run the same days through both, and compare the fills and the exits. Switching tools in the middle of a drawdown is a bad time to find out that the new tool counts a stop differently.
There are three common routes. You can move to a more flexible builder, to a platform that accepts custom logic, or to your own code connected to a broker's API. Each trades convenience for control. If you take the code route, expect to spend time on order handling, reconciliation and logging, which the builder was doing for you without being asked. Do not underestimate that work. Whichever route you take, read SEBI's retail algo circulars on sebi.gov.in directly, because platform rules on orders and approvals have been changing.
Frequently Asked Questions
How many conditions does a good option-selling strategy need?
Fewer than most people think. A hedged short-premium strategy can work with a hard stop on the combined position, a time exit, one profit-protection rule and one filter. Extra conditions should each pass a drop-one test. If removing a rule does not change the worst day or the net result, it does not belong.
Should I use a stop-loss on each leg or on the whole position?
For a hedged multi-leg position, the combined stop is usually the better first choice because it describes the loss you actually care about and takes one slot. Per-leg stops can help when legs behave very differently, but they often act before the combined rule would and cost several slots. Test both on the same days and compare the worst day, not only the total.
Is re-entry after a stop-loss a good idea?
It is a separate strategy, not a feature. It adds exposure after a loss, and it needs its own trigger and size. If you want to test it, build it as its own version and compare it with the version that has no re-entry over the same dates.
Can I skip trading on high-VIX days?
You can, but check how many days the filter would change. In a study of 163 NIFTY and SENSEX expiry sessions, only 11 had a 09:20 VIX above 20, so that cut-off rarely fires. A cut-off in the low teens would skip a large share of days and is effectively a different strategy. Decide which you mean.
What if my broker or platform does not allow more than five conditions?
First check how it counts, since per-leg rules can use several slots. Then move structure, timing and calendar rules out of the condition list. If the strategy still needs more after that and every extra rule passes testing, the cap may mean it is time to look at a more flexible tool.
How do I know if a condition is worth keeping after costs?
Run the backtest with realistic brokerage, taxes and slippage, then run it again without the condition. If the gain from the rule is smaller than the uncertainty in your cost assumptions, treat it as unproven and leave it out.
Conclusion
A condition cap is a prompt to decide what matters. Rank rules by the loss they prevent on the worst day. Keep a hard stop, a time exit and a profit-protection rule before anything else. Count how often a filter actually fires, and be suspicious of rules that sit idle on most days or that change the character of the whole strategy. Move structure, schedule and calendar rules out of the builder, and use your own written override for the rest. Then prove each remaining condition by removing it and looking at the worst day.
If that process still leaves you with a design that needs more than the cap allows, you have found a real limit, and it is fine to move on. Just move deliberately, with your rules written down and a plan to compare old and new behaviour on the same days.
Algo trading carries a real risk of loss, including the loss of more than you expected on a bad day. EliteAlgo is analytical software and not an investment adviser. Nothing in this article is investment advice, a recommendation to trade, or a promise of any result. Test any rule set on paper and with small size before you rely on it.

Top comments (0)