Partner Brief — xtoura × Busflow
Purpose: One-page overview you scan before the meeting. Contains the key arguments, the key tactics, and the key boundaries. For full details, drill into the linked documents.
Situation Update (2026-05-14)
IMPORTANT
The partner is a potential strategic partner, not a cofounder. Their current focus is the xtoura PIM relaunch. They want a basic, improved version of the Kuschick booking form — which we will not provide. The meeting goal shifts: decline the freelance ask elegantly, gather intelligence, advance your own agenda, and preserve the relationship.
Adjusted Posture
- Say no without burning bridges. Frame the decline around focus and product fit, not rejection.
- Gather intel. Use the meeting to learn about relaunch timelines, operator pain points, and their booking flow requirements.
- Plant seeds. Mention Busflow's direction naturally, but do not hard-pitch. Let them connect the dots.
- Stay warm. This relationship has long-term value. Leave every door open.
The Six USPs — At a Glance
| # | Argument | One-Liner |
|---|---|---|
| 1 | Websites sell | Your websites generate bookings, not just traffic |
| 2 | Revenue sharing | You earn up to 80% of yearly operator revenue — for five years |
| 3 | Catalog converts | Your interactive catalog drives trackable, measurable bookings |
| 4 | Full-stack position | Together we offer a complete digital presence no single party can match |
| 5 | App improves | Busflow features surface inside xtoura-app with minimal effort on your side |
| 6 | No competition | Busflow does not build websites, catalogs, or PIMs — documented and codified |
→ Full arguments with scripts and evidence: USPs for Partner
Conversation Flow (Updated)
| Step | What to Do | Key Line |
|---|---|---|
| 1 | Listen first — let them talk about the relaunch and booking form needs | Ask: "Walk me through what you need — what does the ideal booking flow look like?" |
| 2 | Decline the freelance ask — respectful, focused on fit | "I can't take that on right now — my full capacity goes into Busflow. But I want to understand your needs so we can find a path that works." |
| 3 | Gather intel — relaunch timeline, operator pain, Kuschick gaps | Ask: "What is not working with the current Kuschick form? What do operators complain about?" |
| 4 | Plant the Busflow seed — mention direction, don't hard-pitch | "The booking engine I am building handles exactly that — but it is not ready for your timeline. When it ships, your operators are the first I would want to support." |
| 5 | Explore future alignment — website synergy, widget integration | "When Busflow's widget is ready, your websites and PIM would be the ideal distribution layer." |
| 6 | Close warm — leave every door open | "Let me know how the relaunch goes. When the time is right for the booking side, I would love to revisit this." |
→ Full scenario scripts and developer management: Deal Playbook
The Deal — Key Numbers
| Term | Detail |
|---|---|
| Commission | Up to 80% of yearly Busflow revenue per referred operator, for 5 years |
| Commission type | Relationship-level (not per-transaction) — partner earns regardless of booking channel |
| Pricing model | Commission on bookings; zero upfront cost for operators |
| Exclusivity | None contractual — frame as first-mover advantage ("You are our launch partner") |
| IP (xtoura-app) | We own it (§ 69b UrhG); transfer only as quid pro quo in a signed agreement |
→ Full founder decisions and concession ladder: Deal Playbook § Founder Decisions
Red Lines — What We Never Give
- ❌ Geographic or segment exclusivity
- ❌ Feature restrictions ("don't build a passenger portal")
- ❌ Dedicated xtoura PIM connector as contractual obligation
- ❌ Revenue share on Busflow's direct-sales operators
- ❌ App IP transfer without signed partnership agreement
Top 3 Objections to Expect
| Objection | Core Response |
|---|---|
| "Our developer can build this." | "A form, yes. But payment processing, Klarna, Apple Pay, digital tickets, refunds — that is a product, not a project. And it delays the PIM relaunch." |
| "The commission is too expensive." | "On a €1,200 trip, 4% is €48. If the widget generates one extra booking per month, it pays for itself." |
| "We don't want to depend on your system." | "You integrate with it, you don't depend on it. The widget is an embed — replace it anytime. No data lock-in, no contract lock-in." |
→ Full 13-row objection matrix: Deal Playbook § Objections
What We Want to Walk Away With
- [ ] Relaunch timeline — when does the new xtoura PIM go live?
- [ ] Kuschick pain points — what exactly is broken or missing in the current booking form?
- [ ] Operator names — which operators need booking capability most urgently?
- [ ] Technical requirements — what does their ideal booking flow look like?
- [ ] Relationship intact — partner feels heard, respected, and open to future collaboration
- [ ] Busflow seed planted — partner knows Busflow is building exactly this, just not on their timeline