FundedQuant

Simulate Your Prop Firm Success Before You Trade

AI-powered strategy generation, backtesting, and Monte Carlo simulations for prop firm traders. Know your odds before risking real capital.

Everything You Need

⚡

AI Strategy Generator

Describe your trading idea in plain English. Our AI writes the backtest code and runs it on real historical data instantly.

📈

Monte Carlo Simulator

Run thousands of simulations to see your probability of passing evaluations, hitting payouts, and avoiding account blowups.

🎯

All Major Prop Firms

Pre-loaded rules for Apex, Topstep, FTMO, and 10+ other firms. Select your firm, account size, and phase — we handle the rest.

📊

Real Market Data

Built-in price data for NQ, ES, YM, CL, GC and their micro contracts. Or upload your own OHLCV data.

🛠

10+ Built-In Indicators

SMA, EMA, RSI, ATR, Bollinger Bands, MACD, VWAP, Stochastic — all ready to use in your strategies.

💰

Funded Phase Modeling

Simulate multiple payout cycles — not just pass/fail. See expected payouts, bust rates, and long-term profitability.

How It Works

1

Describe Your Strategy

Tell the AI what you want to trade — entries, exits, indicators, risk rules. It generates the backtest code for you.

2

Run the Backtest

The AI executes your strategy on real historical data and generates a full trade list with P&L stats.

3

Simulate Your Odds

Run Monte Carlo simulations against your prop firm's rules to see your pass rate, expected payouts, and risk of ruin.

Supported Prop Firms

Apex Trader Funding Topstep FTMO Bulenox Alpha Futures TradeDay Blueberry Funded And More...

Ready to Know Your Edge?

Join traders who simulate before they trade. Start with a free account today.

Subscription Required

You need an active subscription to generate a strategy. Please choose a plan below to continue.

Essential
$24.99 $19.99 /mo
with promo code
  • ✓ Generate up to 10 strategies
  • ✓ 365 days of historical data
  • ✓ 1,000 Monte Carlo simulations
  • ✓ Access to all prop firms
Most Popular
Pro
$44.99 $35.99 /mo
with promo code
  • ✓ Generate up to 25 strategies
  • ✓ 365 days of historical data
  • ✓ 10,000 Monte Carlo simulations
  • ✓ Access to all prop firms
  • ✓ Priority support

Maybe later

How to Add Indicator to TradingView

Step 1 of 5

Account

Manage your account details and security

Profile

Email
—

Security

Password
••••••••

Danger Zone

Delete Account
Permanently delete your account and all data

Example diagram

Strategy Builder Tips

Read these before building to avoid common issues

The Custom Builder lets you pick confluences, confirmations, targets, and stop losses. Following these tips will help you build strategies that actually generate trades and compile without errors.
⚡ Key Level Selection
  • Start with 1-2 key levels. Each key level you add makes it harder for the system to arm. Start simple (e.g. just Order Blocks) and add more only after testing.
  • Key levels use OR logic. If you select OB + FVG + Sweep, the system arms when ANY ONE of them is detected — not all three. More key levels = more opportunities.
  • Don't select every timeframe for every key level. Pick 2-3 timeframes max per key level. Selecting all 5 timeframes creates too many request.security() calls and can cause TradingView to timeout.
  • Higher timeframes detect less frequently. A 4H Order Block forms much less often than a 5m one. If you only select 4H, expect fewer signals.
⚡ Entry Confirmations
  • Pick 1-2 confirmations max. Confirmations fire on the execution timeframe after a key level arms. Too many confirmations with AND logic means nothing fires.
  • BOS, ChoCH, and Displacement are the most reliable. These fire frequently enough to confirm entries within the arm expiry window.
  • Engulfing candles are strict. True engulfing patterns are rare. If your only confirmation is engulfing, expect fewer trades.
