initiative delivery

Tour Operator B2B Partner Portal

Sabrina (PM) Updated 2026-03-11 applications tour-operator
applications b2b-portal tour-operators partner-experience

Tour Operator B2B Partner Portal

MIGRATED FROM CONFLUENCE: This initiative was extracted from Confluence during the handbook consolidation project (Feb 2026).

The Bet

We believe that providing tour operators with a self-service B2B partner portal for property integration will: - Reduce partner onboarding time from 45 days to 14 days (70% improvement) - Reduce support ticket volume by 50% - Increase partner satisfaction scores by 30%

Because tour operators currently wait for manual account manager setup, creating bottlenecks and frustration.

Background

Current Partner Onboarding Process (45 days average)

  1. Sales handoff to account management (3-5 days)
  2. Manual property data collection via spreadsheets (10-15 days)
  3. Technical integration setup by engineering (15-20 days)
  4. Testing and validation with partner (7-10 days)
  5. Go-live coordination (3-5 days)

Key Pain Points Identified

From customer interviews with 12 tour operators (Oct-Dec 2025):

  • "We have to wait weeks for someone to get back to us" (8/12 partners)
  • "The spreadsheet process is error-prone and slow" (11/12 partners)
  • "We can't track progress or know where we stand" (10/12 partners)
  • "Our technical team is ready but has to wait for yours" (7/12 partners)

Target Metrics

Metric Current Target Impact
Avg onboarding time 45 days 14 days -70%
Support tickets/month 85 tickets 40 tickets -50%
Partner satisfaction 6.2/10 8.0/10 +30%
Account manager hours/partner 40 hours 12 hours -70%

Success Criteria

Phase 1: Self-Service Setup (Weeks 1-4)

  • [ ] Partners can register and authenticate independently
  • [ ] Property data can be uploaded via structured forms or CSV
  • [ ] Real-time validation and error feedback provided
  • [ ] Integration status dashboard shows progress

Phase 2: Technical Integration (Weeks 5-8)

  • [ ] API credentials auto-generated and securely delivered
  • [ ] Test environments provisioned automatically
  • [ ] Integration guides and documentation accessible in-portal
  • [ ] Technical support chat integrated

Phase 3: Go-Live (Weeks 9-12)

  • [ ] Production environment auto-provisioned after testing
  • [ ] Partners can initiate go-live independently
  • [ ] Monitoring dashboard shows integration health
  • [ ] Automated onboarding completion notification

Architecture Overview

Tour Operator Portal (Vercel + Clerk Auth)
    ↓
Partner Registration & Data Collection
    ↓
Property Validation Engine (New Service)
    ↓
Auto-Provisioning Service (New Service)
    ↓
Integration Testing Suite (Enhanced)
    ↓
Go-Live Automation (New Service)

Technology Decisions: - Frontend: Vercel (Next.js) - Fast deployment, great DX - Authentication: Clerk - B2B SSO support built-in - Backend: New microservices (not monolith extension) - Database: PostgreSQL for partner data - Integration: Existing Duetto APIs + new partner-specific endpoints

Team & Resources

Core Team: - PM: Sabrina (product strategy, partner requirements) - Tech Lead: TBD (architecture, API design) - Frontend Dev: TBD (React/Next.js portal) - Backend Dev: TBD (integration services) - Designer: TBD (partner-facing UX)

Stakeholders: - Account Management: Process handoff design - Customer Support: Reduced ticket handling workflow - Engineering Platform: Infrastructure requirements - Legal/Security: B2B data handling compliance

Timeline

Q1 2026 Delivery Schedule

Week Milestone Deliverable
Weeks 1-2 Foundation Clerk auth, basic portal structure
Weeks 3-4 Data Collection Property upload forms, validation
Weeks 5-6 Integration Engine API provisioning, test environments
Weeks 7-8 Testing Suite Partner testing dashboard
Weeks 9-10 Go-Live Automation Production provisioning
Weeks 11-12 Launch & Measure Beta partner testing, metrics collection

Risk Mitigation

Risk Probability Impact Mitigation
Partner resistance to self-service Medium High Hybrid model: assisted mode available
Complex integration edge cases High Medium Phased rollout, fallback to manual process
Data validation accuracy Medium Medium Comprehensive test suite, partner feedback loop
Infrastructure scaling Low High Auto-scaling architecture, load testing

Experiments Completed

Design Assets

Technical Specifications

Meeting Notes

Last Updated: 2026-02-24 by Sabrina Status: Ready for PRD generation and engineering handoff Next Steps: Generate PRD using /apex-prd command with experiment results