AGENT SKILL

loyalty-programs

Design loyalty programs — points, tiers, rewards, and retention mechanics that keep customers coming back.

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
loyalty-programs
category
business-marketing
description
Design loyalty programs — points, tiers, rewards, and retention mechanics that keep customers coming back.

03 SKILL.md 正文

Overview

Loyalty programs increase repeat purchase, raise lifetime value, and generate first-party data. This skill covers designing programs that actually change behavior: choosing the right structure (points, tiers, paid, coalition), setting earn/burn economics, launching, and measuring incremental lift — not just rewarding purchases that would have happened anyway.

When to use

  • Designing a new loyalty program

  • Fixing an underperforming program

  • Choosing between points, tiers, or paid models

  • Setting reward economics

  • Increasing repeat purchase rates

  • Launching VIP or referral tiers

  • Revamping a stale points program

  • Launching paid loyalty tiers

  • Integrating loyalty with mobile apps

  • Designing coalition loyalty programs

Core concepts

Program structures. Points (earn and redeem — flexible, familiar), tiers (status-driven — Silver/Gold/Platinum), paid membership (upfront fee for benefits — highest commitment), coalition (multi-brand earning). Hybrid (points + tiers) is most common for good reason.

Earn/burn economics. Earn rate (points per dollar), point value at redemption, breakage (unredeemed points — typically 10–30%), and liability management. Model: incremental margin from lift must exceed reward cost + program operating cost. Target reward cost at 1–3% of revenue for most retail.

Behavioral design. Reward the behaviors you want: not just purchases, but reviews, referrals, social shares, profile completion, app downloads. Tier thresholds should stretch the middle customer slightly — achievable but aspirational.

Status and psychology. Tiers work on status and loss aversion (nobody wants to drop from Gold). Progress bars, "you're 200 points from Gold" nudges, and surprise-and-delight rewards drive engagement beyond pure economics.

Data value. Programs generate identified purchase data: personalization, targeted offers, churn prediction. This data value often exceeds the direct revenue lift — quantify it.

Incrementality. The key question: did the program cause the purchase, or just reward it? Measure with holdout groups (eligible non-members) or pre/post analysis of enrolled cohorts vs. matched controls.

Earning velocity. Members should earn a meaningful reward within 2–3 purchases — slow earn rates kill engagement before habits form. Model: average order value × earn rate × purchase frequency = time to first reward. If first reward takes 10+ purchases, redesign — most members never get there. Tier psychology. Silver/Gold/Platinum works because status is relative and visible. Tiers need meaningful differentiation (not just 5% vs. 7% off) and achievable entry (60–70% of members should reach tier 2). Publish tier criteria transparently; mystery thresholds breed suspicion. Paid loyalty (Prime-style). Membership fees create commitment and fund richer benefits. Works when: purchase frequency is high, benefits are tangible (free shipping, not "exclusive access"), and the fee pays for itself in 3–4 orders. Test willingness-to-pay before building — surveys lie, pilots do not.

Practical workflow

  1. Define objectives. Repeat purchase rate? Average order value? Visit frequency? Data capture? One primary objective drives design choices.
  2. Choose the structure. Match to purchase frequency and margins: high frequency → points; aspirational brand → tiers; subscription-like → paid membership. Keep it simple enough to explain in 30 seconds.
  3. Model the economics. Earn rates, redemption values, expected breakage, tier distribution, incremental lift assumptions. Stress-test: what if breakage is lower than expected? What if top tier is overpopulated?
  4. Design earn/burn rules. What earns (purchases + bonus behaviors), what rewards (discounts, free products, experiences, early access — experiences often motivate more than discounts), expiration policy (drives urgency; 12–18 months typical).
  5. Build and launch. Enrollment (frictionless — auto-enroll at purchase with opt-out beats opt-in forms), communications (welcome, points balance, tier progress, reward reminders), staff training (they must sell it at point of sale).
  6. Measure and optimize. Enrollment rate, active rate (% earning/redeeming), repeat purchase lift vs. control, breakage, reward cost as % of revenue, NPS of members vs. non-members. Adjust earn rates and rewards annually.

Launch checklist: simple value proposition, easy enrollment, welcome reward (immediate gratification), clear earn rules, visible progress tracking, staff able to explain it, communications calendar, fraud controls.

Program design canvas: earning mechanics (what earns points: purchases only, or also reviews, referrals, engagement?) → tiers (2–4 levels; name them aspirationally) → rewards (mix of discounts, exclusives, experiences — experiences drive emotional loyalty, discounts drive transactions) → redemption friction (points must be easy to understand and spend) → breakage target (unredeemed points are profit but also disengagement — aim for healthy redemption, not maximum breakage).

Launch math: incremental margin from lift in frequency and AOV must exceed reward costs + program ops. Model: (members × incremental visits × margin per visit) − (points issued × redemption rate × cost per point) − platform costs > 0. Pilot with a segment before full rollout.

Program health metrics: enrollment rate → activation rate (earned or redeemed in 90 days) → repeat purchase lift (members vs. non-members) → redemption rate → breakage → NPS of members vs. non-members. Review monthly; declining activation is the earliest warning — fix onboarding before rewards. Win-back for lapsed members: identify dormancy (no earn/burn in 6 months) → remind of point balance ("you have $12 waiting") → limited-time bonus → survey non-responders. Point-balance reminders are the highest-ROI loyalty email — unredeemed value motivates.

Common pitfalls

  • Rewarding non-incremental behavior. Paying for purchases that would happen anyway. Design for lift, measure incrementality.
  • Too complex. Earning rules nobody understands. If it needs a manual, simplify.
  • Unattainable tiers. Top tier so exclusive it demotivates everyone else. Calibrate thresholds to stretch, not exclude.
  • Ignoring breakage risk. Assuming high breakage to fund generosity — if redemption spikes, liability explodes. Model conservatively.
  • No expiration. Points accumulating forever create growing liability and no urgency. Expire thoughtfully.
  • Launch without staff buy-in. Frontline staff who can't explain the program kill enrollment. Train and incentivize them.
  • Discount-only rewards. Training customers to wait for points instead of buying. Mix in experiential and status rewards.
  • Devaluing points. Changing earn/burn rates punitively destroys trust overnight. If economics require change, grandfather existing balances and communicate far in advance.
  • Rewards nobody wants. Discounts on products members do not buy. Survey members on desired rewards before designing the catalog.
  • Complexity. Earning rules nobody understands. If members cannot explain the program in one sentence, simplify.
  • Rewarding transactions, ignoring emotion. Points for purchases but nothing for birthdays, anniversaries, or referrals. Emotional rewards build loyalty; transactional rewards build mercenaries.
  • Expiration surprises. Points expiring without warning. Notify before expiry — surprise expiration destroys trust instantly.
  • No tier requalification clarity. Members confused about maintaining status. Publish clear, achievable requalification rules.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0