Free client preparation guide
The rules, examples and platform assumptions an MQL5 developer needs before turning a trading idea into a testable Expert Advisor.
Define the exact indicators, comparisons, bar timing and conditions that must all be true.
State the spread, session, news, exposure or cooldown rules that block an otherwise valid entry.
Specify stop loss, take profit, time exit, opposite signal, break-even and trailing behaviour independently.
Choose fixed lots or an exact risk formula, including minimum, maximum and rounding rules.
Define maximum positions, symbols, directions, daily trades and whether hedging is allowed.
Provide symbol, timeframe, broker, account mode, terminal build and any required custom indicators.
Choose completed-bar or intrabar evaluation and define how duplicate signals are prevented.
List which values must remain configurable and their safe defaults and ranges.
Provide at least two expected trades and one expected no-trade case with dates or screenshots.
Separate the first version from future strategy changes, optimization or additional dashboards.
No. A short rules list and representative chart examples are enough for an initial feasibility check. Unresolved decisions should be identified before the fixed build scope is agreed.
No. Data feeds, bar construction, execution, spread and platform timing can differ. Acceptance should use agreed behavioural examples and documented tolerances.
No. A specification makes software behaviour testable; it does not validate the trading edge or guarantee future results.
Ready for a feasibility check?