Your strategy’s logic was never the problem. Latency, slippage, and costs are the gap between a beautiful backtest and a losing live account — and the gap is measurable.
Assume your edge is real. Assume it survives out-of-sample testing, beats its baselines, and holds up across market regimes. It can still lose money live. The reason is not mysterious, and it is not your logic. It is execution friction — the gap between the price your backtest books and the price the market actually gives you.
Latency becomes slippage becomes losses
A backtest books the decision price as the fill price. Live markets deliver neither instant fills nor requested prices. Latency is the delay between signal and fill; slippage is the worse price you get because the market moved during that delay. They are one chain, not two problems: cut the delay, and most of the slippage goes with it.
The damage is invisible per trade and only shows up in aggregate — which is why it surprises people. Take a system backtesting at a small average profit per trade. Add routine retail slippage per round trip and the edge shrinks by more than half. Push slippage higher in a volatile session and expectancy turns negative. Across a year of trades, ordinary slippage alone can erase a year’s expected profit. The strategy did not break. The market charged it rent the backtest forgot to include.
The full friction list
- Slippage and latency, worst during news and high volatility — exactly when backtests stay silent.
- Brokerage, taxes, and exchange charges, per trade, every trade.
- Spread and market impact, which grow with size and thin liquidity.
- Partial fills and missed trades, which quietly change the strategy you thought you were running.
- Outages and disconnections, which turn an automated strategy into an unmonitored bet while positions are live.
How to close the gap before risking capital
- Model friction explicitly. Re-run the backtest with realistic slippage and full costs. If the edge survives, it is an edge worth discussing. If it does not, you have learned something cheaply.
- Measure expectancy net of everything. Gross profit per trade is a vanity metric. Net expectancy per trade, after all friction, is the number that decides whether to trade.
- Forward-test on paper first. Live data flow exposes latency, fill inconsistency, and data quirks that no historical simulation contains. Backtesting tells you if a strategy could have worked; forward testing tells you if it actually functions.
- Watch the backtest-live divergence. A strategy whose live results shrink steadily against its backtest, with no explanation beyond “market conditions,” is usually confessing over-optimisation after the fact.
The sequence that works
Backtest to screen. Validate to filter — recompute, baselines, walk-forward folds, leakage, trial-count correction. Forward-test to confirm function. Then, and only then, trade small. Each stage exists to kill a different kind of false confidence, and skipping one means paying for its lesson with capital instead of time.
The validation stage is where BuildIT Index sits, and where the seven checks apply. It does not test execution, pick models, or promise a future return. It answers a narrower question that has to be answered first: does the record in the file support the number on the page?
If the answer is no, the live account was never the place to find out.
This article is educational, not financial advice. Past backtest results do not predict future returns.
