Est. 1766
London · New York
Hong Kong · Tokyo

Case study · UHNW editorial platform · shipped 2021

Luxury, defined —
then engineered.

Hired as a Web Application Developer for a 260-year-old house's real-estate division. With no designer and no PM on the project, the scope became the whole product: I owned the design, the code, and the editorial platform read by buyers of $5M–$80M properties — and learned that at this tier, a slow website is never a luxury website.

Solo
Design + full-stack + product
9 mo
Concept → shipped
$5–80M
Audience · listing range
1.4s
Mobile load · was 8.2s
Shipped · christiesrealestate.com/blog Editorial · not transactional 50+ global editors

The catalogue

Lots 01–06The contribution · at a glance

Sale catalogue of one build.

Every figure is scoped and sourced. This is an editorial and brand-translation build — its evidence is range, ownership and craft; live engagement analytics are managed by Christie's internally; the point-in-time post-launch figures shown are my own measurements, causation not isolated.

Lot 01 · Ownership
1 person
Product owner, designer & full-stack developer
Hired as Web Application Developer — scope expanded; no designer or PM on the project
Lot 02 · Duration
0 mo
Concept to shipped editorial platform
2021 · end-to-end, including two SOP handoff manuals
Lot 03 · Heritage
0 yrs
Brand voice translated to digital register
Christie's · founded 1766 · InDesign brand book as source of truth
Lot 04 · Performance
8.2→1.4s
Mobile 4G load time, V1 → V2
Lighthouse, post-launch · mobile bounce 67% → 28% (Google Analytics)
Lot 05 · Architecture
47→18
Database queries per page
Server logs, New Relic · custom SQL join replaced 27 WP_Query calls
Lot 06 · Operations
0+
Global editors retained, zero retraining
HK · NY · London · Tokyo · publishing from day one post-migration

Scope honestly stated: quantitative rows above carry their instruments (Lighthouse · New Relic · Google Analytics); everything else is scoped to the build artefact and the design discipline, not internal traffic data.

ProvenanceBehind the scenes · first-hand

Not researched from a desk. Observed in the room.

Badge access to private auction previews — events closed to the public — put me in the same rooms as the clients the platform serves. Physical brand standards (spacing, materials, subdued lighting) became the digital design brief.

Christie's International Real Estate display at a luxury hotel venue — Luxury Lifestyle Edition catalogue stand beside a client lounge
Christie's International Real Estate venue display — the white-glove physical register the digital platform had to match. Own photograph · venue display

The readerThree private auction previews · 6 months

Field notes on how this segment actually thinks.

Over six months I attended three private previews. Fewer than ten unstructured conversations — attendees who assumed I was floor staff. Not research, and not claimed as research. What it gave me is harder to source: direct exposure to the reader.

Field note 01

Unsentimental self-knowledge

Several knew many employees disliked them — and said so, without defensiveness. If you need everyone to think well of you before deciding, your organisation has no future.

Design implicationDon't soften information for emotional comfort. A 15% decline needs clear attribution and decision context — not optimistic framing.
Field note 02

Directness as default register

No preamble, no softening, no circling toward the point. Questions were specific; opinions were stated as observations, not positions to negotiate.

Design implicationCopy that hedges or hand-holds signals the design was built for someone else. Never tell a UHNW client to "get started."
Field note 03

Acquisition as recognition of peers

For some, deep substantive knowledge; for others, social currency. Both are UHNW. They are not the same user.

Design implication"UHNW" is not a monolithic persona — accommodate the range without visibly distinguishing between them.
n < 10 · qualitative · unstructured · stated as observation, not research

The briefStrategic context

A heritage house enters digital. Three constraints collide.

The severed funnel

The editorial platform was disconnected from the property CRM. Readers consuming stories about luxury architecture had no pathway to the related $5M–$80M listings — revenue leaking through a broken content-to-listing pipeline.

The continuity break

Moving from an editorial piece to the estates it described meant leaving the experience entirely and manually searching the listings site. For an audience whose in-person experience is seamless, every manual step reads as "not built for someone like me."

Fidelity vs. performance

Stringent print guidelines — exact typeface weights, whitespace ratios, cropping rules — rendered responsively under massive 4K payloads. Any performance compromise would destroy the very luxury the brand demanded.

The turnAsked vs. done

The brief said template. The brand said otherwise.

What I was asked to do

"Implement the approved designs using an existing WordPress template."

Pick a premium theme, customise it, ship it. The assumption lasted until prototyping showed standard templates couldn't hold the typographic nuance or the relational data model tying editorial to high-value listings — not without performance trade-offs the audience would read instantly.

What the project became

