Portal Unification: 11 Portals → 1
Executive Summary
RRI customers today navigate 11 disconnected portals to access their purchases, events, coaching, content, and Tony AI. Each portal has its own login, its own UI, its own data silo. A customer who buys at UPW, subscribes to Tony AI, and enrolls in coaching has three separate accounts with no awareness of each other.
Portal Unification replaces all 11 with a single Tony Robbins portal built on Nick Jensen’s Experience API (Sanity + Next.js). One login. One home. Every purchase, every event, every coaching session, every piece of content, and Tony AI — all in one place.
This isn’t just a UI project. It’s the platform that makes cross-sell and upsell natural instead of forced. When a coaching client finishes a session, they see their next event. When an event attendee logs in, they see Tony AI. When a Tony AI user hits a plateau, they see the Mastery Path. Support costs drop because customers aren’t confused about which portal to use.
This is the largest SCALE initiative — 16-20 weeks with full completion in Q1 2027 — and it depends on U3 SSO being complete and S2 K8s migration providing the infrastructure foundation.
What Needs to Happen
- Audit all 11 existing portals — map features and data sources — Document every portal: Members Portal, Tony AI, RPM, coaching portals, event portals, content library, community platforms. Map which Salesforce objects, APIs, and databases each one uses. Identify overlapping functionality and unique features.
- Design unified information architecture — Create the single-portal IA: Home, My Events, My Coaching, My Content, Tony AI, My Account. Define navigation, data relationships, and personalization rules. Ken (UI/UX) leads design with Nick Jensen on technical architecture.
- Build Experience API foundation (Sanity headless CMS + Next.js) — Nick Jensen’s architecture: Sanity as the content and data orchestration layer, Next.js for server-rendered frontend. This is the “TR Experience” platform already in early development. Foundation demo expected within 2 weeks of project start.
- Implement SSO integration (depends on U3) — Single Cognito-based login across all portal features. Depends on U3 SSO being fully deployed. Users authenticate once and access everything. Session management must handle all downstream services.
- Migrate events module from Members Portal — Move event registration, ticket management, and event access from the legacy Members Portal (Node 11) into the unified portal. Integration with
rri-event-apifor Obv.io attendee sync. - Migrate coaching module — Move coaching session scheduling, AI summaries (from S6), progress tracking, and coach communication into the unified portal. Integration with Chris Schenke’s coaching team workflows.
- Integrate Tony AI as persistent companion — Tony AI becomes a persistent sidebar/widget available on every page of the portal. Context-aware: knows what page the user is on, their purchase history, their coaching progress, their event attendance. This is the “connective tissue” of the entire platform.
- Migrate remaining modules (content library, community) — Move content library (videos, courses, downloads), community features, and any remaining portal functionality. Each migration follows the same pattern: map data, build in Experience API, validate, sunset legacy.
- Sunset legacy portals one by one — Each legacy portal is sunset only after its replacement is validated in production. Redirect old URLs. Communicate changes to customers. Monitor for regressions. Target: all 11 legacy portals dark by end of Q1 2027.
- Mobile app via React Native (parallel track) — Once the Experience API is stable, build a React Native mobile app sharing the same data layer. Nick + Stacey are already planning React → React Native path. Parallel track that doesn’t block web portal.
Claude Code acceleration: The portal rebuild is fundamentally an architecture and design project that requires significant product decisions. Claude Code accelerates the implementation: API integrations, component scaffolding, migration scripts, and SSO plumbing. The 10 steps above compress from 16-20 weeks to 10-14 weeks, but the product design and stakeholder alignment phases cannot be compressed.
Completion Criteria
- Single portal serves events + coaching + Tony AI + content under one login
- SSO integration working — one Cognito login accesses all features
- Events module migrated from Members Portal with full functionality
- Coaching module migrated with AI summaries (S6) integrated
- Tony AI available as persistent companion across all portal pages
- Content library and community features migrated
- All 11 legacy portals sunset with URL redirects active
- Cross-sell and upsell paths working (e.g., coaching client sees Mastery Path upgrade)
- Mobile app in React Native launched or in beta
Initiative Attributes
Tools Required
| Tool | Purpose | Cost |
|---|---|---|
| Sanity CMS | Headless CMS for content orchestration and data modeling across all portal features | Existing license |
| Next.js | Server-rendered frontend for the unified portal | Free (OSS) + Vercel or K8s hosting |
| React Native | Mobile app sharing data layer with web portal | Free (OSS) |
| Cognito SSO | Single sign-on across all portal features (from U3) | $495-700/month (existing from U3) |
| Tony AI API | Persistent AI companion integrated across all portal pages | API inference costs |
Related Risks
| ID | Risk | Severity | Probability | Mitigation |
|---|---|---|---|---|
| RF1 | Nick Jensen disengagement / departure | CRITICAL | MEDIUM | Nick is the owner and architect of the Experience API. He is bus factor 1 on TonyRobbins.com and this entire initiative. If Nick leaves, S5 is at existential risk. Frame portal unification as his flagship project. D1 pairing sprint provides backup knowledge, but Nick’s architectural vision is irreplaceable in the short term. |
| RF5 | S2 Heroku migration misses September deadline | HIGH | MEDIUM | S5 needs K8s infrastructure from S2 to run at scale. If S2 is delayed, S5 can start on Heroku but will need re-deployment later. Plan for portable containerization from Day 1 to avoid rework. |