← Work / Midseason

Case study · Founder work

An AI-powered sports marketplace that processed $250K+ in its first 90 days.

  • Strategy
  • UX/UI
  • Design system
  • Development leadership
Role
Founder & product lead
Team
Lean founding team — I oversaw our developers
Timeline
April 2024 — 2026
Platform
iOS · Android · Web

Midseason — the AI-powered sports marketplace

The 90-second versionSkip to outcomes ↓

The problem

Sports organizations run on fragmented admin tools while athletes have no central place to discover events, courts or community.

My role

I owned strategy, research, UX/UI, the design system and go-to-market, and oversaw our team of developers.

$250K+Processed within 90 days of launch
11,696Matches generated
3,000+Users
01 — ContextWhy this, why now

Club sport runs on software that treats sport as admin work.

Organizations stitch together registration, scheduling, payments and communication from tools that were never designed for them. Athletes get the leftovers: no central place to find events, courts or community.

Midseason was the marketplace answer: one AI-powered platform connecting both sides across mobile and web. Volleyball first, on purpose — a single sport keeps the cold-start problem winnable and the product opinionated.

02 — The two-sided problem

Every decision has two customers.

Athletes want

  • Discovery — events, leagues, courts near them
  • Profiles that get them seen and scouted
  • Simple sign-up and payment
  • Community around their sport

Organizations want

  • Registration that runs itself
  • Payments without the paper chase
  • Insight into their leagues and members
  • A pipeline of new athletes
Midseason discover screen — events plotted on a dark map
Discover. Events on a map, not in a list.
Midseason event list with status badges such as Closing soon and Near capacity
Discover. Status badges do the talking.
Midseason registration flow where a parent selects dependents to register
Register. Parents book for dependents in one flow.
Midseason league leaderboard
Leaderboard. League-wide, updated after every session.

The athlete side

03 — Decision 01 · AI search & discoveryProblem → options → call → shipped

Finding your sport should feel like the sport.

The problem

A plain search box over early-stage inventory returns empty results — and empty results teach athletes to never come back.

The options

Three ways to make discovery work on a young marketplace.

Option ARejected
An AI chat assistant bolted on top
Great in a demo, hollow in daily use.
Option BRejected
Classic filter-and-browse taxonomy
Works only when inventory is deep.
Option CChosen
AI inside the surfaces athletes already understand
Search, profiles and dashboards — invisible as a feature, useful as a behavior.

The call & the cost

It demos less flashily and took longer than wrapping an off-the-shelf chat UI. The win: AI that personalizes results athletes were already asking for.

Shipped

Intelligent search across events and organizations, plus map-based court and venue discovery — courts were real even before inventory was deep, so the app was useful on day one in a brand-new region.

AI that has to be discovered as a feature has already failed.
Midseason intelligent search results
Intelligent search. Results personalize to sport, level and region.
Midseason map discovery of courts and venues
Map discovery. Courts and venues as the entry point.
04 — Decision 02 · Marketplace payments

The marketplace isn’t real until money moves.

The problem

Club sport money moves through e-transfers, cheques and spreadsheets. For a marketplace, payments aren’t a feature — they’re the proof the model works.

The options

Launch free and add payments later, or carry marketplace payments from day one.

Option ARejected
Launch free, add payments “later”
Less build, less compliance, less risk — and it proves nothing.
Option BChosen
Payments in v1, built on Stripe
The heaviest lift in the product. Revenue is the only validation that doesn’t lie.

What happened

$250K+

in transactions within 90 days of launch.

Organizations trusted the rails enough to move their registration revenue onto a brand-new platform — run by clubs, paid by parents, in three regions.

Midseason checkout summary listing athletes and fees with a Pay button
Checkout. One summary, every athlete, every fee, one tap to pay.
Midseason registration screen
Registration. Designed for the athlete-and-parent side.
05 — Design systemA strategic bet

One system, every sport.

The design system was mobile-first and token-driven — color, type and spacing as tokens, components built once and reused across the athlete app, the organization surfaces and the web platform.

Volleyball was a theme, not a hard-coding. Expanding to the next sport meant re-theming the product, not redesigning it. Spend once, flex forever.

Six registration status badges: Closing soon, Near capacity, Waitlist open, Past event, Registration closed, Registration open
One component, six registration states
06 — OutcomesShipped on mobile + web

Built to grow with every sport it touched.

$250K+Processed within 90 days of launch
11,696Matches generated
3,000+Users
From a Midseason customer

“Nathan has shown a great amount of care when it comes to our experience using Midseason. He quickly developed a deep understanding of how we operate as a league and business.”

Shane HydeOwner, Oceanside Outdoor Sport
From the players
I registered 2 spring doubles teams today using Midseason. Super easy process! Love the app!
JenParent · registered two youth teams
07 — ReflectionWhat I’d tell myself in April 2024

What I learned.

  1. 01

    Two-sided means everything ships twice

    The smallest thing that serves both sides, or it doesn’t ship.

  2. 02

    Payments-first was the right hard call

    Usage can flatter you; revenue can’t.

  3. 03

    Constraints were the best design tool

    Every constraint I resented made the product more focused.

  4. 04

    A marketplace is operations, not just product

    The screens are half the job.

Next case study

All work ↗