Club OS for grassroots football
Fball.vn
Turn a scattered match plan into a repeatable rhythm for the whole team.
Fball connects club operations — schedules, attendance, lineups, members, permissions and the team fund — with live public discovery for finding teams, arranging matches and browsing venues.
CASE STUDY
Fball.vn
Turn a scattered match plan into a repeatable rhythm for the whole team.
Fball connects club operations — schedules, attendance, lineups, members, permissions and the team fund — with live public discovery for finding teams, arranging matches and browsing venues.
Context
- Before a match, a captain needs three answers: when are we playing, who is coming and how will the squad be split. Those answers often live across long chat threads and hand-built lists.
- Fball gives each club its own workspace, making recurring coordination visible while preserving the flexibility of grassroots football.
- Public surfaces for finding teams, arranging matches and browsing venues are live; provider-cost modules such as AI, media and messaging remain gated by configuration or feature flags.
Key decisions
- Make attendance shared state, not another chat message.
- Build the match-day loop before expanding the platform.
- Keep captain controls distinct from the member experience and require confirmation for automation.
Current outcomes
- A public product connecting grassroots club operations with match discovery in Vietnam.
- A core loop covering schedules, attendance, lineups, membership, permissions and the team ledger.
- Finding teams, arranging matches and browsing venues are live; AI, media and messaging remain behind configuration or feature flags.
The challenge is not adding screens. It is keeping teams, permissions and state correct as a match-day tool grows into finance, discovery and automation.
