01
Schedule
Events, recurrence, and a calendar feed that lands in the phone people already use. When something moves, the message says exactly what changed — “practice moved from 6:00 to 6:45” — instead of “the schedule was updated”.
Pre-season — not yet public
The operating system for a hockey association.
Association-grade governance, money, and ice management underneath a team app people actually want to open — connected to the registry you already have to use.
Being built now, in the open, for the 2026-27 season. The first thing it does is the thing every team fights with weekly: getting a straight answer on who is coming.
U13 A · Practice
Availability
Be at the rink
5:45PM
Ice 6:15 – 7:15 pm · Bell Arena, Pad 2 · Room 4
14
Yes
2
No
1
Maybe
2
Silent
17 of 19 in 3h 12mGoalies 2 / 2
The screen a coach actually needs
01 The stack you’re running now
Nine tools, none of which talk to each other.
Data gets re-keyed three to five times a season. The ice scheduler is one volunteer with one spreadsheet. The team treasurer is holding four thousand dollars in a personal chequing account.
Associations don’t churn because of features. They churn because the one person who understood the system moved on when their kid aged out. The real product problem
Registration & paymentsSportsEngine / RAMP / Jotform + e-transfer
Roster of recordHockey Canada HCR / USA Hockey Registry — stays
Ice schedulingA spreadsheet owned by one volunteer
Game scheduleLeague system, re-keyed into a team app
Team commsTeamSnap + a group text + a Facebook group
Money at team levelA parent’s bank account and a spreadsheet
VolunteersA signup sheet taped to the glass
EquipmentA garage and institutional memory
TournamentsEmail, PayPal, and a laminated bracket
We don’t replace your registry
Hockey Canada’s HCR and the USA Hockey registry are the roster of record, and they should stay that way — that is where insurance and eligibility live. ClubHQ reads from them and reconciles against them. What we replace is the re-keying: the same twenty families typed into a registry, a team app, a spreadsheet and a group text.
02 The daily loop
Schedule, availability, chat — done properly first.
Every association platform starts at the top and hopes the families follow. We start where the habit is: the seventeen parents trying to work out whether Tuesday is a practice or a game.
02
Availability
One question, one tap, from the notification. Standing rules for the family that never misses. Goalie-aware, because two goalies is a practice and zero is a skate.
03
Chat
Announcements with read receipts. And no adult can message a child privately: a parent and a second adult are always in the conversation — the safe-sport “two-deep” rule, enforced by the software rather than by a policy nobody reads.
No account · No install
A guardian answers straight from the email link. No password to reset in a rink parking lot in February, and no thirty-family install campaign before the tool is worth anything.
03 Where the difference lives
Five things the incumbents don’t do.
01
Ice as a first-class resource
Arena contract → slot inventory → allocation → chargeback, modelled end to end. It is 60–75% of an association’s budget and nobody treats it as data.
02
Works in a concrete arena
Offline-first schedule, roster, attendance, and scoring. Every competitor fails at the blue line where the signal dies, and everybody notices.
03
Ambient compliance
Certifications, screenings, and roster eligibility show up as a live state on the team you’re about to ice — not a report someone has to remember to run.
04
Safe by default for minors
A child is never in a private conversation with an adult — a parent and a second adult are always included. Guardians see what their own child sees. Real consent records, retention and export. Built into the data model, not bolted on as a policy page.
05
Money with real controls
Per-team ledgers, approval thresholds, and separation of duties — so no parent ever again holds team money in a personal account.
04 Where it stands
Honest about the stage.
The plan, the data model, the permission system, and the first slice of the product are written. Nothing here is a shipping product yet — the alpha runs with a small number of real teams this season, and we’d rather say so.
Now
Alpha, with real teams
Mobile web — nothing to install. The manager builds the schedule; the families answer from email.
- Schedule & roster
- The availability loop
- Roster import from your registry export
- Calendar feeds
Next
The association layer
What a board buys: registration that turns into a roster with no re-keying, and money that reconciles.
- Registration & payments
- Registry import & reconciliation
- Eligibility & certifications
- Treasurer’s ledger
Then
Ice & operations
The part nobody models, where the money actually is.
- Contracts → slots → allocation
- The swap market
- Volunteers & equipment
- Tournaments & game sheets
One identity, every org
The parent with three kids in two associations is the hardest user in this category, and the one we designed for on day one.
Access is not a hierarchy
Being able to administer a team is not the same as being able to read a child’s medical record. Sensitive data is a separate, audited dimension.
Data stays in Canada
Postgres in ca-central-1, Canadian email delivery, no ad tracking, no open-tracking pixels in mail to families.
05 Design partners
We’re looking for a few teams for this season.
Not a waitlist and not a pilot fee. A handful of managers and coaches who will use it in-season and tell us plainly what’s wrong with it. Association boards welcome too — if you’re deciding for 2027-28, we want to be in that room early.
What we ask
- One real team, one real season
- Twenty minutes on the phone every few weeks
- Blunt feedback, including “this is worse than the group text”
What you get
- Free, permanently, for your team
- Your schedule set up for you — we do the data entry
- Direct line to the person building it
- Your data exportable on request, always