OpenAI Travel and Hospitality Europe & UK

loveholidays

Application Refactoring · IT Operations Automation

loveholidays needed to let product, design, and commercial teams test and ship ideas without waiting for scarce engineering and platform specialists, while also making infrastructure and data changes easier to self-serve safely.

4x more Data Platform changes per support request
73% increase in AI-assisted deployment frequency
93% Data Platform change success, up from 58%
AI-assisted code changes grew from 7% to 79% in a year

Reported impact

Business outcome

loveholidays raised AI-assisted code changes from 7% to 79%, increased deployment frequency by 73% without more engineers, improved Data Platform change success from 58% to 93%, and lowered cloud-storage and processing costs while letting non-engineers ship new experiences.

  • Cost Reduction
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

loveholidays embedded Codex into both customer-experience prototyping and internal platform operations so more of the business could build software directly. Search Playground, built with the company's design system, frontend technologies, and Codex, lets non-engineers turn ideas into working travel experiences, gather feedback, and even launch them on the production site. Behind the scenes, the company encodes data-platform and infrastructure best practices, validations, and release checks into Codex-guided workflows so employees can propose changes, run validations, and move work through deployment without mastering every specialist tool. Codex has become a control plane across engineers and business users, so specialists spend less time handling routine requests and more time improving the platform. The result is an operating model where more experiments become products, deployments rise without more headcount, and data-platform efficiency improves along with cloud-cost discipline.

Data flow

Business ideas enter Search Playground through Codex, which uses loveholidays' design system and frontend stack to produce working experiences for feedback or launch. For infrastructure and data changes, users submit the intended change to Codex, which applies encoded best practices, runs checks, and guides work through release workflows.

Solution architecture

3 components · 2 layers
  1. Serving
    • Search Playground Lets teams turn new travel ideas into working customer experiences using loveholidays' own design system and frontend stack.
    • Inspire Me Shows how non-engineer-built experiences can become live discovery products on the loveholidays website.
  2. Orchestration
    • Codex Acts as the common interface for prototyping, infrastructure changes, validation, and release guidance across the business.

Architecture clues

  • Codex is becoming a single control plane shared across engineering and business users
  • Codex-guided workflows encode best practices and validations from platform specialists
  • Search Playground is built on the company's design system and frontend technologies

Evidence from the source

"A year ago, around 7% of its code changes were AI-assisted. Today, that figure is 79%."
"Its engineers created Search Playground using the company's design system, frontend technologies, and Codex."
"Successful AI-assisted changes to loveholidays' Data Platform have risen from 58% to 93%"
"The expertise of our data and infrastructure engineers is available through Codex"
Transparency Evidence & methodology 100/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    6 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    loveholidays customer story

    First-party
    https://openai.com/index/loveholidays/
    Source type
    Vendor-published customer story
    Published
    Aug 26, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.