Inside the Scalper Bot: Why It Fires More Trades Than Any Other Bot in Your Portfolio

Thirteen bots live in the Push Button Trading lineup, and none of them trade like the Scalper. While a strategy like the ORB Bot might fire once or twice around the open and then go quiet, the Scalper is built to work the whole session — hunting small, fast moves and taking dozens of trades a day where other bots in your portfolio might take three or four. That's not a flaw. It's the entire point of running it. But it does mean the Scalper punishes sloppy sizing faster than any other bot on the desk, and if you're stacking it next to your other bots without adjusting for that, you're carrying more risk than your account statement is telling you.

Why the Scalper Trades So Much More Than the Rest of Your Portfolio

The Scalper is designed around small, high-probability price moves rather than the bigger swings a breakout or trend-following bot waits on. That means it's scanning for setups constantly instead of sitting on its hands between a handful of A+ signals. More setups triggered means more fills, more exits, and — critically — more total contracts changing hands over the course of a session. On a active day, it's normal for the Scalper to generate several times the trade count of a bot like NR7 or the 10 EMA strategy running the same instrument. High frequency isn't the bug here; it's the strategy working as designed.

The Sizing Mistake Traders Make With High-Frequency Bots

The most common mistake we see isn't running the Scalper — it's sizing the Scalper the same way you'd size a bot that trades twice a day. One contract per signal feels conservative until you realize that "per signal" is happening 20-30 times instead of two or three. Your per-trade risk might look fine in isolation, but your cumulative exposure across the session compounds in a way slower bots never approach. If you're backing a funded account with a firm like Apex, Lucid, BluSky, or TakeProfit, that compounding risk is exactly what trips a daily loss limit before lunch — not one bad trade, but twenty small ones stacked in the wrong direction.

How to Actually Size the Scalper on a Funded Account

Start from your daily loss limit, not your account balance. Divide that number by the trade frequency you're actually seeing in the Scalper's backtest data for your instrument, not a rough guess, and size contracts so a realistic losing stretch — five or six trades against you in a row, which happens even in a strategy backed by 4.5 years of data — still leaves room to breathe. Then check what else is running. If you're also running the Volume Spike Bot or another short-duration strategy on the same instrument, you're not adding two independent risk budgets, you're stacking correlated exposure on top of each other. That's exactly what the Bot Portfolio Tracker is built to surface before it costs you a payout.

When the Scalper Belongs in Your Lineup — and When It Doesn't

The Scalper earns its seat in a portfolio when you have the account size and the risk budget to absorb a higher trade count without flinching at every fill notification. It's a poor fit if you're already running two other active bots on the same instrument, or if you're newer to a funded account and still learning what a normal losing stretch feels like. If that's you, our buyer's guide to matching your first bot to your account size walks through which of the 13 bots fits a smaller risk budget better while you get your footing.

No Coding Required — But the Sizing Still Needs You

The Scalper runs on NinjaTrader 8 exactly like the rest of the lineup — no coding required, no manual entries to babysit. But automation doesn't remove the math, it just moves it to before you flip the bot on. Get the sizing right for your account and the daily loss limit you're actually trading against, and a high-frequency bot like the Scalper becomes one of the more consistent pieces of a portfolio instead of the one that blows it up.

Not sure how the Scalper fits your current lineup? Start your 14-day free trial and run it against your own backtest data before you commit contracts to it.