Demo Video Flows

This page lists recording-ready demo flows built on the demo seed data. It is for anyone preparing a Clapilot demo video or live walkthrough: each flow tells one coherent client story instead of touring modules. UI labels, seed names, and chat prompts are kept in German because that is what appears on screen in the demo instance.

All flows assume a full reset was run under Admin -> Demo Daten. The reset rebuilds appointments, deadlines, tasks, and mail data relative to the current month.

Storytelling principle

The demo videos are not module tours. A good flow always shows work being taken off someone's plate:

1. A real inbound item arrives: mail, document, deadline, or new activity.
2. Clapilot understands the professional substance and names the critical points.
3. Clapilot links the right artifacts: Mandant, document, task, appointment, reply draft, chat context.
4. The user reviews a prepared decision instead of assembling context by hand.

Before rendering a video, the storyline must work as one connected case. Screenshots of E-Mails, Dokumente, Aufgaben, or Kalender are only evidence inside that case story.

Recommended flagship flows

Flow 1: Law firm - from email to real due diligence

Seed reference: scenario rechtsanwaltskanzlei, mail-3, document-3, task-3, event-3.

1. Under Admin -> Demo Daten, select the Rechtsanwaltskanzlei scenario and run Demo-Daten neu aufbauen.
2. In E-Mails, open the message MediCo Labs: IP-Abtretung und Change-of-Control-Risiko from Sophie Krueger.
3. Briefly show the real case: founder IP transfer and the change-of-control clause in the clinic framework agreement.
4. In the workflow area, show that Clapilot linked Mandant, document, task, and appointment.
5. Click Dokument oeffnen and show Red-Flag-Checkliste MediCo Labs Beteiligung - Sophie Krueger.
6. Switch back to the mail and show the reply suggestion: concrete recommendations on the IP chain, consent concept, closing condition, and purchase-price reservation.
7. Show Aufgabe oeffnen: Red-Flag-Vermerk zu IP- und Change-of-Control-Klauseln erstellen.
8. Show the calendar entry Beteiligung MediCo Labs - Red-Flag-Call.
9. Optionally ask in chat: Fasse mir den Fall Sophie Krueger zusammen und nenne die naechsten drei Schritte.

Flow 2: Tax firm - contract and tax review

Seed reference: scenario steuerberaterkanzlei, mail-1, document-1, task-1, event-1.

1. Under Admin -> Demo Daten, select the Steuerberaterkanzlei scenario and run Demo-Daten neu aufbauen.
2. In E-Mails, open the message Series-A Due Diligence: SPA, VSOP und USt-Risiko from Nora Feldmann.
3. Show the three concrete points: IP chain, convertible loans in the cap table, VAT correction 2025.
4. Show the prepared reply draft: Clapilot asks for the cap table, confirms the review, and names the red-flag memo.
5. Show Dokument oeffnen: Series-A Vertragsentwurf mit Red-Flag-Vermerk - TechVentures GmbH.
6. Show Aufgabe oeffnen: Red-Flag-Vermerk zur Series-A-Beteiligung erstellen.
7. Show the appointment Due Diligence Call - TechVentures GmbH.
8. Optionally ask in chat: Erstelle aus dem TechVentures-Kontext einen kurzen Red-Flag-Vermerk als Dokumententwurf.

Flow 3: Automation on new email

Seed reference: existing seed automations from email_thread_automations, visible in the workflow area of the mail detail view.

1. Run a full reset under Admin -> Demo Daten.
2. In E-Mails, open a mail with a workflow area, for example mail-3 in the law-firm scenario.
3. Show the status line Antwortvorschlag im Workflow.
4. In the context area, show the linked chips: email, task, document, to-do, question.
5. In Geplante Aufgaben, create a new automation for Neue E-Mail.
6. Use the prompt: Wenn eine Mandantenmail eine Frist oder einen konkreten Dokumentenbezug enthaelt, analysiere den Fall, erstelle eine Aufgabe, bereite eine Antwort vor und poste eine kurze Zusammenfassung in den Hauptchat.
7. Select Hauptchat as the result target and save.
8. Go back to Admin -> Demo Daten and run Fake Activity erzeugen.
9. In E-Mails, open the new follow-up question and show that Clapilot generates follow-up context from it.

Flow 4: Specialized agents and automations

Seed reference: specialized agent @steuer-manager, when the Steuer-Manager module is installed.

1. In Spezial-Agenten, open the Steuer-Manager Assistent and show its tightly scoped tools.
2. Create a new automation in Geplante Aufgaben.
3. Choose the trigger Zeitplan or Neues Dokument.
4. Select the Steuer-Manager Assistent as the agent.
5. Use the prompt: Pruefe neue Belege fuer den ausgewaehlten Mandanten, importiere relevante Dokumente in den Steuer-Manager, markiere unklare Belege als needs_review und poste eine knappe Finanzuebersicht mit legal_notice.
6. Save and run manually, or import a matching document.
7. In the main chat, show that the specialized agent appears as its own background run.
8. Show the final specialist output and explain that the automation runs with the restricted Steuer-Manager context, not with the general agent.

Flow 5: Agent creates a document from seed context

Seed reference: rechtsanwaltskanzlei with mail-3 and document-3, or steuerberaterkanzlei with mail-1 and document-1.

1. Open the case in the mail detail view.
2. Open the floating chat or /chat.
3. Prompt for the legal demo: Erstelle auf Basis der Sophie-Krueger-Mail und der Red-Flag-Checkliste einen kurzen Red-Flag-Vermerk als Dokumententwurf. Struktur: Sachverhalt, rechtliche Einordnung, Risiken, Empfehlung, naechste Schritte.
4. Prompt for the tax demo: Erstelle aus dem TechVentures-Fall einen Red-Flag-Vermerk fuer SPA, VSOP und Umsatzsteuer. Fuege eine Mandantenmail als Antwortentwurf an.
5. Save the generated content to the Word Editor or Dokumente.
6. Open the new document in Dokumente and show the preview.
7. In Aufgaben, show a follow-up task with a deadline in the current month, or have the agent create one.