← All workMajor international sports tournament · GCC

The tournament that couldn't move its date.

Digital Experience Platform for a Global Sporting Event
The problem

A host committee needed two digital products live and load-tested before a six-week tournament of 92 games across 4 venues. The hard part was the integration surface: 22 third-party systems spanning ticketing, biometric entry, indoor positioning, payments and government platforms, most with vendors not yet selected at kickoff.

What we built

A single Flutter codebase for both app stores, backed by a Node.js and NestJS integration layer. The 22 integrations were sorted into 4 risk tiers, so live vendors started on day one while unselected ones moved through change control off the critical path.

FlutterNode.jsNestJSAzureCI/CDBiometricsIndoor positioning
What it does
01

Fan and volunteer in one app

Onboarding, live scores, biometric entry, wayfinding, in-venue commerce and volunteer scheduling on a dual-persona build.

02

Sequenced to the fixed date

Website and ticketing were built first to protect the immovable deadline, with live operational dashboards behind them.

03

Senior team, full handover

A team of ten across the full stack with on-site presence, Azure dev, UAT, staging and production with CI/CD from phase one. Full source and IP handed over at close.

By the numbers
14 monthsWebsite and ticketing delivered ahead of the tournament
35–40%Less mobile delivery effort than separate native builds
22Integrations with zero critical-path slippage
0Core schedule re-baselines despite late vendor specs
What it changed

The tournament got its products early, and late vendors never touched the date.

Start here

Bring us the business problem.

Tell us what it's costing you. We'll tell you honestly what we'd build, and what we wouldn't.