Shrink the scope
I proposed integrating the experience into the company's existing platform instead of launching a separate website. It reduced the implementation scope, which was the only way to meet the timeline.
Case study 02 — Delivery under pressure
A high-traffic booking experience, shipped on a fixed deadline, that supported about $20,000 in revenue per match event.
( 01 ) — Context
The Sailors needed World Cup ticket booking for its customers. The tournament dates were fixed, and the timeline was highly constrained.
The challenge
High traffic, a booking flow customers could trust with their money, and very little time.
( 02 ) — The options
Option A
A separate World Cup website
A clean start, but everything to build, test and launch from zero.
What we went with
Inside the existing platform
Reuse what the platform already had, and build only what was new.
( 03 ) — What I did
I proposed integrating the experience into the company's existing platform instead of launching a separate website. It reduced the implementation scope, which was the only way to meet the timeline.
I built and launched it with React, TypeScript and Material UI, working with product, design, management and backend.
Traffic spiked whenever match tickets opened. I kept the booking path minimal, cached match information and lazy-loaded the heavy parts.
The result
Booking stayed usable during the peaks, and the experience supported about $20,000 in revenue per match event.
Lesson: Under a fixed deadline, reuse is an engineering decision, not a shortcut.
( ✦ ) — Related
Next case study
Choosing Next.js for a multi-store SaaS platform→