Mr Porter

Strategy — Four Whys

Mr Porter — Four Whys Strategy

Last Updated: 2026-05-12
Urgency: HIGH — Active platform migration to Mytheresa/Sylius stack + 700 job cuts = lean teams need automated analytics + Toby Bateman returned as brand lead + shared LuxExperience buying committee with Net-a-Porter (already CMO+CEO approved)
Status: Draft — CMO review


Why 1: Why Do Anything?

Business Imperative: MEASURE THE LUXURY MENSWEAR DIGITAL EXPERIENCE DURING A HIGH-STAKES PLATFORM MIGRATION — WITH LEANER TEAMS AND HIGHER STAKES

Mr Porter is a ~£500M premium luxury menswear D2C platform with 3.5M monthly visitors, now part of the LuxExperience Group (NYSE: LUXE) following Mytheresa's acquisition of YOOX Net-a-Porter in April 2025. The entire Mr Porter operation is being migrated onto Mytheresa's Sylius-based tech stack (PHP/Symfony, GO, Kotlin, MySQL, Redis, OpenSearch, AWS, React frontend) over 24-36 months. There is no confirmed DXA incumbent — this is a green field.

Mr Porter shares infrastructure decisions with sister brand Net-a-Porter under Group CTO Philipp Barthold and Group CDO Gareth Locke — but Mr Porter has a distinct customer base, distinct merchandising, and distinct digital experience patterns that require separate measurement.

Pain Dimensions:

  • Migration Without Measurement: The 24-36 month platform migration affects every customer touchpoint. Without session-level analytics, the Mr Porter team cannot answer: "Did this sprint's migration milestone improve or degrade the menswear shopping experience, and by how much in £?" Aggregate dashboards cannot isolate migration-induced friction from seasonal variation or merchandising changes.

  • Luxury Menswear AOV Amplification: Mr Porter's average order values exceed £400. A single checkout friction point — payment timeout, size selector failure, shipping calculator error — costs disproportionately per session. At 3.5M monthly visits, even 0.1% checkout friction = 3,500 abandoned luxury baskets per month. Conservative estimate: £1.4M/month in invisible friction cost.

  • 700 Job Cuts = Fewer Eyes on Experience: LuxExperience announced ~700 role cuts across Mr Porter, Net-a-Porter, and YOOX. Leaner teams mean less manual QA capacity, less time for session analysis, fewer people monitoring post-deployment experience. Automated session capture and AI-driven anomaly detection (Felix AI) directly replaces the human monitoring capacity that has been cut.

  • Toby Bateman Returns — Brand Identity at Stake: Toby Bateman, a founding member of Mr Porter, returned to lead the menswear brand. His mandate is to preserve Mr Porter's distinct editorial and shopping experience through the migration. Without session-level measurement showing whether the curated luxury menswear experience survives migration onto shared infrastructure, that mandate is unverifiable.

  • Cross-Brand Cannibalisation Risk: Mr Porter and Net-a-Porter will share infrastructure but serve different audiences. Without per-brand session analytics, there is no way to detect if shared infrastructure optimisations that benefit Net-a-Porter's womenswear experience inadvertently degrade Mr Porter's menswear experience. A checkout flow optimised for Net-a-Porter's product mix may underperform for Mr Porter's higher-AOV, lower-frequency purchase patterns.

Quantified Cost of Inaction: At £500M revenue and 3.5M monthly visits, 0.5% undetected friction = £2.5M annually. During active platform migration, friction rates typically spike 2-5x above baseline. Conservative migration-period cost: £5-12.5M in undetected, unquantified experience degradation over 24-36 months.


Why 2: Why Now?

