Reset fees stay public
The benchmark standard is simple: the reset price mirrors the current monthly combine fee. Mayospell should keep that same transparency instead of burying reset economics.
Mayospell publishes more than package prices: resets, reactivations, seat limits, and session timing are visible so traders know exactly how the program operates.
The benchmark standard is simple: the reset price mirrors the current monthly combine fee. Mayospell should keep that same transparency instead of burying reset economics.
The funded seat should not feel like a one-strike black box. A public Back2Funded-style reactivation path keeps traders inside the same operating system.
How many active funded seats a trader can hold, when a live account becomes available, and how many resets are allowed per day should all be public-facing.
Prop products feel real when the trading day, flatten window, payout counting, and reset timing all run on a formal operating schedule.
The reset fee mirrors the current monthly price, making the cost of a retry visible before a trader commits.
Benchmark program mechanics snapshot: July 5, 2026. Derived from the current public Topstep pricing and help-center mechanics. Mayospell copies the commercial structure where it fits and adapts the trading-day and risk overlays to listed options.
Mayospell does not force every funded stumble back to a brand-new combine. Public reactivation pricing makes the recovery path structured and reviewable.
50K funded seat
Responsible-trading profile: $549
Two reactivations available within 30 calendar days of closure.
100K funded seat
Responsible-trading profile: $649
Benchmark-style mid-ladder reactivation for the core desk lane.
150K funded seat
Responsible-trading profile: $779
Flagship-size reactivation path with the same public structure.
These are Mayospell's public mechanics for billing, resets, reactivation, and seat limits.
The benchmark rebills every 30 days until the account passes or the trader cancels. A reset pushes the billing date out by another 30 days.
The benchmark allows two resets per account per day. That kind of hard edge is exactly the sort of policy Mayospell should publish instead of improvising in support email.
The current benchmark offers up to two public reactivation opportunities within 30 calendar days of an account closure. That creates a stronger retention loop than sending traders all the way back to a new combine.
The benchmark publicly allows up to five active funded simulation accounts before live. Once live opens, that funded stack closes. Mayospell should mirror that clarity, even if the exact live-desk permissions stay discretionary.
The commercial rhythm stays clear while the desk clock follows listed-options market hours and cash-close risk.
Benchmark desk clock
That is the current public benchmark trading-day boundary. It matters because payout counts, resets, and end-of-day lock behavior all anchor to a formal clock.
Mayospell options adaptation
Options should flatten by the cash close, avoid overnight risk by default, and keep a short post-close review window for tagging, notes, and desk feedback.
The clearer Mayospell is about operations, the more the whole thing starts to resemble a real prop system instead of a pretty outline.
Copy the reset and reactivation economics exactly where they map cleanly.
Adapt the trading session to listed-options market hours instead of pretending futures and options are the same thing.
Publish funded-seat limits, desk escalation, and live-call-up criteria before traders need support to discover them.
Treat the platform, not just the pricing ladder, as the thing traders stay inside every day.
That is how public mechanics stop feeling like brochure text and start feeling like part of a working prop system.
Open the article lane for monthly rebills, reset math, and how the desk expects traders to use resets inside the product.
See how the free sandbox account keeps rehearsal, failed ideas, and automation testing inside the same operating system.
Open the funded-seat recovery path where closures, reactivations, and restricted conduct turn into explicit product states.
Walk the bridge from funded simulation into the live desk, where costs, permissions, and oversight get more serious again.
See the billing, payout, reset, and account-state surfaces that make the public operations story feel real after purchase.
Open the member proof archive where released payouts, share state, and cycle reset artifacts stay attached to seat history.
These shared POP records connect the public mechanics to actual release timing, lane labels, and account-history proof.
Next surface