When is a trading strategy ready to go live?

By John, builder of Wise Apple · Updated August 27, 2026

The backtest is green. Paper trading has been fine for six weeks. You've posted the equity curve and asked strangers whether you're ready, which is a sign you already know the honest answer is "I can't tell."

"Am I ready to go live?" is one of the most-upvoted questions on r/algotrading every year, and the replies split between "send it" and "you'll lose everything", neither of which is evidence. Readiness is not a feeling and not a vote. It is a gate: a short list of things that must be true, each of which a specific test can settle. This page is that list, in order, with what each stage can and cannot prove — because most of the pain at the paper-to-live boundary comes from asking one stage to prove something only the next one can.

It ends with the one thing almost nobody writes down before going live, and which decides whether a losing month is a data point or a disaster: the kill rule.

Three stages, three different questions

A backtest, a paper account and a small live stake each answer exactly one question. Mixing them up is where the trouble starts.

What the backtest has to have proved

Before paper trading is worth your time, the backtest needs to have survived the tests that would have said no. Not "it looks good" — survived. That means the full loop: next-bar fills, realistic costs, a time-ordered split with an embargo gap, walk-forward windows, enough trades per regime, and a sealed holdout checked once. A backtest that skipped any of those has not earned a paper account, let alone a real one.

What paper trading actually proves

Less than people think. A paper fill is a lie told politely: you get the price you asked for, in the size you asked for, with no queue and no impact. What paper trading genuinely tests is everything around the edge — the data feed, the signal logic running on live bars instead of a downloaded file, order construction, logging, what happens when the connection drops at 9:31. That is worth testing. It is not evidence about the edge, and six clean weeks of it are not six weeks of validation.

What a small live stake proves

Two things nothing else can. First, real fills: where you actually got in, how often you did not get filled at all, what the spread did at your entry time. Second, you. Whether you override the system at the third loss, whether you "just check" it during a drawdown, whether you add size after a good week. The stake should be small enough that these lessons are cheap, because they are the lessons, not the profit.

The seven gates, in order

Go through these in sequence. A no at any gate means the answer to "am I ready?" is no, and the fix is at that gate, not further down.

1. The sealed holdout passed, once. A final stretch of history the rule never touched during development, checked a single time. If you checked it, tweaked, and checked again, it is not a holdout any more. The out-of-sample guide explains why one look is the limit.
2. The cost sweep passed. Multiply every cost by 1.5 and by 2. If the edge vanishes at 1.5×, the edge was the cost model, and live costs will find that out for you. See realistic backtest costs.
3. Enough trades per regime. Not a total — a count in rising, falling and sideways markets, and in high and low volatility. An empty bucket is an untested condition, and the untested condition is usually the one that arrives first.
4. Walk-forward holds. The out-of-sample windows are individually positive more often than not, and no single window carries the result.
5. A written kill rule exists. See below. If it is not written, you are not ready, whatever the numbers say.
6. An alert-only rehearsal has run. The system emits its signals live and you act on none of them, for long enough to see it behave on bars it has never seen and to catch the plumbing mistakes before they have a price.
7. The first live size is the smallest size that still produces real fills. Not the size the Kelly formula suggests. The smallest one.

How long is long enough?

A recurring question on r/algotrading is "how long should I forward test before going live?", and the honest answer is that it is not measured in weeks. It is measured in two counts.

Trades. A forward test with eleven trades has told you almost nothing about the edge, however many calendar weeks it took. The sample-size arithmetic does not change because the trades are recent. A daily-bar strategy that trades twice a month needs a year of forward testing to produce a sample that would still be too small to prove anything — which is why the forward test's job is plumbing and behaviour, not proof.

Regimes. A forward test run entirely inside one quiet uptrend has tested one condition. If the rehearsal period happened to include a volatility spike or a trend reversal, you learned more in that fortnight than in the calm quarter before it. You cannot schedule regimes. You can refuse to go live until the rehearsal has met at least one stretch you would not have chosen.

The kill rule: decide before, not during

Here is the gate almost everyone skips, and the one that would have saved most of the "where did I go wrong" posts. Before the first live trade, write down what evidence would take the strategy off. Not a feeling — evidence.

The backtest gives you the material. It contains a worst drawdown, a longest losing streak, and a longest stretch without a new equity high. Those numbers describe what the strategy did while it was working. A reasonable kill rule says: if live results go meaningfully beyond them — a drawdown well past the worst seen, a losing streak longer than any in the history — the strategy is not behaving like the one you tested, and it comes off until you understand why.

• Drawdown: off if live drawdown exceeds the backtest's worst by a margin you chose in advance. Many people use something like one and a half to two times, on the grounds that the backtest's worst is a sample, not a limit.
• Streak: off if the losing streak exceeds the longest in the backtest by more than a trade or two.
• Time: off for review if the strategy goes longer without a new equity high than it ever did in the history.
• Behaviour: off if it does anything the backtest never modelled — a fill size it should not have taken, a trade at a time it should not have been awake.

The point of writing it first is that during a drawdown you are the worst-placed person to decide whether the drawdown is normal. The rule decides. And when it fires, the guide to why strategies stop working is the diagnostic: variance, overfitting that took a while to show, crowding, cost creep, or a genuine regime change.

What goes wrong at the paper-to-live boundary

Ask people who have crossed it what their bot did that they did not expect, and the same answers come back. None is about the signal.

• Partial fills. The backtest filled the whole order at one price. Live, half filled and the rest chased or never came.
• Missed fills. A limit order that the backtest counted as filled because price touched it, which live sat in the queue and watched the move leave without it.
• Latency. The bar closed, the signal fired, the order arrived a few seconds later at a different price. On daily bars this is noise; on one-minute bars it can be the whole edge.
• Things the backtest never modelled. A halted stock, a weekend crypto gap, a data feed that delivered a bar twice, a broker rejecting an odd lot.
• You. The most-reported failure is the human overriding the system — skipping the signal after three losses, adding size after three wins, or turning it off during exactly the drawdown it was built to survive.

The guide to why backtests fail live ranks these by damage and gives a diagnostic order that starts by reconciling trades, not by retraining the model. Most live gaps are a fill or cost problem, and the fix is in the backtest's assumptions.

Sizing the first live version

The first live size has one job: to produce real fills and real behaviour at a cost you will not notice. It is not the size the edge "deserves". A useful test is to take the backtest's worst drawdown, double it, apply it to the proposed size, and ask whether that loss would change anything about your week. If yes, halve the size and ask again. The position-sizing guide covers why doubling the backtest's worst is the right instinct, and why fractional Kelly exists.

Scale up only on evidence: more trades, more conditions, fills reconciling with the backtest's assumptions. Never on a good week.

How the alert-only rehearsal works in Wise Apple

Wise Apple is built around gate six. A rule you have tested in PowerCore Studio — with the holdout, the embargo gap and walk-forward windows on by default — can be handed to the Alert Node, which runs on your own machine and sends each new signal to Telegram, Discord, email, SMS or a webhook on 1H, 4H, 1D or 1W bars. Nothing is traded. You see the strategy behave on bars it has never met, reconcile what it would have done against what the market actually offered, and decide, trade by trade, whether to act. It tests one instrument at a time and is early software from one builder; it has no broker connection by design, so the step from rehearsal to real money is one you take deliberately, somewhere else, at the size you chose.