Project specifications
- Market
- USDJPY
- TF
- M30
- Platform
- MT5
- Client type
- Professional trader
- Delivery window
- 7 weeks
- Stack
- MQL5, yen-pair M1 data, holiday calendar
- Strategy
- Session trend + timed exit
- Modules
- Session calendar + holiday close
- Testing
- Three-year test
Who this was for
Bahman Kashani
- Role
- Yen-pair trader
- City
- Rasht
- Project reference
- TBT-1404-14
The client's idea
Bahman Kashani works USDJPY on M30; the opening brief was: Trade only the Tokyo session, and never hold anything over the weekend.
Initial challenge
Yen positions were carried into the weekend, and the Sunday gap undid the week's work.
Solution
A Tokyo-only rule, a timed exit before the session ends, and a forced close ahead of market holidays.
Why this design
The timed exit is part of the strategy rather than a Friday-afternoon decision. It matches how USDJPY 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.
- 1 Sessions controlled
- 540 Trades reviewed
- 8.7 % Max drawdown in test
- 3 years Test window
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 USDJPY, separating decision rules from execution habits.
Day 1–3
-
Written specification
CompletedAgreeing the modular architecture and the parameters that must stay extensible.
Day 4–10
-
Implementation
CompletedBuilding the expert with independent signal, risk, execution and reporting modules.
Day 11–27
-
Testing and validation
CompletedTesting each module alone, then the combination on M30 data, reviewing every output.
Day 28–39
-
Handover and support
CompletedHandover with a module map and a walkthrough of the inputs.
Day 40–43