Before a customer meeting, the same manual prep tends to repeat itself: a quick look in the CRM, googling the name, checking LinkedIn, trying to recall the last conversation. This workflow takes over exactly that prep work. As soon as a new meeting with external participants appears on the calendar, it reads out participants, company and agenda, matches the contact against the CRM by email address, and adds current web research on the company and the person.
\nThese three sources combine into a structured briefing with customer context, recent developments, concrete talking points, open items from the history, and a short recommendation of what still needs doing before the meeting. The briefing is delivered automatically by email or Notion to the meeting owner, with enough lead time before the conversation.
\nWhat gets automated is the research and the assembly, not the conversation itself. A human stays in the loop at two points: maintaining the calendar filter that decides which meetings trigger a briefing in the first place, and reading the briefing before the actual meeting. For sales teams with many recurring customer meetings, this saves the half hour of research that would otherwise happen before every call, and it keeps every briefing consistent with the others.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: termin-briefing-staffel.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Trigger", "beschreibung": "A new meeting on the calendar with the label \"Customer Meeting\" or with external participants starts the process.", "rolle": "mensch" }, { "nr": 2, "titel": "Extract meeting context", "beschreibung": "Participants, agenda, company and time are read from the calendar entry.", "rolle": "automatisch" }, { "nr": 3, "titel": "CRM lookup", "beschreibung": "The contact's email address is used to determine contact, deal stage and recent interactions in the CRM.", "rolle": "automatisch" }, { "nr": 4, "titel": "Web research", "beschreibung": "Current company news, LinkedIn updates and relevant trigger events are gathered.", "rolle": "automatisch" }, { "nr": 5, "titel": "Generate briefing", "beschreibung": "Customer context, recent developments, talking points, open items and recommended preparation are condensed into a structured briefing.", "rolle": "automatisch" }, { "nr": 6, "titel": "Delivery", "beschreibung": "The briefing goes out by email or as a Notion or Slack link to the meeting owner.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Prepared without research", "text": "A finished briefing is ready instead of googling the contact right before the meeting." }, { "titel": "CRM context at hand", "text": "Deal stage, recent interactions and notes are included directly in the briefing." }, { "titel": "Better conversations", "text": "Current news and updates provide natural talking points." }, { "titel": "Consistency per meeting", "text": "Every briefing follows the same structure, no matter who prepares it." } ], "voraussetzungen": [ { "label": "Calendar tool", "text": "Google, Outlook or Calendly supplies the meeting and participant data.", "icon": "calendar_month" }, { "label": "CRM system", "text": "HubSpot, Salesforce or similar, for contact, deal stage and interaction history.", "icon": "contacts" }, { "label": "Web research", "text": "A search API or a service such as Perplexity for current news and updates.", "icon": "travel_explore" }, { "label": "LLM access and delivery", "text": "API access to OpenAI, Claude or Gemini, plus a delivery channel such as Gmail, Notion or Slack.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test meeting", "text": "Set up a calendar meeting in two hours with a CRM contact and the label \"Customer Meeting\".", "icon": "event" }, { "label": "CRM and web research", "text": "Check whether contact match, recent interactions and current news arrive in the briefing.", "icon": "contacts" }, { "label": "Briefing structure", "text": "Check whether context, developments, talking points and open items are cleanly separated.", "icon": "fact_check" }, { "label": "Edge cases", "text": "Test a meeting without a CRM match, with several companies, set up on very short notice, and with an ambiguous name.", "icon": "rule" } ], "goLive": [ { "label": "Approve", "text": "Activate the workflow only once the filter, CRM lookup, web research and delivery work cleanly together.", "icon": "check_circle" }, { "label": "Pilot", "text": "Align the briefing template with sales and start with one team.", "icon": "groups" }, { "label": "Refine", "text": "Adjust the sources and keywords of the web research over two to three weeks.", "icon": "tune" }, { "label": "Expand", "text": "Add a Slack short version, a competitor analysis, an automatic agenda or a follow up, as needed.", "icon": "rocket_launch" } ], "haeufigeFehler": [ { "label": "Calendar trigger does not fire", "text": "Check the label or category for customer meetings for correct assignment.", "icon": "event_busy" }, { "label": "CRM data missing", "text": "Make sure the match runs on the email address, not the name.", "icon": "alternate_email" }, { "label": "Web research stays empty", "text": "Check name extraction and the search API, and define a fallback.", "icon": "search_off" }, { "label": "Briefing too long", "text": "Limit the length strictly to one page and to fixed section lengths in the prompt.", "icon": "straighten" } ] }, "arbeitsprompts": [ { "titel": "Research analysis and briefing", "beschreibung": "Used in step 5 to turn meeting details, CRM data and web research into a structured meeting briefing.", "prompt": "You are a sales assistant preparing for a customer conversation.\n\nMeeting details:\nCustomer: [CUSTOMER_NAME]\nCompany: [COMPANY_NAME]\nMeeting: [DATE] at [TIME]\nTopic: [MEETING_SUBJECT]\n\nCRM data:\n[RECENT_INTERACTIONS]\n\nCurrent research:\n[WEB_RESEARCH_RESULTS]\n\nCreate a structured meeting briefing with the following sections:\n\n1. Customer context (two to three sentences): Who is the customer, what role do they have, what relationship already exists?\n2. Recent developments (three to four bullet points): relevant news, company developments, LinkedIn updates.\n3. Talking points (three to five bullet points): concrete topics that should be raised in the conversation.\n4. Open items (two to three bullet points): what still needs clarifying or following up on according to the CRM history.\n5. Recommended preparation (one to two sentences): what still needs to be done before the meeting.\n\nKeep the briefing concise, action oriented and to a maximum of one page." } ], "prompt": "GOAL\nBuild a workflow that automatically creates a structured briefing from calendar details, CRM context and current web research before every customer meeting, and delivers it to the meeting owner in good time before the meeting.\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, the parallelism and the data flow.\n\nTRIGGER\nType: new meeting on the calendar (Google Calendar, Outlook or Calendly), alternatively time based, for example two hours before the meeting starts.\nFilter: customer meetings only, that is a meeting with the label or category \"Customer Meeting\", or with at least one external participant whose email domain differs from your own domain.\n\nSTEPS\n1. Extract meeting context: participants with names and email addresses, company, agenda or subject, date and time. After this, step 2 and step 3 run in parallel.\n2. CRM lookup (HubSpot, Salesforce or similar): match on the email address, not the name. Load contact, deal stage, recent interactions and notes.\n3. Web research (search API, Perplexity or similar): current company news, LinkedIn updates and relevant trigger events for the company and the person.\n4. AI step: generate briefing. Use exactly the \"Research analysis and briefing\" prompt below. Inputs: meeting details from step 1, CRM data from step 2, research results from step 3.\n5. Output: deliver the briefing by email to the meeting owner, alternatively as a Notion page or a Slack message with a link, in good time before the meeting starts.\n\nPROMPTS (use exactly and unchanged)\nPrompt 1, research analysis and briefing:\n\"\"\"\nYou are a sales assistant preparing for a customer conversation.\n\nMeeting details:\nCustomer: [CUSTOMER_NAME]\nCompany: [COMPANY_NAME]\nMeeting: [DATE] at [TIME]\nTopic: [MEETING_SUBJECT]\n\nCRM data:\n[RECENT_INTERACTIONS]\n\nCurrent research:\n[WEB_RESEARCH_RESULTS]\n\nCreate a structured meeting briefing with the following sections:\n\n1. Customer context (two to three sentences): Who is the customer, what role do they have, what relationship already exists?\n2. Recent developments (three to four bullet points): relevant news, company developments, LinkedIn updates.\n3. Talking points (three to five bullet points): concrete topics that should be raised in the conversation.\n4. Open items (two to three bullet points): what still needs clarifying or following up on according to the CRM history.\n5. Recommended preparation (one to two sentences): what still needs to be done before the meeting.\n\nKeep the briefing concise, action oriented and to a maximum of one page.\n\"\"\"\n\nDATA FLOW\nStep 1 to step 2: email addresses of the external participants and the company name.\nStep 1 to step 3: company name and participant names.\nStep 1 to 3 to step 4: [CUSTOMER_NAME], [COMPANY_NAME], [DATE], [TIME], [MEETING_SUBJECT], [RECENT_INTERACTIONS], [WEB_RESEARCH_RESULTS].\nStep 4 to step 5: finished briefing, a maximum of one page.\n\nERROR HANDLING\nNo CRM match: create and send the briefing regardless, with the note \"No CRM entry found\" and an empty CRM section.\nWeb research returns nothing: create the briefing only from meeting and CRM context and flag this in the briefing.\nAmbiguous company or person name: prioritize the match on the email domain.\nVery short notice meeting: run the workflow immediately instead of waiting for the planned lead time.\n\nPLACEHOLDER CONVENTION\nAll placeholders in square brackets are variables. Map them dynamically to data from previous steps, as described in the data flow. Placeholders that cannot be filled dynamically are set manually before activation. List these separately at the end.\n\nSELF CHECK BEFORE COMPLETION\nCheck, before you report the workflow as finished:\n1. Are all steps connected correctly, including the parallelism of step 2 and step 3?\n2. Is the prompt inserted in full and unchanged, and are all placeholders mapped?\n3. Are the trigger filter and delivery channel configured as specified?\n4. Are all points listed that require manual configuration: the calendar connection, CRM access, the search API access, the owner or recipient mapping, and the label \"Customer Meeting\"?", "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": "w26_termin-briefing-staffel__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Termin-Briefing-Staffel", "beschreibung": "Erstellt vor jedem Kundentermin automatisch ein strukturiertes Briefing aus Kalenderdetails, CRM-Kontext und aktueller Web-Recherche und stellt es rechtzeitig vor dem Termin an den Termin-Owner zu.", "trigger": { "typ": "Neuer Termin in Google Calendar, native Kalender-Integration", "bedingung": "Kein Webhook und kein Zeitplan: Der Trigger beobachtet Google Calendar direkt und reagiert, sobald ein neuer Termin angelegt wird. Die Filterung auf Kundentermine läuft über eine Sucheingabe im Trigger selbst, etwa ein Stichwort wie „Kunde“ im Titel, oder über einen eigenen Kalender, der ausschließlich für Kundentermine geführt wird." }, "schritte": [ { "nr": 1, "titel": "Trigger", "rolle": "mensch", "aktion": "Ein neuer Termin wird in Google Calendar angelegt. Die native Kalender-Integration erkennt ihn ohne Zwischenschritt, sofern die Sucheingabe des Triggers greift (Stichwort im Titel oder dedizierter Kalender für Kundentermine).", "prompt_ref": null, "eingang": [], "ausgang": [ "Kalendertermin mit Teilnehmern, Titel, Datum und Uhrzeit" ] }, { "nr": 2, "titel": "Termin-Kontext extrahieren", "rolle": "automatisch", "aktion": "Im tatsächlichen Aufbau ist dies kein eigener Knoten: Die Extraktion von Teilnehmer-Namen, E-Mail-Adressen, Firma und Zeitpunkt geschieht als Teil der Sucheingabe des folgenden CRM-Lookups, dort steht das Suchfeld auf automatisch, und die KI liest Name und E-Mail-Adressen direkt aus den Kalender-Teilnehmern.", "prompt_ref": null, "eingang": [ "Kalendertermin mit Teilnehmern, Titel, Datum und Uhrzeit" ], "ausgang": [ "Automatische Sucheingabe für den CRM-Lookup: Teilnehmer-E-Mail-Adressen und Firmenname" ] }, { "nr": 3, "titel": "CRM-Lookup", "rolle": "automatisch", "aktion": "Zwei HubSpot-Abrufe laufen hier nacheinander. Der erste sucht mit automatischer Sucheingabe und einer Treffergrenze von eins den passenden Kontakt und lädt die Felder email, firstname, lastname, company, jobtitle, phone, website und lifecyclestage. Der zweite übernimmt die gefundene Kontakt-ID als Eingabefeld id und ruft darüber die letzten fünf Aktivitäten ab, also E-Mails, Anrufe, Meetings und Notizen aus der HubSpot-Historie.", "prompt_ref": null, "eingang": [ "Automatische Sucheingabe für den CRM-Lookup: Teilnehmer-E-Mail-Adressen und Firmenname" ], "ausgang": [ "HubSpot-Kontaktdaten: email, firstname, lastname, company, jobtitle, phone, website, lifecyclestage", "Die letzten fünf HubSpot-Aktivitäten zum Kontakt" ] }, { "nr": 4, "titel": "Web-Recherche", "rolle": "automatisch", "aktion": "Zwei Web-Suchen laufen parallel, beide direkt im Anschluss an den CRM-Lookup und nicht an den Kalender-Trigger. Die eine recherchiert aktuelle Unternehmens-News und Pressemitteilungen zur Firma aus dem HubSpot-Feld company. Die andere recherchiert das LinkedIn-Profil und aktuelle Updates zur Person aus den HubSpot-Feldern firstname, lastname und company. Der nachfolgende Briefing-Schritt ist der Merge-Punkt und wartet, bis beide Suchen abgeschlossen sind.", "prompt_ref": null, "eingang": [ "HubSpot-Feld company", "HubSpot-Felder firstname, lastname, company" ], "ausgang": [ "Aktuelle Unternehmens-News und Pressemitteilungen", "LinkedIn-Profil und aktuelle Updates zur Person" ] }, { "nr": 5, "titel": "Briefing generieren", "rolle": "automatisch", "aktion": "Ein KI-Agent verdichtet Termin-Details, HubSpot-Kontaktdaten, die letzten fünf Aktivitäten und beide Rechercheergebnisse zu einem Briefing. Die Ausgabe ist strukturiert (Modus: erstellen, Ausgabeform: structured) und liefert zwei Felder: briefing als Pflichttext mit dem vollständigen formatierten Briefing, und success als Pflicht-Wahrheitswert, der anzeigt, ob die Erstellung geglückt ist.", "prompt_ref": "arbeitsschritt-1", "eingang": [ "Terminbetreff, Datum und Uhrzeit aus dem Kalendertermin", "HubSpot-Kontaktdaten und die letzten fünf HubSpot-Aktivitäten", "Aktuelle Unternehmens-News und LinkedIn-Updates aus beiden Web-Suchen" ], "ausgang": [ "Strukturiertes Ausgabefeld briefing (Text)", "Strukturiertes Ausgabefeld success (Wahrheitswert)" ] }, { "nr": 6, "titel": "Zustellung", "rolle": "ergebnis", "aktion": "Das Briefing wird per Gmail versendet. Das Feld mailBody wird direkt mit der Ausgabe briefingGenerator.output.structured.briefing befüllt. Das Feld mailSubject wird dynamisch im Format „Briefing: [Terminbetreff]“ aus dem Kalendertitel gebildet. Das Feld mailRecipient ist im Original ohne feste Vorgabe hinterlegt, es wird automatisch auf den Termin-Organisator beziehungsweise Owner aufgelöst.", "prompt_ref": null, "eingang": [ "Strukturiertes Ausgabefeld briefing (Text)" ], "ausgang": [ "Versendete Briefing-E-Mail beim Termin-Owner" ] } ], "prompts": { "arbeitsschritt-1": { "titel": "Recherche-Analyse und Briefing", "text": "Sie sind ein Vertriebs-Assistent und bereiten ein Kundengespräch vor.\n\nTermin-Details:\nKunde: [KUNDENNAME]\nUnternehmen: [UNTERNEHMENSNAME]\nTermin: [DATUM] um [UHRZEIT]\nThema: [TERMINBETREFF]\n\nCRM-Daten:\n[LETZTE_INTERAKTIONEN]\n\nAktuelle Recherche:\n[WEB_RECHERCHE_ERGEBNISSE]\n\nErstellen Sie ein strukturiertes Termin-Briefing mit folgenden Abschnitten:\n\n1. Kundenkontext (zwei bis drei Sätze): Wer ist der Kunde, welche Rolle hat er, welche Beziehung besteht bereits?\n2. Aktuelle Entwicklungen (drei bis vier Bulletpoints): relevante News, Unternehmensentwicklungen, LinkedIn-Updates.\n3. Gesprächsthemen (drei bis fünf Bulletpoints): konkrete Themen, die im Gespräch angesprochen werden sollten.\n4. Offene Punkte (zwei bis drei Bulletpoints): was laut CRM-Historie noch zu klären oder nachzufassen ist.\n5. Empfohlene Vorbereitung (ein bis zwei Sätze): was vor dem Termin noch erledigt werden sollte.\n\nHalten Sie das Briefing prägnant, handlungsorientiert und auf maximal eine Seite." } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Kalendertermin mit Teilnehmern, Titel, Datum und Uhrzeit, aus dem Google-Calendar-Trigger" }, { "von": 2, "nach": 3, "nutzlast": "Automatische Sucheingabe (Suchfeld auf automatisch) mit Teilnehmer-E-Mail-Adressen und Firmenname, für den Kontakt-Fund in HubSpot" }, { "von": 2, "nach": 5, "nutzlast": "Terminbetreff, Datum und Uhrzeit aus dem Kalendertermin, direkt an den Briefing-Agenten" }, { "von": 3, "nach": 4, "nutzlast": "HubSpot-Feld company aus dem Kontakt-Fund, für die parallele Firmen-News-Suche" }, { "von": 3, "nach": 4, "nutzlast": "HubSpot-Felder firstname, lastname und company aus dem Kontakt-Fund, für die parallele LinkedIn-Suche zur Person" }, { "von": 3, "nach": 5, "nutzlast": "HubSpot-Kontaktdaten (email, firstname, lastname, company, jobtitle, phone, website, lifecyclestage) und die letzten fünf HubSpot-Aktivitäten" }, { "von": 4, "nach": 5, "nutzlast": "Aktuelle Unternehmens-News und LinkedIn-Updates aus beiden parallelen Web-Suchen, zusammengeführt im Merge-Punkt des Briefing-Agenten" }, { "von": 5, "nach": 6, "nutzlast": "Ausgabefeld briefing (Text) aus dem strukturierten Agenten-Output, eingesetzt als mailBody im Versand-Schritt" } ], "voraussetzungen": [ "Kalender-Tool wie Google, Outlook oder Calendly zur Erkennung von Termin und Teilnehmern", "CRM-System wie HubSpot oder Salesforce für Kontakt, Deal-Stage und Interaktionshistorie", "Web-Recherche-Zugang, etwa eine Search-API oder Perplexity, für aktuelle News und Updates", "LLM-Zugang, etwa OpenAI, Claude oder Gemini, sowie ein Zustellweg wie Gmail, Notion oder Slack", "Sauber gepflegter Kalender-Filter oder ein Label für Kundentermine" ], "fehlerbehandlung": [ { "fall": "Fehler in einem beliebigen Knoten (Trigger, CRM-Lookup, Web-Recherche, Briefing-Agent oder Versand)", "massnahme": "Im Original-Export ist für jeden Knoten die Fehlerstrategie auf stop gesetzt. Ein Fehler in einem einzelnen Knoten hält den gesamten Workflow an, es gibt keinen eingebauten Fallback. Wer stattdessen ein Briefing trotz fehlendem CRM-Treffer oder leerer Web-Recherche ausliefern will, muss diese Kulanz beim Nachbau selbst ergänzen." }, { "fall": "Kalender-Trigger feuert nicht", "massnahme": "Sucheingabe beziehungsweise Filter des Trigger-Knotens prüfen: Stichwort im Titel oder Auswahl des richtigen Kalenders." }, { "fall": "CRM-Daten fehlen", "massnahme": "Sicherstellen, dass die Sucheingabe des Kontakt-Fund-Knotens über die Teilnehmer-E-Mail-Adresse trifft, nicht nur über den Namen." }, { "fall": "Web-Recherche liefert nichts", "massnahme": "Namens- und Firmen-Extraktion aus den HubSpot-Feldern sowie die Anbindung der beiden Such-Knoten prüfen, Fallback für den Briefing-Agenten definieren." }, { "fall": "Briefing zu lang", "massnahme": "Im Prompt des Briefing-Agenten die Länge strikt auf eine Seite und feste Abschnittslängen begrenzen." } ], "platzhalter": [ { "name": "KUNDENNAME", "quelle": "HubSpot-Felder firstname und lastname aus dem Kontakt-Fund" }, { "name": "UNTERNEHMENSNAME", "quelle": "HubSpot-Feld company aus dem Kontakt-Fund" }, { "name": "DATUM", "quelle": "Datum des Kalendertermins aus dem Trigger" }, { "name": "UHRZEIT", "quelle": "Uhrzeit des Kalendertermins aus dem Trigger" }, { "name": "TERMINBETREFF", "quelle": "Titel des Kalendertermins aus dem Trigger" }, { "name": "LETZTE_INTERAKTIONEN", "quelle": "Ausgabe des zweiten CRM-Knotens: die letzten fünf HubSpot-Aktivitäten (E-Mails, Anrufe, Meetings, Notizen) zur Kontakt-ID" }, { "name": "WEB_RECHERCHE_ERGEBNISSE", "quelle": "Zusammengeführte Ausgabe der Firmen-News-Suche und der LinkedIn-Suche zur Person" }, { "name": "searchQuery", "quelle": "Suchfeld des Kontakt-Fund-Knotens, im Original auf automatisch gestellt: die KI liest die Teilnehmer direkt aus dem Kalendertermin" }, { "name": "properties", "quelle": "Liste der abgerufenen HubSpot-Kontaktfelder im Kontakt-Fund-Knoten: email, firstname, lastname, company, jobtitle, phone, website, lifecyclestage" }, { "name": "limit", "quelle": "Trefferbegrenzung des Kontakt-Fund-Knotens, im Original auf 1 gesetzt" }, { "name": "id", "quelle": "Kontakt-ID aus dem Kontakt-Fund-Knoten, Eingabefeld des Aktivitäten-Abrufs" }, { "name": "mailBody", "quelle": "Ausgabefeld briefing des Briefing-Agenten (structured output), eingesetzt im Versand-Knoten" }, { "name": "mailSubject", "quelle": "Betrefffeld des Versand-Knotens, dynamisch aus dem Titel des Kalendertermins gebildet: Briefing: [Terminbetreff]" }, { "name": "mailRecipient", "quelle": "Empfängerfeld des Versand-Knotens, im Original ohne feste Anweisung: automatisch der Termin-Organisator beziehungsweise Owner" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "calendar-clock", "recommended": [ { "slug": "angebots-schiene", "category": "workflow", "name": "The Quote Pipeline", "teaser": "A workflow that automatically turns an incoming quote request into a reviewed quote draft, from requirements extraction through to sales approval.", "domaene": "Vertrieb & Outreach", "itemIcon": "file-badge" }, { "slug": "pipeline-schiene", "category": "workflow", "name": "The Pipeline Pulse", "teaser": "A weekly report that reads your open pipeline from the CRM and flags risks, opportunities and stagnating deals for the sales team.", "domaene": "Vertrieb & Outreach", "itemIcon": "git-branch" }, { "slug": "meeting-planer", "category": "assistent", "name": "The Meeting Planner", "teaser": "The Meeting Planner turns a company name, contact person and offer into a client-meeting briefing that reads in fifteen minutes and leaves you fully prepared.", "domaene": "Vertrieb & Outreach", "itemIcon": "calendar-check" }, { "slug": "account-dossier", "category": "skill", "name": "The Account Dossier", "teaser": "The Account Dossier gathers publicly available information on a target company into a structured briefing covering profile, strategy, decision makers, and reasoned pain point hypotheses to prepare for sales conversations.", "domaene": "Vertrieb & Outreach", "itemIcon": "building-2" }, { "slug": "clay", "category": "tool", "name": "Clay", "teaser": "A spreadsheet-based platform that combines over 100 data sources and an AI research agent for lead enrichment and personalized outbound.", "domaene": "Vertrieb & Outreach", "logoFile": "clay.png", "logoEinzug": 1 }, { "slug": "kundentermin-protokoll", "category": "skill", "name": "The Client Meeting Protocol", "teaser": "Turns notes or a transcript from a client meeting into a structured protocol with a BANT or MEDDIC opportunity analysis, action items, and a follow-up email draft.", "domaene": "Vertrieb & Outreach", "itemIcon": "notebook-pen" }, { "slug": "pipeline-protokoll", "category": "skill", "name": "The Pipeline Protocol", "teaser": "Systematically checks your CRM pipeline, flags deals that need action, and delivers a compact report with metrics and prioritized next steps.", "domaene": "Vertrieb & Outreach", "itemIcon": "git-branch" }, { "slug": "qbr-dossier", "category": "skill", "name": "The QBR Dossier", "teaser": "Creates a structured Quarterly Business Review for existing customers, from health score to a prioritized roadmap for the next quarter.", "domaene": "Vertrieb & Outreach", "itemIcon": "pie-chart" }, { "slug": "scoring-schema", "category": "skill", "name": "The Scoring Framework", "teaser": "Scores incoming leads against your ICP criteria, assigns a traceable score with a confidence rating, prioritizes them into Hot, Warm and Disqualified, and delivers first-outreach drafts for the top leads.", "domaene": "Vertrieb & Outreach", "itemIcon": "star" }, { "slug": "lead-staffel", "category": "workflow", "name": "The Lead Relay", "teaser": "Every new lead from a form is automatically scored on budget, need and timing and reaches the right salesperson within minutes, complete with a priority score and rationale.", "domaene": "Vertrieb & Outreach", "itemIcon": "user-plus" }, { "slug": "vertriebsantwort-schiene", "category": "workflow", "name": "The Sales Response Pipeline", "teaser": "Automatically drafts a personalized sales reply from CRM context for incoming lead emails and notifies the responsible sales rep for review before it is sent.", "domaene": "Vertrieb & Outreach", "itemIcon": "send" }, { "slug": "call-analyst", "category": "assistent", "name": "The Call Analyst", "teaser": "Turns call notes or a sales call transcript into a CRM-ready follow-up document with needs analysis, BANT assessment and a scheduled follow-up plan.", "domaene": "Vertrieb & Outreach", "itemIcon": "phone-call" }, { "slug": "kundentermin-dossier", "category": "skill", "name": "The Client Meeting Dossier", "teaser": "Researches a target company and its contact person ahead of a client meeting and turns the findings into a meeting briefing with a conversation strategy, agenda, prepared questions and objection handling.", "domaene": "Vertrieb & Outreach", "itemIcon": "calendar-clock" }, { "slug": "pitch-geruest", "category": "skill", "name": "The Pitch Deck Builder", "teaser": "Builds a complete sales deck from target audience, goal and available time.", "domaene": "Vertrieb & Outreach", "itemIcon": "rocket" }, { "slug": "kaltakquise-sequenzer", "category": "assistent", "name": "The Cold Email Sequencer", "teaser": "Builds a short, personalized cold email from target contact, offer and research, complete with subject line, connection point and a low-friction call to action, optionally as the starting point of a multi-step sequence.", "domaene": "Vertrieb & Outreach", "itemIcon": "phone-outgoing" }, { "slug": "11x", "category": "tool", "name": "11x", "teaser": "11x is a vertically integrated GTM platform offering autonomous AI sales agents for outbound sales: lead research, multi-channel sequencing, voice calls and appointment booking in one tool.", "domaene": "Vertrieb & Outreach", "logoFile": "11x.png", "logoEinzug": 0.78 }, { "slug": "hubspot", "category": "tool", "name": "HubSpot", "teaser": "Cloud based customer platform that bundles marketing, sales, customer service, content marketing, data management, and billing around a shared CRM database, with AI agents under the Breeze product brand.", "domaene": "Vertrieb & Outreach", "logoFile": "hubspot.png", "logoEinzug": 0.78 }, { "slug": "instantly", "category": "tool", "name": "Instantly", "teaser": "Sales platform for automated cold email outreach with built-in deliverability infrastructure, a B2B lead database, and AI sequence writing.", "domaene": "Vertrieb & Outreach", "logoFile": "instantly.svg", "logoEinzug": 1 }, { "slug": "pipedrive", "category": "tool", "name": "Pipedrive", "teaser": "Visual sales-pipeline CRM with AI-assisted deal prioritization, workflow automation, and an optional projects module for post-sale delivery.", "domaene": "Vertrieb & Outreach", "logoFile": "pipedrive.png", "logoEinzug": 1 }, { "slug": "salesforce", "category": "tool", "name": "Salesforce", "teaser": "Cloud CRM combining connected building blocks for sales, commerce, and customer service, extended with the Agentforce 360 agent layer for industry-specific AI use cases such as appointment scheduling or case management.", "domaene": "Vertrieb & Outreach", "logoFile": "salesforce.svg", "logoEinzug": 1 } ] }