← Work
02

Arc'teryx Membership & Customer Engagement Platform

Connecting guest relationships across retail, digital, and service without defaulting to another points program.

Investment and platform strategy

$5.2M

approved capital funding

0-to-1 membership definition, MVP scope, and phased roadmap while the program continues toward launch.

MembershipCustomer PlatformsProduct StrategyIntegrations
Arc'teryx Membership & Customer Engagement Platform hero visual

Overview

Guests already loved Arc'teryx in stores, online, and through product care, but those relationships lived in different systems. Membership was the chance to connect them without turning the brand into another points program.

As Senior Product Manager, I led the product strategy and platform definition to move the initiative from early concept toward phased delivery.

The opportunity

The hard part was not imagining benefits. It was deciding what membership should mean for Arc'teryx specifically, and which platform pieces had to exist before any of it could ship.

Several constraints shaped the work:

  • Activity was spread across channels that did not share a single guest view
  • Value had to go beyond discounts to feel on-brand
  • Every experience had to integrate with existing commerce, identity, service, and marketing systems
  • Stakeholders needed agreement on what belonged in release one versus later

The product problem was experiential and architectural at once: a compelling guest proposition backed by reusable capabilities, not a collection of loyalty features.

Starting state

Commerce

Retail

Customer Service

Marketing

Events & Services

  • Inconsistent identity
  • Disconnected activity history
  • Limited cross-channel recognition
  • Operational complexity
  • Difficult personalization

Unified membership layer

A connected profile and capability model spanning channels, without replacing existing systems.

My approach

1.Started with the relationship, not the rewards

We framed membership around long-term participation with the brand (gear, service, events, care) rather than defaulting to tiers and points.

That principle became the filter for roadmap debates.

2.Named the capabilities before the features

I broke the vision into durable building blocks: identity, profiles, activity, eligibility, benefits, orchestration, and measurement. Stakeholders could discuss trade-offs in shared language instead of debating isolated UI ideas.

3.Drew a credible MVP line

The first release needed to communicate value quickly, give members a useful destination after joining, and establish identity and eligibility foundations without manual operations overhead.

Everything else waited until the platform could support it reliably. We mapped integrations early so the roadmap reflected real delivery risk, not wishful sequencing.

Turning a broad vision into a credible first release

Establish

Foundational capabilities required for membership to function.

  • Membership identity
  • Enrollment
  • Activity model
  • Eligibility foundation
  • Service visibility

Prove

Focused experiences that demonstrate meaningful guest value.

  • Member destination
  • Product ownership experiences
  • Selected services & events
  • Lifecycle communications

Expand

Future capabilities enabled by the foundation.

  • Additional benefits
  • Deeper personalization
  • Broader channel integration
  • New experience models

The product strategy

Membership became a connected layer across the guest relationship, not a standalone rewards site.

Three principles guided both experience and technology:

Useful from the beginning

Clear value on day one, with no distant spending threshold required to feel like a member.

Connected to product ownership

Membership should support owning, maintaining, and engaging with Arc'teryx gear, not just checking out faster.

Built to evolve

New benefits and eligibility models should extend the platform, not force a program rebuild.

Underneath, the platform tied together identity, activity, benefits, orchestration across channels, and trusted data for lifecycle engagement and future personalization.

From guest activity to connected member experiences

Experience layer

  • Web
  • Mobile
  • Retail
  • Guest Services
  • Communications

Membership capabilities

  • Enrollment
  • Member profile
  • Activity history
  • Benefits & eligibility
  • Product ownership
  • Service & event access

Shared platform services

  • Identity
  • Consent
  • Rules
  • Event processing
  • Notifications
  • Measurement

Enterprise ecosystem

  • Commerce
  • Customer service
  • Marketing technology
  • Data & analytics
  • External services
Simplified capability model. Technical and commercial details have been intentionally generalized.

Investment and platform direction

Approved capital funding

I led the product definition and investment case for a 0-to-1 membership platform, securing $5.2M in approved capital funding. That funding reflected confidence in the customer proposition, MVP definition, platform strategy, and phased roadmap. It was an investment decision, not revenue realized in market.

Build versus buy

I led a build-versus-buy evaluation across five vendors that shaped a headless loyalty platform strategy. The chosen direction was projected to reduce delivery time by approximately two quarters while preserving flexibility for future membership capabilities.

What the platform had to connect

Scope included member enrollment and onboarding, customer identity and profile integration (Okta CIAM), membership data and eligibility, loyalty platform integration, member benefits and engagement, Salesforce Service Cloud requirements, and phased rollout dependencies across teams.

What is still in flight

The full membership MVP has not launched yet. Funding, architecture, and roadmap decisions continue to advance the program; separately scoped work such as Sperro SV owner-benefits delivery is phased benefits delivery, not the complete membership launch. This case study describes strategy, investment, and platform definition I am still helping drive, not a finished member product already in market.

From guest activity to connected member experiences

Experience layer

  • Web
  • Mobile
  • Retail
  • Guest Services
  • Communications

Membership capabilities

  • Enrollment
  • Member profile
  • Activity history
  • Benefits & eligibility
  • Product ownership
  • Service & event access

Shared platform services

  • Identity
  • Consent
  • Rules
  • Event processing
  • Notifications
  • Measurement

Enterprise ecosystem

  • Commerce
  • Customer service
  • Marketing technology
  • Data & analytics
  • External services
Simplified capability model. Technical and commercial details have been intentionally generalized.

Impact

The win was creating enough shared clarity to move from ambition to a fundable, executable platform plan.

I translated a fuzzy membership concept into a capability-based strategy, aligned executives on a focused MVP, led vendor evaluation, and surfaced integration dependencies before they became delivery surprises. The organization gained a credible foundation for membership as a long-term customer platform, with approved funding and a delivery path we are still executing.

What I learned

A loyalty mechanic is not a membership strategy

Points can support a program; they do not explain why a guest should go deeper with a brand.

Dependencies deserve a product voice

Simple member experiences often hide identity, data, and operational work across the company. Surfacing that early produces better roadmaps.

MVP discipline matters most when the vision is exciting

The more possibilities people see, the more you need a clear story about what not to build yet.