Event Passport: Predictable Annual Revenue
Executive Summary
Today, RRI sells each event individually. Every ticket is a separate transaction, a separate marketing campaign, a separate conversion funnel. The Event Passport flips this model: one annual subscription that includes multiple events.
Three tiers create a predictable revenue ladder: Base ($1,997/yr) for all virtual events, + Mastery Path ($2,997/yr) adding the monthly subscription progression from S3, and VIP ($7,997/yr) including one in-person event. Marketing sells once per year instead of five separate times.
Revenue becomes predictable. At 5,000 passport buyers, this represents $10M+ in predictable annual revenue — money that arrives before events are even scheduled. This transforms RRI from an event company that sells tickets into a subscription company that delivers experiences.
What Needs to Happen
- Design passport tier structure and define included events per tier — Map which events are included at each tier. Define upgrade paths between tiers. Establish renewal incentives and early-bird pricing for Year 2 renewals.
- Build subscription products in Stripe with annual billing — Create annual billing products with correct pricing. Configure Stripe to handle mid-year upgrades with proration. Set up renewal reminders and grace periods for failed payments.
- Create Salesforce Event Credit auto-allocation logic — When a passport is purchased, automatically create
Event_Credit__crecords for each included event. Credits should auto-allocate based on tier and be visible in Members Portal. Tim Hooker’s team owns the Salesforce side. - Build passport management UI — Subscriber dashboard showing passport tier, available credits, redeemed events, and upgrade options. Upgrade/downgrade flows with clear pricing comparison. Cancel flow with retention offers.
- Integrate with event registration system — Passport holders skip the checkout flow entirely when registering for included events. One-click registration using allocated Event Credits. Integration with
rri-event-apifor attendee sync to Obv.io. - Marketing landing pages with tier comparison — Side-by-side comparison of Base, + Mastery Path, and VIP tiers. ROI calculator showing savings vs. individual ticket purchases. Jesse’s marketing team builds in HubSpot or Sanity.
- Pilot with 50-100 buyers at Business Mastery (August) — Soft launch to highest-value attendees at Business Mastery event. Measure purchase velocity, tier distribution, and buyer feedback. Iterate pricing and packaging before full launch.
- Full launch at Date with Destiny (September) — Scale to all event attendees. Full marketing push with tier comparison and savings messaging. Target 5,000 passport holders by end of Q4 2026.
Claude Code acceleration: Stripe subscription code, Event Credit allocation logic, and the passport management UI are all highly automatable. The Salesforce integration for auto-allocation is the most complex piece but follows established patterns from order-ingestion. Estimated savings: 2-3 weeks (from 8 weeks to 5-6 weeks).
Completion Criteria
- Passport tiers purchasable via Stripe with correct annual billing
- Event Credits auto-allocated in Salesforce upon passport purchase
- Upgrade/downgrade between tiers working with correct proration
- Passport holders can register for included events with one click (no checkout)
- Marketing landing pages live with tier comparison and ROI calculator
- Pilot completed at Business Mastery with 50-100 buyers
- Full launch executed at Date with Destiny
Initiative Attributes
Tools Required
| Tool | Purpose | Cost |
|---|---|---|
| Stripe Billing | Annual subscription management, proration, renewal reminders | 2.9% + 30c per transaction (existing) |
| Salesforce | Event Credit auto-allocation, subscription lifecycle tracking | Existing license |
| Sanity CMS | Marketing landing pages and tier comparison content | Existing license |
| Members Portal | Passport management UI, credit dashboard, one-click registration | Existing infrastructure |
Related Risks
No direct risk factors mapped to this initiative. S4 depends on upstream work (U3 SSO, U4 PAD) being complete, but carries no independent structural risks. The primary risk is market acceptance — which is why the Business Mastery pilot exists before full launch.