A membership renewal system built on usage, not reminders.
Renewals depended on a manual email three weeks before expiry. We instrumented member usage and built a year-round program that makes renewal a consequence, not a request.
What does a member need to have experienced by month nine for renewal to feel obvious rather than negotiable?
- Data audit
- Loyalty design
- Lifecycle architecture
- Custom membership
- HubSpot
- WhatsApp Business
- BigQuery
The problem
A membership is renewed on the strength of what the member remembers using. Exclusive Traveler Club had no reliable record of usage, so the renewal conversation was a reminder rather than a case.
What we built
- A benefit-usage event model, so every interaction becomes a fact rather than a note.
- An activation sequence pushing new members towards the two benefits most predictive of renewal.
- Inactivity triggers that route to concierge instead of another automated email.
- A personal year-in-review that leads the renewal moment.
The result
Renewal rate rose 18 points on the first full cohort, and concierge time moved from chasing renewals to handling requests that generate value.
"We stopped asking people to renew and started showing them what they had already used."– Membership Director, Exclusive Traveler Club
- PHASE 1Instrument
Defined what a used benefit means and captured it as an event. Before this, usage was anecdotal.
- PHASE 2Onboard
First-90-days activation sequence tied to the two benefits most correlated with renewal.
- PHASE 3Year-round value
Quarterly value recap, concierge nudges triggered by inactivity, WhatsApp as the fast lane.
- PHASE 4Renewal
Renewal moment reframed around a personal usage summary instead of a generic reminder.
Renewal lift compares the first full renewal cohort after launch with the equivalent cohort in the prior year. Benefit usage is measured from the newly instrumented events, so pre-launch comparison uses reconstructed concierge records and is approximate. Client-approved, flagged as partially reconstructed.
Read our evidence standardWant the same system inside your stack?
See more cases