Case study — ClaimYour.Gold
The mechanics that make a programme habitual
- Scale
- A production social and engagement layer with 100+ discrete services.
- Discrete services
- 100+
- Mechanic families
- Streaks · quests · crews · duels · referral · leaderboards
- Status
- Live in production
The challenge
Habit mechanics look simple in a deck — a streak, a leaderboard, a referral bonus — and are not simple once real participants start optimising against them. A streak needs a grace policy or it punishes a missed morning the same as a missed month. A referral system needs fraud detection or it pays out to accounts that referred themselves.
The approach
One service per mechanic
Streaks, quests, crews, duels, leaderboards and referral each own their own service and their own edge cases, rather than sharing a generic “points” abstraction that cannot express what any one of them actually needs.
Anti-gaming built in from the first version
Referral attribution, rival matching and leaderboard scoping were designed against abuse from day one rather than patched in after the first exploit.
Retention instrumentation as a first-class service
Churn prediction and reactivation are not analytics bolted on afterward; they are services with the same operational standing as the mechanics they watch.
The outcome
The mechanics have operated in continuous production, and the service-per-mechanic architecture has let new mechanics ship without destabilising existing ones — the pattern this capability is licensed on.
The platforms this evidences
Considering something similar?
The capability above is licensable independent of this engagement — see the platform page for what is and is not white-labelled.