A bespoke platform — and a solo product ownership role.

I presented the trade-offs to stakeholders and pivoted the engagement from template implementation to a fully tailored build: custom theme, custom data model, custom editorial system — while keeping the WordPress dashboard 50+ editors relied on daily.

Rejected

Premium theme modification

Fast (~2 weeks), but prototyping showed Avada/Enfold-class themes lock typography to their systems and restrict custom data structures. Brand compromise guaranteed.

Fast · 2 weeksBrand compromiseNo custom data model
Rejected

Headless CMS + React

Maximum flexibility — catastrophically misaligned with a WordPress-native editorial operation. Retraining 50+ global editors meant publishing delays measured in months.

Max flexibilityEditor retrainingPublishing delays
Chosen

Bespoke theme + custom SQL

A theme built from scratch — no page builders — plus custom SQL for the content-to-property relationships. Pixel-perfect brand alignment, and the dashboard editors already knew.

Brand-perfectEditor-friendly · zero retrainingCustom data model

Full build-vs-buy register, data-architecture detail and the Salesforce sync decision live in the deep record below — kept complete, folded for reading pace.

Exhibit ALive demo · the thesis, made physical

Feel 8.2 seconds. Then feel 1.4.

The brand team demanded print-magazine fidelity; V1 delivered raw 4K and an 8.2-second mobile load. The argument that won wasn't rhetorical — it was this comparison. Press load and wait the real seconds. Luxury is the absence of waiting.

christiesrealestate.com · V1 · raw 4K PNGMaximum fidelity
Awaiting loadLuxury Defined editorial article page — V1 loading simulation
Elapsed0.0s
document.html42 KB theme.css · builder bundle610 KB hero-fullres.png12.0 MB 47 database queriesblocking
christiesrealestate.com · V2 · WebP + srcsetPerceived luxury
Awaiting loadLuxury Defined editorial article page — V2 loading simulation
Elapsed0.0s
document.html38 KB bespoke theme.css64 KB hero-1024.webp · srcset1.8 MB 18 queries · single JOINsub-100ms
Simulation of measured V1/V2 timelines (Lighthouse, mobile 4G) — not a live network request.
12 → 1.8 MB
Hero payload · WebP + srcset
67 → 28%
Mobile bounce · Google Analytics
83%
Faster · 8.2s → 1.4s · Lighthouse

Exhibit BLive demo · the severed funnel, repaired

From story to private viewing. Three clicks. Zero searches.

The product argument of the whole build: a reader inside an editorial should reach the property it describes without ever leaving the experience. The custom SQL foreign key made editorial content a conversion surface. Walk it yourself.

christiesrealestate.com/blog/inside-hong-kong
1 · Story 2 · Listing 3 · Viewing

Home Tours · Luxury Defined

Inside Hong Kong: A Private Tour of The Peak's Hidden Mansions

By Christie's Editorial · 8 min read

Above the city's famous skyline, an enclave of extraordinary homes reveals how Hong Kong's most discreet buyers define luxury living. Past the winding roads and banyan shade, the properties here rarely reach the open market — and when they do, they move quietly.

Among them, has become the reference point for what discreet luxury means at this altitude: gardens that terrace toward the water, interiors calibrated to the light, and a provenance that predates the skyline itself.

Click 1 of 3 — the property mention is the doorway ↑

The Peak · Hong Kong

Harbourview Residence

Six bedrooms · Victoria Harbour aspect · linked from the story you were reading

$64M
Guide price · USD
9,400
Sq ft · terraced gardens
6 / 8
Beds / baths
1938
Provenance · pre-war estate

Click 2 of 3 — no search, the FK join carried you here

3clicks · 0 searches

Your advisor will be in touch.

Named market advisor · Hong Kong desk
Not a generic inbox — the enquiry routes to the listing's own advisor

Click 3 of 3 complete —

Concept reconstruction · content and property data simulated · demonstrates the editorial-to-listing architecture shipped on the live platform Previous platform: leave the article → open listings site → search manually

Exhibit CLive demo · the machine behind the magazine

One console. Four markets. Fifty editors.

The editorial system I designed and built: market presets carry title, category, hero treatment and read-time in one switch, and every article rides the Salesforce property bridge — the custom sync that keeps 847 listings joinable without touching the CRM team's schema.

cms.christiesrealestate.com/wp-admin/post-new.phpConcept reconstruction

Editorials › Add new

Article title · market preset
Inside Hong Kong: A Private Tour of The Peak's Hidden Mansions
Taxonomy · carried by preset
Home Tours Market · Hong Kong 8 min read EN · ZH
Property data bridge · Salesforce API · live · last sync 2 min ago · 847 listings indexed
✓ Article live on the Hong Kong edition · christiesrealestate.com/stories

