SafeSwitch case study · Private members club, London · 21 September–4 November 2026 · from the site’s GitHub history

ARRIBA moved its website onto Chad: 38 changes in six weeks, a median of 3 minutes to approve, and nothing live without a yes.

ARRIBA, the private members house above Arros QD in London, wanted to launch its membership: three tiers, a cultural programme of events, and its food and wine menus, on a site the team could keep current themselves. SafeSwitch moved arriba.london onto Chad’s managed setup, and the team has run it since by asking Chad for changes in plain English and approving a preview, with no development queue.

The headline numbers

21 September to 4 November 2026, from every merged change to arriba.london.

Changes shipped
38
35 through Chad, 3 by a developer
Median time to approve
3 min
32 of 35 Chad changes within the hour
Pages live
12
from 5 on the old site, all in the sitemap
Development queue
None
six weeks, 21 Sep to 4 Nov

The switch: what SafeSwitch carried across

Before anything new was added, the basics a business relies on: its old addresses, its forms, its search signals and its consent banner.

Previous site addressOn arriba.london today
/Works
/book-a-tourWorks
/enquiryWorks
/member-formWorks
/contact-formRetired: replaced by /book-a-tour and /member-form, both reached from /enquiry
Foundations first

The first six changes were search and compliance basics: a canonical URL, homepage structured data and Open Graph metadata, GA4 cookie consent controls, and enquiry forms rebuilt so submissions are delivered. Four of the five addresses from the previous site still work. The fifth, the old /contact-form, was deliberately replaced by two forms, Book a tour and Apply for membership, both reached from /enquiry.

Nothing goes live without a yes, and anything can be undone

The parts of the record that matter most to a business handing over its website.

Changes not approved
8
closed without going live
Changes rolled back
1
undone in one step
Waiting for a decision
3
open, not live
Old addresses kept
4 of 5
the fifth retired on purpose
The approval gate works

Eight changes Chad proposed were closed without going live, most because a revised version replaced them, and three more are waiting for a decision. A proposed change has no effect on the site until it is approved. When a Food & Drinks page build was not right, it was reverted in a single step and rebuilt a few days later.

38 changes in six weeks, in four stages

Each change was asked for in plain English, opened by Chad on the site’s code, sent as a private preview, and went live only once someone at ARRIBA approved it.

  • Foundations (21 Sep – 1 Oct, 6 changes) — Search basics, cookie consent and working forms, before anything new was added: a canonical URL, structured data and Open Graph metadata on the homepage, GA4 consent controls, and enquiry forms that deliver.
  • Launch pages (2 – 12 Oct, 17 changes) — The Memberships, Cultural Programme and Food & Drinks pages, the wine list, cookie and privacy pages, navigation, a robots file and XML sitemap, and corrected titles and structured data.
  • The members club (22 – 27 Oct, 10 changes) — A page for each membership tier (Society, Patrón and Corporate) with apply buttons, the favicon, and the first Cultural Programme events.
  • Running it week to week (29 Oct – 4 Nov, 5 changes) — New events, new menus and small design changes, asked for and approved in minutes.
Six weeks after the rebuild began, arriba.london had grown from 5 pages to 12, with a page for each membership tier and a cultural programme the team updates itself. Median time from a proposed change to approval: 3 minutes.

How we measured this

  • Every figure comes from the merged GitHub pull requests on the arriba.london repository, read on 4 November 2026. Approval time runs from Chad opening a change to its approval.
  • This case study makes no traffic or revenue claims. It shows how the site was moved and run.
  • A developer handled 3 of the 38 changes (the form delivery set-up, a form fix and the rollback) and worked directly on the code at times, so the claim is no development queue, not no developer.
  • The previous site was a small custom build of 5 pages, not a move off a CMS such as WordPress. ARRIBA asked for new pages from the start, so the site was grown as well as moved.
  • Old addresses are from the Wayback Machine (July 2026), checked against the live site.

Moving your own site? See how SafeSwitch works, or more client results in the case studies.

How does your site look to Chad?

Drop your domain. In 11 seconds you get your GEO score, your biggest gap, and the first thing Chad would fix.

Free scan, usually under a minute. No sign-up.