What happens to the existing site, the mail@ inbox and the guestandphilips.co.uk domain?
The domain stays, only the hosting moves. The site moves from the legacy Apache CMS to Astro on Vercel. The mail@guestandphilips.co.uk mailbox is left untouched; per-branch addresses (beverley@, cottingham@, driffield@, pocklington@) can be added if you want individual branches to take their own enquiries. Legacy hosting bill is cancelled, savings depend on what you currently pay, typically £30-50/month freed up). Every customer who emails after launch sees the same address they used before, plus optional per-branch routing.
I do not have a brand book or a designer on hand. Are you going to make us commit to a single design now?
No. The preview at /preview/ is one direction worth opening with, the honey-stone-and-antique-brass palette is sampled from Beverley Market Cross stone and the antique jewellery itself, but treat it as one option in the conversation, not a final commitment. The price covers one round of revisions before launch, and the design tokens (colours, fonts, type scale) live in a single file that takes minutes to retune. If you want it greener, more Minster-stained-glass, or closer to your existing logo, that retune is included.
The four branches, do they really each need their own page, or is that overkill?
They each need their own page. A customer in Cottingham searching "jeweller Cottingham" is not landing on a generic "Our Stores" list, they want a page that confirms there is a Guest and Philips at 22 Finkle Street, with the Cottingham phone, the Cottingham hours, and a photo of the Cottingham shopfront. Same for Driffield. Once each branch has its own page with proper LocalBusiness schema, Google’s map results for "jeweller Cottingham" and "jeweller Driffield" begin pointing at you instead of the next-best alternative. The same content effort, one page per branch, is what the chain jewellers already do.
How does the antique collection get added to and updated on the rebuild?
Two options. (1) Keep the existing legacy CMS as the source-of-truth for stock; the new Astro site pulls from it on each build (overnight, or on demand). Karen and Philip keep adding stock the way they already do; the new site just renders it properly. (2) Replace the legacy CMS with a small CMS-like admin where new antique pieces are dropped in with a photo, gemstone list, period, price and reference number, and on the next build they appear in the antique grid with proper schema. Option (1) is what we ship first; option (2) is available as a follow-up if the legacy CMS becomes a maintenance burden.
How does this compete against Hatton Garden online dealers and the chain jewellers for the big-ticket sales?
It does not compete on marketing budget, Hatton Garden specialists spend dozens of times Guest and Philips on AdWords. It competes on the queries those dealers cannot answer convincingly. "Antique engagement ring Beverley" (the Hatton Garden answer is "we ship from London"; the Guest and Philips answer is "Karen will sit down with you in the Saturday Market shop next Tuesday"). "Cartier authorised dealer East Yorkshire" (the chains have it but bury it; the rebuild surfaces it). "Vintage Rolex Driffield" (a four-shop regional specialist with 60 years of stock; nobody else is competing). With Organization + LocalBusiness + Person + Service + Brand + FAQPage schema, those queries become Guest and Philips territory.