Compelling Events (stacked — 4 simultaneous triggers):

  1. Active platform migration — 24-36 month window from April 2025: The migration to Mytheresa's Sylius stack is underway. Migration risk is highest in the first 12 months as core infrastructure transitions. The measurement baseline must be established NOW — before the first major migration milestone — so that before/after comparisons are possible. Deploying analytics mid-migration means losing the pre-migration baseline forever.

  2. 700 job cuts — operational capacity reduced: Fewer people means automated analytics is not optional — it is operational survival. Felix AI autonomously detecting friction across Mr Porter's 3.5M monthly visits replaces the monitoring capacity of a team that no longer exists.

  3. Toby Bateman's return — new leadership evaluation window: New (returning) brand leadership creates a 90-day window for vendor conversations. Bateman's mandate to preserve Mr Porter's editorial identity during migration directly aligns with session-level experience measurement.

  4. LuxExperience NYSE listing (LUXE) — investor scrutiny on digital KPIs: Public company metrics now include digital experience indicators. Investor calls will ask about customer experience during the transformation. Quantified answers require quantified measurement.

Cost of Delay: Each month without session-level measurement during active migration means ~290K sessions unmeasured. Migration-induced friction accumulates invisibly. The pre-migration baseline window is closing — once infrastructure migrates, the "before" state is gone permanently.


Why 3: Why Us (Quantum Metric)?

Capability-to-Need Mapping:

Mr Porter Need QM Capability Value
Measure experience before/during/after Sylius migration 100% session capture, autocapture on new stack Pre-migration baseline + migration regression detection without re-instrumentation
Quantify friction in £ for luxury AOVs Revenue quantification (patented) "Checkout friction on the new Sylius stack costs £1.4M/month — here are the top 5 fixes"
Replace manual QA capacity lost in 700-person layoff Felix AI autonomous investigation AI monitors 3.5M monthly visits continuously, surfaces anomalies without human prompting
Cross-brand visibility alongside Net-a-Porter Multi-brand deployment under single LuxExperience instance Gareth Locke (Group CDO) sees Mr Porter and Net-a-Porter experience data in unified view
Deploy on Sylius/Symfony/React without engineering sprints Tag-based deployment, days not months Live on Mr Porter before next migration milestone
Preserve distinct menswear experience during shared infrastructure migration Per-brand session analytics with brand-level segmentation Detect when shared infrastructure changes degrade Mr Porter's specific experience

Proof Points:

Proof Point Relevance Metric
Chalhoub Group Multi-brand luxury retailer with unified visibility — direct parallel to LuxExperience multi-brand model Portfolio-wide experience visibility
Wyndham Hotels Unified data across distinct properties on shared infrastructure — maps to Mr Porter/NAP on shared Sylius stack Multi-property unified measurement
Lululemon Premium fashion scale, millions in recovered revenue Multi-tens of millions $ recovered
UNTUCKit Premium menswear D2C — closest product-market parallel +20% web conversions

Chalhoub Group remains the lead proof point — multi-brand luxury on shared infrastructure with unified analytics.


Why 4: Why Not Us?

# Alternative Likelihood QM Reframe
1 Extend Mytheresa's existing analytics HIGHEST Mytheresa's analytics stack is unknown. If they have a DXA tool, the question is whether it can serve Mr Porter's distinct menswear audience adequately. If they don't, the green field extends group-wide. Either way, QM's multi-brand deployment means one platform for all LuxExperience brands without forcing Mr Porter onto analytics optimised for Mytheresa's womenswear customer base.
2 Build into migration project HIGH Migration teams focus on functional parity — "does checkout work on the new stack?" not "does checkout convert as well on the new stack?" These are different questions requiring different tools. QM measures what migration teams cannot: the revenue cost of experience changes that are functionally correct but experientially inferior.
3 Contentsquare MEDIUM Implementation complexity across a custom Sylius stack + multi-brand environment = 6+ months minimum. During active migration, adding a 6-month analytics implementation creates scope risk and engineering distraction. QM deploys in days via tag, no engineering sprint required.
4 FullStory LOW Quota-based session capture at 3.5M monthly visits means sampling or prohibitive cost. No revenue quantification. No multi-brand architecture. FullStory revenue declining — platform risk for a luxury group planning multi-year analytics investment.
5 Do nothing until migration completes MEDIUM Migration takes 24-36 months. Measuring only AFTER means 24-36 months of unmeasured friction at £500M revenue scale. No pre-migration baseline for comparison. No ability to detect migration-induced degradation in real time. By the time measurement starts, millions in friction cost have accumulated invisibly.

Warm Routes

