Bring last season's roster, divisions and fields from a spreadsheet or your old app, and the setup agent drafts the season: divisions with birth-date windows, spot counts and the registration dates. You review the draft, fix what you want and approve it. Nothing is created until you do.
The scheduler proposes a season of games across your teams and fields, round robin inside each division, with practices beside them. When a field closes or games are rained out, rainout reflow proposes new times for the games that moved. Coaches and families are told only after your staff approve.
After registration closes, the team builder proposes balanced teams for each division from the registered players, honoring the requests you enter, such as playing with a sibling or a carpool. If your division holds tryouts, the builder uses the evaluations too. You review the teams, move players around and publish. Coaches and parents see their team once you do.
The family assistant answers parent questions from your schedule and documents, in their language. The coach copilot helps a coach draft the weekly message, check who is coming and plan a practice. The director agent answers the board's questions in plain words, such as which divisions are full, which families still owe a fee and which background checks are about to expire.
No. They draft, propose and answer. A person on your staff approves a schedule, a set of teams or a message before it reaches families.
The family assistant answers in the parent's language, and the whole app is translated into 250+ languages.
No. Every agent is optional, and everything it does can also be done by hand.
We build Bloomz for Sports Leagues to cost less than TeamSnap in total, processing included. League pricing is not published yet, so talk to us about founding leagues.
A short call about your divisions, your fields and the tools you use today, not a generic pitch.