Gamified Loyalty Platforms — Current Market
Modern enterprise loyalty platforms with gamification layers. None of them do what Guild does.
Antavo
What it is: Enterprise loyalty management platform. Mid-market to enterprise (Levi’s, KFC, Benefit Cosmetics). Composable, API-first, modular architecture. HQ in London/Budapest.
Gamification layer: Challenges, leaderboards, quizzes, treasure hunts, UGC rewards (points for reviews/photos). Leaderboards show customer rank. Challenge campaigns with spend/visit triggers. Badges for milestones.
POS integration: APIs and webhooks connect to POS systems, e-commerce, CRM, marketing clouds. Physical kiosk modules exist for in-store sign-up and redemption. Not pre-built Square integration — requires custom API work.
What it lacks: No RPG class system. No narrative layer. No character identity. No XP leveling. Gamification is additive to a points program — a badge here, a challenge there. The underlying structure is still a points-and-tiers dashboard. The character sheet is nowhere.
Price point: Enterprise SaaS, typically $1,000–5,000+/month. Not SMB-accessible.
Open Loyalty
What it is: Open-source-core, API-first loyalty platform. Targets mid-enterprise retailers. Clients include Heineken, JTI (tobacco), INTERSPORT, ALDO (45+ countries). Won Deloitte/Google Tech Rocketship 2024. Listed in Gartner’s Market Guide for Loyalty Program Vendors.
Gamification layer: Challenges, wallets, points, tiers, leaderboards. No-code campaign builder for marketers. QSR-focused research suggests “challenges and streaks” outperform badges alone for restaurant engagement. Standard behavioral gamification playbook.
What it lacks: Same as Antavo — no RPG narrative, no class identity, no character sheet. The platform is a flexible engine for building sophisticated points programs with game-like features bolted on. Not a game-first design.
Open source note: The community edition is available but the enterprise features (multi-tenant, advanced analytics, SLA support) require a paid contract. Theoretically forkable for a custom implementation, but not designed to be self-hosted by an indie bookstore.
Captain Up
What it is: Behavioral psychology + game mechanics platform for user engagement and retention. Originally B2C (gaming sites, media), now B2B loyalty. Won Gold “Innovation in Mobile” 2024 and 2025.
Gamification layer: Missions, levels, badges, leaderboards, streaks, virtual goods. More game-native than Antavo or Open Loyalty — the vocabulary is closer to actual game design. Levels exist (not just tiers). Mission systems.
What it lacks: Generic gamification vocabulary — levels and missions but no class identity, no world-building, no narrative. The “game” is a points game dressed in game language. Still no answer to “what does it mean to be a Mage vs. a Warrior” — both would just be level 14 with the same XP bar.
Relevant observation: Captain Up comes closest to Guild’s vocabulary (missions, levels) but the identity layer — the part where your class reflects who you are and routes you into a different relationship with the merchant — doesn’t exist in any platform reviewed.
The Market Gap
Every platform reviewed follows the same design pattern:
points → tier → earn multiplier → reward redemption
+ optional gamification layer (badges, challenges, leaderboards)
The gamification is a feature added to a points program. The identity layer — who you are inside the system — is absent or reduced to tier names.
Guild’s design inverts this:
class identity → behavior routing → XP accrual → level progression
→ tier (paid subscription)
→ universal currency (store credit)
The game is the container, not the feature. Class shapes the experience from day one: a Mage and a Warrior are routed differently, see different quest prompts, unlock different perks, receive different event invitations. This is what none of the platforms above have built.
The Class Differentiation Problem
The hardest design question in Guild’s system: what makes a Level 14 Mage meaningfully different from a Level 14 Warrior, beyond cosmetics?
The predecessors all failed this test — their game mechanics were cosmetic overlays on identical underlying programs. Here’s the model for making class identity functional:
Classes should reflect actual behavioral identity
Class assignment isn’t arbitrary. It should map to real observed patterns:
| Class | Behavioral signal | Example at Dungeon Books |
|---|---|---|
| Mage | Deep into lore, long reads, world-building | Buys fantasy/sci-fi, attends author talks |
| Warrior | Action-oriented, systems thinker | Buys RPG sourcebooks, tabletop, wargames |
| Healer | Community-builder, social hub | Hosts events, brings friends, refers members |
| Rogue | Eclectic, hidden-gem seeker | Buys used books, obscure back-catalog, staff recs |
If the class assignment reflects who you actually are, wearing the class feels like recognition, not randomization. It’s closer to a personality type than a team assignment.
Perks must follow the behavioral logic
The class isn’t meaningful unless it routes you into genuinely different experiences:
| Class | Perk direction |
|---|---|
| Mage | Early access to new releases, author event priority, reading list curation from staff |
| Warrior | New RPG system drops, game demo nights, first access to limited print sourcebooks |
| Healer | Social XP bonus (friend referrals, event hosting), community recognition, group discount unlocks |
| Rogue | Staff pick queue, access to hidden inventory, “secret menu” discounts on back-catalog |
If a Level 14 Mage gets author event priority and a Level 14 Warrior gets first access to RPG drops, the classes are functionally different. The level is the same; the relationship to the store is different.
Name Level (9) as the inflection point
In BECMI, level 9 is “Name Level” — the point at which a Fighter builds a castle and becomes a minor lord, a Magic-User builds a tower and attracts apprentices. The game changes from leveling up to building a legacy. The player stops being a visitor to the world and starts being part of its architecture.
This is what SCVNGR was originally reaching for with “the game layer on top of the world” — at high enough engagement, players shape the world. Priebatsch had the right idea and the wrong scale. You don’t need to overlay the game on all of reality; you need one world small enough that a high-level player can visibly change it. The store is that world — not the dungeon, the guildhall. The dungeon is out there. The guildhall is where you return, level up, post your quests, and eventually put your name on the wall.
At level 9, the mechanic shifts from “earn XP toward a number” to “leave your mark”:
| Class | Name Level title | Real-world unlock |
|---|---|---|
| Fighter | Warlord | Named plaque on the physical “Hall of Heroes” wall in the store |
| Magic-User | Wizard | Write a “spellbook entry” — a recommendation card displayed on the shelf |
| Cleric | High Priest | Nominate the theme for a future event (community vote) |
| Rogue | Shadowblade | Access to a secret quest no other class can see |
The BECMI framing earns its keep here. A level-9 Wizard’s recommendation card is a physical artifact in the store — part of the world, not just a number on a screen. That’s harder to churn away from than any badge. The player has become part of the place.
This idea should be developed in guild-achievements or rpg-loyalty-system-design.
The retention mechanism
This is why the class system solves the intrinsic value problem that killed Foursquare and SCVNGR:
- A Foursquare mayorship had no utility — it was a leaderboard position
- A Dungeon Books Mage membership means you get the ARC before it hits the shelf
The game layer (XP, levels, class) is an interface to a relationship that has real value. The Mage isn’t incentivized to keep showing up because of the XP bar — they’re incentivized because this is the store that knows they’re a Mage and acts accordingly.
Class identity is the mechanism that converts “a store with a loyalty program” into “a store that knows who you are.”
POS Integration Comparison
| Platform | Square integration | Real-time webhooks | SMB price |
|---|---|---|---|
| Antavo | Custom API | Yes (generic) | $1,000+/mo |
| Open Loyalty | Custom API | Yes (generic) | $500+/mo |
| Captain Up | Limited | Limited | $200+/mo |
| Guild | Native (built on Square) | Yes (Square webhooks) | $99–299/mo |
Guild’s Square-native architecture is a structural advantage for any SMB already on Square. No middleware, no custom integration project. The purchase event fires, the XP engine responds.
Related
- gamified-loyalty-prior-art — SCVNGR, Foursquare, Gowalla, Niantic (historical cases)
- rpg-loyalty-system-design — XP math, BECMI leveling table, class assignment logic
- roles-classes-jobs — Tank/DPS/Support role system design
- square-loyalty-decision — why Guild doesn’t use Square Loyalty
- magic-loyalist-comp — Magic/Loyalist (current well-funded competitor)