In most small and mid-sized businesses, onboarding is a manual patchwork: sales hands off a new customer, but the checklist gets built ad hoc, tasks land in the project tool with delay, and by the third customer of the week the welcome email noticeably loses its personal touch. This workflow addresses exactly that bottleneck.
\nAs soon as a deal in the CRM moves to customer status, the workflow pulls the relevant customer data (name, industry, product, company size, contact person), has an industry and product specific onboarding checklist generated from it, creates the individual tasks in the project management tool, and in parallel prepares a personal welcome email as a draft. It concludes with a notification to the responsible customer success manager containing all the links, so that person only needs to review and approve the results.
\nA human stays in the loop at two points: approving the tasks on the board, and sending the email, which is deliberately saved as a draft rather than sent automatically. This keeps the tone under control while removing the manual grind.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: onboarding-strecke.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Trigger: new customer in the CRM", "beschreibung": "A deal in the CRM moves to customer status and triggers the process.", "rolle": "mensch" }, { "nr": 2, "titel": "Retrieve customer data", "beschreibung": "Name, industry, product, company size and contact person are pulled from the CRM, along with the responsible customer success manager.", "rolle": "automatisch" }, { "nr": 3, "titel": "Create the onboarding checklist", "beschreibung": "A language model generates five to eight industry and product specific tasks, including a time estimate.", "rolle": "automatisch" }, { "nr": 4, "titel": "Create tasks", "beschreibung": "The checklist is created as individual tasks on the onboarding board and assigned to the responsible customer success manager.", "rolle": "automatisch" }, { "nr": 5, "titel": "Draft the welcome email", "beschreibung": "A language model writes a personal welcome email introducing the customer success manager, outlining the next steps along the checklist, and proposing times for the kickoff call.", "rolle": "automatisch" }, { "nr": 6, "titel": "Notify the CSM", "beschreibung": "The responsible customer success manager receives a message in the team chat with the customer data, a link to the tasks, and the email draft for review.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Consistent process", "text": "Every new customer goes through the same complete onboarding process, regardless of who is handling the request." }, { "titel": "Quick start", "text": "The checklist, tasks and email draft are ready as soon as the deal in the CRM moves to customer status." }, { "titel": "Clean handoff", "text": "The responsible customer success manager receives customer data, a task link and the email draft bundled in a single message." }, { "titel": "Personalization that scales", "text": "The checklist and email are tailored to industry, product and company size, even as customer volume grows." } ], "voraussetzungen": [ { "label": "CRM system", "text": "HubSpot, Salesforce or a comparable system provides the customer data and the trigger.", "icon": "contacts" }, { "label": "PM tool", "text": "Asana, Trello or Monday for the onboarding tasks.", "icon": "checklist" }, { "label": "Email tool", "text": "Gmail, Outlook or a comparable tool for the welcome email.", "icon": "mail" }, { "label": "LLM access and team chat", "text": "Access to OpenAI, Claude or Gemini, plus a team chat tool such as Slack or Teams for notifying the customer success manager.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test customer", "text": "Create a demo contact with complete data and set the status to customer.", "icon": "person_add" }, { "label": "Checklist and tasks", "text": "Check whether five to eight industry specific tasks are created and assigned to the responsible customer success manager.", "icon": "task_alt" }, { "label": "Welcome email", "text": "Check whether the email is personalized, the data is correct, the kickoff slots fit, and the draft is ready for the customer success manager.", "icon": "outgoing_mail" }, { "label": "Edge cases", "text": "Test requests without an industry specified, solo businesses versus enterprise customers, other languages, and multiple contact persons.", "icon": "rule" } ], "goLive": [ { "label": "Approve", "text": "Activate the workflow only once the checklist, tasks and email are reliably correct.", "icon": "check_circle" }, { "label": "Segment start", "text": "Begin with a single customer segment and add further segments step by step.", "icon": "tune" }, { "label": "Draft mode", "text": "Let the first run save the email as a draft only, so the customer success manager can adjust the tone.", "icon": "drafts" }, { "label": "Expand", "text": "Add a calendar invite, follow-ups and a notification for especially important customers later on.", "icon": "rocket_launch" } ], "haeufigeFehler": [ { "label": "CRM trigger does not fire", "text": "Check the webhook and the customer status value.", "icon": "sensors_off" }, { "label": "Tasks land in the wrong project", "text": "Check the target board and permissions.", "icon": "move_to_inbox" }, { "label": "Email with empty fields", "text": "Fill in the required fields in the CRM before the customer is created.", "icon": "edit_note" }, { "label": "Checklist too generic", "text": "Enrich the prompt with industry specific examples.", "icon": "auto_awesome" } ] }, "arbeitsprompts": [ { "titel": "Onboarding Checklist", "beschreibung": "Creates an industry and product specific checklist with five to eight tasks and a time estimate from the customer data.", "prompt": "You are an experienced customer success manager. Create a personalized onboarding checklist for the following new customer:\n\nCustomer data:\n- Name: [CUSTOMER_NAME]\n- Company: [COMPANY_NAME]\n- Industry: [INDUSTRY]\n- Product/service: [PRODUCT]\n- Company size: [NUMBER_OF_EMPLOYEES]\n- Contact person: [CONTACT_NAME] ([CONTACT_ROLE])\n\nYour task:\nCreate an onboarding checklist with 5 to 8 concrete tasks tailored to the industry and the product. In doing so, take into account:\n- industry specific best practices\n- product specific setup steps\n- company size (smaller companies need simpler processes)\n\nFormat:\nOutput the checklist as a numbered list. Each task should be concrete, actionable, and include an estimated time.\n\nExample format:\n1. [Task name]: [Short description] (Duration: [time estimate])\n\n[ADDITIONAL_REQUIREMENTS]" }, { "titel": "Welcome Email", "beschreibung": "Writes a personal welcome email with proposed times for the kickoff call, based on the onboarding checklist.", "prompt": "You are the customer success manager [CSM_NAME] from [COMPANY_NAME]. Write a warm, professional welcome email to a new customer.\n\nCustomer data:\n- Contact person: [CONTACT_NAME]\n- Company: [CUSTOMER_COMPANY]\n- Product/service: [PRODUCT]\n\nOnboarding checklist:\n[ONBOARDING_CHECKLIST]\n\nEmail structure:\n1. Personal greeting and welcome\n2. Brief introduction as the responsible customer success manager\n3. Overview of the next steps, referring to the onboarding checklist\n4. Invitation to a kickoff call, with two to three proposed time slots: [TIME_SLOTS]\n5. Contact information and availability\n6. Motivating close\n\nTone: [TONE] (for example professional-friendly, casual-modern, formal)\n\nImportant:\n- Keep the email to a maximum of 250 words.\n- Use a clear structure with paragraphs.\n- Include a clear call to action for the kickoff call.\n- Sign off with: [CSM_NAME], [CSM_POSITION], [CONTACT_DETAILS]" } ], "prompt": "GOAL\nBuild a workflow that, for new customers in the CRM, automatically generates a tailored onboarding checklist, creates the corresponding tasks in the PM tool, prepares a personalized welcome email as a draft, and notifies the responsible customer success manager with all the links.\n\nAdapt the structure to the concepts of your automation tool (for example nodes, steps, zaps or agent actions). While doing so, preserve the trigger logic, the sequence and the data flow.\n\nTRIGGER\nType: CRM trigger (HubSpot, Salesforce or comparable). Fires when a deal or contact receives customer status.\n\nSTEPS\n1. Retrieve customer data: pull customer name, company, industry, purchased product, company size, contact person (name and role) and the responsible customer success manager from the CRM.\n2. AI step: onboarding checklist. Use exactly the Onboarding Checklist working prompt (see the Working Prompts section). Output: a numbered list with five to eight tasks, including a time estimate.\n3. Create tasks: create one entry per task on the onboarding board and assign it to the responsible customer success manager.\n4. AI step: welcome email. Use exactly the Welcome Email working prompt (see the Working Prompts section), with the checklist from step 2 as input. Save the output as an email draft, no automatic sending.\n5. Output: notify the responsible customer success manager in the team chat, with the customer data, a link to the tasks and a note about the email draft.\n\nPROMPTS\nTake over both working prompts from the section of the same name unchanged. Pay particular attention to the double meaning of [COMPANY_NAME]: in the Onboarding Checklist working prompt it refers to the customer's company, in the Welcome Email working prompt it refers to your own company. Map both separately.\n\nDATA FLOW\nTrigger to step 1: CRM record of the new customer.\nStep 1 to step 2: customer name, customer company, industry, product, company size, contact name, contact role.\nStep 1 to step 4: contact name, customer company, product.\nStep 2 to step 4: onboarding checklist.\n\nERROR HANDLING\nCRM trigger does not fire: check the webhook and the customer status value.\nRequired fields missing, for example industry or contact person: stop the run and notify the customer success manager with a note, instead of sending the email with empty fields.\nTasks land in the wrong project: check the target board and permissions.\nChecklist too generic: extend the prompt with industry specific examples (placeholder [ADDITIONAL_REQUIREMENTS]).\nMultiple contact persons present: use the primary contact from the CRM.\n\nPLACEHOLDER CONVENTION\nAll customer data as well as [ONBOARDING_CHECKLIST] are mapped dynamically from the CRM or from step 2, as described in the data flow. Not dynamic, to be set manually before activation: [CSM_NAME], [CSM_POSITION], [CONTACT_DETAILS], your own [COMPANY_NAME] in the Welcome Email working prompt, [TONE], [ADDITIONAL_REQUIREMENTS], and [TIME_SLOTS] (ideally dynamic from the customer success manager's calendar, otherwise manual). The square brackets in the example format of the Onboarding Checklist working prompt are formatting instructions to the language model and remain unchanged. List all placeholders that require manual configuration separately at the end.\n\nSELF CHECK BEFORE COMPLETION\nCheck, before you report the workflow as finished:\n1. Are all steps connected correctly, and is the welcome email saved exclusively as a draft?\n2. Are both working prompts inserted in full and unchanged, and is the double meaning of [COMPANY_NAME] resolved correctly?\n3. Are the tasks assigned to the right customer success manager, and does the notification contain all the links?\n4. Are all points listed that require manual configuration: CRM webhook, onboarding board, CSM details, tone, the source of the time slots, and LLM access?", "einrichtung": { "intro": "Two routes lead to the same result. Pick the one that fits your setup.", "varianten": [ { "variante": "Builder-Prompt", "einleitung": "Suitable when you want to build the workflow in your own automation tool.", "schritte": [ "Open your workflow tool, for example n8n, Make, Zapier or Langdock.", "Create a new workflow and give it a name.", "Choose the AI-assisted build option if your tool offers one.", "Paste the builder prompt from above in full.", "Check the result against the step sequence in this document, then add your access credentials and channels." ] }, { "variante": "JSON-Import", "einleitung": "Suitable when you want to take the workflow over unchanged.", "schritte": [ "Download the JSON file from the JSON export section.", "Open the workflow area of your tool and create a new workflow.", "Give it a name and confirm.", "Open the menu on the workflow name and choose to import a JSON file.", "Upload the file, then add your own access credentials.", "Run a test before you activate the workflow." ] } ] }, "exportMeta": { "datei": "w12_onboarding-strecke__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Onboarding-Strecke", "beschreibung": "Erstellt bei jedem neuen Kunden im CRM automatisch eine passgenaue Onboarding-Checkliste, legt die zugehörigen Tasks im PM-Tool an, bereitet eine persönliche Welcome-Mail vor und benachrichtigt den zuständigen Customer Success Manager mit allen Links.", "trigger": { "typ": "Formular (Referenz-Build), produktiv empfohlen: CRM-Status-Trigger oder Webhook", "bedingung": "Der Knoten newCustomer startet den Ablauf in der Referenz über den Absende-Link eines Formulars, das an das Vertriebsteam geht. Für den produktiven Einsatz wird empfohlen, das Formular durch einen CRM-Trigger zu ersetzen, der beim Statuswechsel eines Deals oder Kontakts auf Kunde feuert, etwa bei HubSpot oder Salesforce, oder bei anderen CRM-Systemen durch einen Webhook, der bei neuen Kunden einen POST-Request sendet." }, "schritte": [ { "nr": 1, "titel": "Trigger: neuer Kunde im CRM", "rolle": "mensch", "aktion": "In der Referenz-Implementierung startet der Formular-Knoten newCustomer den Ablauf, dessen Link an das Vertriebsteam geht. Für den Produktivbetrieb wird empfohlen, das Formular durch einen echten CRM-Trigger zu ersetzen, der beim Statuswechsel eines Deals auf Kunde feuert, oder bei anderen CRM-Systemen durch einen Webhook.", "prompt_ref": null, "eingang": [], "ausgang": [ "Formular- beziehungsweise CRM-Datensatz des neuen Kunden (newCustomer.output)" ] }, { "nr": 2, "titel": "Kundendaten abrufen", "rolle": "automatisch", "aktion": "Hierfür gibt es in der Referenz keinen eigenen Knoten: Name, Branche, Produkt, Unternehmensgröße und Ansprechpartner liegen bereits als Felder im Trigger-Datensatz vor, konkret nachweisbar sind newCustomer.output.email (Kunden-E-Mail) und newCustomer.output.csm_email (E-Mail des zuständigen Customer Success Managers).", "prompt_ref": null, "eingang": [ "Formular- beziehungsweise CRM-Datensatz des neuen Kunden" ], "ausgang": [ "Kundendaten, unter anderem newCustomer.output.email, newCustomer.output.csm_email, Name, Unternehmen, Branche, Produkt, Unternehmensgröße, Ansprechpartner" ] }, { "nr": 3, "titel": "Onboarding-Checkliste erstellen", "rolle": "automatisch", "aktion": "Der KI-Knoten onboardingChecklist erzeugt mit dem Arbeitsprompt Onboarding-Checkliste eine strukturierte Ausgabe mit den Pflichtfeldern tasks (Array der Onboarding-Tasks), summary (Zusammenfassung der Onboarding-Strategie) und success (Boolean). Die Fehlerstrategie dieses Knotens ist Stop.", "prompt_ref": "arbeitsprompt-1", "eingang": [ "Kundendaten" ], "ausgang": [ "onboardingChecklist.output.structured.tasks", "onboardingChecklist.output.structured.summary", "onboardingChecklist.output.structured.success" ] }, { "nr": 4, "titel": "Tasks anlegen", "rolle": "automatisch", "aktion": "Eine Schleife (taskLoop) läuft über das Array onboardingChecklist.output.structured.tasks, das aktuelle Element steht je Durchlauf unter taskLoop.output.item zur Verfügung. Für jedes Element legt der Knoten createTask einen Task mit den Feldern name, notes, assignee, projectId und workspace an, assignee wird dabei auf newCustomer.output.csm_email gemappt. Der Loop-Ende-Knoten taskLoopEnd sammelt anschließend alle Ergebnisse ein und ist auf die Fehlerstrategie Weiter gesetzt, sodass ein einzelner fehlgeschlagener Task die übrigen Durchläufe nicht stoppt.", "prompt_ref": null, "eingang": [ "onboardingChecklist.output.structured.tasks", "newCustomer.output.csm_email" ], "ausgang": [ "Angelegte Tasks im Onboarding-Board (createTask je Schleifendurchlauf)", "Gesammeltes Loop-Ergebnis (taskLoopEnd)" ] }, { "nr": 5, "titel": "Welcome-Mail als Entwurf erstellen", "rolle": "automatisch", "aktion": "Der KI-Knoten welcomeEmailGenerator erzeugt mit dem Arbeitsprompt Welcome-Mail eine strukturierte Ausgabe mit den Pflichtfeldern subject, body und success. In der Referenz folgt darauf ein eigener Aktions-Knoten sendWelcomeEmail, der die Mail direkt per Gmail-Aktion verschickt: mailRecipient auf newCustomer.output.email, cc auf newCustomer.output.csm_email, mailSubject und mailBody auf welcomeEmailGenerator.output.structured.subject beziehungsweise .body gemappt. Das entspricht einem automatischen Versand statt einem reinen Entwurf. Wer die Kontrolle über die Tonalität behalten möchte, richtet diesen Schritt bewusst als Entwurfsablage ein, bevor der Workflow aktiviert wird.", "prompt_ref": "arbeitsprompt-2", "eingang": [ "Kundendaten", "onboardingChecklist.output.structured.summary" ], "ausgang": [ "welcomeEmailGenerator.output.structured.subject", "welcomeEmailGenerator.output.structured.body", "Welcome-Mail, in der Referenz direkt versendet über sendWelcomeEmail" ] }, { "nr": 6, "titel": "CSM benachrichtigen", "rolle": "ergebnis", "aktion": "Der Knoten notifyCsm sendet eine Slack-Nachricht an das Customer-Success-Team mit Kundenname, zuständigem Customer Success Manager und Anzahl der angelegten Tasks. In der Referenz läuft dieser Schritt nach dem Mailversand, er dient dort als Abschlussmeldung und nicht als Freigabe-Gate vor dem Versand.", "prompt_ref": null, "eingang": [ "Angelegte Tasks im Onboarding-Board", "Welcome-Mail beziehungsweise Welcome-Mail-Entwurf" ], "ausgang": [ "Benachrichtigung im Team-Chat" ] } ], "prompts": { "arbeitsprompt-1": { "titel": "Onboarding-Checkliste", "text": "Erstellen Sie als erfahrener Customer Success Manager aus den Kundendaten (Name, Unternehmen, Branche, Produkt, Unternehmensgröße, Ansprechpartner) eine Onboarding-Checkliste mit fünf bis acht konkreten, auf Branche und Produkt zugeschnittenen Tasks. Geben Sie die Checkliste als nummerierte Liste mit Zeitschätzung je Task aus." }, "arbeitsprompt-2": { "titel": "Welcome-Mail", "text": "Verfassen Sie als zuständiger Customer Success Manager eine persönliche Willkommens-Mail an den neuen Kunden, mit Begrüßung, kurzer Vorstellung, Überblick über die nächsten Schritte entlang der Onboarding-Checkliste, Einladung zum Kick-off-Call mit zwei bis drei Zeitfenstern sowie Kontaktdaten. Maximal 250 Wörter, in der vorgegebenen Tonalität." } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Formular- beziehungsweise CRM-Datensatz aus newCustomer.output, darunter email und csm_email" }, { "von": 2, "nach": 3, "nutzlast": "Kundendaten für den Arbeitsprompt Onboarding-Checkliste: Kundenname, Unternehmen, Branche, Produkt, Unternehmensgröße, Ansprechpartner" }, { "von": 2, "nach": 5, "nutzlast": "Ansprechpartner-Name, Kunden-Unternehmen und Produkt für den Arbeitsprompt Welcome-Mail, dazu newCustomer.output.email als Empfängeradresse und newCustomer.output.csm_email für Assignee und cc" }, { "von": 3, "nach": 4, "nutzlast": "onboardingChecklist.output.structured.tasks als Schleifen-Array, aktuelles Element unter taskLoop.output.item" }, { "von": 3, "nach": 5, "nutzlast": "onboardingChecklist.output.structured.summary als Onboarding-Checkliste-Text für den Arbeitsprompt Welcome-Mail" }, { "von": 4, "nach": 6, "nutzlast": "Ergebnis der Aufgaben-Schleife aus taskLoopEnd, Link zu den angelegten Tasks im Onboarding-Board" }, { "von": 5, "nach": 6, "nutzlast": "welcomeEmailGenerator.output.structured.subject und .body, in der Referenz über sendWelcomeEmail bereits verschickt, bevor notifyCsm die Abschlussmeldung sendet" } ], "voraussetzungen": [ "CRM-System mit Status-Trigger und Kundendaten, zum Beispiel HubSpot oder Salesforce", "PM-Tool für die Onboarding-Tasks, zum Beispiel Asana, Trello oder Monday", "E-Mail-Tool für die Willkommens-Mail, zum Beispiel Gmail oder Outlook", "LLM-Zugang für Checkliste und Mailtext, zum Beispiel OpenAI, Claude oder Gemini", "Team-Chat für die Benachrichtigung des Customer Success Managers, zum Beispiel Slack oder Teams" ], "fehlerbehandlung": [ { "fall": "Fehler in Trigger, Checkliste-Erstellung, Mailtext-Erstellung, Task-Anlage, Mailversand oder CSM-Benachrichtigung", "massnahme": "Alle genannten Knoten sind in der Referenz auf die Fehlerstrategie Stop gesetzt, ein Fehler bricht den gesamten Lauf ab." }, { "fall": "Ein einzelner Task innerhalb der Aufgaben-Schleife schlägt fehl", "massnahme": "Der Loop-Ende-Knoten taskLoopEnd ist auf die Fehlerstrategie Weiter gesetzt, die Schleife verarbeitet die übrigen Tasks weiter und sammelt alle Ergebnisse." }, { "fall": "CRM-Trigger feuert nicht", "massnahme": "Webhook und den Status-Wert Kunde prüfen. Ersetzen Sie dafür zunächst das Formular aus der Referenz durch den tatsächlichen CRM- oder Webhook-Trigger." }, { "fall": "Pflichtfelder fehlen, etwa Branche oder Ansprechpartner", "massnahme": "Lauf anhalten und den Customer Success Manager mit einem Hinweis informieren, statt die Mail mit leeren Feldern zu verschicken." }, { "fall": "Tasks landen im falschen Projekt", "massnahme": "Ziel-Board und Berechtigungen prüfen, insbesondere die Felder projectId und workspace im Task-Knoten." }, { "fall": "Checkliste zu generisch", "massnahme": "Den Prompt um branchenspezifische Beispiele ergänzen." }, { "fall": "Mehrere Ansprechpartner vorhanden", "massnahme": "Den Hauptkontakt aus dem CRM verwenden." } ], "platzhalter": [ { "name": "newCustomer.output.email", "quelle": "Kunden-E-Mail-Adresse aus dem Trigger, Empfänger der Welcome-Mail" }, { "name": "newCustomer.output.csm_email", "quelle": "E-Mail-Adresse des zuständigen Customer Success Managers aus dem Trigger, genutzt als Assignee der Tasks und als cc beim Mailversand" }, { "name": "onboardingChecklist.output.structured.tasks", "quelle": "Array der generierten Onboarding-Tasks, Grundlage der Aufgaben-Schleife" }, { "name": "onboardingChecklist.output.structured.summary", "quelle": "Zusammenfassung der Onboarding-Strategie, Eingabe für die Onboarding-Checkliste im Welcome-Mail-Prompt" }, { "name": "taskLoop.output.item", "quelle": "aktueller Task der Aufgaben-Schleife, je Iteration verfügbar" }, { "name": "welcomeEmailGenerator.output.structured.subject", "quelle": "generierter E-Mail-Betreff, Eingabe für den Versand-Schritt" }, { "name": "welcomeEmailGenerator.output.structured.body", "quelle": "generierter E-Mail-Text, Eingabe für den Versand-Schritt" }, { "name": "CSM_NAME", "quelle": "Name des zuständigen Customer Success Managers, vor der Aktivierung manuell hinterlegen" }, { "name": "CSM_POSITION", "quelle": "Positionsbezeichnung des Customer Success Managers für die Signatur" }, { "name": "KONTAKTDATEN", "quelle": "Kontaktdaten des Customer Success Managers für die Signatur" }, { "name": "EIGENES_UNTERNEHMEN", "quelle": "Name des eigenen Unternehmens im Arbeitsprompt Welcome-Mail, zu unterscheiden vom Kunden-Unternehmen aus den Trigger-Daten" }, { "name": "TONALITÄT", "quelle": "gewünschte Tonalität der Welcome-Mail, zum Beispiel professionell-freundlich, locker-modern oder formell" }, { "name": "ZUSÄTZLICHE_ANFORDERUNGEN", "quelle": "ergänzende, branchenspezifische Vorgaben für die Onboarding-Checkliste" }, { "name": "ZEITFENSTER", "quelle": "vorgeschlagene Termine für den Kick-off-Call, idealerweise dynamisch aus dem Kalender des Customer Success Managers" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "door-open", "recommended": [ { "slug": "termin-bruecke", "category": "workflow", "name": "The Appointment Bridge", "teaser": "A workflow that reads incoming appointment requests, checks calendar availability, and drops a ready reply draft with three time proposals into the inbox for review before sending.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "calendar-check" }, { "slug": "buero-lotse", "category": "assistent", "name": "The Office Navigator", "teaser": "An assistant that guides you through three recurring office tasks, structured brainstorming, ready-to-use communication drafts, and concrete project planning, based on the context knowledge you provide.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "printer" }, { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "office", "category": "skill", "name": "The Office Workbench", "teaser": "The Office Workbench is an executable Claude skill that builds, reads, and edits Word, PowerPoint, and Excel files with the right tools, formatting rules, and quality checks for each format.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "table" }, { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "retro-regelwerk", "category": "skill", "name": "The Retro Rulebook", "teaser": "The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "rotate-ccw" }, { "slug": "uebergabe-paket", "category": "skill", "name": "The Handover Package", "teaser": "Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "package-check" }, { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "team-digest-schleife", "category": "workflow", "name": "The Team Digest Loop", "teaser": "A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mails" }, { "slug": "okr-stratege", "category": "assistent", "name": "The OKR Strategist", "teaser": "Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "target" }, { "slug": "projekt-sparringspartner", "category": "assistent", "name": "The Project Sparring Partner", "teaser": "Guides you through every phase of a project with systematic risk analysis, prioritized courses of action for acute problems, and structured lessons learned after completion.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "kanban-square" }, { "slug": "verhandlungs-stratege", "category": "assistent", "name": "The Negotiation Strategist", "teaser": "Analyzes a supplier quote along with its market context and develops a concrete, ready-to-use negotiation strategy with goals, levers, arguments and fallback positions.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "handshake" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "einarbeitungs-spur", "category": "workflow", "name": "The Onboarding Track", "teaser": "A workflow that automatically creates a position specific onboarding checklist for the first 30, 60 and 90 days when a new employee is added to the HR system, generates tasks from it in the project tool, and notifies the manager and IT in good time.", "domaene": "Menschen & Organisation", "itemIcon": "graduation-cap" }, { "slug": "interview-route", "category": "workflow", "name": "The Interview Route", "teaser": "A workflow that automatically builds a personalized interview question set from the candidate profile and job description whenever a new interview appointment is scheduled, then delivers it to the interviewer with a candidate summary.", "domaene": "Menschen & Organisation", "itemIcon": "mic" }, { "slug": "korrespondenz-skript", "category": "skill", "name": "The Correspondence Script", "teaser": "Drafts a ready-to-send business email, from subject line to a concrete next step, matched to the recipient, occasion and tone.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mail" }, { "slug": "gmail", "category": "tool", "name": "Gmail", "teaser": "Gmail is Google's email service, offering mailbox access, powerful search, filter rules, AI-assisted drafting, and automation interfaces through the Gmail API.", "domaene": "Betrieb & Projektmanagement", "logoFile": "gmail.png", "logoEinzug": 1 }, { "slug": "google-calendar", "category": "tool", "name": "Google Calendar", "teaser": "Google Calendar is Google's web-based calendar application for appointments, invitations and calendars shared across teams, tightly linked to Gmail, Meet and Drive.", "domaene": "Betrieb & Projektmanagement", "logoFile": "google-calendar.png", "logoEinzug": 0.78 }, { "slug": "google-drive", "category": "tool", "name": "Google Drive", "teaser": "Google's cloud file storage for documents, spreadsheets and presentations, with real-time collaboration, granular sharing and automation through the Drive API.", "domaene": "Betrieb & Projektmanagement", "logoFile": "google-drive.png", "logoEinzug": 1 } ] }