increase-repeat-purchases
Skill5 starsChanged 36 days agoMITView on GitHub
Use when someone wants more customers to come back and buy again — "repeat rate is low", "improve retention", "get a second order", "customers buy once and disappear", "what should our post-purchase flow do" — for any online store.
In this repository18 other files it gives its agents.
- checkout-uxSkill
- digital-product-pricingSkill
- discountsSkill
- event-pricingSkill
- increase-aovSkill
- increase-conversionSkill
- post-purchaseSkill
- price-researchSkill
- pricingSkill
- product-copySkill
- product-pageSkill
- product-visualsSkill
- promotionsSkill
- raise-pricesSkill
- referralsSkill
- reviewsSkill
- store-auditSkill
- subscription-pricingSkill
The file
Files
Increase repeat purchases
Turn "only 12% buy again" into a ranked backlog. Leave the how-to and the papers in the Depth skills. Several effects show up in retention over years, not in next month's numbers — say so. Every number is what a cited study measured in its own context; do not turn it into a forecast for the user's repeat rate.
When to use
- The user names repeat rate, retention, lifetime value, or "second order" as the goal
- Reviewing what happens after checkout: emails, box contents, returns, loyalty
When not to use
- First purchase →
increase-conversion; order size →increase-aov - Cart and payment-step UX →
checkout-ux; abandonment email timing stays here viapost-purchase - Review solicitation and complaint handling in depth →
reviews; referral mechanics →referrals
Inputs
Collect, or state your assumption:
- Product and how long it takes to judge (instant vs weeks)
- Post-purchase emails: what is sent, when, first question asked
- Box contents (inserts, codes, packaging)
- Return and refund policy; loyalty program (opt-in or automatic, tiers, reward type)
- Abandoned-cart email timing; whether the store replies to reviews
Procedure
Walk each check; include applicable levers the user didn't mention; list the rest as considered.
- Loyalty: automatic, single tier, threshold reward. Enroll everyone; one rule ("buy 10, get 1 at no cost"). Effect is in multi-year retention. Depth:
post-purchase. - Feedback request with a positive open-ended first question. "What did you enjoy most?" before any rating. Depth:
reviews. - Ask for reviews at 9–13 days, later for products that take weeks to judge. Measured on review volume, not repeat purchase; it is the delivery vehicle for step 2. Depth:
reviews. - Handwritten thank-you note, nothing attached. A discount on the note cancels the effect. Depth:
post-purchase. - Instant refund when the return ships. Carrier scan, not after inspection, for items that don't need inspection. Depth:
post-purchase. - Free, easy returns. Depth:
post-purchase. - Free-shipping membership with a minimum order. Depth:
post-purchase. - Reply to every review — measured on ratings and volume, not repeat. Depth:
reviews. - Abandoned-cart reminder at 24–72 h, never within the hour. Depth:
post-purchase. - Referrals as the next step once repeat customers exist: friend's benefit as the headline. Depth:
referrals. - Rank. Note which effects are long-horizon (loyalty) versus immediate (email timing, refund timing). Cheap changes ahead of program builds at equal effect.
Output
| # | Finding | Change | Measured effect (study context) | Horizon | Depth |
| 1 | Opt-in tiered points | Auto-enroll, single "buy 10, get 1" | +29.5% customer value over 5 years | Long | post-purchase |
| … |
Then: what already complies. Each effect was measured on its own; don't add them up. Ship the top two or three, measure, then take the next.
Common mistakes
- Inventing a lift ("could double repeat rate") — quote the study's number and its context.
- Building a replenishment sequence first — reasonable, but not in this evidence.
- Making the loyalty program visible but still opt-in — the finding is automatic enrollment.
- Keeping the discount on the thank-you note — it cancels the note's effect.
- Judging the loyalty program on next quarter's numbers — the effect is in multi-year retention.
Quick reference
| Lever | Depth | Horizon |
| Auto-enroll single-tier loyalty | post-purchase | Long |
| Positive open-ended first question | reviews | Immediate |
| Review ask at 9–13 days | reviews | Immediate |
| Handwritten note, no promo | post-purchase | Immediate |
| Refund on carrier scan; free returns | post-purchase | Immediate / ongoing |
| Abandoned-cart email 24–72 h | post-purchase | Immediate |
| Referral ask, friend's benefit first | referrals | Next |
Evidence and effect sizes: see reference.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

