Project specifications
- Market
- XAUUSD
- TF
- M5
- Platform
- MT5
- Client type
- Professional trader
- Delivery window
- 6 weeks
- Stack
- MQL5, order and volume data, render profiling
- Strategy
- Order pressure drawn on the chart
- Modules
- Status bar + threshold alerts
- Testing
- Render-speed testing in busy data
Who this was for
Arman Kiani
- Role
- Gold trader
- City
- Tehran
- Project reference
- TBT-1408-31
The client's idea
Arman Kiani works XAUUSD on M5; the opening brief was: Show buy/sell pressure on the chart itself, not across half a dozen side windows.
Initial challenge
The client opened a separate window for every analytical question, and in busy periods the terminal slowed down and decisions got harder.
Solution
A single on-chart dashboard with an order-pressure bar, threshold alerts, and calculations bounded to the candles required so it stays fast.
Why this design
The calculation window was bounded from the start so adding another readout cannot slow it down. It matches how XAUUSD is actually traded and can be tested against the data already available.
Safeguards and risk control
The indicator only reads and never sends an order, and its load on the terminal was measured.
Our next-step proposal
The next step is an output the expert can consume, turning the signal into execution.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 90 ms Order round-trip time
- 99.7 % Runtime stability in test
- 3,200 Bars in the test set
- 8 Configurable inputs
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
CompletedUnderstanding the decision the trader must make faster and the data that decision needs.
Day 2–4
-
Written specification
CompletedDefining the chart elements, colours, alerts and behaviour across XAUUSD timeframes.
Day 5–12
-
Implementation
CompletedBuilding a light indicator with a bounded calculation window and no per-tick duplication.
Day 13–25
-
Testing and validation
CompletedMeasuring render cost on a busy chart and checking the maths against historical data.
Day 26–33
-
Handover and support
CompletedHandover of the file, a guide to pairing it with a strategy and the parameter notes.
Day 34–37