Portfolio

London session breakout expert

A session range breakout with a spread filter, an allowed slippage ceiling, a controlled retry when an order is rejected, and a pause during high-impact news.

MT5 Professional trader Saeed Moghaddam Cable and index trader

Project specifications

Project specifications

Market
GBPUSD
TF
M15
Platform
MT5
Client type
Professional trader
Delivery window
8 weeks
Stack
MQL5, M1 data for the range build, an on-chart status panel
Strategy
Range breakout + spread filter
Modules
Execution filter + retry
Testing
Three-year backtest

Who this was for

Saeed Moghaddam

Role
Cable and index trader
City
Karaj
Project reference
TBT-1402-05
Trade flow

The client's idea

Saeed Moghaddam works GBPUSD on M15; the opening brief was: Take the opening range breakout automatically — but never during a wide spread.

Initial challenge

The first minutes of the London session are the most volatile of the day; wide spreads and heavy slippage turned manual entries into instant losses.

Solution

A session range breakout with a spread filter, an allowed slippage ceiling, a controlled retry when an order is rejected, and a pause during high-impact news.

Why this design

The spread filter runs before the entry logic, because in this session execution cost matters more than the signal. It matches how GBPUSD 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.6 pip Spread ceiling enforced
  • 0.6 pip Average execution slippage
  • 890 Trades reviewed
  • 15 min Pause around news releases

Portfolio

How the delivery ran

Every project moves through these five phases, with the window for each agreed in the specification.

  1. Discovery and problem framing

    Completed

    Learning how the client actually works GBPUSD, separating decision rules from execution habits.

    Day 2–4

  2. Written specification

    Completed

    Agreeing the modular architecture and the parameters that must stay extensible.

    Day 5–13

  3. Implementation

    Completed

    Building the expert with independent signal, risk, execution and reporting modules. A small status panel was added so the spread filter is visible on the chart.

    Day 14–35

  4. Testing and validation

    Completed

    Testing each module alone, then the combination on M15 data, reviewing every output.

    Day 36–51

  5. Handover and support

    Completed

    Handover with a module map and a walkthrough of the inputs.

    Day 52–55