Skip to main content

When is a trading system ready to go live? (pre-launch checklist)

Verify your logic, run clean backtests in Profectus, avoid over-optimisation, forward test on demo for 4 to 6 weeks, then go live small.

When is a trading system “ready” for live trading?

Many trading systems “fail” not because the idea is bad, but because builders skip steps: they trust a backtest too early, over-optimize settings, or never verify what the trading system is actually doing candle-by-candle.

This article gives you a practical workflow to validate a strategy from first build to live execution: find out fast in Profectus, confirm on your broker's feed, then go live small.

Disclaimer

This is educational content only and not financial or investment advice.

Step 1 — Start with a strategy (don’t start from a blank canvas)

If you don’t have a strategy idea yet, start with proven examples and adapt from there:

  • Trading System Library: prebuilt strategies, price action patterns, management templates, and portfolios
    ​(Link your library section here)

  • Build From Scratch: guided fundamentals and “core logic” articles
    ​(Link your build-from-scratch section here)

Step 2 — Verify the logic with SEE CHART (before trusting any backtest number)

Before you care about performance, confirm the trading system behaves correctly.

Run a backtest in Profectus, then open SEE CHART to confirm the behaviour — every trade is drawn on the candlestick chart (entries marked, winners green, losers red, up to 200 trades), so you can check:

  • Are entries triggered where you expect?

  • Are SL/TP levels placed correctly?

  • Do time/session filters behave correctly?

  • Do “one trade per day/session” rules work as intended?

  • Are trades blocked by a condition you forgot about?

Where to check when something looks wrong

Most “my trading system is not trading” issues are explained by checking the right place:

  • Backtests: open VIEW for the full Backtest Report, or SEE CHART to see every trade candle-by-candle

  • Live trading: Terminal Toolbox → Journal in MT5

Pro move: Keep the Backtests panel open while you review a run, so you can compare it against the previous one.

Step 3 — Backtest with realistic assumptions

Backtests are screening tools. They tell you if a strategy is worth deeper validation.

Minimum standard:

  • Test multiple years (not a cherry-picked window)

  • Include realistic spread/commission assumptions (and expect slippage in live)

  • Ensure you have enough trades to judge anything (more trades = more signal)

If your trading system only makes a handful of trades, it may look “amazing” by accident.

Backtests run on 1-minute historical bar data, free for every user. Tick-level backtesting is coming soon.

Step 4 — Avoid over-optimization (this is where most trading systems die)

Over-optimization creates trading systems that look perfect in the past and collapse in the future.

Rules to keep your trading system robust:

  • Optimize max 1–2 inputs at a time (ideally 1)

  • Prefer parameter ranges that work over one perfect value

  • Validate on unseen data (out-of-sample), not only the period you optimized on — run a backtest in Profectus after each change and compare the runs in the Backtests panel

Step 5 — Run quick robustness checks (Pareto tests)

Before forward testing, do a few “cheap stress tests”:

  • Out-of-sample check: test on a different period than you optimized on

  • Sensitivity check: small parameter tweaks should not kill performance

  • Cost check: increase spread assumptions; does it still survive?

Run each variation as its own backtest in Profectus and compare Net Profit %, PF and Win Rate side by side in the Backtests panel. If the trading system breaks easily, it’s fragile, not robust.

Step 6 — Forward test on a demo account (same broker conditions)

Forward testing answers a different question than backtesting:

Does the strategy hold up in real-time execution, with real spreads, market behavior, and platform quirks?

How to do it:

  • Run demo with the broker/account type you plan to use live

  • Don’t tweak settings daily (that ruins validation)

  • Track: trade frequency, behavior, execution, max drawdown

Minimum timeframe:
​4–6 weeks (longer is better), or enough trades to be meaningful for your strategy frequency.

Step 7 — Go live small (this is still forward testing)

The first live phase is for execution validation, not “getting rich.”

Start small and confirm:

  • Execution/slippage reality

  • Platform reliability (terminal uptime, VPS, reconnects)

  • Your operational discipline (no panic edits)

Scale only after stable live behavior over time.

When is a trading system “ready” for live?

Use this checklist. If any item is “no,” you’re not ready yet.

Live-ready checklist

  • ✅ Logic verified candle-by-candle using SEE CHART in Profectus

  • ✅ Backtest works across multiple market phases (not one lucky period)

  • ✅ No heavy optimization (1–2 inputs max)

  • ✅ Robustness checks passed (cost, sensitivity, out-of-sample)

  • ✅ Demo forward test ran 4–6+ weeks without breaking risk limits

  • ✅ Live rollout starts small with monitoring and clear risk limits

In short: find out fast in Profectus, confirm on your broker’s feed, then go live small.

Common reason trading systems “don’t trade” (quick reminder)

If your trading system trades on one account but not another, the MT5 Journal often shows why:

  • Not enough balance / margin

  • Leverage limitations

  • Trading disabled (Algo Trading off)

  • Symbol not tradable / market closed

  • Broker restrictions (min lot size, stop levels, etc.)

If you see this behavior, go straight to the Journal first.

Related Articles
Did this answer your question?