Route Status Detail
Gareth Locke (Group CDO, LuxExperience) CONFIRMED WARM — Adrian LinkedIn connected 08 Sep 2021 Gareth Locke owns analytics tooling decisions for the combined Mytheresa/NAP/MR PORTER group. A 5-year LinkedIn connection. He is the single most important decision-maker for DXA across LuxExperience. Frame: "Gareth — with NAP and Mr Porter migrating onto the Mytheresa stack, how are you planning to measure experience quality across brands during the transition?"
Martin Beer (Group CFO) VERIFIED — Cold Group CFO overseeing financial governance of the €250M transformation. Frame: quantifying migration risk in £ terms. Approach via Gareth Locke introduction.
Philipp Barthold (Group CTO) VERIFIED — Cold (no LinkedIn URL found) Group CTO leading the Sylius migration. Frame: deploy experience measurement alongside each migration milestone without engineering overhead. Approach via Gareth Locke.
Toby Bateman (Mr Porter brand lead) NOT IN PEOPLE.CSV — needs enrichment Returned founding member leading Mr Porter. Brand identity preservation = experience measurement mandate. Approach after Gareth Locke engagement.

Primary approach: Gareth Locke is the entry point for both Mr Porter and Net-a-Porter. A single conversation covers both brands. The Mr Porter angle strengthens the Net-a-Porter pitch — "you need cross-brand visibility during the migration, not per-brand analytics silos."


Entry Sequence

  1. Week 1: Coordinate with Net-a-Porter outreach (if Board approves the 7-brand batch). Gareth Locke engagement should explicitly reference both Net-a-Porter AND Mr Porter: "unified experience measurement across the LuxExperience portfolio during migration."

  2. Week 1: LinkedIn connect Toby Bateman (Mr Porter brand lead, returned founding member). Frame: brand experience preservation during platform transition.

  3. Week 2: If Gareth Locke responds, expand the conversation to include Mr Porter-specific concerns: menswear AOV patterns, editorial experience preservation, cross-brand cannibalisation detection.

  4. Week 2-3: Approach Philipp Barthold (Group CTO) with migration measurement angle. Frame: "Deploy QM alongside each migration milestone — days per brand, not engineering sprints."

  5. Week 3-4: If multi-threaded engagement is progressing, request meeting with Gareth Locke + Toby Bateman together. Frame: how to preserve Mr Porter's distinct luxury menswear experience while migrating to shared infrastructure.

Timeline: Platform migration is actively underway. Pre-migration baseline window is closing. Engage within 1 week of Net-a-Porter outreach start.

Success Criteria: Gareth Locke engagement covering both NAP + Mr Porter within 21 days. Toby Bateman connection within 14 days. Group-level QM evaluation conversation within 45 days.


Verified Data Points

Claim Source Verified
Revenue ~£500M brands.csv Yes
3.5M monthly visitors brands.csv Yes
Custom platform (migrating to Sylius) signals.csv, investor relations Yes
LuxExperience Group (NYSE: LUXE) signals.csv Yes
24-36 month platform migration LuxExperience Q1 FY26 results Yes
Sylius-based Mytheresa tech stack Sylius case study, investor relations Yes
700 job cuts across YNAP brands Retail Gazette Sep 2025 Yes
Toby Bateman returned to lead Mr Porter Retail Gazette, signals.csv Yes
Gareth Locke Group CDO — Adrian connected Sep 2021 people.csv, adrian-contacts.csv (via NAP) Yes
Martin Beer Group CFO people.csv (via NAP) Yes
Philipp Barthold Group CTO people.csv (via NAP) Yes
No confirmed DXA incumbent Investigation complete Yes — green field
Chalhoub Group multi-brand QM deployment QM case study Yes
Wyndham Hotels unified data QM case study Yes
UNTUCKit +20% web conversions QM case study Yes

Outreach

Outreach Sequence (3-Step): Mr Porter — Gareth Locke (Group CDO, YNAP/Richemont)

