Busflow Docs

Internal documentation portal

Skip to content

Project Scope: busflow

Vision

A verticalized AI-SaaS replacing the outdated IT landscape of SMB bus tour operators (DACH region). Targets two segments: companies using no software ("Patchwork Operators") and those trapped in legacy systems like Kuschick/Turista ("Legacy Operators").

Three Pillars

  1. AI-Driven Backoffice: "Magic Upload" converts PDF itineraries to structured data in seconds. Copilot handles compliance (driving hours) and automated communication.
  2. Conversion-Optimized Sales: Modern B2C booking widget with visual seat maps, Apple Pay/Klarna, digital tickets (Apple/Google Wallet).
  3. Seamless Operations: Mobile-first driver app with live passenger lists, QR check-ins, automated WhatsApp updates.

Value Pillars

  • Do More With Less: AI halves operational overhead — scale volume without scaling headcount.
  • Revenue Engine: Consumer-grade checkout turns the website into a 24/7 sales channel.
  • Premium Passenger Journey: Digital wallet passes, proactive WhatsApp updates, enterprise-level experience.
  • Modern Employee Experience: Intuitive mobile-first tools that attract digitally native talent.
  • Zero-Downtime Migration: Concierge onboarding handles data migration — value on day one.

Design Principles

North Star: 5 Minutes to Value. A new operator must experience tangible product value within five minutes of first interaction. No empty states, no configuration wizards, no training manuals. The system works out of the box.

Five mechanisms enforce this:

  • Smart Defaults: Every setting ships with a sensible default so operators never face blank forms. Override when needed — never configure from scratch. Decision test: "Can the operator skip this step entirely and still get a working result?" If not, the default is missing.
  • Convention over Configuration: The system makes opinionated choices so operators only configure the exceptions. Standard patterns (base demographics, payment terms, notification triggers) reduce cognitive load and eliminate decision fatigue. Decision test: "Are we asking the operator to decide something that 90% of operators would answer the same way?" If yes, make it a convention.
  • Progressive Disclosure: Show the minimum required to act. Reveal advanced options only when the operator asks for them. Complexity exists in the system — it never exists on the first screen.
  • Offline-First: The system never fails the user because of their network. Driver boarding, cash sales, and manifests work without connectivity. Data syncs when the connection returns.
  • Do It For Them First: Before asking operators to learn the system, do the work for them. Concierge Onboarding configures the first tours using the operator's real data. Self-serve follows after trust is earned.

Brand Identity

  • Archetyp: Der „Co-Pilot" (Mischung aus Der Weise und Der Helfer). busflow ist Enabler im Hintergrund — mächtiges, aber unsichtbares Werkzeug.
  • Markenwerte: Pragmatisch (KI = Zeitsparer), Souverän (Enterprise-Stabilität), Reibungslos (alles fließt).
  • Claim: Das KI-Betriebssystem für den Bus-Tourismus. / Mehr Busse auf der Straße. Weniger Zettel auf dem Schreibtisch.
  • Mission: Mittelständische Busreiseveranstalter von veralteter IT und manuellem Chaos befreien.
  • Vision: Die globale Infrastruktur, die jede Busreise von Buchung bis Ausstieg nahtlos, digital und intelligent macht.

Tone of Voice

  • Klartext statt Tech-Blabla: „Reisepläne als PDF rein, fertige Tour raus – in 3 Sekunden."
  • Respektvoll & auf Augenhöhe: Tradition wertschätzen, Management modernisieren.
  • Dynamisch & Lösungsorientiert: Aktive Verben, kurze Sätze, Fokus auf Zeitersparnis.

Zielgruppen-Messaging

ZielgruppePain PointBotschaft
GF / InhaberPersonalkosten, Margendruck, Angst vor Systemwechsel„Wachstum ohne Overhead."
DisponentExcel-Hölle, WhatsApp-Chaos, PDF-Abtippen„Dein KI-Copilot übernimmt."
BusfahrerZettelwirtschaft, unklare Passagierlisten„Die Tour in deiner Tasche."
FahrgastKomplizierte Buchung, keine digitalen Tickets„Buchen wie bei Netflix."

Target Segments

Patchwork OperatorLegacy Operator
Current ToolsExcel, Email, WhatsAppKuschick, Turista
Core PainLost revenue (no booking engine), drowning in manual workBad UX, closed ecosystems, employee turnover
MotivationSave time, look professionalBetter UX, modern integrations
Key Objection"We can do this for free""Migration is too risky"
Hook"Stop typing out passenger lists""Give your team tools they actually like"
Anti-ICPTech-averse owners, non-bus-tourism, unwilling to invest in software

Core User Journeys

→ See user-journeys.md

Domain Model

→ See domain-model.md


Target Version 0.1 Scope

Definition: The absolute minimum feature set required for a "Patchwork Operator" to migrate off Excel/WhatsApp and begin paying for the platform.

To aggressively mitigate build risk and focus engineering effort, our initial release (V0.1) explicitly strips away the grander visions to focus on core viable utility:

  • Core Entity Management (CRUD): Tours.
  • Commerce / B2C Booking: Live booking-widget with Mollie checkout and automated fulfillment via Wallet passes.
  • Deferred to V0.2+: Resources (Vehicles, Crew), Dispatch (manual assignment and AI Agents), PWA Driver App, complex financial integrations (DATEV exports), and Cross-operator marketplaces.

Internal documentation — Busflow