Organizations
One club. Every team. One place to run it.
An organization account is for the person who oversees fourteen teams, not one. Your staff reach every team without being invited to each of them, teams arrive by import instead of by hand, and the club hosts its own leagues and tournaments.
We're building this now and talking to clubs while we do. Tell us how yours runs and it shapes what ships — and you'll be first in when it does.
How a club is shaped
Org roles are a separate axis from team roles — staff reach org teams without a per-team invite.
A coach can work at two clubs with a different role at each. Team roles keep working exactly as they do today.
What an organization account does
Built for the person holding fourteen rosters.
Everything a solo coach gets, plus the club layer above it. Nothing changes for the coaches themselves.
Every team under one club
Teams belong to the organization, not to whoever happened to create them. People leave; the club keeps its teams.
In buildStaff who reach every team
A director joins the club once, not fourteen times. Club roles are a separate axis from the coach and parent roles on each team.
In buildBring your teams in by import
Upload a CSV of teams — and rosters if you have them — instead of hand-entering a club's worth of jerseys. Re-runnable, so a fixed file doesn't create duplicates.
In buildOne approval queue for new people
Coaches ask to join a team with a code; the request lands in the club's queue and an admin or rep approves. Nobody gets write access by forwarding a link.
In buildHost your own leagues and tournaments
Competitions with divisions, standings and brackets, run by the club rather than tracked in a shared spreadsheet.
After the coreA public club page — with the children behind auth
Your club and its competitions can be found; rosters, player names and photos stay visible to invited members only.
After the coreBilling built for a club, not an app store
Per seat, monthly or annual, bought on the web. Clubs and schools that pay on a purchase order get invoiced with net terms.
Priced laterRoles
Four club roles, matched to how a club actually runs.
Club roles govern club-level actions and reach into the club's teams. They're separate from the coach and parent roles on each team.
| Club role | Create / import teams | Edit a team | Delete a team | Invite to a team | Leagues & tournaments | Manage staff | Billing |
|---|---|---|---|---|---|---|---|
| OwnerOne per club. The only role that can buy seats. | Any role | ||||||
| AdminEverything except billing. The working role for a club director. | Any role | ||||||
| RepresentativeBuilds teams out and brings people in — but can't dissolve anything. | |||||||
| StaffFront office. Reads everything, changes nothing. | Read only | Viewers only |
Staff can invite viewers, never coaches — otherwise "read only" wouldn't be true, since a staff member could invite an account that writes. Coaches and representatives arrive through the approval queue instead, which puts one control point on write access.
Seats
You pay for teams and club staff. Nobody else.
Parents, players and anyone following a game never pay, and never count.
One unit covers both, so the number on your invoice is a single count you can check yourself. Per-seat pricing isn't set yet — that's part of what we're asking clubs about.
- The team is the billable unit. Once a team is paid for, put as many coaches on it as you like — they don't add seats.
- People are counted once. Someone holding three roles across four teams is one person, one seat.
- Checked when you add, never afterwards. Adding a fifteenth team past your seat count asks you to buy a seat; nobody already working loses access mid-season over billing.
- Deleting a team frees its seat. Archiving doesn't. An archived team keeps its history and can come back.
- Monthly, annual, or invoiced. Clubs and schools on a purchase order get an invoice with net terms instead of a card form.
Not in the first release
What we're not going to pretend about.
If one of these is the reason you'd switch, say so in the form — it's how we'll decide what comes next.
- Collecting family fees
- Taking registration money from parents on the club's behalf is a payments marketplace, not a button. It's specced as its own phase, deliberately after this one.
- Cross-team reporting dashboards
- Per-team box scores and season averages are there today. Club-wide analytics across every team are not.
- Buying seats inside the iPhone app
- Club billing lives on the web. Individual coach Pro is bought in the app; a club's seats aren't.
- Anything between clubs
- Shared scheduling with another club, or moving a player from one club to another, isn't in this release.
Are you interested?
Tell us about your club.
Organization accounts aren't open yet. Say you're interested and you'll be first in — and what you tell us here decides what ships first.
You're on the list.
A person will reply, usually within two business days. If your season starts sooner than that, say so in a reply and we'll move.
What happens if you say yes
- We read it. Not a form queue — the person building this reads it.
- We reply with a straight answer on whether Statra will fit your club, including when it won't.
- You go on the early list and we set the club up with you when organization accounts open, rather than mailing you a signup link.
Paying on a purchase order?
Mention it in your message. Invoiced billing needs a few details from your finance office, and that's easier to start early than at the point you want to be playing games.
Not a club?
A single team won't need an organization account. The main page covers what Statra does courtside.
Back to StatraQuestions clubs ask first
Before you bring it to your board.
Can we be invoiced instead of paying by card?
Yes — clubs and schools that pay on a purchase order get an invoice with net terms. Self-serve card billing exists for clubs that prefer it, monthly or annual.
Do parents have to pay for anything?
No. Coaches and clubs pay; parents and anyone following a game never do, and they never consume a seat.
Who can see our players?
Invited members only. A club can have a findable public page and public competition results, but player names, rosters and photos stay behind authentication. We're building this for children's sport and treat that as a hard line, not a setting.
What happens to our data if we leave?
It's your club's. Deletion means deletion, not a hidden archive — that's designed into the data model rather than bolted on. Ask in the form and we'll walk you through exactly what's stored.
Does an organization account change how coaches work?
No. Team roles, stat-taking and the live feed behave exactly as they do for a solo coach. The club layer sits above that — a coach on a club team just finds their team already set up.