Concept reconstruction of the CMS architecture and editorial workflow I designed and built — hourly WP-Cron sync writes Salesforce listings to a local wp_properties table; page loads query the local DB only. The CRM schema stayed untouched, read-only.

Plates I–VThe shipped surfaces

Not a mockup. The platform itself.

Screenshots of the live Christie's International Real Estate surfaces — the editorial platform, the listing journeys it feeds, and the brand pages that carry 260 years of provenance.

Luxury Defined blog article page — High Spirits editorial with category navigation
Plate I · The deliverable

"Luxury Defined" — the editorial platform

The blog itself: serif masthead, category taxonomy (Architecture · Home Tours · Interiors · Events), and article templates that hold the print register on the web. This surface — and everything beneath it — is the nine-month build.

Editorial story grid — Home Tours cards with generous whitespace
Plate II · The grid

Whitespace as status signal

The editorial grid: generous spacing, restrained cards, no urgency patterns. Each story links to a property listing via the custom SQL foreign key — the conversion bridge the previous platform was missing.

Global developments listing — multi-market luxury properties
Plate III · The listings

Where the journey lands

Global developments across markets — Vietnam to Niseko to Bangkok. Property value, not alphabetical order, drives the visual priority stack. This is the surface the editorial funnel feeds.

Property detail page — Aki Niseko Onsen Villa with named advisor card
Plate IV · The relationship

A named advisor, not a form

Property detail with 4K hero (WebP + srcset — 12MB raw reduced to 1.8MB) and the named market advisor as primary contact. UHNW buyers expect a relationship; the enquiry routes to a person, never a generic inbox.

Brand pages — Our Global Network and Artfully Aligned sections
Plate V · The provenance

Heritage before product

"Our Global Network" and "Artfully Aligned" — institutional authority established before anything is asked of the reader. The same sequencing private-banking onboarding should follow.

Condition reportBefore · after · instrument

Every claim, with its instrument.

Metric Legacy Custom build Instrument
Page load · mobile 4G 8.2s 1.4s Lighthouse · post-launch
Database queries / page 47 18 Server logs · New Relic
Hero image payload 12 MB raw 4K 1.8 MB WebP + srcset Network waterfall
Mobile bounce rate 67% 28% Google Analytics
Page views · 3-month post-launch baseline +20% Google Analytics · vs prior period
Brand guideline compliance ~70% · template limits 100% · bespoke Weekly pixel-diff vs InDesign book
Content-to-listing pathway None · manual search Automated FK join Architecture · new funnel

Figures are the build's own measured outcomes at launch; ongoing engagement analytics for the live site are managed by Christie's internally; the point-in-time post-launch figures shown are my own measurements, causation not isolated.

V1 · The honest failure

Maximum fidelity

  • Full 4K resolution at every viewport — "pristine quality or nothing"
  • No compression; client-side rendering of all property cards
  • The brand book, taken literally
Result · 8.2s load · 67% mobile bounce — the luxury destroyed by its own fidelity
V2 · The recovery

Perceived luxury

  • Responsive srcset across six breakpoints · WebP with JPEG fallback
  • Lazy-loading via Intersection Observer; single-JOIN property queries
  • The brand book, interpreted — feeling over pixel values
Result · 1.4s load · 28% bounce — presented to the brand team as evidence, not opinion

The insight that survived the project: luxury UX is not maximum resolution — it is the absence of waiting. Convincing a 260-year-old brand team of that required side-by-side evidence, diplomacy, and a load-time gauge they could feel.

Exhibit DLive demo · UHNW property intelligence

The comp set an RM presents before the client asks.

UHNW buyers don't negotiate on emotion — they negotiate on comparables. Sale price against size; point area encodes $/sqft premium; the gold band is the current listing's estimated range. Filter by market and asset type.

Apartment Villa / House Penthouse Current listing Point size = $/sqft premium · data simulated

AppendixThe deep record · kept complete

For the reader who wants the whole ledger.

Build-vs-buy, the data architecture, the stakeholder tension map, the handoff SOPs, the principles — everything the curated narrative above summarises, in full.

Open the deep record Unfold ↓Fold ↑

Build vs. buy — the register

Bought · commoditised
  • Yoast SEO — mature, update-safe
  • WP Rocket — caching; no need to reinvent
  • Gravity Forms — editorial submission workflows
Built · differentiating
  • Theme layer — pixel-perfect brand compliance; ~80 DOM nodes/page vs 500+ under page builders
  • Property–editorial bridge — custom SQL for the CRM integration
  • Editorial templates — luxury-specific layouts beyond generic builders

