# PIVOT T2C — Strategy and Product Brief Use this as the source of truth for the product, proposal and RFP response. Do not invent a new strategy. Do not treat this as a generic travel app. Do not assume the goal is simply to build a booking website. The goal is to help PIVOT create a travel product it can sell repeatedly across the sports organizations it already works with. --- # 1. What PIVOT is trying to build PIVOT works with sports organizations, governing bodies and event partners. Those organizations already have athletes, parents, coaches and members traveling to competitions and events. Today, much of that travel happens outside of PIVOT. People search Google Flights. They book hotels separately. They use room blocks where available. They arrange the rest themselves. PIVOT already has the relationships. The opportunity is to give those relationships somewhere to transact. The product is called **Travel to Compete / T2C**. T2C should become the travel layer PIVOT can offer to every sports organization it works with. --- # 2. The main product idea PIVOT should build the product once. Each client gets its own branded version. For example: USA Karate gets its own travel experience. A wrestling organization gets its own version. A boxing organization gets its own version. The next client gets another version. The branding, events, fees and available travel products can change. The underlying platform stays the same. This is not a collection of separate websites. It is one multi-client platform. --- # 3. Why this matters The first client should not be the end product. The first client should create the product PIVOT can sell again. The second organization should be much easier to launch than the first. PIVOT should not have to commission another development project every time it signs a new client. A new client should mostly be configuration: - Create organization - Add logo and branding - Add events - Set booking fees - Choose active travel products - Add support information - Publish That is the long-term value. --- # 4. What we believe PIVOT should own PIVOT should own the parts of the experience that make the business valuable. PIVOT should control: - Client relationships - Client branding - Events - Traveler experience - Booking/service fees - Client-specific rules - Traveler data - Booking data - Reporting - Partner economics - Which travel products are turned on - How value is returned to the sports organization PIVOT does not need to recreate airline, hotel or payment infrastructure from zero. Those systems already exist. The product should connect to them. --- # 5. What should come from outside suppliers The platform should be able to connect to established providers for things such as: - Flight inventory - Hotel inventory - Ground transportation - Payment processing - Ticketing - CRM - Travel servicing - Nexion - Concur - Other future travel suppliers The exact supplier should not define the whole product. If PIVOT changes air suppliers later, the traveler experience should not need to be rebuilt. If PIVOT changes hotel suppliers later, the same principle applies. The product should sit above the suppliers. --- # 6. The first thing to prove Do not try to launch every part of the future vision at once. Start with the travel behavior where there is real demand. Based on PIVOT's current conversations, that is likely self-service air booking. The first working flow should be: Event → traveler chooses where they are coming from → traveler chooses who is traveling → live flight search → traveler selects flight → traveler information → booking/service fee → payment → booking created → confirmation → booking appears inside PIVOT Admin → PIVOT can see what happened and service the traveler The first product needs to prove this full loop: **Search. Book. Pay. Confirm. Service.** Do this completely before trying to build every future feature. --- # 7. Events are central to the experience This is not a generic leisure travel site. Travel begins with the event. The platform should already understand: - What event the traveler is attending - Where it is - When it begins - When it ends - When someone should reasonably arrive - When someone can leave - Whether there are preferred hotels - Whether there are room blocks - Whether the traveler may want to extend the trip Example: A family is traveling to a USA Karate competition in Spokane. The competition ends Sunday. The platform can offer: "Your competition ends Sunday. Stay four more days?" If the traveler says yes, the trip can change around that choice. The point is to make the booking experience understand why the person is traveling. --- # 8. Traveler types matter Different travelers have different needs. The platform should recognize: - Athlete - Athlete + parent - Family - Coach - Staff - Other approved traveler types Most travelers are expected to book economy. Upgrades should still be available when appropriate. The product should not assume every traveler has the same needs. --- # 9. PIVOT needs its own backend PIVOT should have a simple internal control room. This is not a technical database interface. It is the place PIVOT operates T2C. PIVOT Admin should eventually allow the team to manage: ## Organizations - Client name - Logo - Branding - Support information - Active modules - Commercial settings - Status ## Events - Event name - City - Venue - Competition dates - Suggested arrival date - Suggested departure date - Room block information - Preferred hotel information - Status ## Travel products Turn modules on or off: - Flights - Hotels - Ground transportation - Experiences - Future services ## Fees - Domestic booking fee - International booking fee - Client subscription - Other commercial settings ## Travelers - Traveler - Organization - Event - Booking status - Contact information - Travel dates ## Bookings - Booking - Supplier - Traveler - Event - Amount - Fee - Status - Confirmation - Support status ## Reporting PIVOT should be able to answer: - Who booked? - Which organization did they come through? - Which event are they attending? - How much travel is moving through the platform? - What did PIVOT earn? - What value belongs to the partner? - Which bookings need attention? - Which organizations are growing? - Which events are driving activity? --- # 10. PIVOT should be able to change normal business information without Pure Strategy If an event date changes, PIVOT changes it. If a client logo changes, PIVOT changes it. If PIVOT signs another organization, PIVOT creates it. If a booking fee changes, an authorized PIVOT user changes it. If flights are turned off for one program, PIVOT controls that. PIVOT should not need an engineer for normal operating changes. Engineering should control sensitive technical areas such as: - API credentials - Supplier logic - Security rules - Payment secrets - Database permissions - Integration code - Webhooks - Core calculation logic --- # 11. The business model for PIVOT T2C should create two possible revenue streams for PIVOT. ## Platform revenue PIVOT can charge a sports organization for access to its branded T2C program. This could include: - Client onboarding/setup fee - Monthly platform subscription - Premium modules PIVOT decides what it charges each client. ## Travel revenue PIVOT can also earn from the actual travel business. Potential economics include: - Booking/service fees - Hotel commissions - Supplier commissions - Markups where appropriate - Sponsorship economics - Rebates - Packages - Ground transportation - Experiences - Other future travel products Pure Strategy should not take a permanent percentage of every travel booking. PIVOT should keep the upside of its travel business. --- # 12. The business model for Pure Strategy Pure Strategy is the technology partner. The recommended model is: ## Initial build A fixed development fee creates: - T2C Core - PIVOT Admin - First live client - First working transaction - Core integrations - White-label foundation Current working price: **$34,000 for the initial build.** ## Ongoing platform Once the product is live, PIVOT pays a predictable platform fee. This can include: - Core platform maintenance - Monitoring - Security - Infrastructure oversight - Core product improvements - Technical support ## Additional client environments As PIVOT adds more organizations, each active client environment can carry a predictable wholesale platform fee. PIVOT decides what it charges the end client. Pure Strategy should not take a percentage of whatever PIVOT charges. ## Premium modules Future modules can create additional platform revenue. Examples: - Hotels - Ground - Advanced reporting - CRM automation - Team travel - Experiences - Advanced intelligence ## Custom work Client-specific features that are not part of the common T2C product are separately scoped. --- # 13. How new features should work T2C should become stronger for every client over time. There are three types of product work. ## Core improvements These improve the main platform. Examples: - Better mobile experience - Better search - Security improvements - Performance improvements - Booking management improvements - Core reporting improvements Core improvements can roll out across the installed client base. ## New commercial modules Examples: - Hotels - Ground - Ticketing - Experiences - Advanced analytics - Loyalty - CRM automation - Team travel These can be activated for clients that want them. PIVOT can sell more value to organizations it already has. ## Custom client work If one organization asks for something unique that does not belong in the main platform, it can be scoped separately. --- # 14. The long-term product Do not think of T2C as only a flight booking product. Air is the first useful transaction. The platform can grow into: ## T2C Book - Flights - Hotels - Ground - Changes - Cancellations - One itinerary ## T2C Events - Events - Venues - Travel windows - Room blocks - Team travel - Participant travel ## T2C Partners - White-label organizations - Branding - Admin users - Commercial rules - Modules - Reporting ## T2C Money - Booking fees - Commissions - Rebates - Subscriptions - Partner economics - Reconciliation ## T2C Service - Traveler support - Booking changes - Disruption support - Alerts - Agent view ## T2C Intelligence - Travel behavior - Booking conversion - Event growth - Uncaptured travel - Revenue by client - Recommendations - Opportunity intelligence ## T2C Experiences - Tickets - Extended stays - Activities - Hospitality - Packages Do not build all of this now. Build the foundation so it can exist later. --- # 15. White-label strategy This should be a true white-label platform. Each PIVOT client can have: - Its own brand - Its own logo - Its own events - Its own support information - Its own fees - Its own modules - Its own reporting access - Its own traveler experience But the clients share the same underlying technology. Do not create a separate codebase for every organization. --- # 16. Subscription strategy PIVOT should be able to sell T2C as software. A client can pay PIVOT: - Setup fee - Monthly subscription - Additional module fees This is separate from travel transaction economics. This matters because PIVOT can make money even before considering commissions from flights or hotels. It also means PIVOT is selling a repeatable product, not only travel services. --- # 17. Pure Strategy should use a wholesale model Pure Strategy should set predictable technology pricing to PIVOT. PIVOT controls its retail pricing. Example structure: Pure Strategy charges PIVOT a fixed amount per active client environment. PIVOT can charge that client whatever makes sense commercially. PIVOT may: - Mark it up - Bundle it - Discount it - Include it inside another relationship Pure Strategy's economics should not change because PIVOT chose to discount a client. Avoid percentage-based software revenue share where possible. --- # 18. Usage should still be protected A tiny client and an enormous client should not necessarily have identical technology economics forever. The platform can eventually use fixed usage bands. For example: - Small program - Growing program - Large program - Enterprise portfolio This keeps pricing predictable without Pure Strategy taking a percentage of travel revenue. Exact thresholds are not yet decided. Do not invent them. --- # 19. Supplier and infrastructure costs Third-party costs should be transparent. Examples may include: - Air API/order fees - Hotel supplier fees - Payment processing - Email - SMS - Cloud infrastructure - Other third-party systems These should either be contracted directly by PIVOT or passed through clearly. Do not hide these inside Pure Strategy margins. --- # 20. Current systems and operating environment PIVOT already uses existing systems. Do not assume everything should be replaced. Known examples include: - Playbook 365 for some event/hotel programs - Direct hotel links in some cases - Concur for certain internal travel use cases - Nexion is specifically identified in the RFP - Salesforce and HubSpot are named CRM requirements The product should connect to useful systems rather than replace them simply because it can. One of the first implementation tasks is to map what happens after a booking: Traveler books → payment clears → booking/ticket is created → PIVOT sees it → support can service it → finance can reconcile it → relevant CRM/operations systems receive what they need Do not invent the final workflow until that mapping is complete. --- # 21. Important unresolved questions These are real questions. Do not hide them. We still need to confirm: - Which organization will be the first live pilot? - What air booking/ticketing infrastructure PIVOT already has access to - Whether PIVOT has an existing GDS, TMC, host agency, ARC/IATA or ticketing relationship - Who services flight changes and cancellations - Who is merchant of record - Where completed bookings should live - How Nexion fits into the transaction - How Concur should interact with T2C - Which CRM is the production source of truth - Exact client subscription economics - Exact domestic/international booking fee - Final supplier APIs - Native app timing Do not pretend these are already decided. --- # 22. AI philosophy The RFP asks for AI. Do not turn the product into an AI demo. Use intelligence where it removes work or improves a decision. Useful examples: - Recommend arrival dates based on the event - Recommend departure dates - Understand athlete vs. parent vs. coach - Recommend trip extensions - Surface preferred hotels - Identify booking patterns - Identify abandoned searches - Surface events with increasing travel demand - Help PIVOT understand what needs attention - Help travelers answer questions The traveler does not need to see the words "AI-powered" everywhere. The product should simply feel smarter. --- # 23. Mobile strategy Travelers will often use the product on their phones. The experience should be mobile-first. The architecture should be capable of supporting web, iOS and Android without creating three completely separate products. Do not make native app-store distribution a requirement for proving the first transaction unless PIVOT requires it. The first priority is usability. --- # 24. Product architecture principle Keep the product modular. The traveler-facing experience should not directly depend on one particular supplier. Conceptually, the platform should understand actions such as: - Search flights - Create booking - Retrieve booking - Cancel booking - Search hotel - Create hotel reservation - Take payment - Retrieve client - Update CRM Supplier-specific logic should sit underneath those actions. That gives PIVOT the ability to change suppliers later without rebuilding the whole customer experience. --- # 25. Product ownership principle PIVOT should own: - Its data - Its clients - Its branding - Its commercial settings - Its proprietary workflows - The custom work created specifically for PIVOT Pure Strategy should retain: - Reusable platform architecture - Generic software components - Generic modules - Reusable