Project specifications
- Market
- US30 / NAS100
- TF
- M15
- Platform
- MT5
- Client type
- Prop trader
- Delivery window
- 7 weeks
- Stack
- MQL5, M5 and M15 data, a basket panel
- Strategy
- Index basket + break-even moves
- Modules
- Staged exit + basket trailing
- Testing
- Two-year test across both indices
Who this was for
Amirhossein Taheri
- Role
- Prop index trader
- City
- Mashhad
- Project reference
- TBT-1403-09
The client's idea
Amirhossein Taheri works US30 / NAS100 on M15; the opening brief was: Manage the open US30 and NAS100 positions as one basket, not one by one.
Initial challenge
The two indices are highly correlated; managing positions separately left both open through every reversal.
Solution
Basket management with a break-even move at a fixed threshold, staged profit exits and basket trailing, consistent with prop account rules.
Why this design
The break-even move is calculated from the basket's profit rather than a single position's. It matches how US30 / NAS100 is actually traded and can be tested against the data already available.
Safeguards and risk control
Every change starts from a saved backup, and the previous behaviour is kept as the test reference.
Our next-step proposal
The next step is a full technical review of the expert and clearing the old code's debts.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 4 Concurrent position cap
- 620 Trades reviewed
- 8.1 % Max drawdown in test
- 2 Symbols covered
Portfolio
How the delivery ran
Every project moves through these five phases, with the window for each agreed in the specification.
-
Discovery and problem framing
CompletedAuditing the existing code, finding the cause of the fault and fixing the change scope on US30 / NAS100.
Day 1–3
-
Written specification
CompletedA written list of approved changes — and of what stays untouched at this stage.
Day 4–11
-
Implementation
CompletedApplying small, reviewable changes instead of needlessly rewriting healthy parts.
Day 12–29
-
Testing and validation
CompletedRegression testing the old behaviour and targeted testing of what had to change.
Day 30–41
-
Handover and support
CompletedHandover of the fixed build with a change report and the reason behind each change.
Day 42–45