Portfolio

Equity guard retrofitted to an index expert

An equity guard based on floating profit, staged position closing and an automatic resume on the next trading day.

MT5 Existing EA owner Pedram Rostami Index trader

Project specifications

Project specifications

Market
NAS100
TF
M5
Platform
MT5
Client type
Existing EA owner
Delivery window
6 weeks
Stack
MQL5, the client's code, index M1 data
Strategy
Equity guard on existing code
Modules
Drawdown limit + auto resume
Testing
Index crisis-day testing

Who this was for

Pedram Rostami

Role
Index trader
City
Tehran
Project reference
TBT-1408-28
Trade flow

The client's idea

Pedram Rostami works NAS100 on M5; the opening brief was: The index expert works well, but it has no guard on bad days.

Initial challenge

In volatile index stretches the expert opened many positions at once and intraday equity fell with no limit at all.

Solution

An equity guard based on floating profit, staged position closing and an automatic resume on the next trading day.

Why this design

The automatic resume was added so the client never has to restart the expert by hand. It matches how NAS100 is actually traded and can be tested against the data already available.

Safeguards and risk control

The risk layer sits outside the strategy logic, so a later change to the signal cannot bypass it.

Our next-step proposal

The next step is a monthly compliance report that proves the account rules were respected.

Portfolio

Measured results

These are the figures the test produced — not a promise about future performance.

  • 6.8 % Max drawdown in test
  • 1 day Recovery after drawdown
  • 3 Concurrent position cap
  • 1 Regressions caught

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

    Reading the client's risk rules and measuring how the account currently behaves on NAS100.

    Day 1–3

  2. Written specification

    Completed

    Turning the rules into numeric caps: risk per trade, daily loss and exposure ceiling.

    Day 4–10

  3. Implementation

    Completed

    Building a risk layer independent of the signal, with each cap testable on its own.

    Day 11–25

  4. Testing and validation

    Completed

    Testing the critical scenarios: fast drawdown, simultaneous positions and a dropped connection.

    Day 26–35

  5. Handover and support

    Completed

    Handover of the risk layer with a rules document and the emergency-stop path.

    Day 36–39