This app started in a hockey locker room
Not a boardroom. Not a VC pitch deck. A locker room, after a game, when someone asked “wait, what’s our record?” and nobody knew.
The problem
A captain managing a hockey team with group texts, spreadsheets, and a lot of unanswered "who's in Thursday?" messages.
The first version
A quick app to track attendance and lineups. Built for one team. One sport. One frustrated captain.
The realization
Every rec league captain has the same problem — hockey, basketball, soccer, volleyball, flag football, softball, kickball, pickleball, tennis. The tools don't exist because nobody builds for adult rec.
Today
A full team and league management platform across 9 sports with the analytics and commissioner tools that rec leagues have never had.
What we believe
These aren’t marketing lines. They’re the decisions we make every day when building the product.
Rec leagues deserve real tools
Not enterprise software designed for travel ball. Not a stripped-down version of something built for professionals. Real tools, built from scratch, for the way rec leagues actually work.
Data should help you have more fun
We track stats and line chemistry because it makes game night more interesting — not to turn your beer league into the NHL combine. The data serves the fun, not the other way around.
Free should mean free
Not "free until we hook you." Not "free with ads so aggressive you can't use it." The core team management features are free forever because that's how you build something people actually adopt.
The best app is the one your whole team uses
It doesn't matter how powerful your team management tool is if only the captain opens it. We designed every screen for the player who checks it once before game day — and it has to work for them too.
Built by captains. For captains.
Rosterlytic isn’t backed by a sports tech conglomerate. It’s built by someone who plays rec sports every week, manages a team, and knows what it’s like to track stats on a napkin at the bar after a game.
Every feature exists because a captain needed it. Every design decision is tested against one question: “Would my team actually use this?”