What they came with
An annual football pool that had outgrown its analog roots — picks by email, manual spreadsheets, and the occasional invalid choice.
What the conversation revealed
The pool's community ranged from an 80-year-old on an old iPad to a stats ninja with multiple browser tabs open. Every feature decision had to work for both — and everyone in between.
What we built
A modern pool platform with automated pick validation, real-time standings, and a two-layer statistics system designed around how different people actually make decisions.
What changed
The labor disappeared. The tradition didn't. And for the first time, every player — regardless of how seriously they took it — had something genuinely useful to go on.
Service areas
App developmentData analysis
Motivation
Improve efficiencies
Human factor

The same data had to work for an 80-year-old picking on instinct and a stats ninja with five browser tabs open.

Technology

Web app · Statistics engine · Data visualization · NCAA data integration

Friendly football pool

Building for every player

The labor disappeared. The tradition didn't. And for the first time, every player — regardless of how seriously they took it — had something genuinely useful to go on.

"Different stones. Same pool."

"Different stones. Same pool."

Some of our most interesting work grows out of relationships that started somewhere else entirely.

We had been working with a family medical practice for years — building their website, helping them migrate data between systems, designing a patient record repository. The relationship was easy and productive. So when the practice mentioned that their annual college football bowl pool had become more labor than love, the conversation felt natural.

The pool had been running for years as a cherished tradition. Players ranged from practice staff to colleagues, friends, and even a handful of patients. Every year, people sent in their picks by email. Someone transcribed those picks into a spreadsheet by hand. Someone else inevitably had to call Dr. Rob to explain that USC was not, in fact, one of the teams playing in the Rose Bowl — and was therefore not available as a pick. An easy mistake when you're working from memory and a long list of bowl games. But a phone call that happened every year.

The pool needed modernizing. That part was clear. What was less obvious — until we started asking questions — was what modernizing actually had to mean.

The human challenge

The pool's community spanned generations, devices, and levels of interest. An 80-year-old on a ten-year-old iPad. A twenty-something on the latest iPhone. Players who picked based on team colors or mascots. Players who had multiple browser windows open cross-referencing expert predictions and Las Vegas odds.

This wasn't a technical problem. It was a human one. Every feature decision had to work for both ends of that spectrum — and everyone in between — without making anyone feel like the system wasn't built for them.

We started with the fundamentals.

Automation and data integrity

The first thing we eliminated was the manual process. Players submitted their picks directly through the app. The system only offered valid teams for each game — no more invalid picks, no more tracking people down, no more spreadsheet. Picks were confirmed immediately. Standings updated in near real time as games completed.

For the people running the pool, the labor disappeared almost entirely. For the players, the experience became what it was always supposed to be — focused on the games, not the paperwork.

Statistics designed for every kind of player

Here is where the human challenge became most interesting.

Some players wanted data. Real data — not just win-loss records but a genuine picture of how each team had performed across the season. We pulled in every Division I game played that year and generated detailed statistics for every team. Including a strength of schedule calculation that went beyond simply looking at who a team had played — it accounted for the quality of each opponent's opponents, giving a more honest picture of whether a record had been earned or accumulated against weaker competition.

The challenge was making that data useful without making it intimidating.

We solved this two ways — one for each kind of player.

For the player who wanted to go deep, we built a dedicated research section. Selecting any team surfaced their full statistical profile. Terms like "avg. pts. scored — away" came with plain-language explanations available on tap. Each opponent in a team's schedule was a live link to that team's own statistics. Someone willing to spend time before the deadline had everything they needed.

For the player deciding between two teams while filling out their picks — and not wanting to leave the page to do it — we added a small stats icon next to each matchup. One tap opened a side-by-side comparison of the two teams' key numbers. No jargon, no deep dive required. Just enough to make an informed inference rather than a blind guess.

The research feature didn't change how everyone played. It wasn't supposed to. The mascot pickers kept picking mascots — and that's entirely legitimate. But the players who wanted more had something genuinely useful. And the side-by-side comparison gave every casual player a moment of insight they hadn't had before, without asking anything of them except a single tap.

The pool's tradition stayed exactly what it had always been — a community of people who enjoyed a friendly competition across a season of games. What changed was that nobody had to do the labor that surrounded it, nobody could make an invalid pick, and nobody — regardless of how seriously they took it or what device they were using — was left without something useful to help them decide.

Dr. Rob, for the record, no longer picks teams that aren't in the game.

The technology served the tradition. That was the whole point.




slug: football-pool
story: Building for every player
available...