When a lead inquiry lands in the inbox, the sales team usually starts the same work over again: open the CRM, read through the history, find the right tone, draft a reply. This workflow anticipates exactly that step. It detects incoming emails tagged with the Sales Lead label, pulls contact, company, deal stage and past interactions from the CRM, and writes a reply draft with a clear next step directly into the mail thread.
\nWhat gets automated is the groundwork: research in the CRM, the first text draft, filing it as a reply in the right thread, and notifying the responsible sales owner. The human stays in the loop at the decisive point: no draft leaves the system unchecked, the owner reads it, adjusts it if needed, and only then sends it. This mainly saves time on the first pass, but it does not replace the professional judgment on whether an offer, a price or a commitment is actually allowed to stand in the reply as written.
\nThe benefit shows most clearly in teams with several sales owners, where everyone would otherwise reply differently: tone, structure and call to action become more consistent across all replies because they come from the same template instead of being written from scratch each time.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: vertriebsantwort-schiene.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Trigger: new sales inquiry", "beschreibung": "A new email tagged with the Sales Lead label starts the process.", "rolle": "mensch" }, { "nr": 2, "titel": "CRM match", "beschreibung": "Using the sender address, contact, company, deal stage and past interactions are looked up in the CRM.", "rolle": "automatisch" }, { "nr": 3, "titel": "Draft reply", "beschreibung": "A personalized reply draft with a clear call to action is created from the CRM context and the email content.", "rolle": "automatisch" }, { "nr": 4, "titel": "File the draft", "beschreibung": "The draft is saved as a reply in the same mail thread, ready to send with one click.", "rolle": "automatisch" }, { "nr": 5, "titel": "Notify the owner", "beschreibung": "The sales owner receives a message in the team chat with lead details and a link to the draft.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Draft ready", "text": "Once the CRM match is complete, the reply draft is ready directly in the mail thread." }, { "titel": "Real personalization", "text": "Every draft uses deal stage, interaction history and CRM notes instead of a generic template." }, { "titel": "CRM context visibly used", "text": "The draft refers to concrete earlier conversations instead of being written without reference to the history." }, { "titel": "Consistency across the team", "text": "Tone, structure and call to action stay the same across all sales owners because every draft comes from the same template." } ], "voraussetzungen": [ { "label": "Email tool", "text": "Gmail, Outlook or a comparable tool that receives leads and can save drafts in the thread.", "icon": "mail" }, { "label": "CRM system", "text": "HubSpot, Salesforce or Pipedrive for context and interaction history.", "icon": "contacts" }, { "label": "Team chat (optional)", "text": "Slack, Teams or Discord for notifying the sales owner.", "icon": "notifications" }, { "label": "LLM access", "text": "OpenAI, Claude or Gemini, via an API key.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test email", "text": "Send a test inquiry from a known CRM address tagged with the Sales Lead label.", "icon": "outgoing_mail" }, { "label": "CRM lookup", "text": "Check whether contact, company, deal stage and interaction history are loaded correctly.", "icon": "manage_search" }, { "label": "Draft quality", "text": "Assess the draft for concrete relevance to the inquiry, CRM context, matching tone and length, and a clear call to action.", "icon": "fact_check" }, { "label": "Edge cases", "text": "Check the behavior without a CRM entry, with multiple matches, with multilingual inquiries, and with very long emails.", "icon": "rule" } ], "goLive": [ { "label": "Approval to start", "text": "Activate the workflow only once the CRM lookup, drafting and notification run reliably.", "icon": "check_circle" }, { "label": "Pilot", "text": "Start with one or two sales owners and review the drafts before they are sent.", "icon": "visibility" }, { "label": "Refine", "text": "Adjust tone and template based on the versions that were actually sent.", "icon": "tune" }, { "label": "Expand", "text": "Add urgency scoring, language detection or multiple draft variants for comparison if needed.", "icon": "rocket_launch" } ], "haeufigeFehler": [ { "label": "CRM match runs on the name instead of the address", "text": "Switch the search field in the CRM lookup to the email address.", "icon": "alternate_email" }, { "label": "Draft is saved as a new email instead of a reply", "text": "Enable the \"Save as reply\" option in the mail tool.", "icon": "reply" }, { "label": "Draft stays too generic", "text": "Bind the CRM fields as variables and set the tone in the prompt.", "icon": "auto_awesome" }, { "label": "Duplicate drafts on repeated triggers", "text": "Check the thread ID for an already existing draft before creating a new one.", "icon": "content_copy" } ] }, "arbeitsprompts": [ { "titel": "Sales reply generator", "beschreibung": "The prompt for the AI step that generates the reply draft from the CRM context and the email content. Usable on its own, also outside the full workflow specification.", "prompt": "You act as an experienced sales representative creating professional email replies for incoming lead inquiries.\n\nCONTEXT INFORMATION FROM CRM:\n- Contact name: [CONTACT_NAME]\n- Company: [COMPANY]\n- Current deal status: [DEAL_STATUS]\n- Past interactions: [INTERACTION_HISTORY]\n- Notes/Tags: [CRM_NOTES]\n\nINCOMING EMAIL:\nFrom: [SENDER_EMAIL]\nSubject: [EMAIL_SUBJECT]\nContent: [EMAIL_CONTENT]\n\nTASK:\nCreate a professional, personalized email reply draft that\n1. addresses the specific inquiry and answers all questions,\n2. uses the CRM context, for example by mentioning earlier conversations or referring to the deal stage,\n3. uses [COMPANY_TONE],\n4. contains a clear call to action, for example a meeting suggestion or next steps,\n5. is at most [MAX_LENGTH] words long.\n\nFORMAT:\nOutput only the finished email text, from the salutation to the closing. No explanations, no meta commentary." } ], "prompt": "GOAL\nBuild a workflow that automatically loads the CRM context for incoming sales inquiries and files a personalized reply draft in the same mail thread. The responsible sales owner is then notified and reviews the draft before it is sent.\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: new incoming email in the email tool (Gmail, Outlook or comparable).\nFilter: only emails tagged with the Sales Lead label or category.\n\nSTEPS\n1. Extract email data: sender address, subject, content and thread ID.\n2. Dedup check: if a draft has already been generated for this thread ID, abort the run so no duplicate drafts are created.\n3. CRM lookup (HubSpot, Salesforce or Pipedrive): match on the email address, not the name. Load contact name, company, deal status, interaction history, notes and tags, and the responsible owner.\n4. AI step: create the reply draft, using the prompt below exactly.\n5. Save the draft: as a reply in the same mail thread, not as a new email, ready to send with one click.\n6. Output: notify the sales owner in the team chat, with lead details and a link to the draft.\n\nPROMPT (use exactly as written)\nSales reply generator:\n\"\"\"\nYou act as an experienced sales representative creating professional email replies for incoming lead inquiries.\n\nCONTEXT INFORMATION FROM CRM:\n- Contact name: [CONTACT_NAME]\n- Company: [COMPANY]\n- Current deal status: [DEAL_STATUS]\n- Past interactions: [INTERACTION_HISTORY]\n- Notes/Tags: [CRM_NOTES]\n\nINCOMING EMAIL:\nFrom: [SENDER_EMAIL]\nSubject: [EMAIL_SUBJECT]\nContent: [EMAIL_CONTENT]\n\nTASK:\nCreate a professional, personalized email reply draft that\n1. addresses the specific inquiry and answers all questions,\n2. uses the CRM context, for example by mentioning earlier conversations or referring to the deal stage,\n3. uses [COMPANY_TONE],\n4. contains a clear call to action, for example a meeting suggestion or next steps,\n5. is at most [MAX_LENGTH] words long.\n\nFORMAT:\nOutput only the finished email text, from the salutation to the closing. No explanations, no meta commentary.\n\"\"\"\n\nDATA FLOW\nStep 1 to step 3: sender address for the CRM match, thread ID for the dedup check and draft filing.\nStep 1 to step 4: sender address, subject and content of the email.\nStep 3 to step 4: contact name, company, deal status, interaction history and CRM notes.\nStep 3 to step 6: the responsible owner as the recipient of the notification.\nStep 4 to step 5: the finished draft text.\n\nERROR HANDLING\nNo CRM entry found: create the draft anyway, using only the email content, and flag this clearly in the owner notification.\nMultiple CRM matches: choose the most recent active deal and flag this choice in the notification.\nInquiry in a different language: create the draft in the language of the inquiry.\nNo owner set in the CRM: send the notification to a defined fallback channel.\n\nPLACEHOLDER CONVENTION\nAll placeholders in square brackets are variables. Map all email and CRM placeholders dynamically, as described in the data flow. Not dynamic are [COMPANY_TONE] and [MAX_LENGTH]: set these manually before activation. 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, in particular the dedup check before the draft is created?\n2. Is the prompt inserted in full and unchanged, and are all dynamic placeholders mapped?\n3. Is the draft stored as a reply in the thread, not as a new email, and does the CRM match run on the email address?\n4. Are all points listed that require manual configuration: the Sales Lead label, CRM access, the LLM API key, the team chat channel, [COMPANY_TONE] and [MAX_LENGTH]?", "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": "w22_vertriebsantwort-schiene__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Vertriebsantwort-Schiene", "beschreibung": "Lädt bei eingehenden Sales-Anfragen automatisch den CRM-Kontext, erstellt daraus einen personalisierten Antwort-Entwurf im selben Mail-Thread und benachrichtigt den zuständigen Sales-Owner zur Prüfung vor dem Versand.", "trigger": { "typ": "Integrations-Trigger: Gmail-Ereignis bei Label-Änderung", "bedingung": "Ausgelöst, sobald der eingehenden E-Mail das Label Sales-Lead hinzugefügt wird. Das Entfernen des Labels löst den Ablauf nicht aus." }, "schritte": [ { "nr": 1, "titel": "Trigger: neue Sales-Anfrage", "rolle": "mensch", "aktion": "Eine neue E-Mail mit dem Label Sales-Lead trifft im Postfach ein und startet den Ablauf. Absenderadresse, Betreff, Inhalt und Thread-ID werden aus der E-Mail extrahiert. Existiert für diese Thread-ID bereits ein Entwurf, endet der Lauf hier, damit kein doppelter Entwurf entsteht.", "prompt_ref": null, "eingang": [], "ausgang": [ "Absenderadresse, Betreff, Inhalt, Thread-ID" ] }, { "nr": 2, "titel": "CRM-Abgleich", "rolle": "automatisch", "aktion": "Über die Absenderadresse, nicht über den Namen, wird der Kontakt im CRM gesucht, geladen werden Vorname, Nachname, Telefon, Position, Unternehmen, Lifecycle-Stage und der zuständige Owner. Aus dem gefundenen Kontakt laufen zwei Abfragen parallel weiter: die vollständige Interaktionshistorie mit Zeitstempel, Typ und Details je Aktivität sowie bis zu fünf verknüpfte Deals, sortiert nach letzter Änderung, mit Name, Betrag, Status, Pipeline, Abschlussdatum und Owner. Beide Zweige laufen erst im nächsten Schritt wieder zusammen.", "prompt_ref": null, "eingang": [ "Absenderadresse" ], "ausgang": [ "Kontaktdaten: Vorname, Nachname, Unternehmen, Telefon, Position, Lifecycle-Stage, zuständiger Owner", "Interaktionshistorie mit Zeitstempel, Typ und Details", "Bis zu fünf Deals mit Status, Betrag, Pipeline, Abschlussdatum und Owner" ] }, { "nr": 3, "titel": "Entwurf erstellen", "rolle": "automatisch", "aktion": "Ein KI-Agent erzeugt aus Betreff und Inhalt der eingehenden E-Mail, den Kontaktdaten, der Interaktionshistorie und den Deal-Informationen ein strukturiertes Ergebnis mit drei Feldern: dem vollständigen Entwurfstext im HTML-Format, einer kurzen Zusammenfassung der Anfrage und einer Prioritätseinstufung. Erzeugt wird exakt mit dem hinterlegten Prompt.", "prompt_ref": "arbeitsprompt-1", "eingang": [ "Betreff und Inhalt der E-Mail", "Kontaktdaten aus dem CRM-Abgleich", "Interaktionshistorie", "Deal-Informationen" ], "ausgang": [ "Entwurfstext im HTML-Format", "Zusammenfassung der Anfrage", "Prioritätseinstufung" ] }, { "nr": 4, "titel": "Entwurf ablegen", "rolle": "automatisch", "aktion": "Der Entwurfstext wird als Antwort im selben Mail-Thread gespeichert, nicht als neue E-Mail, versandfertig mit einem Klick. Die Thread-Kennung stammt aus dem Trigger, das Empfängerfeld bleibt leer, damit die Antwort automatisch an den ursprünglichen Absender geht.", "prompt_ref": null, "eingang": [ "Entwurfstext im HTML-Format", "Thread-ID" ], "ausgang": [ "Gespeicherter Entwurf im Thread" ] }, { "nr": 5, "titel": "Zuständigen benachrichtigen", "rolle": "ergebnis", "aktion": "Parallel zur Entwurfsablage, nicht danach, wird ein fester Team-Chat-Kanal benachrichtigt. Die Nachricht enthält die Absenderinformation aus der eingehenden E-Mail sowie Zusammenfassung und Prioritätseinstufung aus dem KI-Agenten, dazu den Hinweis, dass der Entwurf im Mail-Thread zur Prüfung bereitsteht. Der im CRM hinterlegte Owner wird geladen, aber im Referenz-Aufbau nicht für eine persönliche Adressierung genutzt, die Benachrichtigung geht an einen konfigurierten Kanal.", "prompt_ref": null, "eingang": [ "Absenderadresse aus der eingehenden E-Mail", "Zusammenfassung der Anfrage", "Prioritätseinstufung" ], "ausgang": [ "Benachrichtigung im Team-Chat" ] } ], "prompts": { "arbeitsprompt-1": { "titel": "Sales-Antwort-Generator", "text": "Sie erstellen als erfahrener Sales-Mitarbeiter professionelle E-Mail-Antworten für eingehende Lead-Anfragen.\n\nKONTEXTINFORMATIONEN AUS CRM:\n- Kontaktname: [KONTAKT_NAME]\n- Unternehmen: [UNTERNEHMEN]\n- Aktueller Deal-Status: [DEAL_STATUS]\n- Bisherige Interaktionen: [INTERAKTIONS_HISTORY]\n- Notizen/Tags: [CRM_NOTIZEN]\n\nEINGEHENDE E-MAIL:\nVon: [ABSENDER_EMAIL]\nBetreff: [EMAIL_BETREFF]\nInhalt: [EMAIL_INHALT]\n\nAUFGABE:\nErstellen Sie einen professionellen, personalisierten E-Mail-Antwort-Entwurf, der\n1. auf die konkrete Anfrage eingeht und alle Fragen beantwortet,\n2. den CRM-Kontext nutzt, etwa frühere Gespräche erwähnt oder auf die Deal-Phase eingeht,\n3. [UNTERNEHMENS_TONALITAET] verwendet,\n4. einen klaren Call-to-Action enthält, zum Beispiel einen Meeting-Vorschlag oder nächste Schritte,\n5. maximal [MAX_LAENGE] Wörter lang ist.\n\nFORMAT:\nGeben Sie ausschließlich den fertigen E-Mail-Text aus, von der Anrede bis zur Grußformel. Keine Erklärungen, keine Meta-Kommentare." } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Absenderadresse, für die CRM-Suche über die E-Mail-Adresse" }, { "von": 1, "nach": 3, "nutzlast": "Betreff und Inhalt der E-Mail" }, { "von": 1, "nach": 4, "nutzlast": "Thread-ID, für die Ablage im richtigen Mail-Thread" }, { "von": 1, "nach": 5, "nutzlast": "Absenderadresse, für die Nachricht im Team-Chat" }, { "von": 2, "nach": 3, "nutzlast": "Kontaktdaten, Interaktionshistorie und bis zu fünf Deals, aus zwei parallelen Abfragen nach dem Kontakt-Fund" }, { "von": 3, "nach": 4, "nutzlast": "Entwurfstext im HTML-Format" }, { "von": 3, "nach": 5, "nutzlast": "Zusammenfassung und Prioritätseinstufung, läuft parallel zur Entwurfsablage, nicht erst danach" } ], "voraussetzungen": [ "E-Mail-Tool mit Schreibrechten, das Leads empfängt und Entwürfe im Thread speichern kann (Gmail, Outlook oder vergleichbar)", "CRM-System für Kontext und Interaktionshistorie, zum Beispiel HubSpot, Salesforce oder Pipedrive", "Team-Chat für die Owner-Benachrichtigung, optional, zum Beispiel Slack, Teams oder Discord", "LLM-Zugang per API-Key, zum Beispiel OpenAI, Claude oder Gemini", "Empfänger oder Kanal für die Owner-Benachrichtigung im Vertrieb" ], "fehlerbehandlung": [ { "fall": "Kein CRM-Eintrag zur Absenderadresse gefunden", "massnahme": "Entwurf ausschließlich aus dem E-Mail-Inhalt erstellen und dies in der Benachrichtigung deutlich kennzeichnen." }, { "fall": "Mehrere CRM-Treffer zur Absenderadresse", "massnahme": "Den jüngsten aktiven Deal wählen und diese Auswahl in der Benachrichtigung kennzeichnen." }, { "fall": "Fremdsprachige Anfrage", "massnahme": "Entwurf in der Sprache der Anfrage erstellen." }, { "fall": "Kein Owner im CRM hinterlegt", "massnahme": "Benachrichtigung an einen festgelegten Ausweichkanal senden." }, { "fall": "Mehrfacher Trigger auf dieselbe Anfrage", "massnahme": "Dedup-Check auf die Thread-ID vor der Entwurfserstellung, kein zweiter Entwurf bei bereits vorhandenem Entwurf." }, { "fall": "CRM-Abgleich läuft fälschlich über den Namen", "massnahme": "Suchfeld im CRM-Lookup auf die E-Mail-Adresse umstellen." }, { "fall": "Fehler in einem einzelnen Automatisierungsschritt, etwa weil CRM- oder Mail-API nicht erreichbar ist", "massnahme": "Im Referenz-Aufbau ist für jeden Schritt die Fehlerstrategie Abbruch hinterlegt, der gesamte Lauf stoppt ohne automatischen Wiederholungsversuch. Für den Produktivbetrieb empfiehlt sich eine eigene Retry- oder Fallback-Logik, besonders für die CRM-Abfragen und die Team-Chat-Benachrichtigung." } ], "platzhalter": [ { "name": "KONTAKT_NAME", "quelle": "CRM-Kontaktsuche über die E-Mail-Adresse, Felder Vorname und Nachname" }, { "name": "UNTERNEHMEN", "quelle": "CRM-Kontaktfeld Unternehmen" }, { "name": "DEAL_STATUS", "quelle": "CRM-Feld Deal-Status aus den bis zu fünf zuletzt geänderten Deals des Kontakts" }, { "name": "INTERAKTIONS_HISTORY", "quelle": "Engagement-Abfrage zur Kontakt-ID, vollständige Liste mit Zeitstempel, Typ und Details je Aktivität" }, { "name": "CRM_NOTIZEN", "quelle": "CRM-Felder Position und Lifecycle-Stage sowie hinterlegte Notizen und Tags zum Kontakt" }, { "name": "ABSENDER_EMAIL", "quelle": "Absenderadresse aus den Trigger-Daten der eingehenden E-Mail" }, { "name": "EMAIL_BETREFF", "quelle": "Betrefffeld aus den Trigger-Daten der eingehenden E-Mail" }, { "name": "EMAIL_INHALT", "quelle": "Inhaltsfeld aus den Trigger-Daten der eingehenden E-Mail" }, { "name": "UNTERNEHMENS_TONALITAET", "quelle": "Kein Feld aus dem CRM oder der E-Mail, vor der Aktivierung manuell festzulegen" }, { "name": "MAX_LAENGE", "quelle": "Kein Feld aus dem CRM oder der E-Mail, vor der Aktivierung manuell festzulegen" }, { "name": "CHANNEL_ID", "quelle": "Kanal-Feld im Benachrichtigungsschritt, im Referenz-Aufbau fest auf einen Sales-Kanal gesetzt und vor der Aktivierung auf den echten Kanalnamen anzupassen" }, { "name": "THREAD_ID", "quelle": "Thread-Kennung im Ablage-Schritt, aus den Trigger-Daten der eingehenden E-Mail extrahiert" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "send", "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": "artisan", "category": "tool", "name": "Artisan", "teaser": "Artisan is an AI outbound sales tool centered on Ava, an autonomous agent that researches leads, personalizes email sequences and manages follow-ups for B2B SaaS teams.", "domaene": "Vertrieb & Outreach", "logoFile": "artisan.png", "logoEinzug": 0.78 }, { "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": "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": "termin-briefing-staffel", "category": "workflow", "name": "The Meeting Briefing Relay", "teaser": "A workflow that automatically prepares a structured briefing before every customer meeting by combining calendar details, CRM history and fresh web research.", "domaene": "Vertrieb & Outreach", "itemIcon": "calendar-clock" }, { "slug": "angebots-skript", "category": "skill", "name": "The Quote Builder", "teaser": "The Quote Builder turns conversation notes into a structured, ready-to-send quote with a personal cover letter, matching service packages, a transparent price table, and clear next steps.", "domaene": "Vertrieb & Outreach", "itemIcon": "file-badge" }, { "slug": "einwand-drehbuch", "category": "skill", "name": "The Objection Playbook", "teaser": "Classifies a customer objection psychologically and delivers three ready-to-use response strategies with concrete phrasing instead of a generic stock answer.", "domaene": "Vertrieb & Outreach", "itemIcon": "shield-question" }, { "slug": "kaltakquise-drehbuch", "category": "skill", "name": "The Cold Outreach Playbook", "teaser": "Builds a multi-stage, cross-channel cold outreach sequence across email, LinkedIn and optionally phone from a few prospect details, with a timing plan, talking points and GDPR-compliant messages including opt-out.", "domaene": "Vertrieb & Outreach", "itemIcon": "phone-outgoing" }, { "slug": "nachfass-konzept", "category": "skill", "name": "The Follow-up Sequence", "teaser": "Plans and drafts a multi-step follow-up sequence after a business contact, with a rotating focus per email, an opt-out notice, and a GDPR reference in every template.", "domaene": "Vertrieb & Outreach", "itemIcon": "mail-check" }, { "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": "vertrags-dossier", "category": "skill", "name": "The Contract Dossier", "teaser": "Turns internal pricing models and contract terms into a customer-friendly overview document with a package comparison, transparent pricing, and answers to the most common questions.", "domaene": "Vertrieb & Outreach", "itemIcon": "file-signature" }, { "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": "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": "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 } ] }