Team Builder / Section 02 of 06
Problem
How do we safely reconcile legacy systems, inconsistent program structures, and conflicting user mental models — without creating irreversible mistakes?
Every season feels like triage. Moving players in a spreadsheet, sending invite emails, then praying nobody declines. It's stressful and takes away from coaching.
We spend entire weekends placing kids on teams. Parents call, coaches complain, and I'm essentially doing data entry instead of organizing a safe, fun season.
Team Builder needed to operate across two major use cases:
- Recreational leagues
Prioritize balanced team formation and inclusion. Everyone plays. - Club organizations
Prioritize talent evaluation and selective invites. Only the best make the cut.
Both groups shared a critical pain point: LeagueApps' core product lacked a fluid, visual interface for bulk moving players between teams, viewing roster capacities, or filtering players by skill, position, or evaluation metrics.
Internally, the project sat at the intersection of several initiatives — registration, evaluations, and member experience — primarily in the soccer space. Soccer is one of LeagueApps' most profitable verticals, and the lack of a roster-building experience was a major source of customer churn.
Director of Coaching
- See roster gaps at a glance
- Balance teams by skill/age
- Bulk moves without data loss
- Trust an audit trail / history
Program Admin
- Bulk select + drag to teams
- Filter by payment/waiver status
- Resolve conflicts quickly
- Export clean rosters
Head Coach
- Player notes visible
- Simple swaps post-draft
- Mobile-friendly view
- Change notifications
League Ops
- Copy/move with history kept
- Avoid duplicates
- Cross-program visibility
- Clear permissions model
Admins are making decisions that can trigger registration invitations, cancel existing registrations, invalidate previously sent invites, and affect payments, invoices, and player expectations. The core problem was not "how do we move players" — but how do we give admins speed and flexibility without letting them accidentally cause irreversible outcomes they don't fully understand?
The original roster management workflow had five critical gaps:
- No visual overview of all teams and players simultaneously
- Rosters could only be built one at a time
- Fragmented visibility into custom form data (coach preference, school, teammate requests)
- Manual roster uploads done in spreadsheets outside the platform
- No safeguard against duplicate players or overfilled rosters