Skip to content

Product & Technology Delivery

From One Franchise to a Platform

How a rugby club’s app became Envorso Sports

Client
Envorso — incubated and spun out, built with the Seattle Seawolves
Sector
Sports
Headline result
62%

The challenge

Building a fan app for the Seattle Seawolves solved one club’s problem: a passionate supporter base and no direct digital relationship with it. Then other Major League Rugby teams asked for the same thing — and the honest answer was that building it bespoke each time would not scale. The underlying problem was bigger than an app anyway. A professional sports organization typically runs its website, mobile app, ticketing, merchandise and CRM as five separate vendor relationships, with a different fan record in each, so the club can see five fragments of a supporter and never the supporter.

What we did

  • Started from a live engagement rather than a market thesis — the Seawolves app was the design input, and the demand from other clubs was the signal that it generalized.
  • Generalized the app into a modular platform of eight components: team website and content, mobile app, ticketing, merchandise and commerce, fan identity and CRM, marketing automation, in-stadium and game-day, and AI-powered personalization.
  • Built it around one fan identity and a single data layer from the start, rather than assembling acquisitions behind middleware — which is how most platforms in this category are put together.
  • Designed it for the rhythms professional sport actually runs on: seasons, game days, transfers, and fan communities.
  • Deployed four modules for the Seawolves as one system — the team site at seawolves.rugby, iOS and Android apps, ticketing at tickets.seawolves.rugby, and a unified fan profile behind all three.
A unified fan platform that enables us to engage with our customers across all shopping experiences — from ticketing to retail.
JoAnne Anderson, President, Seattle Seawolves Rugby
For the first time, the website, the app, ticketing, and CRM feel like one product. We can focus on building fan loyalty, not juggling vendors.
Noah Johnson, Manager of Ticket Sales, Seattle Seawolves Rugby

The practice behind this

Product & Technology Delivery

End-to-end delivery from concept to launch — the product operating model, cross-functional teams, CI/CD, Agile enablement, and a toolchain configured to carry it.

Read about this practice

Where AI fits here

AI here is an architectural decision made at the start, not a feature added later — and the reason it can be is that the platform holds one fan identity rather than five. A club running its site, app, ticketing, merchandise and CRM as separate vendor relationships has five partial records of the same supporter and no way to join them, which makes personalization impossible however good the model is. Unify the identity and the same data becomes usable: what someone watches, when they buy, which matches they attend, what they wear. That is the difference between recommending a fixture to a season-ticket holder who never misses one and recommending it to someone who has not attended since the season opener. It is also the argument Envorso makes to every other client — that the data layer has to be right before AI returns anything — applied to its own product rather than asserted in a deck.

Two hours to find out whether we recognise your problem.

No deck, no obligation. We listen, we tell you whether we have seen this before, and we say what we think it would take. If a Jump Start is the right next step we will say so — and if it is not, we will say that too.