Product strategy and phased scope
Shaped the vision, MVP boundaries, and sequence from a non-monetary pre-launch application to the main platform.

WNNR is a pre-launch online gaming platform connecting gameplay, wallets, bonuses, progression, and rewards. As Product Manager, I shaped its vision, phased scope, core systems, business rules, and cross-functional delivery.
WNNR connects player-facing gaming, wallet, bonus, reward, progression, and referral experiences with the Back Office controls needed to operate them consistently.
Shaped the vision, MVP boundaries, and sequence from a non-monetary pre-launch application to the main platform.
Defined how wallets, bonuses, gameplay, rewards, progression, and operational controls work together.
Turned decisions into buildable requirements and led clarification, acceptance testing, and cross-functional delivery.
A real WNNR MVP delivery board showing how product scope and pre-launch work were tracked across delivery.
Gameplay, wallets, bonuses, challenges, ranks, referrals, rewards, and Back Office controls began as broad concepts rather than one coherent system.
I defined MVP boundaries, dependencies, shared user states, edge cases, and the business rules connecting each system.
Users needed a clear experience, the business needed configurable controls, and delivery teams needed buildable requirements with less ambiguity.
Real and bonus funds needed predictable behavior across currencies, eligibility rules, wagering, and withdrawals.
ContributionDesigned centralized multi-currency bonus logic
The real-money MVP needed more time without delaying acquisition, referrals, and early validation.
ContributionDefined the non-monetary pre-launch ecosystem
Operational teams needed appropriate access without broad permissions or difficult-to-audit exceptions.
ContributionDesigned layered Back Office role-based access
A single account lock was too broad for proportionate Fraud, Risk, Support, Payments, and Operations workflows.
ContributionCo-designed restrictions, tags, and context rules
Defined WNNR-specific Vault behavior, boundaries, warnings, and edge cases without presenting the established pattern as an original invention.
Translated a collaborative strategy into system boundaries, user states, reward interactions, claim behavior, and implementation-ready requirements.
These are expected outcomes because WNNR remains in development and has not yet launched to real users.
Clearer understanding of real and bonus funds
Earlier acquisition before the real-money launch
Clearer boundaries between connected systems
Implementation-ready requirements from broad ideas
A real pre-launch product screen showing how gameplay, rewards, navigation, and original games come together.
A WNNR platform view showing navigation, account context, promotions, recent activity, and original games.
A WNNR Back Office player screen bringing account, financial, reward, security, and engagement context into one operational view.
A WNNR product screen showing the Infinity Pool, claimable and estimated rewards, tokens, Pulse, and earnings context.