Case study
Membership, payments and scheduling platform for a youth sports club
- The problem
- A club running on spreadsheets, a small hand-built admin panel, and a lot of individual know-how, as it grew past what any of that could carry.
- What was built
- One system covering members, teams, events, attendance and payments, in place of spreadsheets and one-off pages built over the years.
- What changed
- Payments, refunds and per-family balances, waivers and consents, and who can see what, all in one place instead of several.
Where it started
A US youth sports club ran on a website with a small custom admin panel, a set of one-off pages built over the years, and a great deal of knowledge held by the people who had always done the job. As the club grew, that stopped working.
What replaced it
What replaced it covers the whole operation:
- Members and families — players, parents, coaches, with parents linked to their children and able to grant permissions on their behalf
- Teams and seasons — rosters, schedules, tournaments and league types, with pages published or held back as needed
- Events — training sessions, camps and tryouts, with bulk creation, invitations, registrations and volunteer assignment
- Attendance — recorded and verified against each session
- Payments — card payments, cash and card handling at the desk through a point-of-sale tool, payment plans and instalments, refunds, and outstanding balances tracked per family
- Documents and consents — waivers and permissions collected and stored against members
- Who sees what — coaches see only their own teams, cashiers only what they need, and administrators everything
- Communication — automated emails through the registration and payment lifecycle, an internal messenger, club and player news, and a log of everything sent
What makes this kind of system hard
The pieces that make this kind of system difficult are rarely the obvious ones: a payment that has to be refundable months later, a parent who needs to act for two children on different teams, a coach who must not see another team's data, a cash payment taken at a desk that has to end up in the same ledger as a card payment taken online.
How it unfolded
Requirements on a project like this rarely arrive all at once — why asking for one thing at a time costs more is the longer story behind how this one actually unfolded.
If your own project is arriving one request at a time, the Admin Automation Audit is how I'd see the whole job first, or work out what the same patterns cost.
Recognise this in your business?
Tell me which task takes the most time, and we'll see whether it's worth fixing.
Book a free 20-minute call