Chief Technology Officer — Luxury Retail Portfolio

The mandate

The portfolio's most valuable relationships are often held by individual advisers and expressed across boutique visits, private appointments, remote conversations, events, purchases and after-sales care. Technology has supported those moments unevenly. Some maisons use local client books, others rely on separate campaign or appointment tools, and digital profiles do not always reflect the permissions or context of an adviser relationship. The result is fragmented recognition, duplicated contact and a risk that personal service becomes either inaccessible or inappropriately automated.

The Chief Technology Officer will build the product and engineering foundations for a new clienteling model. The remit covers customer and adviser product platforms, client identity and preference services, appointment and event technology, remote-selling tools, relationship workflows, experience architecture, engineering, reliability and applied personalisation. The CIO retains enterprise systems and workplace infrastructure; brand leaders own the client proposition; privacy, security and legal functions maintain independent authority. The CTO is accountable for making the chosen relationship model secure, usable and scalable.

This urgent new role is not a brief to convert luxury loyalty into points or automated frequency. Recognition must be meaningful, discreet and under client control. A client may want continuity with one adviser but not broad visibility across a group; another may value service across markets. Technology should enable those choices without encouraging intrusive outreach or turning adviser judgement into a scripted next-best-action queue.

Scope and operating context

Based onsite in Paris, the CTO will shape an ecosystem of approximately 2,425 employees and material partners across France and a wider international region. Direct leaders will span product management, architecture, engineering, experience design, quality, site reliability, data interfaces and technical delivery. Brand, boutique and regional teams will provide product ownership and adoption through matrix relationships.

The estate includes customer records, commerce, appointments, events, service cases, messaging, adviser tools and digital identity. Different brands have legitimate relationship models and legal entities, so a single group profile may not be appropriate. The architecture must support separation, explicit sharing and purpose-based access, with clear rules for what an adviser, boutique, brand and central team can see or do.

Boutique technology operates under constraints unlike a normal office or website. Advisers may move through the space with shared or mobile devices, connectivity can vary, and client interaction should not be interrupted by cumbersome authentication or data entry. Remote service adds approved messaging, payment, content and record-keeping requirements. Product design must begin with those moments.

First-year agenda

The first one hundred days will trace several client relationships across boutique, remote, digital and after-sales journeys. The CTO will observe adviser work, review access and consent models, map applications and integrations, assess reliability and quantify manual duplication. Client and colleague research will identify where technology supports continuity and where it creates discomfort, delay or inappropriate contact.

The executive will then define a clienteling architecture around identity, relationship, permission, interaction, appointment, service and product-interest capabilities. Each domain will have an authoritative owner, purpose and access model. Brands may configure experience and workflow within approved boundaries. Shared services should reduce technical duplication without pooling client information beyond lawful and expected use.

Adviser workflow will be redesigned with front-line participation. The first releases may improve appointment preparation, preserve context when an adviser is unavailable, connect an after-sales case to the relationship or give clients clearer control over contact preferences. The final priorities will follow evidence. Success requires less colleague effort and better continuity, not more recorded interactions.

Personalisation and artificial intelligence will be introduced cautiously. Recommendations may support an adviser by organising authorised information, but they cannot infer sensitive attributes, fabricate relationship knowledge or contact clients automatically without an approved basis. Models must disclose source, confidence and limitations, and performance should be assessed across brands, languages and client groups.

Migration will protect provenance and consent. Legacy notes cannot simply be copied into a new shared platform; records must be reviewed for ownership, purpose, accuracy and retention. The CTO will create staged cutovers, service fallback and adoption support by boutique cohort. By year-end, selected journeys should show demonstrably stronger continuity and fewer fragmented tools.

Leadership responsibilities

The CTO will own clienteling product strategy, engineering quality, reliability and technical adoption. They will chair portfolio choices with brand and regional leaders, requiring a clear client need, business owner and privacy model before investment. Demands for local features will be tested against relationship value and lifecycle cost rather than rejected by default.

The executive will build authoritative internal capability in experience architecture, identity, permissions, platform product and boutique reliability. Agencies and integrators may provide scale or specialist design, but critical knowledge and decision rights must remain inside the portfolio. The CTO will assess leaders and develop a strong succession bench.

During material incidents, the role will protect clients and advisers first: contain inappropriate access or contact, provide accurate guidance, preserve evidence and coordinate remedy. Learning will change design, access, tests and monitoring. Technical recovery alone is not sufficient if relationship trust remains damaged.

Measures of success

The executive committee will review adviser adoption, time spent preparing and recording, appointment completion, relationship continuity, service-case linkage, client preference accuracy and complaints about contact or recognition. Technology measures include availability, latency, access incidents, release quality, recovery and retirement of duplicate tools.

Client value may appear through repeat, cross-channel continuity, service satisfaction and adviser-supported conversion, but attribution will remain careful. The number of profiles, notes or messages will not be a success measure. Platform progress will include supported brand adoption, lower integration effort and demonstrable internal ownership of critical capabilities.

Candidate profile

Candidates should bring 22–28 years of product engineering and technology leadership in luxury, premium retail, hospitality, private banking, travel or another high-trust relationship business. They must have built customer and adviser platforms across countries, with direct accountability for identity, consent, security and operational adoption.

The board will seek examples of supporting personalised service without over-centralising client information, migrating sensitive relationship records and designing tools that front-line professionals chose to use. Candidates should understand appointment, messaging, service, payment and preference boundaries. Experience governing responsible recommendation technology is expected.

The successful CTO will be technically credible and emotionally intelligent. They must challenge a brand leader who wants uncontrolled data access and a technologist who mistakes standardisation for relationship quality. Visible engagement in boutiques and with advisers is essential, as is clear board communication.

Compensation and appointment terms

The anticipated base range is EUR 285,000–390,000, with annual incentive and long-term participation linked to client, technology and enterprise value. Final placement will reflect relevant platform scale, luxury or relationship experience and current arrangements. Relocation and responsible treatment of forfeited awards will be considered individually.

Confidentiality

The portfolio is unnamed because the role involves sensitive clienteling plans, relationship data and technology weaknesses. Detailed platform and organisational information will be shared after identity, conflict and confidentiality checks. Applications must not include client records, adviser notes, source code, security findings or unpublished designs from another organisation.