What information does a developer need to code a trading strategy?
To implement a strategy as software, a developer needs every decision the strategy makes, written as a precise rule. The checklist below is what a well-prepared brief contains. Gaps here become assumptions in the code, and assumptions are where live behaviour surprises you.
1. Universe and instruments
- Exact instruments or symbols, and the exchange/segment (for example NSE cash, NSE F&O, MCX).
- For derivatives: which expiry, how to roll, how strikes are selected.
- Whether the list is fixed or generated by a screen (and if so, the screen's rules).
2. Data and timeframe
- Primary timeframe (tick, 1-minute, 5-minute, daily…) and any secondary timeframes.
- How much history each indicator needs before it is valid.
- Data source, if you have a preference, and how to treat missing bars or holidays.
3. Entry rules
- The full set of conditions that open a position, each with a value, comparison and timeframe.
- Whether entries act on bar close or intrabar.
- Order type: market, limit (with what offset), stop.
- What happens if multiple instruments signal at once.
4. Exit rules
- Profit target logic (fixed, ATR-based, indicator-based, trailing).
- Stop-loss logic and how/when it moves.
- Time-based exit (for example square off at 15:15).
- Signal-based exit (an opposite or neutralising condition).
- Priority if two exits trigger on the same bar.
5. Position sizing
- The exact formula: fixed quantity, fixed capital, percent-risk, volatility-scaled.
- Rounding to lot size, and minimum/maximum size.
- How margin or available capital constrains size.
6. Re-entry and scaling
- Whether you can re-enter the same instrument the same day, and any cooldown.
- Whether you add to a winning position (pyramiding) and the rules for it.
- Maximum concurrent positions overall and per instrument.
7. Trading hours and calendar
- Allowed entry window and any "no new trades after" time.
- Behaviour around the open and close, and on expiry days.
- Days or events to skip entirely, if any.
8. Risk limits
- Maximum daily loss and what happens when it is hit (flatten? stop new entries?).
- Maximum drawdown behaviour, if you want a rule for it.
- Maximum trades per day; maximum exposure.
- Kill-switch conditions — when the system should stop and alert a human.
9. Execution and environment
- Broker and whether its API permits automated order placement for your account type.
- How credentials/API keys will be provided and stored.
- Where it should run: your machine, a server you control, or delivered as code.
- What monitoring, alerting and reporting you need.
10. Acceptance criteria
- How you will verify correctness (historical replay you can inspect; live test with small size).
- What counts as "matches the specification".
Shortcut
The TimeXtrade enquiry form is structured around this checklist. You do not need every field filled to start a conversation — but the more of it you can answer, the faster the scope becomes clear.
Note
Providing complete information helps the software match your intent. It does not make the strategy profitable and does not remove risk. See the Risk & Regulatory Disclosure.