Tournament Engine / Section 01 of 06
Background
When LeagueApps underwent a company-wide reduction in force, I inherited leadership of two major product squads: Payments and Program Registration. My focus quickly shifted to the tournaments initiative — the highest-priority opportunity to capture share in the competitive youth sports market.
At the time, the platform only supported completing one team registration at a time and lacked mobile optimization. We needed to reimagine the system from the ground up: a scalable, mobile-first experience supporting bulk team registration, complex pricing logic, and seamless payments.
LeagueApps was mid-transition between its legacy (OG) and Next-Gen (NG) platform architectures. Data synchronization between the two environments introduced real complexity — requiring surgical precision in both design and engineering decisions at every step.