All work
Case study · MLSE

Four franchises. One platform. Every opening night.

Role

Director of Product Design

Scope

Multi-app ecosystem

Toronto Maple Leafs app Toronto Raptors app Toronto FC app Toronto Argonauts app
Team

PMs, designers, engineers across four apps

Timeline

2018·25

Protected

The rest of this case study is password protected.

It carries client figures and material that is not public. If Eugene sent you here, the password came with the link.

During COVID, mobile slipped to a supporting channel. I made the case for it as a strategic lever for fan experience and revenue, then led the rebuild. Four team apps shipped in the same year, on a reliability-first foundation.

Page views
+693%
↑ vs pre-launch
Dwell time
+283%
↑ vs pre-launch
Unique users
+154%
↑ vs pre-launch
App ranking
#1
↑ Sports category, iOS
Leafs app, App Store
One year, four opening nights

Four launches, and not one of the dates was ours to move.

Each app had to be live before its own team's first home game. TFC in March, the Argonauts in June, the Leafs and Raptors in the same October. Two-month design and build cycles, four times over.

Jan
Apr
Jul
Oct
TFC · Mar
Argos · Jun
Leafs · Oct
Raptors · Oct
The problem

Strong traffic, shallow trust.

MLSE's team apps had evolved independently, each solving the same problems in slightly different ways. That left fragmented fan experiences, duplicated internal effort, and no shared read on why engagement fell off after the final score. Fans opened an app for tickets or scores, then left.

Worse, the apps failed at the exact moments they existed for. tickets not loading at the gate, freezes during game moments, forced reinstalls. If mobile was going to matter, it had to work as one ecosystem, and it had to be trusted first.

48/100

Security score, FY23 baseline

a failing grade on game day

150K+

Crashes per season

across the four apps

$500K+

Revenue at risk

sponsorship value eroding with fan trust

The move

Reliability as the growth thesis.

Nine pillars across three areas, with reliability underneath all of them. Fans who trust the app at the gate open it earlier and use it more.

For the fansWhat made the app worth opening
01

Clear navigation and content discovery

Fans needed to find scores, highlights, tickets, and news without friction. The new structure prioritized intent-driven navigation, moving between live content, team updates, and ticketing in a few taps.

02

Deeper engagement beyond scores and tickets

The app evolved from a utility into a daily destination. Personalized content, richer video, and interactive features brought fans back between games and kept them connected year-round.

03

Real-time experiences that respect attention

Live Activities and in-app updates delivered real-time scores and moments without drowning fans in notifications. Informed, with control over how and when they engaged.

For the businessWhat made it worth funding
04

Seamless continuity across revenue channels

Ticketing, retail, and partnership integrations stayed stable through launch. The transition was invisible to fans and partners, protecting critical revenue streams while opening room to optimize.

05

Sustained growth in engagement and retention

Month-over-month increases in active users, dwell time, and content consumption showed the new experience driving measurable business value and stronger fan loyalty.

06

Actionable insight into fan behavior

Unified analytics gave a clear view of what fans were doing, when, and why, so marketing and partnership teams could make data-informed decisions and refine campaigns in real time.

Across the platformWhat made it repeatable
07

Shared architecture and design system

A single foundation supported multiple team apps, reducing duplication and ensuring consistent quality. Build once, deploy across brands with minimal rework.

08

Standardized analytics and instrumentation

Every app captured data the same way, enabling cross-team comparison and faster learning. Consistency turned analytics into a strategic asset instead of a maintenance burden.

09

Scalable operating model for future seasons

Repeatable processes for design, development, and release. New features ship faster and at lower cost, season after season, across all team apps.

A crowd outside Scotiabank Arena at night, phones raised, confetti in the air during a championship celebration
What shipped

Four apps, ahead of four opening nights.

Each app shipped on a two-month design and development cycle, on a vendor platform pushed well past its out-of-the-box feature set.

Raptors app home screen Argonauts app home screen Toronto FC app home screen Maple Leafs app home screen

Seasonal launches at scale

4 seasons, 4 apps, shipped ahead of opening nights on tight 2-month design and dev cycles.

Partner-ready inventory

Repeatable placements with attribution reporting, built for sponsorship scaling.

Segmentation foundation

20+ segments, CDP integration, event and location-based targeting.

Vendor strategy

Vendor platform as baseline, evolved beyond its included feature sets to execute the vision.

Engagement + utility features

Live Activities, PiP video, interactive ads, personalization surfaces.

Governance + quality gates

Release-readiness discipline for live events.

MLSE app ecosystem overview
The numbers

It performed on game day, when it mattered.

Stability and security rebuilt fan trust, cut support load, and removed friction at entry. The shared foundation protected core revenue streams and unlocked new ones.

Security score
82/100
↑ 34 pts from a failing 48
Crashes
45K
↓ 70% from a 150K+ baseline
Game-day support tickets
−48%
↓ from 42 per home game
Food & beverage
$1.62M+
↑ 13% over the $1.43M target
Advertising
$1.2M+
↑ 2× the $600K target
Partnerships
$1.43M
↑ 43% over the $1M target
New feature revenue
$794K+
↑ net new for the fiscal year
From features that did not exist the season before
Video views
+4102%
↑ averaged across the apps
App downloads
+56%
↑ across all four apps

Leafs

Jul 2023 to Jun 2024
$764K
Mobile order revenue
↑ 18% YoY
22%
Ticket scans via app
↑ 4% YoY
405K
MAU season average
↑ 9% YoY
Monthly active usersThousands
550K 275K
JulOctFebMay

Raptors

Jul 2023 to Jun 2024
$626K
Mobile order revenue
↑ 22% YoY
18%
Ticket scans via app
↑ 3% YoY
310K
MAU season average
↑ 11% YoY
Monthly active usersThousands
550K 275K
JulOctFebMay
Learnings

Reliability is a growth lever

In live-event contexts, trust is the funnel. When fans believe the app won't fail at the gate, they open it earlier and use it more.

Governance is speed

A centralized design system and shared patterns cut development time across four apps at once. Consistency wasn't the tax; it was the accelerant.

Vendor platforms are baselines

Out-of-the-box is a starting position. The vision came from pushing the platform's APIs past their included feature set.