Mithril Consulting | Client: Ticketmaster Authored by: Aragorn (Managing Consultant) Slogan: "Guiding every agent toward the goal." Date: 28 April 2026 Engagement: Iteration 12 — Octalysis Fan Loyalty Engine
Ticketmaster has a structural product problem: across the customer lifecycle (Discovery → Purchase → Pre-event → Attend → Post-event → Re-engagement), there is currently no continuous identity, status, mastery, or community signal. Every fan re-enters the funnel at zero. The platform activates only the two most ethically risky gamification drives (scarcity at sale moments, loss-avoidance via cart timers) — both at the customer rather than for them — while leaving the five sustainable engagement drives (Meaning, Accomplishment, Creativity, Ownership, Social) entirely dormant. This is the inverse of every successful consumer engagement architecture in adjacent categories (Starbucks Rewards, Duolingo, Sephora Beauty Insider, Spotify Wrapped, Manchester United, Ultra Music Festival Passport).
Iteration 12 introduces the Fan Loyalty Engine as the visible product surface that closes that gap. It is a recognition architecture — not a points programme, not a rewards programme, not a paid priority queue. It consists of four interconnected components: a persistent Fan Profile; a four-tier Fan Status ladder (Newcomer / Regular / Devoted / Lifer); a growing Fan Artefact collection (commemorative tickets, milestone badges, Year in Live cards); and personalised Fan Surfaces at eight specific journey moments where the trust deficit is greatest and where gamification mechanics can address it without manipulation.
The architectural premise is bound by three commitments that the Iteration 12 prototype implements as working UI, not as marketing copy:
The recommendation to Ticketmaster's senior leadership: take the Iteration 12 design forward as the basis for the next product release. The Fan Loyalty Engine is the structural change that the customer-trust position has needed for several quarters; the prototype demonstrates that it can be implemented within the constraints that the regulatory, ethical, and commercial environment now imposes.
The work that produced this recommendation could not have been produced by a single AI system or a single individual consultant. It crossed four fundamentally different reasoning modes — forensic evidence synthesis, human-centred design, engineering build, and trust-restoring communication — under a quality-and-ethics gate. This is precisely the scenario in which an agentic organisation outperforms both a single-model approach and a traditional consulting team.
Why a single AI system would have failed. A single model asked to "design a gamification layer for Ticketmaster" would have generalised across the four reasoning modes and diluted each. It would have produced a research summary that read as a design document, a design that read as a build specification, communication that read as research framing. The specialisation that an agentic pipeline imposes — Saruman only researches, Galadriel only designs, Gimli only builds, Pippin only communicates — preserves the depth of judgement that each mode demands.
Why a traditional consulting team would have been too slow. The same five specialists working as a traditional team would have produced equivalent quality at 10–20× the cost and 5–10× the elapsed time, with no ability to iterate the entire deliverable in days. The Iteration 12 work was completed in a single working day from research brief to executive summary; a traditional engagement would have completed it in 4–8 weeks.
Why the gate matters. The four review points (Saruman → me → Galadriel → me → Gimli → me → Pippin → me) caught and corrected three concrete issues that would have compounded otherwise: (a) at Review 1, I confirmed Saruman had stayed within the Researcher's lane and not selected Core Drives — protecting Galadriel's design discretion; (b) at Review 2, I confirmed the Octalysis Design Rationale table was complete and bound — giving Gimli a contract to build to; (c) at Review 3, I verified Gimli had built CD8 (Loss Avoidance) into nothing — protecting Pippin's framing position. Without the gate, these errors would have propagated and the Iteration 12 work would not have held its ethical line.
HBR ("Obelisk") parallel. The pipeline architecture mirrors the multi-agent consulting models being analysed in Harvard Business Review's recent work on agentic organisations: specialised agents with clear handoff contracts and a named orchestrator. The Iteration 12 deliverable is a working instance of that architecture against a real client problem.
| Agent | Contribution | Critical decision |
|---|---|---|
| Saruman (Research) | Introduced the Octalysis Framework as the strategic lens; identified Problem 10 (purely transactional engagement architecture); flagged eight gamification opportunities (G1–G8) with the trust deficit each addresses; produced the gamification competitive landscape and the Black Hat ethical risk register | Held the role boundary: did not select Core Drives, did not specify mechanics. Left the design canvas for Galadriel. |
| Aragorn (Review 1) | Approved Saruman's brief; confirmed multi-agent justification was now embedded; bound Galadriel to the disclosability test as the binding ethical position | Refused to let the brief overstep into design |
| Galadriel (Design) | Consolidated Iteration 11's social and post-event features into a coherent Fan Loyalty Engine architecture; designed the Fan Profile + four-tier Fan Status ladder + Fan Artefacts; mapped Octalysis Core Drives onto each of G1–G8; produced the Octalysis Design Rationale table | Held the ethical line: 13 design concepts, all leading with White Hat; CD8 used in zero design concepts; status only gained, never lost |
| Aragorn (Review 2) | Approved Galadriel's spec; confirmed the Octalysis Design Rationale table was Gimli's binding contract; named the seven non-negotiables for the build | Refused to let the design extend gamification beyond G1–G8 |
| Gimli (Build) | Extended the Iteration 11 prototype with three new screens (Fan Presale, Pre-Event Hub, Show Memory); rebuilt the Profile screen as the Fan Profile with four collapsible sections; added the tier badge component used across the app; built the lapsed-fan welcome-back card with zero loss-avoidance copy | Built the Fan Presale countdown as a real ticking timer; built the Show Memory mood input as private-by-default; built every gamification mechanic as working interactive UI rather than static placeholder |
| Aragorn (Review 3) | Approved Gimli's prototype; confirmed all seven Iteration 12 non-negotiables held; named the framing constraints that Pippin's communication had to honour | Refused to let any feature flagged DEFERRED be communicated as if shipped |
| Pippin (Communicate) | Produced the Go-to-Market Package built around the core message "Ticketmaster remembers"; wrote the trust-rebuilding narrative that names the actual problems; produced finished UX copy for every Iteration 12 surface; wrote Campaign 2 ("Why Am I Seeing This?") to treat EU AI Act Art. 50 transparency as a feature in its own right | Held the binding language constraint: no "streak / lose / expire / FOMO" in any loyalty copy; no "points programme" framing anywhere |
| Aragorn (Review 4) | Approved Pippin's package; confirmed every binding constraint held; closed the iteration | Verified the chain held end-to-end |
Yes, on three load-bearing tests:
The diagnosis is sound: Ticketmaster currently activates only the two highest-risk gamification drives (scarcity, loss-avoidance) and uses both at the customer rather than for them. The five sustainable drives are dormant. This is structurally backwards relative to every successful consumer engagement programme in adjacent categories. The Fan Loyalty Engine inverts this: White Hat foundation (recognition, mastery, ownership, community), Black Hat used sparingly and truthfully (presale countdowns; nowhere else). The architectural premise is correct.
Iteration 12 was the highest-risk single iteration in this engagement because gamification on top of a damaged trust position is the move most likely to compound the brand harm. The pipeline held the line: status is gained, never lost; the Fan Presale qualifies on real history; the Show Memory is private by default; AI personalisation is honest about what it does and does not use. The Black Hat ethical risk register that Saruman established at the research stage and Galadriel built into the design is now visible in the prototype. The work deepens trust; it does not damage it.
Mid-eight-figure GBP order-of-magnitude recoverable annual revenue if 10% of currently-churning customers are retained by the introduction of a credible motivational engagement layer (Saruman §4 Problem 10 estimate; low-to-moderate confidence; industry composites, not Ticketmaster proprietary). The five KPIs Pippin has recommended are the right tests of this hypothesis — particularly KPI 5 (lapsed-fan reactivation against a discount-led control), which builds in a specific test of whether the ethical commitment costs revenue.
The commercial recommendation: invest in the Fan Loyalty Engine as the next product release; instrument the five KPIs from launch; review the lapsed-fan reactivation result at 90 days as the load-bearing decision point on whether the ethical commitment is also commercially viable. Mithril's confidence is high that it will be — but the test must be run.
Every personalised surface in the Iteration 12 prototype carries a "Why am I seeing this?" affordance and a plain-language disclosure of what data is used. The Fan Profile Privacy & Data section is the single source of truth for loyalty-engine consents. Ticketmaster is positioned ahead of the regulatory floor.
The AI Feature 5 specification (Fan Loyalty Engine) explicitly prohibits vulnerability-targeting logic. The engine has no inputs that signal user financial, emotional, or attentional state, and the design specification in Galadriel's §8 binds the implementation to that prohibition. Gimli's build does not contain any time-sensitive nudges that key off such signals. The disclosability test that Saruman established (§8.1) is the operational rule the design and build held.
The CMA-disfavoured patterns (false urgency, fake low-stock indicators, drip pricing, default opt-ins, confirmshaming) are absent from the Iteration 12 build. The Fan Presale countdown is real; the Fan Status downgrade does not exist; pricing transparency is preserved from Iteration 11; the Privacy & Data toggles default to OFF for social features and ON for personalised recommendations (with an immediate one-tap path to disable).
"Status is gained, never lost." This is implemented in the design (no downgrade UI anywhere), in the build (Gimli held it), in the communication (Pippin made it visible in five places). If Ticketmaster honours it in production, Iteration 12 will be remembered as the iteration where the platform's ethical position changed. If Ticketmaster breaks it in production by introducing a downgrade mechanic later, the Iteration 12 work was wasted. The commitment is the iteration.
Ticketmaster currently treats every fan as a transaction. After Iteration 12, the platform remembers them. That structural change — implemented as a Fan Profile, a Fan Status, a Show Memory, and the binding ethical commitment that status is gained but never lost — is the basis on which the customer-trust position can begin to be rebuilt. The design is ready, the prototype is built, the communication is written, the regulatory posture is sound. The recommendation to senior leadership: ship it.
| # | Document | Author | Length | Status |
|---|---|---|---|---|
| 01 | Saruman Research Brief | Saruman | ~360 lines new material | Approved |
| 01a | Aragorn Review 1 of Saruman | Aragorn | — | Approved |
| 02 | Galadriel Design Specification | Galadriel | full Iteration 12 spec | Approved |
| 02a | Aragorn Review 2 of Galadriel | Aragorn | — | Approved |
| 03 | Gimli Working Prototype Documentation | Gimli | full build manifest | Approved |
| 03 (HTML) | Iteration 12 Working Prototype | Gimli | 3,487 lines | Demonstrable |
| 03a | Aragorn Review 3 of Gimli | Aragorn | — | Approved |
| 04 | Pippin Go-to-Market Package | Pippin | full GTM package | Approved |
| 04a | Aragorn Review 4 of Pippin | Aragorn | — | Approved |
| 05 | This Executive Summary | Aragorn | — | Final deliverable |
All documents in Output/Iteration 12/. Iteration 12
pipeline complete.
Aragorn — Managing Consultant, Mithril Consulting "Guiding every agent toward the goal."
Last edited: 29 April 2026