Agent skill
loyalty-lifecycle
Customer loyalty and lifecycle orchestration - tiered loyalty design, lifecycle journey programs, milestone triggers, and retention economics for B2B and B2C.
Filed under Pricing and packaging.
From varunk130/ai-gtm-skill-library · 31 skills · 5 · pushed 2026-07-31
What it does when it runs
Customer loyalty and lifecycle orchestration - tiered loyalty design, lifecycle journey programs, milestone triggers, and retention economics for B2B and B2C. Use when: loyalty program, customer lifecycle program, tiered loyalty, milestone marketing, retention program design, lifecycle journey, loyalty economics, member tiers, retention motion.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/varunk130/ai-gtm-skill-library.git /tmp/ai-gtm-skill-library git -C /tmp/ai-gtm-skill-library sparse-checkout set "revops-skills/loyalty-lifecycle" mkdir -p ~/.claude/skills/loyalty-lifecycle cp -R "/tmp/ai-gtm-skill-library/revops-skills/loyalty-lifecycle/." ~/.claude/skills/loyalty-lifecycle/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from varunk130/ai-gtm-skill-library/blob/90e878c73a8fbfd1cab864424ccf674fdc889157/revops-skills/loyalty-lifecycle/SKILL.md, which is licensed MIT (repository). 785 words, 11 headings.
Loyalty & Lifecycle (BOND Framework)
Design a loyalty and lifecycle program that produces measurable retention lift - not a tier ladder for its own sake. BOND forces clarity on what behaviors loyalty is supposed to reinforce, what evidence the customer sees, and how the program economics actually pay back.
Core Principle
A loyalty program is a behavior contract, not a points system. Most loyalty programs fail because they reward existing behavior (free margin loss) instead of net-new behavior (retention lift). BOND structures the program around behaviors that change the unit economics.
The BOND Framework
| Letter | Stage | The Question |
|---|---|---|
| B | Behavior Targeting | Which 3-5 customer behaviors, if reinforced, would shift retention and LTV? |
| O | Offer Architecture | What earn / burn mechanics + tier benefits reinforce those behaviors? |
| N | Notification & Lifecycle | What lifecycle triggers and moments deliver the program in-context? |
| D | Defend the Economics | How does the program pay back, and what's the cannibalization guardrail? |
Behavior Targeting
A useful program changes behavior in measurable ways. Start with:
| Behavior Lift | Example Metric | Loyalty Lever |
|---|---|---|
| Frequency | Purchases per quarter | Visit-based earn, accelerator tiers |
| Basket / Expansion | Average order value, modules per account | Bonus earn on add-ons |
| Retention | Renewal rate, churn rate | Time-in-program rewards, tier downgrade protection |
| Advocacy | Referrals, reviews | Referral bonus, badge / status |
| Engagement Depth | Workflow coverage, feature adoption | Achievement-based rewards |
Tier Design
| Element | Best Practice |
|---|---|
| Number of tiers | 3-4; more dilutes status |
| Tier criteria | Mix of spend + behavior; behavior-only tiers possible |
| Tier benefits | At least one experiential benefit per tier (not just discounts) |
| Tier durability | Annual review or rolling 12-month; never punitive |
| Recognition | Visible status (badges, color, named cohort) at every tier |
Lifecycle Moments
Loyalty earns its keep when it shows up at moments that matter:
| Moment | Program Action |
|---|---|
| Onboarding | Welcome bonus + first-value reward |
| First repeat | Bonus earn + tier preview |
| Tier promotion | Status reveal + new-benefit walkthrough |
| Milestone (anniversary, usage) | Recognition + curated benefit |
| Risk signal (engagement drop) | Re-engagement reward, not generic discount |
| Tier downgrade risk | "Keep your tier" path with achievable bar |
| Win-back | Personalized re-entry offer with social proof |
Defend the Economics
A loyalty program is a long-lived liability. The economics must be defensible:
| Lens | Question |
|---|---|
| Incremental Retention | What's the retention uplift of program members vs matched non-members? |
| Incremental ARPU | Do members spend more because of the program, or were they pre-selected? |
| Cost of Liability | What's the unredeemed-points exposure on the balance sheet? |
| Cannibalization | What % of rewards subsidize behavior that would have happened anyway? |
| Payback Window | How long until program cost is recovered by incremental margin? |
Output
Save to outputs/loyalty-lifecycle-[program]-[YYYY-MM-DD].md
| Artifact | Description |
|---|---|
| Behavior Spec | Targeted behaviors and metrics they should move |
| Earn / Burn Mechanics | Point or status system, redemption catalog |
| Tier Architecture | Tiers, criteria, benefits, recognition |
| Lifecycle Trigger Map | Moments, triggers, program actions, owners |
| Economic Model | Incremental retention / ARPU, liability projection, payback |
| Member Communication Plan | Welcome, tier reveal, anniversary, risk, win-back |
| Governance | Tier review cadence, benefit refresh schedule, sunset criteria |
Process
- Pick 3-5 target behaviors with quantified retention / LTV thesis
- Design the earn / burn mechanics to reinforce those behaviors (not all behaviors)
- Architect tiers with experiential benefits and visible status
- Map lifecycle moments to specific program actions
- Build the economic model with incrementality controls
- Stand up governance - programs decay without quarterly refresh
Tips
- Status > discount - experiential benefits are stickier and cheaper
- Always test against a holdout - incrementality is the only honest metric
- Cap tier downgrade pain - punitive downgrades nuke trust
- Refresh the redemption catalog quarterly; staleness kills engagement
- Track liability like a finance line item, not a marketing footnote
Pairs With
- customer-success - Health signal informs risk-moment triggers
- growth-loop - Loyalty is a retention loop input
- customer-analytics - Incrementality and segment behavior analysis
- referral-program - Pairs naturally with advocacy and referral tiers
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- lifecycle-marketing-campaigns by realjaymes · 55
- account-lifecycle by taizen-ai · 8
Need help setting it up?
This page tells you what loyalty-lifecycle does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.