About PuckDesk

Two brothers.
One rink.

We built the tool we wished existed — because we were tired of running a program out of six different tools ourselves.

Why we're building this

Every program we've been part of runs on the same patchwork: a group chat for lineups, a spreadsheet for the roster, a shared photo album for scouting clips, and a notebook that lives in one coach's bag for player notes.

It works, technically — right up until the coach with the notebook takes a job somewhere else, or the spreadsheet gets a broken formula three weeks before playoffs. We wanted a system built specifically for how a hockey staff actually works, not a generic project tool with a puck icon slapped on it.

“We got tired of running a program out of six different tools — so we built the one we wished existed.”
Who's building it

A two-person shop, split down the middle.

NW

Backend, Infrastructure & Distribution

Co-Founder

Owns the database, multi-tenant architecture, auth & roles, external data integrations, and getting the product in front of real programs.

BW

UI/UX & Feature Design

Co-Founder

Owns the product experience end to end — from the on-ice whiteboard to the lineup card your staff prints before puck drop.

Where we are

Our 3-month build plan.

We're heads-down building toward a beta with real teams this season.

Weeks 1–4

Foundation

Auth, multi-tenancy, and the roster & lineup builder — the core every other system is built on.

Weeks 5–8

Practice & performance

Practice whiteboard, strength & conditioning tracking, and player notes.

Weeks 9–10

Scouting & billing

Scouting module, external roster sync, and subscription billing.

Weeks 11–12

Beta & launch prep

Beta with one or two real teams, fix what breaks, and get ready for the pilot season.

Want to be one of our first two pilot teams?

We're looking for programs willing to trade feedback for a free season and locked-in pricing for life.

Apply for the PilotLimited to select programs this season