Why BluSky's Scaling Plan Changes How You Should Size an ORB Bot

You pass the evaluation. You get funded by BluSky. The congratulations email lands, the account activates, and your ORB bot goes live on day one running the exact same contract size it ran in the eval. Three days later you get a rule-violation warning that has nothing to do with your trading — it's about how many contracts you were allowed to hold at your current account tier. The bot didn't do anything wrong. You just handed it a sizing instruction the scaling plan never approved.

This is one of the more avoidable mistakes we see funded traders make with an Opening Range Breakout bot, and it has nothing to do with strategy quality. ORB is one of the 13 automated bots in the Push Button Trading lineup, and like every one of them, it does exactly what it's told. It doesn't know your account just moved up a scaling tier. It doesn't know BluSky caps contract count differently than Apex, Lucid, or TakeProfit. That's your job, and it's a 20-second check that a lot of funded traders skip.

What a Scaling Plan Actually Controls

A scaling plan isn't just a reward for good performance — it's a leash. Most funded-account programs, BluSky included, increase your buying power and contract allowance in steps as you hit realized profit milestones. Hit the first threshold, your contract cap goes up. Hit the next one, it goes up again. The part traders miss is that this works in both directions: the cap at your current tier is a hard ceiling, not a suggestion, and it's usually lower than what the eval account allowed you to trade.

ORB is built to catch the opening range breakout with real size — that's the whole point of the strategy, it needs enough contracts in the trade to make the move worth taking. If your bot's default sizing was calibrated for a 2-step eval account with a higher allowance, and you drop it onto a freshly-funded BluSky account sitting at tier one, you can oversize a trade without a single manual click. The bot fired correctly. The instructions it was given didn't match the account it was running on.

Why ORB's Full-Size Default Doesn't Fit Every Tier

Breakout bots are sized differently than mean-reversion or scalping bots almost by design. ORB wants to be in the trade at the open with enough size to capture the range expansion — a half-size position on a breakout strategy can mean the difference between a trade that covers its stop and one that doesn't move the needle at all. That's exactly why you can't treat ORB's sizing as a "set it once and forget it" field in the strategy settings.

Think about it tier by tier. At BluSky's entry scaling tier, your contract allowance might only support running ORB at reduced size, maybe paired with nothing else firing in that same opening window. Climb two tiers and suddenly you've got headroom to run ORB at full intended size, possibly alongside a second bot without blowing the cap. The strategy logic never changes. What changes is how much of it the account in front of you is allowed to hold at once — and that's a number you have to go check, not one you can assume carried over from the eval.

Re-Sizing ORB as BluSky Scales You Up

Here's the actual workflow, and it takes less time than most traders think: before you flip ORB live on a newly-funded or newly-scaled account, pull up your current tier's contract allowance from BluSky's dashboard and compare it against what the bot's Strategy Builder has set for quantity. If the bot's default exceeds what your tier allows, reduce the contract field before you hit Enable — not after a warning email makes you do it.

This matters more the moment you're running a bot portfolio instead of a single strategy. If ORB and a second bot — say Scalper or 10 EMA — can both fire inside the same morning window, your tier's allowance has to cover both positions stacking at once, not just ORB in isolation. The Bot Portfolio Analyzer is built to flag exactly this kind of overlap risk, but it can't catch a contract-count problem that's really a scaling-plan problem. That check is on you, and it only takes a glance at two numbers: what the tier allows, and what the bot is set to trade.

A simple habit fixes this for good: every time BluSky bumps you to a new tier, that's your trigger to re-check ORB's sizing before the next session open — not sometime this week, before the next open. Tier changes and sizing changes should happen in the same sitting.

Build the Habit Before It Builds a Violation

None of this is a knock on ORB, or on BluSky's rules, or on scaling plans in general — they exist to protect both you and the firm as real capital gets put behind your trading. The mistake isn't running a breakout bot on a funded account. It's assuming the sizing that worked on one account tier automatically survives the jump to the next one. A bot that executes flawlessly on bad instructions is still a bad outcome, and it's one you can eliminate with a 20-second habit instead of a post-violation scramble.

If you're still dialing in how your bot lineup should flex across a scaling plan — or you haven't settled on which bot deserves the first slot in your rotation — that's exactly what the 30-Day Bot Workshop was built to walk you through. For $199, you get a structured, week-by-week path through sizing, risk, and bot selection instead of guessing your way through tier one. Check out the workshop and the full bot lineup at pushbuttontrading.co and get your sizing right before your next tier bump, not after.