The cheapest failed prop challenge is the one you decide not to buy after a rules replay. Historical replay cannot promise a pass. It can answer a narrower, financially useful question: under one exact program, phase, account size, rule version, account, and evidence window, where would your recorded path breach, pass, stall, or become unevaluable?
This guide keeps FTMO Challenge: 1-Step and FTMO Challenge: 2-Step separate at the same global 100K first-evaluation scope. The current 1-Step and 2-Step facts are shown above; no checkout amount is copied into the evergreen article. The savings method then works with a symbol, P, meaning the verified checkout price of the exact selected program at purchase time.
Disclosure: Trader's Second Brain is our product; FTMO is independent. TSB can replay closed-trade evidence against a reviewed rule snapshot, but FTMO's official terms and Account MetriX remain controlling. Confirm the exact program and current agreement again before paying.
Quick answer: select the exact program first, replay one owned account, inspect the first blocker and all limitations, then buy only if the evidence is complete enough for the rules that matter. Savings are avoided checkout outlay, not guaranteed profit: avoided paid attempts × current exact-program price.
The Cost of “Just Trying” a Challenge
A universal “average trader spends X” number is not defensible without a representative purchase-and-outcome dataset. Public pass-rate snippets also do not reveal how many buyers retry, switch programs, receive a fee refund, or stop. Use your own planned purchase sequence instead.
Define:
- P: current checkout price for the exact region, program, account size, and phase path;
- A: number of paid attempts actually purchased;
- R: fees actually refunded—not refunds merely hoped for;
- X: separately documented extras such as payment conversion or optional services, if applicable.
Gross checkout outlay = A × P + X. Net retained fee cost = A × P + X − R. Keep both figures. Gross outlay describes cash committed along the path; net cost depends on refund eligibility and whether the refund event really happened.
FTMO's official fee FAQ says its Challenge fees are one-time rather than recurring. It also distinguishes the products: the 1-Step entry fee is not refunded, while the 2-Step fee may be returned with the first Reward withdrawal. Do not subtract a possible 2-Step refund at purchase time.
The Same Purchase Decision With a Rules Replay
Constructed planning example—not a customer outcome or pass-rate claim. Both paths use the same exact program and current price P. The first scenario buys four attempts. The second runs three local evidence replays, changes the plan only through separately tested rules, and then buys one attempt.
| Scenario | Paid attempts | Local replays | Gross checkout outlay |
|---|---|---|---|
| Buy-first scenario | 4 | 0 | 4P |
| Replay-first scenario | 1 | 3 | 1P |
| Scenario difference | 3 fewer | 3 more | 3P avoided |
The arithmetic is exact; the behavioral assumption is not. Replay does not prove that the trader would otherwise have bought four attempts, that a rule change will hold under evaluation pressure, or that the remaining paid attempt will pass. Call 3P an avoided-outlay scenario only when the counterfactual purchase plan was written before the replay and the purchases were genuinely cancelled.
Select the Exact FTMO Program Before Doing the Math
“An FTMO challenge” is not one rule set. FTMO's official comparison explains that 1-Step has one evaluation phase while 2-Step has Challenge plus Verification. Current targets, loss rules, minimum-day requirements, Best Day coverage, platforms, and price must be resolved for the exact product and stage.
The comparison above holds region, $100K account size and first evaluation stage constant so the rows are comparable. Use those current values, then confirm the selected program in FTMO checkout and Account MetriX before paying.
The official Trading Objectives remain the final reference. Record the source URL, verified date, program, phase, account size, and rule snapshot used by the replay. A result from 1-Step cannot be relabeled as evidence for 2-Step, and phase-one evidence cannot silently stand in for Verification.
Use Free Trial and History Replay for Different Jobs
FTMO describes its Free Trial as an abridged environment for becoming familiar with the platform and assessing an approach. Its Free Trial objectives are adjusted, so passing it is not the same event as passing the paid product and FTMO explicitly says it does not guarantee success.
A historical replay answers a different question: how one recorded trade path interacts with the selected rule snapshot. The Free Trial samples current execution under a simplified environment; replay stress-tests recorded history and exposes exact blocker dates. Use both when useful, but do not add their results into a fictional pass probability.
The Evidence Contract Behind a Replay
A defensible replay names:
- one owned Journal account—mixed accounts are rejected rather than blended;
- exact firm, program, phase, account size, region, currency, and rule-version checksum;
- date range, account timezone, included trades, excluded trades, exclusion reasons, and evidence cutoff;
- stable trade IDs plus an input fingerprint so the result can be reproduced;
- currency-conversion state and any rows excluded for missing conversion evidence;
- the rule checks evaluated, first blocker, unsatisfied objectives, and limitations.
TSB has processed 600K+ imported trades cumulatively. That scale is useful product context, but it is not the denominator for your replay. A personal result must still say, for example, that one account contributed a specific included count over a specific period and that a separate number was excluded.
The FTMO replay guide shows how pass, breach, stall, and not-evaluable states differ. Do not collapse them into a green/red badge with no evidence trace.
What the Replay Can Reveal Before Checkout
First historical blocker
If the evaluated daily series breaches a supported rule, the result can identify the rule and date that blocked the path. Open the underlying trades. A daily-loss breach, maximum-loss breach, unmet target, minimum-day objective, and Best Day condition require different decisions.
Rule pressure, not only terminal failure
A path may remain inside a limit while operating too close to it for the trader's intended buffer. Record peak usage and the worst day under the exact rule model. The firm limit is a contract boundary, not a recommended personal stop.
Program fit
The same trade history can interact differently with 1-Step and 2-Step because their objectives differ. That does not make one product universally better. It tells you which exact rule path was more compatible with the recorded sequence under the selected account size and phase.
Missing evidence
A useful replay refuses confidence when the input cannot prove a rule. Missing conversion coverage, an ambiguous account scope, an unavailable phase, or too little daily evidence is not a pass. It is a data task or a reason to wait.
Fix the First Blocker Without Overfitting the History
Do not edit the historical trades until they pass. Preserve the baseline, then define one prospective change: a risk cap, session stop, setup gate, or pause rule. The change must be valid for the trading method, not merely tuned to erase the worst historical day.
Test the rule on a later or held-out window. Report starting count, eligible count, exclusions, currency basis, rule version, and outcome. If the same dates are used to discover and validate the fix, label the result exploratory.
The prop-rule tracker guide explains why target, daily/max loss, minimum days, and consistency-style objectives must stay attached to the exact saved program instead of becoming generic journal settings.
Calculate Savings Without Inventing an Average
Use one of three labels:
| Label | Formula | When it is valid |
|---|---|---|
| Planned exposure | planned attempts × P | Before replay; no savings claim yet |
| Avoided gross outlay | cancelled planned attempts × P | The purchase plan existed and was actually cancelled |
| Net retained fee cost | paid attempts × P + X − refunds received | After actual payments and refunds are documented |
Do not count TSB access, a spreadsheet, or time as “free” unless it truly added no cost for this decision. If you compare tools, use the price you can actually buy today and the same time horizon. Do not claim that the first prevented attempt “pays for” anything unless the avoided purchase is documented and greater than the tool cost under the selected plan.
Four Mistakes That Create Fake Savings
1. Replaying the wrong program
A generic FTMO label, stale rule screenshot, wrong phase, or different account size invalidates the cost decision. Resolve the exact program first.
2. Cherry-picking the best window
A window selected after seeing results measures selection bias. Freeze the primary period, then examine additional non-overlapping periods as separate evidence.
3. Treating a closed-trade pass as intraday proof
If unrealized equity or an intraday event matters, a daily closed-trade path may be insufficient. Keep the pass-blocking limitation visible.
4. Counting hypothetical attempts as saved cash
“The average trader needs four attempts” cannot establish your counterfactual. Record your own intended sequence before replay, then count only purchases you genuinely did not make.
Pre-Challenge Replay Checklist
- Choose 1-Step or 2-Step, region, 100K scope or another exact size, and first evaluation phase.
- Check the exact program row above, then open the official objectives and fee/refund sources.
- Write the planned purchase sequence and current exact-program price P.
- Select one owned account and freeze the evidence window.
- Run the replay; reconcile included and excluded trades and conversion coverage.
- Inspect the first blocker, per-rule checks, unsatisfied objectives, and limitations.
- If a rule fails, preserve the baseline and test one prospective correction on later evidence.
- If a rule is not evaluable, obtain the missing evidence or use the firm's environment; do not mark it passed.
- Use FTMO Free Trial when current-platform practice adds value, while remembering its adjusted objectives.
- Buy only after the evidence supports the decision; record actual payments, refunds, and cancelled attempts separately.
Replay the exact program before checkout
Choose the saved FTMO program, phase, size, and Journal account. Review the evidence trace and every limitation before treating the result as a buy signal.
Replay FTMO rules →Who Should Wait Instead of Buying
- No exact program selected: the rule and price scope is still ambiguous.
- Mixed accounts or currencies: scope or conversion evidence cannot be reconciled.
- Pass-blocking intraday limitation: the available history cannot prove the relevant equity rule.
- No strategy contract: replay can find a rule interaction but cannot manufacture an edge.
- Repeated historical pass, repeated paid failure: the gap may be execution under evaluation conditions; buying again without a different intervention repeats the same unsupported bet.
- Rule-source conflict: the official terms and your saved rule version disagree; pause until you know which rules govern the account.
If an attempt already failed, the post-failure analysis separates rule breach, strategy mismatch, missing evidence, and execution drift before another purchase.
Methodology Note
- Price check: P is the checkout price of the exact program when you make the decision. Save that cart instead of copying an old amount.
- Scenario class: 4P versus 1P is a constructed purchase-path example, not a claim about average buyer behavior.
- Program scope: FTMO 1-Step and 2-Step are compared at the same global/default 100K first-evaluation scope.
- Replay boundary: closed-trade evidence can establish supported historical breaches; pass-blocking limitations prevent an unsupported pass.
- Savings boundary: only a documented cancelled purchase creates avoided outlay; only received refunds reduce realized net fee cost.
- Product boundary: 600K+ is cumulative TSB operating scale, not a personal replay denominator or outcome claim.
For sourcing, corrections, and evidence classes, see our editorial methodology.
The Bottom Line: Replay Before You Pay
Historical replay earns its keep by improving the purchase decision, not by promising the evaluation result. It can expose a supported blocker, show rule pressure, make missing evidence visible, and stop a purchase whose exact program does not fit the recorded path.
Keep the savings statement rigorous: exact program, current checkout price P, planned attempts, cancelled attempts, actual payments, actual refunds, and no invented population average. Then use the FTMO execution framework for the paid path without changing the parameters that produced the evidence.
