Make the commercial grammar clear
The package ladder, reset concepts, payout lanes, and future review path should be easy to compare. Mayospell can explain each state without inventing promises that are not live yet.
A-to-Z playbook
The Mayospell operating model, from checkout through review.
One page connects the price ladder, evaluation rules, payout policy, support responsibilities, member workflows, and the options-specific controls that govern the program.
Build the operating system, not only the prices
Mayospell is designed as a full machine: support rails, practice accounts, add-ons, community, Labs, a live leaderboard, and a real platform stack.
Win where options actually change the game
The product edge belongs in structure permissions, liquidity scoring, event governance, assignment avoidance, and desk-quality review, not in weirdly different checkout math.
Pricing clarity
The first thing to publish is exact package math.
Mayospell's ladder should be instantly legible when a trader compares account sizes, fee paths, targets, and loss limits.
Mayospell A-to-Z playbook snapshot: July 6, 2026. Pinned to Mayospell's public pricing, help, community, and live-account plan, with the exact surfaces needed for an options-first program.
Size
Standard
No activation
Responsible trading
Activation
Reset
Back2Funded
50K
$49/mo
$95/mo
$85/mo
$149
$49
$599 / $549
100K
$99/mo
$149/mo
$129/mo
$149
$99
$699 / $649
150K
$199/mo
$229/mo
$199/mo
$149
$199
$829 / $779
System design
The real Mayospell system is bigger than checkout.
These are the Mayospell mechanics that must stay public if the whole program is going to feel trustworthy and category-legible.
Surface
Operating requirement
Mayospell move
Why it matters
First purchase
A first-purchase safety policy should state its window, eligibility, and refund boundary in plain language.
Mayospell can publish a first-purchase policy when enabled; the current site should not imply that a satisfaction guarantee or refund workflow is active unless the checkout confirms it.
It lowers fear without weakening the paid ladder after the first attempt.
Reset Bank
A reset ledger should show the size, source, expiry, and consumption order of each credit.
Keep a visible reset ledger by size and path so the trader can see what is banked, what expires, and what will be consumed first.
Retries stop feeling mysterious and start feeling budgetable.
KYC gate
Identity checks should gate repeat paid actions while keeping existing account history visible during review.
Gate paid actions the same way while leaving the current portal and existing seats visible during review.
This turns compliance into a visible rule instead of a broken checkout surprise.
Practice lane
A practice lane gives traders a place to rehearse structures without risking a paid evaluation seat.
Mayospell's practice-account surface can support options structures, scenario rehearsal, and dry-run automation; availability follows the current account release.
The sandbox keeps reps, research, and retention inside the same product.
Funded stack
Account architecture should make evaluation seats, funded simulation, and a later review queue easy to distinguish.
Mayospell can layer grouped risk, catalyst overlap warnings, and seat-specific permissions over its 50K/100K/150K paths without implying that live promotion is automatic.
Serious traders compare account architecture, not only the headline fee.
Payout engine
Payout math should expose the split, minimum, cadence, deductions, and review state in one place.
Mayospell can document a future funded cash-out model with options-quality review, while clearly stating that verified payout operations are not live today.
Getting paid is one of the core things the product is selling.
Live promotion
A live promotion policy should be discretionary, documented, and separate from evaluation success.
Mayospell's planned review would weigh event discipline, fill quality, assignment risk, and human approval; no live brokerage activation is currently offered.
The live dream becomes concrete instead of vague hero copy.
Arena and labs
Mayospell Arena and Labs use limited, clearly labeled experiments to test new formats without changing the core ladder.
Arena and Labs can remain clearly labeled planned or limited experiments so Mayospell learns in public without changing the core ladder.
The ecosystem becomes part of both retention and roadmap discovery.
Support and media
Mayospell behaves like a platform company, not only a prop checkout.
Support, community, and conduct policy become visible surfaces alongside the combine and funded-seat workflow.
AI concierge plus human escalation
Mayospell should front support through clear intake lanes and a desk bot that hands real incidents to humans fast.
Platform-first incident protocol
Mayospell's incident posture is blunt: stop trading, capture the Order ID, export evidence, then escalate. The options room should make that workflow native.
Prohibited-conduct ladder
Warnings, restrictions, reset pressure, payout denial, and closure should all be visible product states. Unsupported behavior should not feel like an invisible back-office mood swing.
Community and learning as real product
Desk TV, public rooms, coaching, and learning surfaces are part of the funnel and retention loop. Mayospell should keep them first-class.
Options edge
This is where Mayospell becomes unmistakably options-native.
Keep the commercial path clear. Put the intelligence into how the desk evaluates options behavior.
Structure permissions
Start with long premium and defined-risk spreads. Push short premium, assignment-sensitive trades, and unsupported structures behind explicit permissions.
Liquidity scoring
Grade contracts by spread width, volume, open interest, and fill realism so the desk rewards executable behavior instead of fantasy screenshots.
Event governance
Earnings, CPI, Fed, and other binary events need their own policy lane with tighter size, faster exits, and manual approval when necessary.
Cross-seat correlation control
One trader running several seats can accidentally concentrate SPY, QQQ, and NVDA risk everywhere. The options version should detect and police that portfolio behavior.
Assignment and expiry defense
Force earlier exits, reduced sizing, and different permissions as contracts approach assignment or same-day expiry chaos.
Playbook evidence
Every trade should stay attached to screenshots, thesis, structure choice, and reviewer notes so progression reflects process quality, not only curve shape.
Build order
The smartest way to build this is in the same order the business earns trust.
Commercial clarity first. Platform second. Ecosystem third. Options depth everywhere.
Phase 1: Clarify the funnel
- Publish the 50K, 100K, and 150K paths with the currently supported purchase and enrollment states.
- Ship resets, Reset Bank, guarantee, KYC gate, and exact payout-lane copy.
- Make the help center and billing portal feel as complete as the checkout.
Phase 2: Build the platform
- Expose the account board, journal, lockout, brackets, copier rules, and add-ons in one room.
- Keep practice, API, and data upgrades visible as separate software rails.
- Make support evidence capture native to the desk, not a side instruction.
Phase 3: Connect the ecosystem
- Add Desk TV, community pods, live arena ranking, and limited Labs drops.
- Turn support, coaching, and learning into ongoing member reasons to stay.
- Make the business feel like a category platform, not one more challenge page.
Phase 4: Lead on options depth
- Use permissions, event controls, and portfolio-level risk to make the evaluation more truthful.
- Promote live options buying power only after high-quality funded behavior, not only headline profits.
- Let the real moat live in the desk and the review system rather than in weird pricing novelty.
Keep going