After you're funded · Stage 3 · Free
Two funded accounts require two pre-session compliance checks. Five require five — with five separate DLL ceilings, five separate trailing drawdown floor positions, and up to five separate consistency windows at different stages simultaneously. The accounts are independent by contract. On a single adverse session where all five are running the same setup, they are not independent in practice. Scaling a funded account stack correctly means understanding where contract independence ends and combined risk begins.
Part 1 of 4 — The readiness bar for each additional account
The readiness criteria for account two — two payouts from account one, locked floor, positive buffer, written process — establish a minimum for multi-account management. That bar applies at each step, but with a stricter denominator: each new account requires proven payout delivery from all existing accounts in the stack, not just from the most recent one.
Before adding account two, you need two payouts from account one. Before adding account three, you need two payouts from each of the two existing accounts. The pattern holds: each account added requires that every existing account in the stack has already demonstrated repeatable payout delivery across multiple periods. The reason is structural — you are not just proving that one process works; you are proving that a multi-account management process works. That proof requires at least two cycles from each account already in the stack.
The other readiness requirements — locked trailing drawdown floor, positive buffer headroom, written pre-session process — apply to every account in the stack, not just to the oldest one. If account two's floor is still advancing when you are considering account three, the stack has two accounts in different phases of funded management simultaneously. Adding account three introduces three-account complexity while account two is still in its most fragile pre-lock phase.
Two payouts from account one. Account one's floor locked. Account one in positive buffer headroom. Pre-session process covers one account's compliance checks in under five minutes. For full detail on the two-account readiness criteria, see how to manage a second funded futures account alongside the first.
Two payouts from each of the two existing accounts (four total payouts from the stack). Both existing accounts have locked floors and are in positive buffer headroom at the time of application. Pre-session process covers two accounts' compliance in under ten minutes. Pre-session compliance must be written and systematic — not from memory — because three accounts means three DLL ceilings, three trailing drawdown positions, and potentially three consistency window checks before the first position is entered.
At account three, the pre-session workload is the first practical constraint that limits further scaling. If the two-account pre-session check is already taking close to ten minutes, adding a third account pushes the process past what can be reliably completed before the session opens without rushing. A rushed compliance check is a failed compliance check — one that did not catch the consistency window at 28% before you entered the position that pushed it to 34%.
Each additional account requires two payouts from every existing account, all floors locked, all accounts in positive buffer headroom, and a pre-session process that can cover the entire stack in under ten minutes total. At four and five accounts, the pre-session workload becomes the dominant constraint. Five accounts with five DLL checks, five consistency window calculations, and five trailing drawdown position reads cannot reasonably be completed in ten minutes without a systematic spreadsheet or logging tool. The question before adding account four or five is not just "is my process proven?" — it is "does my pre-session process scale to this account count without degradation?"
Most traders who run five accounts successfully use a dedicated compliance spreadsheet where each morning's inputs (each account's current balance, its period profit total, its current best-day P&L) feed into pre-calculated DLL ceilings, consistency percentages, and trailing drawdown floor positions for all five accounts simultaneously. Without a tool like that, five-account compliance is not reliable at the required daily cadence.
Part 2 of 4 — How combined exposure scales with each additional account
Each account's DLL stays independent regardless of how many accounts you add. What scales with each additional account is your combined loss potential on a single adverse session where all accounts are running correlated positions simultaneously.
If N accounts each have a DLL of $1,200 and each account is running one ES contract in the same direction simultaneously, a 5-point adverse move against the position generates the same per-account loss on every account at once. At two accounts: $500 combined. At three: $750. At five: $1,250 — across all five accounts in a single five-point move on what you executed as one ES contract per account. The individual account's DLL is never at risk from that single move. The combined session result is.
The framework for modeling combined exposure at N accounts:
Use the smaller of DLL ÷ 4 and (trailing drawdown distance ÷ 10) for each account separately. If any account is in drawdown recovery, its ceiling drops further — size from whichever constraint is tighter. Do not take the average across accounts or apply the loosest account's ceiling to all.
If account A's ceiling is $250, account B's ceiling is $300, and account C's ceiling is $250, the combined maximum per-trade dollar risk across all three accounts — if all three enter the same setup simultaneously — is $800. That is the number you model against your total risk tolerance before entering any account's position. The individual account ceilings are the per-contract controls. The sum is the total-thesis control.
If all accounts take their maximum per-trade ceiling on the same setup and the trade stops out at the planned stop, what percentage of each account's DLL does that stop-out consume? The answer should be consistent with your single-account practice. If a single-account stop-out typically consumes 20-25% of the DLL and a stop-out on the full stack simultaneously would consume 40% on any single account, the stack is oversized relative to the stop placement or the account count is too high for the stop width you use.
Each account's consistency window runs from its last payout date. Five accounts that received their most recent payouts on five different dates have five windows of five different lengths with five different profit total denominators at any given time. Account A might be in week three of a period with $900 accumulated and a $400 best day (44% — already in high-risk territory). Account B might be in week one of a fresh period with $200 accumulated and a $200 best day (100% — already maxed for the period). The same session P&L adds to each account's window independently.
The practical implication: with five accounts, it is common to have one account near its consistency cap while the others are well within compliance at the same time. The pre-session check must catch the near-cap account before you enter that account's position. Missing that check on a five-account stack is easier than missing it on a two-account stack, because there are more windows to review and more divergence between them.
The discipline that prevents consistency violations at scale: run the consistency percentage calculation for every account, every session, before entering any account's first position. Not just the accounts that have been active recently. Not just the accounts that had a big day last session. Every account, every session. The one you skip is the one that was already at 31%.
Each account's trailing drawdown floor advances independently. Five accounts have five floors in five positions. On a good session where all five accounts produce profit simultaneously, all five floors may advance — which is the desired outcome. On a bad session where all five accounts take losses simultaneously, the floors on pre-lock accounts continue advancing even as the balances drop, tightening the buffer on multiple accounts in the same session.
At two accounts, a bad session where both accounts lose means two floors advancing simultaneously on two accounts. At five accounts, it is five floors advancing simultaneously — and any account whose floor advances to within the recovery threshold requires that account to begin the reduced-sizing recovery protocol while the other accounts continue at normal sizing. Managing four accounts at normal sizing and one in recovery simultaneously is a legitimate operational scenario. Managing two accounts in recovery and three at normal sizing is a significantly higher complexity state. The probability of that state occurring increases with each additional account in the stack.
Part 3 of 4 — Three structural models for 3-5 accounts
A five-account stack where all five accounts trade simultaneously in the same instrument is a different risk structure than a five-account stack where each account trades a different session window. The structure determines whether the accounts multiply each other's exposure or genuinely distribute it.
The lowest combined-risk structure: each account trades in a dedicated session slot, and at most one account has open exposure at any given time. A three-account sequential stack might assign account A to the RTH morning session (8:30–11:30 AM CT), account B to a second window within the same RTH day, and account C to a globex or pre-market session. A five-account stack would extend this across multiple instruments and multiple session windows throughout the week.
The combined risk profile of sequential rotation is the same as a single account at any given moment — because only one account is active at a time. A bad morning session on account A does not produce a simultaneous loss on accounts B through E. The accounts do not insulate each other from correlation in this structure because they are never exposed simultaneously. Each account's DLL is the only limit that matters during its own session window.
The limitation: if you are rotating five accounts through session windows, you are effectively trading for a larger portion of the day. The cognitive load at the end of a long rotation is different from the cognitive load at the start. Decision quality in account E's fifth session slot after managing accounts A through D earlier in the day may be materially worse than decision quality in account A's morning session. Sequential rotation distributes market exposure but concentrates operational time.
A structure where accounts are assigned to different instruments with genuinely different risk drivers: one account in ES (equity index), one in CL (crude oil), one in GC (gold), for example. The accounts trade simultaneously but in instruments that do not respond identically to the same macroeconomic events. A risk-off equity session may move ES significantly against a long position while GC benefits from the same safe-haven flow. CL responds primarily to crude oil supply and demand catalysts, which are often orthogonal to equity index moves on most sessions.
The combined risk profile is lower than a same-instrument parallel structure because the drivers are more genuinely distinct. It is higher than sequential rotation because all accounts are simultaneously exposed in the same session window. The pre-session check for the instrument-diversified stack adds one dimension: verify that no scheduled news event today affects multiple instruments simultaneously (FOMC announcements, for example, affect ES, GC, and CL in correlated ways even though they have different primary drivers). On FOMC days, an instrument-diversified stack may have more correlated downside risk than the daily setup analysis suggests.
Consistency window management in the instrument-diversified stack: on sessions where all three instruments move in your favor simultaneously, all three accounts may record significant P&L on the same day. All three best-day percentages are affected by the same session. The consistency check before a high-conviction multi-instrument setup must cover all three accounts' windows, not just the account in the most active instrument.
The highest combined-risk structure, and the one most often used incorrectly: all accounts run the same setup signal on the same instrument, with entries staggered by account rather than entered simultaneously. The intent is to scale into a high-confidence setup without exceeding any single account's contract ceiling. Account A enters one contract. If the setup holds, account B enters one contract a few ticks later in the same direction. And so on through accounts C, D, and E if the setup continues to hold.
The risk profile of the same-setup fleet is heavily influenced by whether entries are genuinely staggered or effectively simultaneous. A staggered entry that spans five minutes across five accounts provides minor average-cost benefit at the cost of significant operational complexity — five live positions to monitor simultaneously in the same instrument. If the setup reverses after accounts A and B have entered but before accounts C through E, the decision of whether to enter accounts C through E while accounts A and B are already in loss is a live decision that must be made under time and P&L pressure. The pre-session rule for this structure is strict: define the entry sequence, the maximum number of accounts to enter before the setup is validated, and the stop-out price for all accounts before entering account A. Do not improvise the rest of the entry sequence after accounts A and B are live.
A five-account same-setup fleet stop-out where all five accounts take the maximum per-trade loss simultaneously is the worst outcome of any multi-account structure: five DLLs each consumed by 20-25% in a single trade, five consistency windows affected by the same loss day, five trailing drawdown floors at risk of advancing on a losing session. The same-setup fleet is only appropriate for a trader with a documented, statistically verified edge across enough trades that the per-trade expected value is reliably positive — and who has structured the fleet so that a single stop-out does not simultaneously push multiple accounts into drawdown recovery.
Part 4 of 4 — When more accounts is the wrong answer
More accounts increase both payout potential and combined drawdown exposure simultaneously. There is a stack size at which the incremental management overhead and the incremental simultaneous drawdown risk exceed the incremental payout benefit. Recognizing that point is as important as knowing when to add the next account.
The clearest signal that the stack is too large for the current process: you are rushing pre-session compliance checks, skipping accounts you "know are fine," or discovering mid-session that an account you did not check was already near its consistency cap. When compliance is being approximated rather than calculated, the stack is at the management limit. The choice at that point is either to reduce the stack to a size where compliance can be done correctly, or to invest in building the systematic tool (spreadsheet, trading log, dedicated compliance tracker) that enables the larger stack to be managed without approximation.
Reducing the stack is not a failure. Most funded traders find that three well-managed accounts with reliable payout delivery outperform five accounts with degraded daily management. The payout ceiling on a single three-account stack where all accounts make payouts consistently is higher than the payout ceiling on a five-account stack where two accounts are frequently in drawdown recovery and one is in a consistency hold.
Adding accounts is one way to scale payout potential. Increasing account tier size is another — and it eliminates one category of overhead entirely. A single $150K funded account produces a larger payout ceiling per period than three $50K accounts: the $150K DLL of $7,500 allows a $750 per-trade risk ceiling (versus $250 on a $50K account), and the payout request threshold on a $150K account is proportionally higher than on three separate smaller accounts. The $150K account requires one set of pre-session compliance checks: one DLL, one trailing drawdown floor, one consistency window.
The tradeoff: larger account tiers require larger evaluation fees and often involve stricter rule compliance during the evaluation phase. A failed $150K evaluation is a larger fee loss than a failed $50K evaluation. For a trader who has already demonstrated repeatable payout delivery at the smaller tier, the evaluation risk is lower and the management overhead reduction is real. For a trader still establishing their process, starting at smaller tiers and proving the process before upgrading is the lower-risk path.
The decision framework: if you are considering adding account N to the stack and the primary reason is to increase total payout capacity, first model whether upgrading one or two existing accounts to the next tier achieves the same payout ceiling with fewer pre-session compliance checks. If it does, the upgrade is likely the cleaner path. If the account tier upgrade is not available (evaluation cost, risk preference, firm policy), additional accounts at the current tier are the alternative — with the full combined-exposure math applied before adding each one.
An account in drawdown recovery is a signal about current market conditions and your current execution — both of which also affect any additional account you add to the stack. Adding an account while one of the existing accounts is in recovery puts the new account into the same market environment that caused the recovery on the old account. The recovery protocol requires focused management on the recovering account; adding a new account during that period distributes attention at the moment when concentrated attention is most needed.
Model a scenario where the worst-performing two accounts in the current stack simultaneously enter drawdown recovery in the same week. If that scenario would require you to run three other accounts at normal sizing while managing two simultaneous recovery protocols — and you cannot demonstrate that your current process handles that state — the stack is already at or past its management limit before adding the next account.
Ten minutes is the operational ceiling for sustainable daily compliance. Beyond ten minutes, compliance will be abbreviated on high-activity mornings, before major news events, or when the session opens at a price that demands immediate attention. If the current stack's compliance is already at that ceiling, adding another account pushes compliance past the limit at which it can be reliably completed before the first position is entered.
A stack where account A has three payouts, account B has two payouts, and account C has one payout has one account with unproven repeatability. Adding account D before account C has demonstrated repeatable payout delivery means managing four accounts while one of the three existing accounts is still establishing its track record. The stack is not ready for account D until all existing accounts have made two payouts.
Most funded futures firms do not set a hard cap on the number of funded accounts a trader can hold simultaneously — some allow ten or more active funded accounts per trader. The practical limit is your ability to manage each account's pre-session compliance (DLL ceiling, trailing drawdown floor position, consistency window percentage) and your total combined capital exposure per adverse session. A stack of five accounts running the same setup simultaneously is five times the single-account exposure to a single adverse move. Firm policies vary: verify the multi-account policy in your firm's funded account agreement before applying for additional evaluations.
After you have received at least two payouts from each of the two existing accounts — not just one payout each — and both have locked trailing drawdown floors, are in positive buffer headroom (not in drawdown recovery), and can be managed through a written pre-session compliance process in under ten minutes. Adding account three before both existing accounts have proven repeatable payout delivery across multiple periods introduces a third management burden on an already unproven two-account process. The readiness bar rises with each additional account added to the stack.
No. Each account's DLL applies to that account's own intraday P&L independently — five accounts each with a $1,200 DLL gives you five separate $1,200 limits, not one $6,000 combined limit. The firm does not aggregate your losses across all five accounts. What does multiply is your combined exposure on a single adverse move: if all five accounts are long ES simultaneously, a 5-point move against the position generates a loss in each account's P&L at the same time. The DLL ceilings are separate by contract; the market exposure is combined in practice if the accounts are running correlated positions.
Each account has its own consistency window defined by its own payout-period start date and its own period profit total. With five accounts, you have five separate best-day percentage calculations to run before each session. Track each account with three values: current best-day P&L, current period profit total, and calculated best-day percentage (best day ÷ period profit). Flag any account where the percentage is approaching the firm's consistency cap — typically 30% or higher — before entering that account's first position of the session. The windows diverge over time as accounts receive payouts at different dates, producing genuinely different denominators and different compliance positions per account at any given moment.
When pre-session compliance for the current stack already takes more than ten minutes to complete, when any existing account is in drawdown recovery, when a single bad session could push more than two accounts into simultaneous drawdown recovery, or when account management complexity is causing you to skip or rush compliance checks. At that point, the alternative worth modeling is upgrading one or two existing accounts to a larger tier — a single $150K account requires one set of compliance checks and produces the same or greater payout potential as three $50K accounts, without tripling the daily management workload.
The combined-exposure math, the consistency window divergence problem, the pre-session compliance ceiling, and the account-tier alternative to stack expansion — from managing multiple funded accounts through full payout cycles.
Most traders who build large funded account stacks do so by copying the single-account process N times rather than building a process designed for N-account management. The method covers the mechanics of running multiple accounts correctly — the combined risk model, the systematic compliance process, and the tier-upgrade decision. First 100 founding seats at $19/mo — locked for life.