The data architecture

A custom wp_properties table with a foreign key to wp_posts, normalised taxonomy (location · style · price tier), and a single JOIN replacing 27 separate WP_Query calls.

// Salesforce sync · hourly WP-Cron function sync_salesforce_properties() { $api_data = fetch_salesforce_api(); // read-only foreach ($api_data as $property) { upsert_property_to_local_db($property); } set_transient('last_sync', time(), HOUR_IN_SECONDS); } // page loads query the local DB only — zero API latency
62% query reduction · sub-100ms property-card rendering · CRM schema untouched

Real-time Salesforce calls were rejected: 400–800ms per property card × 8 cards = 3–6 seconds of blocking API latency. The hourly sync trades absolute freshness for a page that never waits.

The stakeholder tension map

Brand team · New York

"Pixel-perfect print standards." Resolution: weekly pixel-diff reviews against the InDesign book; fluid clamp() margins argued as more faithful to the golden-ratio system than fixed pixels. By week eight, "better than print" on mobile.

Editorial team · 50+ editors

"Don't disrupt our workflow." Resolution: three usability sessions; custom Gutenberg blocks that looked like the old editor. Zero retraining, publishing from day one.

CRM team · data engineering

"Don't touch our Salesforce schema." Resolution: read-only hourly sync into a local mapping layer; editorial taxonomy joined to their property IDs without a single schema change.

Handoff — two SOP manuals

  • Engineering SOP — architecture rationale, schema, deployment checklist, common tasks. Successor engineer shipping within one week, unassisted.
  • Sales/content SOP — visual step-by-step upload protocol: naming conventions, folder structure, image standards, QC checklist. 100% autonomous publishing within two weeks; zero routine escalations.

What I'd do differently

  • Performance budget before design handoff — a 2s LCP constraint at wireframe stage would have prevented the V1 detour and saved two weeks.
  • Headless API layer from day one (WP-GraphQL) — even with a PHP-rendered frontend, the decoupling would have future-proofed a native app path.
  • Automated visual regression (Percy/Chromatic-class) instead of manual weekly pixel-diffs against the brand book.

What the clients taught me

  • Response speed is a commercial signal. The most successful replied in minutes — delay is a decision.
  • Niche markets preserve margin; commodity markets compress it to zero. Why I chose institutional finance over consumer SaaS.
  • Decisive people act on probable, not certain. The team that waits for perfect research ships nothing.

DisclosureWhat this evidences · and what it doesn't

For a Senior PD or Design Lead interview panel.

◆ What this case study evidences

  • Solo full-stack capability at the UHNW editorial tier — nine months as sole product owner, designer and developer for Christie's International Real Estate blog + community surfaces.
  • Brand-voice translation — 260-year auction-house heritage carried to a digital editorial register without losing institutional weight.
  • Performance as brand equity — 8.2s → 1.4s with instruments named; the argument won with evidence, not taste.
  • The UHNW audience discipline that grounds the concept lineage — Xanthos private bank and the Aureus wealth surface cite this build as production foundation.

○ What it deliberately does not claim

  • Not AML/CFT or transactional workflow — Christie's was editorial + community. Those case studies live at Argos (concept) and ACY Securities (shipped).
  • No certified WCAG 2.1 AA conformance — full disclosure at the accessibility audit.
  • No ongoing engagement-metric claims — live traffic data is managed by Christie's internally; the methodology bar for any future quantitative claim follows the Finlogix disclosure.
  • No post-launch iteration arc documented for this surface — the regulated iteration pattern lives at the ACY RG 268 note; the institutional-adoption pattern at ACY Connect.

"Brand aesthetics are entirely dependent on engineering performance. A slow website is never a luxury website — no matter how perfect the typography."

The lesson that shaped everything after · Ed Chen · Christie's International Real Estate · 2021

ContinueWhere this discipline went next

The UHNW register, carried into finance.

The editorial discipline learned here became the client-surface standard for the private-banking lineage — and the performance obsession became a portfolio-wide law.

Xanthos private bank → Aureus · UHNW AI wealth 90-second recruiter scan All case studies
Portfolio threads

Where this case study sits in the larger web

Every problem we solve for clients has multiple valid approaches — different costs, different ROI, different risk profiles. These threads show how the approach on this page compares to others in the portfolio.

Thread

Editorial Voice in Finance

Luxury, editorial, and brand discipline applied to financial interfaces — where restraint itself is signal.

Continue the tour

More institutional case studies

View all 16 projects → Portfolio map → Hiring? See the 90-second recruiter scan →