Synergy Map — xtoura × Busflow
Cross-surface narrative and synergy overview. For per-surface analysis, see the individual surface files. For negotiation tactics, see the Deal Playbook.
The Narrative Framework
The partner's fear is: "Busflow competes with my investments and eventually I lose control."
The counter-narrative must reframe the relationship from competition to platform leverage:
The Pitch
See USPs for Partner for the full set of six USPs and pitch lines for the partner conversation.
Short-Term Synergy Map (0–12 months)
| Partner Surface | Busflow Role | Partner Benefit |
|---|---|---|
| Marketing Website | Embed booking widget | Website clients become booking clients → recurring revenue share |
| Physical Catalog | None (future: API data source) | No change to existing business |
| PIM (xtoura) | Accept data via API/Email-as-API | Partner's PIM feeds Busflow without partner rebuilding anything |
| App (xtoura-app) | Coexist during transition period | Partner keeps app revenue; Busflow's passenger features roll out gradually |
| Booking Form (Satzart) | Coexist via API | Partner keeps existing booking mask; Busflow provides the backend |
Long-Term Synergy Map (12–36 months)
| Partner Surface | Busflow Role | Partner Benefit |
|---|---|---|
| Marketing Website | Widget + Conversion Analytics + GEO | Partner offers data-driven marketing services on top of Busflow's analytics |
| Physical Catalog | API-sourced tour data | Catalog production pulls live data from Busflow — no manual re-keying |
| PIM (xtoura) | Headless CMS → Busflow pipeline | xtoura becomes the content layer; Busflow becomes the transaction layer |
| App (xtoura-app) | Sunset → Busflow Passenger Portal | Partner's operators get a superior passenger experience at no extra cost |
| Booking Form (Satzart) | Busflow widget replaces custom form | Partner reduces maintenance; Busflow provides the standard checkout |