Micros vs minis for Topstep automation sizing

When this topic matters

• Your automation losers feel “fine” in theory and violent in dollars
• You developed on one contract class and want to jump size casually
• Daily loss stand-downs fire too late because each tick is too expensive
• You are confusing liquidity preference with risk budget math
• You want a promote path for size, not only for strategy logic

The prop-account math (conceptual)

• Daily / trailing constraints are dollar constraints (confirm current official values for your stage)
• Minis move more dollars per tick than micros
• Automation can stack losers quickly if size is too large for the rule set
• Slippage assumptions scale with how aggressively you trade and how wild the session is

So many traders research: prove on micros → promote size deliberately.

When micros are the better automation lab

• You are still validating loser distribution
• Your stand-down thresholds are new
• You want finer granularity vs the daily budget
• You are supervising early live sessions
• You changed strategy logic recently
• You are learning Botfolio’s command-center ops and do not need max tick value drama

When minis may fit later

• Replay and live micros behavior are understood
• Risk per trade still fits the stage budget with room for realistic friction
• Fills and session fit remain acceptable under your rules
• You are not sizing up to “feel funded” or to force a faster evaluation fantasy
• Emergency controls are practiced cold

Automation-specific sizing mistakes

1. Backtesting minis, going live micros (or the reverse) without adjusting assumptions
2. Ignoring that automation removes the human hesitation that previously limited size
3. Promoting to larger size the same week you change strategy logic
4. No stand-down when the day is already spent
5. Using minis because social media trades minis
6. Treating micro success as proof that 10× size is free money (it is not)

Pair sizing with stand-downs and session windows

Size is one lever. Permission logic is another. A micro strategy without stand-downs can still spend a day poorly. A mini strategy with excellent stand-downs can still be too large for the stage. Design them together:

• Daily loss limit automation
• Stand-down rules
• Session windows

Botfolio’s promote mindset applied to contracts

Botfolio markets a train → replay → promote → supervise loop. Use that for contract graduation too: size is part of what you promote, not an afterthought.

A clean promote packet for size might include:

• replay notes under the new tick-value assumptions
• updated fixed risk numbers
• updated stand-down thresholds
• a supervised first-week plan
• explicit demotion criteria if live behavior disagrees with replay

Hypothetical progression (not a performance claim)

Month-like phase A: Ruleset on micros, tight supervision, stand-downs firing occasionally on messy days. Operator learns the command center under lower dollar voltage.

Phase B: Same logic, still micros, fewer operational surprises, better logging hygiene.

Phase C (optional): Consider larger tick-value instruments only if budget math and temperament still fit. If not, staying on micros is a valid professional choice, not a failure.

No phase guarantees profitability. The progression is about process voltage control.

Liquidity and fill quality still matter

Automated strategies live and die on fills. Highly liquid index futures are popular in algo research partly because spreads and depth are generally friendlier than exotic thin contracts. That does not mean “pick the biggest tick value available.” It means do not graduate size into worse execution assumptions by accident.

Confirm what your account path and data access actually support. Do not invent unsupported market lists for Botfolio.

Common failure modes

1. Ego sizing after a green week on micros
2. Ignoring that loser streaks are a distribution, not a surprise
3. Changing contract and session window at the same time
4. No replay under the new dollar risk
5. Assuming Topstep rules care about your intentions more than your outcomes/conduct

Rule-design / sizing checklist

• Stage dollar constraints confirmed from official sources
• Stop distance measured in ticks and dollars for chosen contract
• Fixed risk per trade stated explicitly
• Stand-downs recalculated for the contract’s dollar volatility
• Replay completed under the intended contract assumptions
• Promote size separately from promote logic when possible
• First sessions supervised
• Demotion plan written

What Botfolio does / does not claim

Does

• Support a futures workflow story where sizing/risk are explicit before live automation
• Encourage replay and deliberate promotion
• Discuss liquid index futures and micros conceptually in existing site content

Does not

• Guarantee micros or minis are profitable
• Publish a fixed symbol or historical-data matrix (confirm which symbols and sessions your installed build includes)
• Promise that graduating to minis improves evaluation outcomes

Field notes from supervised operators (composite, not testimonials)

These are composite lessons distilled from common prop-automation failure patterns — not customer quotes, not verified Botfolio case studies, and not performance claims:

• The bot that lacked a day-level stand-down did not fail dramatically; it failed by a thousand cuts.
• The operator who skipped flatten drills discovered that “I know where the button is” is not the same as using it under adrenaline.
• The strategy that looked robust until session windows were segmented was actually a one-hour idea wearing an all-day costume.
• The stage transition that reused old size settings turned a previously tolerable loser into an outsized budget event.

Use them as warning signs in your own review meetings.

Putting the education into a Botfolio-shaped operating cadence

Even when this article is mostly about trading process, the practical cadence still maps to Botfolio’s verified loop:

1. Encode the rule changes you just designed.
2. Replay before granting live-order privileges.
3. Promote only with account/sizing/risk settings explicit.
4. Supervise from the local command center with emergency actions reachable.
5. Demote back to replay when live behavior disagrees with the story you told yourself.

That cadence will not make a weak edge strong. It will keep weak process from impersonating a strategy.

Compliance reminder you should re-read often

Automation does not create a special exemption lane. If Topstep classifies a behavior as prohibited conduct or a prohibited strategy, doing it via software is still doing it — usually faster. Keep official help pages in your weekly ritual, especially around API access, prohibited conduct, prohibited strategies, and responsible trading. This site’s older checklist post remains useful as a prompt, not as a substitute for primary sources: Topstep automated trading rules checklist.

Dollar mapping worksheet (fill with your numbers)

1. Stage constraint that matters today (official source): ___
2. Stop distance in ticks: ___
3. Dollars per tick for candidate contract: ___
4. Dollars risked per contract at that stop: ___
5. Contracts proposed: ___
6. Dollars risked per trade: ___
7. How many full losers fit before your stand-down: ___
8. Does that number scare you for the right reasons? ___

If step 7 is “one,” you do not have a strategy plus a budget — you have a coin flip against the rule.

Why automation changes the sizing conversation

Discretion often includes accidental risk controls: hesitation, fear, lunch breaks, “I need coffee.” Automation removes those accidents. That can be good (consistency) or catastrophic (consistent oversizing). When you automate, size must be chosen for a world without hesitation.

That is why micros are not “less serious.” They are often the correct voltage for learning a supervised system.

Quick takeaways

• Public marketing discusses futures workflows and Topstep-compatible paths generally; choose contracts based on your tested plan and platform access.
• No instrument choice guarantees profits.
• Your automation losers feel “fine” in theory and violent in dollars.
• You developed on one contract class and want to jump size casually.