Busflow Docs

Internal documentation portal

Skip to content

Partner Alignment β€” xtoura ​

Status: Active Goal: Define how Busflow's product vision synergizes with the xtoura partner's four product surfaces β€” short-term and long-term β€” to maximize mutual value without compromising Busflow's architecture or roadmap.

Context ​

A key partner operates four product surfaces with varying degrees of synergy and conflict with Busflow:

#SurfaceGoal ConflictSynergy
1Physical Travel Catalog (Print + PDF)NoneLow
2Marketing WebsiteNoneHigh
3PIM (xtoura)Small–MediumMedium
4App (xtoura-app)HighLow

Constraints ​

  • Non-negotiable: Busflow's vision and architecture must not be compromised for partner compatibility.
  • Preferred outcome: Partner becomes an active sales channel for Busflow while retaining their existing revenue streams.
  • Fallback: Walking away from the partnership is acceptable if alignment proves impossible.

Documents ​

DocumentPurpose
Partner Alignment AnalysisFull synergy/conflict analysis, narrative framework, risk matrix, and open questions
xtoura App Feature AuditCodebase-level analysis of what xtoura-app does, its architecture, and feature overlap with Busflow
Integration StrategyHybrid coexistence model β€” how xtoura-app and Busflow can coexist through a three-tier integration
Partner PitchThe six strongest arguments for why Busflow creates value for the partner's business model
Meeting PlaybookScenario scripts, objection handling, money conversation framework, and exit checklist for the booking widget meeting

Founder Decisions (Resolved) ​

All five strategic decisions are documented in the Partner Alignment Analysis:

  1. βœ… Revenue share β€” Up to 80% of yearly revenue over 5 years as commission (relationship-level, not per-transaction)
  2. βœ… App timeline β€” Coexist until direct competition; no rush to sunset
  3. βœ… App ownership β€” Β§ 69b UrhG gives us IP ownership; transfer only as quid pro quo
  4. βœ… Exclusivity β€” Frame as exclusivity without contractual lock-in; time-limited first-mover clause if pressed
  5. βœ… PIM integration β€” Platform neutrality; generic API only, no dedicated connector

A full Negotiation Playbook with leverage points, concession ladder, and conversation sequencing is included.

Success Criteria ​

  • [x] All five open questions resolved
  • [ ] Revenue share model defined (commission gradient over 5 years)
  • [ ] App handoff terms structured with ex-employee
  • [ ] Partner conversation held β€” outcome documented
  • [ ] Integration boundary (API-only, no UI coupling) agreed upon

Internal documentation β€” Busflow