A booking front end rebuilt on the edge, without touching reservations
Bayt Travel needed a faster, clearer path to booking across the Gulf — without a risky migration of the reservation system underneath it.
Objective
Bayt Travel sells across several Gulf markets, where most of its traffic arrives on mid-range phones over mobile networks. The existing site was rendered by a monolith that also ran reservations, so every marketing change carried operational risk.
The ask was narrow and correct: make the booking journey fast and editable, and do not put the reservation system in the blast radius.
Solution
We put a new front end on the edge and left the reservation engine untouched behind an API boundary. Content and merchandising moved into a model the marketing team owns, so campaign changes no longer queue behind an engineering release.
Performance was a budget agreed before design: a template-level LCP target measured on real devices in the markets that matter, enforced in CI rather than checked at the end.
Outcome
The booking journey now renders in the markets it serves rather than in a lab, and the marketing team publishes without a deployment.
Because the reservation system never moved, the migration had no operational failure mode — the worst case was a front end rollback measured in seconds.
What’s next
We are extending the same content model to the retail surfaces, and instrumenting the funnel so that the next round of work is argued from data rather than opinion.
“The site finally feels like the brand, and nothing we changed put bookings at risk.”Bayt TravelDigital team
