Project specifications
- Market
- EURUSD
- TF
- H4
- Platform
- MT5
- Client type
- Team / company
- Delivery window
- 9 weeks
- Stack
- MQL5, six years of H4 data, monthly reporting
- Strategy
- Higher-timeframe retracement
- Modules
- Trade scheduling + position cap
- Testing
- Six-year backtest
Who this was for
Zaringasht Investment
- Role
- Investment unit
- City
- Isfahan
- Project reference
- TBT-1404-12
The client's idea
Zaringasht Investment works EURUSD on H4; the opening brief was: Write down our swing style as rules — faster than reading charts ourselves every night.
Initial challenge
Every night the team drew levels by hand and entries differed between members; the missing shared rule caused recurring arguments.
Solution
A retracement rule with calculated levels, orders scheduled for the next session, and a fixed cap on concurrent positions.
Why this design
The levels are calculated rather than drawn, which ends the debate about where the line goes. It matches how EURUSD is actually traded and can be tested against the data already available.
Safeguards and risk control
Each module can be switched off on its own, and the exposure cap and daily stop are part of the expert rather than a later add-on.
Our next-step proposal
The proposed next step is a reporting module wired into the trade journal.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 9,000 Bars in the test set
- 2 Concurrent position cap
- 1,050 Trades reviewed
- 12.4 % Max drawdown in test
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
CompletedLearning how the client actually works EURUSD, separating decision rules from execution habits.
Day 2–6
-
Written specification
CompletedAgreeing the modular architecture and the parameters that must stay extensible.
Day 7–17
-
Implementation
CompletedBuilding the expert with independent signal, risk, execution and reporting modules.
Day 18–41
-
Testing and validation
CompletedTesting each module alone, then the combination on H4 data, reviewing every output.
Day 42–55
-
Handover and support
CompletedHandover with a module map and a walkthrough of the inputs.
Day 56–59