Client case study
ORÉA MAISON
ORÉA MAISON deals in gemstones and gold, out of London and by private appointment. We built the whole of it: the public house they send clients to, and the console the house itself works in every day.
- Sector
- Luxury jewellery
- Live
- 2026
- Surfaces
- Website, console
- Scope
- Design, build, run
ORÉA MAISON sells by private appointment and publishes no address, which leaves the website doing the work a salon would otherwise do. It has to carry the stones, set out how a commission runs, take the enquiry and put it in front of the right person, and never once look like a shop. It also had to be theirs to change, because a house that revises its own language cannot wait on a developer to do it.
Website/Admin console/Enquiry intake/Outbound mail
01
The website
Every page of it. The stone and jewellery catalogue, the house and bespoke pages, the appointment, brief and sell-a-stone forms, and the full legal set. Photography led, one typeface, no decoration that does not carry meaning.
02
The admin console
A second application, on its own domain, for the people who run the house. Stones and pieces are added and edited there, with images uploaded in resumable chunks so a large file on a bad connection still arrives.
03
Copy they own
Every line the public site prints is a record in the console. The house rewrites its own pages, saves, and the site says the new thing. No developer, no deploy, no waiting.
04
Enquiries that land somewhere
The forms on the public site post straight into the console. Attachments go to storage, the enquiry is filed against the house it belongs to, and the letters go out to the right desk rather than to an inbox nobody reads.
05
Mail that reports back
A composer in the console writes to a client, keeps the draft and a copy of what was sent, and shows the delivery state of each one. The house can see that a letter arrived instead of assuming it did.
06
Found, and read correctly
A search index built from the site's own content, a saved list held on the visitor's device rather than behind an account, and a generated llms.txt so answer engines describe the house the way the house describes itself.
The site has been live since 2026 and the house runs it without us in the room. Stones and pieces go up from the console, the copy changes on the day they decide it should, and enquiries land somewhere a person answers them. We are still behind it for the hosting, the upgrades and whatever they want next, which is what we mean when we say the work does not stop at handover.
Tell us what you are building. We scope it in days, build it in short sprints, ship it, and stay with it after it is live.