Guild Pro: a verified operating system for game communities

The brief

Another founder build - and the most technically interesting system I’ve shipped. World of Warcraft guilds are 25-to-100-person volunteer organizations with scheduling, personnel, and compensation problems that would strain a real company: who signed up, who actually showed, who received which rewards, and whether any of it was fair. The tooling guilds actually use is a pile of spreadsheets, Discord messages, and tribal memory.

Guild Pro is the operating system for that: raid signups, rosters, verified attendance, an append-only loot ledger, recruitment, automations, and leaderboards - positioned around one wedge every guild leader feels weekly: the gap between the thirty people who clicked “yes” and the twenty-five who actually zoned in.

The hard problem: networking without a network

Here’s what makes Guild Pro a systems-design story worth telling. The authoritative record of what happened in a raid lives inside the game - and WoW addons are forbidden from making network requests. The core product promise (verified, synced data) has to be engineered around a sandbox that prohibits syncing.

The answer is a three-way circle of trust:

• An in-game addon records attendance, loot, and raid events as they happen, with raiders’ clients relaying observations to the raid leader over the game’s own addon-message channel - so one person holds the complete record
• A compressed wire format packs that record into chunked, checksummed payloads - a half-megabyte raid history that would take 140+ manual copy-pastes compresses to three
• A desktop companion app closes the loop hands-free: it finds every WoW install, manages the addon, reads the game’s saved data by running an embedded Lua interpreter, and uploads through a paired, token-scoped connection

Imports are content-addressed and idempotent - re-syncing can never double-count a raid or duplicate a loot award. For guilds that install nothing, combat-log ingestion through Warcraft Logs provides a zero-install path.

Discord as the front door

Guilds live in Discord, so Guild Pro does too - as a bot with an unusual architecture: no server process at all. Every command and button press is a signed, verified request handled at the edge within Discord’s three-second window. Signup sheets with class and role pickers, bench and tentative states, roster cards rendered server-side as shareable images, recaps, announcements - the whole guild workflow runs where the guild already talks. The bot deliberately installs with minimal permissions; expanded management powers are a separate, opt-in grant.

The AI layer - with a safety catch

Guild Pro ships an AI-accessible tool surface (built on MCP, the same protocol Claude uses) so a guild leader can run operations conversationally: post announcements, build events, manage channels and roles. The design rule I care most about: destructive operations don’t execute - they become proposals a human approves. Every AI action is triple-checked against token scope, live subscription tier, and Discord-side verification. It’s the pattern I advise clients toward everywhere: give AI real hands, and a real leash.

The business model

Guilds pay nothing - entire communities onboard free, because charging the group would kill adoption. Revenue comes from individual supporter subscriptions that unlock cosmetics and boost their guild toward premium leadership features, Twitch-style. One rule is written into the billing code: nothing derived from gameplay data is ever paywalled.

Results

• A three-surface product - game addon, Discord bot, web platform - shipped and syncing in production
• Compression and idempotency engineering that turns an offline game into a reliable data source
• An AI operations layer with proposal-based guardrails - agentic capability, human authority
• Community launched August 2026 and onboarding guilds now

Product screenshots and the launch story are being added as the platform grows.