⚡ Targets & Stop Loss
  • Always select a stop loss. Without a stop loss, trades never close on losses and the backtest produces unrealistic results.
  • Select 1-2 take profit targets. The system picks the closest one. Too many TP options can cause confusion in the generated code.
  • Swing High/Low is the most reliable TP. It always exists on any chart. Other targets like Previous Week High may be far away.
⚡ Timeframes & Sessions
  • Your execution timeframe is where entries happen. Key levels can be on higher timeframes, but the actual trade signal always fires on the execution TF.
  • Match your chart timeframe to your execution timeframe. If your execution TF is 5min, set your TradingView chart to 5min too.
  • Session filters reduce trade count. Limiting to NY Session only means no trades during London or Asia. Make sure your instrument has enough activity in your chosen session.
⚠️ Common Mistakes
  • Selecting 5+ key levels across 5 timeframes. This creates 25+ request.security() calls which causes TradingView to timeout or error. Keep it to 2-3 key levels with 2-3 timeframes each.
  • No stop loss selected. The generated code won't have exit logic for losing trades, producing unrealistic backtest results.
  • Conflicting directions. Selecting only bullish key levels but bearish confirmations means trades will never fire.
  • Expecting immediate results after generation. If you see zero trades, don't add MORE conditions — remove some. Fewer conditions = more trades.
  • Arm expiry too short. The default is 50 bars. If you set it lower (like 10-20), most setups will expire before a confirmation fires.

💡 Tips & Tricks

How to structure your strategy to avoid issues

These tips help you build cleaner strategies that backtest better and avoid common logic problems. Whether you're using a template or the custom builder, following these guidelines will save you time and produce more reliable results.
⚡ Best Practices
  • Keep entry conditions clear and specific. Vague descriptions like "when price looks bullish" can't be coded reliably. Instead, describe exact conditions like "when price closes above the 20 EMA."
  • Avoid contradictory confirmations. Selecting both bullish-only and bearish-only confirmations together can create logic that never triggers. Make sure your conditions work in the same direction.
  • Don't overfilter with too many rules. Each additional confluence reduces the number of trades. Start with 2-3 key conditions and add more only if backtests show improvement.
  • Always define stop loss and take profit. A strategy without exit logic will hold positions indefinitely. Make sure both SL and TP are selected and clearly defined.
  • Use time and session filters carefully. Restricting trades to a narrow window reduces sample size. Make sure your chosen session actually has enough activity for your instrument.
  • Avoid repainting or future-looking conditions. Indicators that change historical values (like repainting pivots) produce misleading backtests. Use confirmed, closed-bar data only.
  • Keep higher timeframe logic consistent. If your key level is on the 15m chart, don't expect it to update on every 1m bar. Higher TF signals only change when that TF bar closes.
  • Make rules objective, not vague. "Strong momentum" is subjective. "RSI above 70" or "displacement candle with body > 2x ATR" is objective and codeable.
  • Test one change at a time. If you change three things and results improve, you won't know which change helped. Iterate with single modifications.
  • Make sure every confluence can actually trigger. Some combinations are theoretically possible but practically never align. If your backtest shows zero trades, simplify your conditions.
⚠️ Common Mistakes
  • Too many confirmations causing zero trades. Requiring 5+ confluences to all align at the same time is extremely rare. Most real strategies use 2-3 conditions.
  • Conflicting bullish and bearish logic. For example, requiring price to be in a premium zone (bearish) while also looking for bullish OB entries creates a contradiction.
  • Undefined or missing exits. Entering trades without a clear SL/TP means the strategy can't properly close positions. Always define both before generating.
  • Timeframe-dependent logic bugs. A condition that works on 5m may never trigger on 1h because the bar structure is different. Match your timeframes to your strategy's logic.
  • Conditions based on visual ideas that aren't codeable. "I can see a head and shoulders" is pattern recognition that's hard to express in exact rules. Stick to indicator-based or price-action conditions with clear math.