Partner Pitch — Why Busflow Makes Your Business More Valuable
Audience: This document is the partner-facing argument. It describes Busflow's value for the partner's business model, not for operators directly. Every argument answers one question: "How does this make us money or make our clients happier?"
The Partner's Business Today
The partner operates four activities: physical catalog production (print + PDF), marketing websites for operators, the xtoura PIM, and the xtoura-app. They generate recurring revenue across these activities, but at small scale.
What Busflow Changes for the Partner
USP 1: Turn Websites from Brochures into Sales Machines
The partner's problem: They build beautiful operator websites, but those websites can't close a sale. A visitor reads about a trip, gets excited — and then has to call the office, send an email, or navigate to a clunky Kuschick booking page. Every friction point loses passengers.
What Busflow does: One script tag. The partner embeds Busflow's booking widget on every operator website they build. The website becomes a 24/7 automated salesperson — high-conversion checkout with Apple Pay, Klarna, SEPA, and guest checkout. No phone calls, no emails, no "please call back during business hours."
What the partner gains:
- Every website the partner builds becomes measurably more valuable to the operator — it doesn't just look good, it generates direct revenue
- Up to 80% commission on yearly Busflow revenue for operators the partner brings in, for five years. The partner earns when operators succeed — not per transaction, but as a share of yearly platform revenue.
- Competitive differentiation: The partner can offer operators a combined website + booking solution — the website drives discovery, Busflow closes the sale.
- Client retention: Operators who book through the partner's website are stickier — they depend on the partner for revenue, not just a pretty homepage.
The pitch line: "Right now, your websites are brochures. With Busflow, they become cash registers."
USP 2: The Partner Earns on Operator Success
The partner's problem: The partner earns recurring revenue, but has no direct stake in whether operators grow. Busflow changes that.
What Busflow does: The commission model (up to 80% of yearly Busflow revenue over 5 years) creates recurring income tied to operator success. The partner earns a share of the yearly revenue that each referred operator generates on Busflow. This is not a per-transaction cut — it is a relationship-level commission that compounds as the operator base grows.
What the partner gains:
- Recurring revenue tied to operator growth. Every new operator the partner refers creates a new revenue stream lasting five years.
- No inventory risk. The partner does not need to build, host, or support Busflow. They refer operators. We handle the rest.
- Alignment of incentives. The partner earns more when operators succeed — this makes the partner a growth ally, not just a service provider.
The pitch line: "You earn a share of every operator's success — for five years."
USP 3: The Partner's Catalog Goes Digital — For Real This Time
The partner's problem: Physical catalogs are expensive, seasonal, and static. Once printed, a price change or sold-out trip means the catalog is wrong. The xtoura-app's interactive catalog with hotspots partially solves this by digitizing pages, but the hotspots still redirect to external booking pages or internal trip-detail views that can't convert.
What Busflow does: The partner's interactive catalog hotspots can point directly to Busflow booking widget URLs. A passenger taps a hotspot on a catalog page → lands in Busflow's checkout → books and pays in 60 seconds. The catalog becomes an acquisition funnel, not a reference document.
What the partner gains:
- The catalog generates trackable bookings. For the first time, the partner can tell an operator exactly how many bookings the catalog drove. That is a conversation-changing data point.
- Zero development effort. The xtoura-app's interactive catalog already supports an
externalURL field on hotspots. Pointing it to a Busflow widget URL requires a configuration change, not a code change. - The print catalog stays relevant. QR codes on printed catalog pages can link to Busflow booking URLs. Physical → digital → transaction in one scan. The partner's print business gains a measurable ROI story.
The pitch line: "Your catalog goes from 'nice to browse' to 'tap, book, paid.' And you earn a commission on every operator you bring."
USP 4: The Partner Becomes the Full-Service Digital Partner
The partner's problem: Each of the partner's four activities is valuable on its own, but none of them can close a booking. Busflow fills that gap.
What Busflow does: Busflow completes the partner's offering with capabilities they cannot build alone:
| Capability | Who Provides It |
|---|---|
| Website design & SEO | Partner |
| Product data management | Partner (xtoura PIM) |
| Online booking & payments | Busflow |
| Digital tickets & wallet passes | Busflow |
| Post-booking passenger experience | Busflow |
| Catalog (print + interactive digital) | Partner |
What the partner gains:
- A complete offering. The partner can pitch operators a full digital presence: website + PIM + booking engine + digital ticketing. The partner handles the front-of-house; Busflow handles the back-of-house.
- The partner stops being a vendor and becomes a strategic partner. Operators depend on the partner for revenue generation, not just aesthetics. This changes the power dynamic entirely.
The pitch line: "You bring the brand, the website, the catalog. We bring the booking engine, the tickets, the payments. Together, you offer operators something nobody else can."
USP 5: The xtoura-app Gets Better Without the Partner Investing
The partner's problem: The xtoura-app works, but it's limited. Bookings redirect to external pages. Tickets are PDF downloads. There's no live tracking, no wallet passes, no self-service. Building these features requires significant engineering investment that the partner cannot afford.
What Busflow does: For operators running on Busflow, the xtoura-app can surface enhanced features by consuming Busflow's APIs. The integration path (see Integration Strategy):
| Current xtoura-app State | With Busflow Integration (planned) |
|---|---|
| "Zur Buchung" → opens external booking page | "Zur Buchung" → opens Busflow checkout widget |
| PDF download (Vorgangsdruck) | PDF from Busflow + Wallet Pass deep-link |
| Static trip dates and prices | Real-time availability and pricing from Busflow API |
NOTE
Phase 1 (booking URL swap, catalog hotspot URLs) requires configuration changes only. Phase 2 (API data integration) requires xtoura-side development effort. See the Integration Strategy for effort estimates and dependencies.
What the partner gains:
- The app improves with minimal effort. Busflow builds the features; the xtoura-app surfaces them. Phase 1 requires zero code changes on the xtoura side.
- Proof of platform value. Every Busflow-enhanced feature inside the xtoura-app demonstrates what the operator gains with Busflow. The app becomes a sales tool, not a cost center.
- No cannibalization. The xtoura-app keeps its unique features (interactive catalog, surveys, office finder, checklist). Busflow adds capabilities the app never had.
The pitch line: "Your app gets a modern checkout and real-time data — with minimal development effort on your side."
USP 6: Busflow Explicitly Does Not Compete with the Partner's Core Business
This is the trust argument. The partner needs to believe that Busflow will not absorb their business over time. The architectural evidence is strong:
| Partner Activity | Busflow Non-Goal | Evidence |
|---|---|---|
| Website design & hosting | ❌ Non-goal #5: "Busflow provides an embeddable booking engine, not a website builder, CMS, or design agency." | Codified in STRATEGY_platform-vision.md |
| Physical catalog production | Not in any roadmap. Zero product overlap. | No catalog-related entities in the domain model |
| PIM (xtoura) | Busflow manages operational data, not marketing content. Different scope by design. | "Marketing truth" vs. "operational truth" boundary in the analysis |
| xtoura-app (consumer browsing) | ❌ Non-goal #1: "Consumer travel planning app — Lambus territory." | Codified in STRATEGY_platform-vision.md |
What the partner gains:
- Documented non-compete. These are not verbal promises — they are architectural decisions baked into the product strategy. Busflow's domain model has no entities for website content, catalog layout, or consumer trip planning. Building these features would require violating our own documented strategy.
- The partner's value grows, not shrinks. As Busflow handles booking and operations, the partner's website, catalog, and app become more important — they are the discovery and engagement layer that feeds Busflow's conversion engine. More Busflow transactions → more value from the partner's digital surfaces → more commission revenue.
The pitch line: "We don't build websites. We don't make catalogs. We don't manage your PIM. We make all of those things sell."
What Busflow Needs from the Partner
A real partnership requires reciprocity. These are the concrete asks:
| Ask | Why |
|---|---|
| Introductions to operators | The partner has existing relationships with bus tourism operators. Each introduction is a potential Busflow customer. |
| Booking widget integration on partner-built websites | The partner embeds Busflow's widget on the operator websites they build and maintain. This is the primary conversion channel. |
| Cooperative framing | The partner positions Busflow as part of their offering to operators, not as a competitor to their app. |
| Reasonable timeline for app integration | The partner (or their developer) cooperates on Phase 1 configuration changes and Phase 2 API integration when Busflow's APIs are ready. |
What Busflow does not need:
- Exclusivity or contractual lock-in
- Access to the partner's PIM data (nice-to-have, not required)
- The partner to stop developing their own products
Summary — The Six Arguments
| # | Argument | One-Liner |
|---|---|---|
| 1 | Websites sell | Your websites generate bookings, not just traffic |
| 2 | Revenue sharing | You earn a share 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's features surface inside xtoura-app with minimal development effort |
| 6 | No competition | Busflow's non-goals are documented — we don't build websites, catalogs, or PIMs |
The closing line: "You already own the relationship with operators. You own the websites, the catalogs, the PIM, the app. Busflow adds the booking engine, the payments, and the passenger experience — and pays you a commission for every operator you bring."