Metadata

  • Brand: Mr Porter (YNAP/Richemont/Mytheresa)
  • Contact: Gareth Locke, Group CDO
  • Signal Lead: L2 — Active platform migration to Mytheresa Sylius stack (24-36 month window from Apr 2025)
  • Signal Stack: L2 platform migration + L2 700 job cuts + L2 Toby Bateman return + L2 LuxExperience NYSE listing (LUXE)
  • Urgency: 8 — Platform migration creating maximum friction risk, reduced workforce needs automated monitoring, warm route available
  • Channel Strategy: LinkedIn Message (Step 1 — warm route), Email (Steps 2-3)
  • Draft Date: 2026-05-15
  • Status: Draft — CMO review
  • Existing Relationships: Gareth Locke — Adrian connected since Sep 2021 (5yr). Warm route. Also: Martin Beer (Group CFO) and Philipp Barthold (Group CTO) via Net-a-Porter connections.

Relationship & Intel Flags

  • Warm route — Adrian connected with Gareth Locke since Sep 2021: This is not cold outreach. Peer-to-peer, conversational tone.
  • Platform migration to Mytheresa Sylius stack is the dominant event: 24-36 month migration window from Apr 2025. Migration risk is highest in the first 12 months. Experience measurement baseline must be established NOW.
  • 700 job cuts = automated monitoring is survival: The team that manually monitored experience quality is smaller. Automated friction detection replaces human capacity.
  • Toby Bateman's return as brand leader: New (returning) leadership creates evaluation window. His mandate to preserve Mr Porter's editorial identity during migration aligns with experience measurement.
  • LuxExperience NYSE listing (LUXE): Public company scrutiny on digital KPIs. Investor calls will ask about customer experience during transformation.

Step 1 — Connect (LinkedIn DM — warm, <100 words)


contact: Gareth Locke
brand: Mr Porter
signal_refs: [2025-04-01 platform migration, 2024-02-01 workforce reduction]
signal_levels: [L2, L2]
touch_number: 0
channel: linkedin
status: draft
dnc_checked: true
concentric_rings_used: [Ring 1: Group CDO owns digital experience, Ring 2: platform migration, Ring 5: 5yr warm connection]

Gareth — hope you're well. Been following the YNAP transformation and the Mytheresa migration. The scale of what you're navigating is significant — migrating Mr Porter's experience to a new platform stack while preserving what makes it distinctive, and doing it with a leaner team.

One thing I've seen with platform migrations at luxury scale: the experience baseline captured before the migration is what makes the before/after comparison possible. Without it, you're flying blind on whether the migration improved or degraded the customer experience.

Thought it might be worth catching up.


Step 2 — Value (Email, <100 words)


contact: Gareth Locke
brand: Mr Porter
signal_refs: [2025-04-01 migration, workforce reduction, LUXE listing]
signal_levels: [L2, L2, L2]
touch_number: 1
channel: email
status: draft
dnc_checked: true
concentric_rings_used: [Ring 1: CDO owns digital transformation, Ring 2: migration risk, Ring 3: public company KPIs]

Subject: Experience baseline before the migration milestone

Gareth,

Following up on my LinkedIn note. The migration timeline creates a specific measurement question: when the first major milestone ships on the Sylius stack, how will you quantify whether the Mr Porter experience improved, degraded, or stayed flat?

At 3.5M monthly luxury visits with high AOVs, even a slight experience degradation during migration is expensive. And with LUXE now public, investor calls will ask about customer experience metrics during the transformation.

Session-level measurement established pre-migration captures the baseline. It turns "we think the migration went well" into "here's the before/after in £."


Step 3 — CTA (Email, <75 words)


contact: Gareth Locke
brand: Mr Porter
signal_refs: [2025-04-01 migration, Toby Bateman return]
signal_levels: [L2, L2]
touch_number: 2
channel: email
status: draft
dnc_checked: true
concentric_rings_used: [Ring 2: editorial identity during migration, Ring 5: warm connection]

Subject: Re: Experience baseline before the migration milestone

Gareth,

One more thought. Toby Bateman's mandate to preserve Mr Porter's editorial identity during the migration is exactly the kind of thing session-level measurement proves — or catches early when it drifts.

Happy to walk through how this works technically. Lightweight deployment, no migration disruption. Shall we find 20 minutes?