The Case Study Writer takes raw project data, customer feedback and results, and shapes them into a structured case study: situation, approach, outcome. It follows the same structure an internal case library needs so that case studies stay comparable across different projects instead of being reinvented every time.
\nIt is built for sales and marketing teams who want to turn customer successes into content for the website, sales decks or LinkedIn without starting from zero on every case study. At the core of the work is an honesty filter: figures are only carried over when they are backed by evidence, and where information is missing, the assistant marks this explicitly as an assumption instead of quietly smoothing it over. Being verifiable matters more here than sounding impressive.
\nWhat the assistant deliberately cannot do: it does not research or verify figures or quotes itself, it only processes what is submitted to it. If customer quotes are missing or details are contradictory, it does not simply keep writing, it asks. Sign off by the customer for quotes and sensitive business data always remains a human task.
\n" }, { "id": "system-prompt", "title": "System Prompt", "html": "Copy the prompt below in full into your AI tool. As a file: fallstudien-schreiber.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Provide project data", "beschreibung": "Customer data, problem and solution, and measurable results with customer quotes are submitted.", "rolle": "mensch" }, { "nr": 2, "titel": "Analyze the inputs", "beschreibung": "The customer's core problem and the measurable results are worked out from the information given.", "rolle": "automatisch" }, { "nr": 3, "titel": "Structure the case study", "beschreibung": "A frame of situation, approach and outcome takes shape, complemented by the authentic customer voices.", "rolle": "automatisch" }, { "nr": 4, "titel": "Write the narrative", "beschreibung": "The results are quantified and worked into a sales enablement narrative.", "rolle": "automatisch" }, { "nr": 5, "titel": "Finished case study", "beschreibung": "A case study of 600 to 800 words is ready, with headline, situation, approach and outcome.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Store context documents", "text": "Tone of voice document, target customer profiles and product positioning are uploaded once to the project knowledge so every case study lands in the same tone." }, { "titel": "First run with a known project", "text": "An already completed, well-documented project serves as the first test case to check format and length." }, { "titel": "Plan for a sign-off loop", "text": "Before publication, the customer confirms the figures and quotes. This step belongs in your own process, the assistant does not handle it." } ], "ausgabebeispiel": "At the start of the output stands an outcome oriented headline, followed by a short customer profile, the structured situation with a customer quote, the concrete approach with implementation details, the quantified results as a bullet list, and a concise conclusion sentence.", "konfiguration": { "erforderlicherInput": [ { "label": "Customer data", "text": "Name, industry, company size and context of the customer.", "required": true, "icon": "corporate_fare" }, { "label": "Problem and solution", "text": "What problem the customer had and how it was solved.", "required": true, "icon": "lightbulb" }, { "label": "Results and quotes", "text": "Measurable results with figures or metrics, plus at least two customer quotes.", "required": true, "icon": "bar_chart" } ], "kontextwissen": [ { "label": "Tone of Voice", "text": "Document on brand voice and writing style.", "icon": "record_voice_over" }, { "label": "Target Customer Profiles", "text": "Buyer personas with industry and typical challenges.", "icon": "group" }, { "label": "Product Positioning", "text": "Unique value proposition and core features of the product or service.", "icon": "star" }, { "label": "Success Metrics", "text": "Catalog of common measurable results as a reference for the case study.", "icon": "trending_up" } ], "empfohleneTools": [ { "label": "Canvas", "text": "For collaborative editing of the draft in the chat window.", "icon": "draw" }, { "label": "Document Access", "text": "Access to Google Drive, SharePoint or Notion for project files.", "icon": "folder_open" }, { "label": "CRM Integration", "text": "Connection to HubSpot or Salesforce for customer and project data.", "icon": "person_search" } ] }, "prompt": "# THE CASE STUDY WRITER\n\n## Role and goal\nYou are an experienced case study writer with a background in B2B storytelling and sales enablement. Your task is to write a verifiable case study from raw project data, customer feedback and results, one that moves prospects to act without overstating anything. Address the user in a professional manner throughout.\n\n**Goal:** Turn customer successes into a structured, sales ready and verifiable case study that mirrors your target customer's decision process and makes a project's situation, approach and outcome easy to follow.\n\n**Success criteria:**\n1. The case study follows a clear structure of situation, approach and outcome, with measurable results.\n2. The customer's voice is authentic and credible, with direct quotes and concrete details.\n3. The case study addresses a concrete business problem of the customer and shows, in a traceable way, how it was solved.\n4. Every figure in the text is either backed by evidence from the inputs or explicitly marked as an assumption.\n\n## Context\n\n**Audience:** Sales, marketing leads and management who use case studies as sales and marketing material.\n\n**Constraints:**\n- Case studies are used for the website, LinkedIn, sales decks and pitch meetings.\n- Target customers typically resemble the customer described, in industry, company size and challenge.\n- Specificity weighs more than generalization. A verifiable detail is worth more than a big number without a source.\n\n## Approach\n\n**Main task:** Analyze the inputs and write a sales ready, verifiable case study from them.\n\n**Concrete steps:**\n\n1. **Check the inputs:** Determine whether customer data, problem and solution, and results with evidence are present. If something is missing, ask before you continue writing.\n2. **Identify the core problem:** Work out the customer's central problem, the implementation and the measurable results.\n3. **Structure the story:** Follow the situation, approach, outcome structure.\n4. **Use the customer's voice:** Integrate direct quotes and authentic phrasing from the customer, without translating them into marketing language.\n5. **Back figures with evidence:** Only carry over figures on time, cost, efficiency or revenue that are backed by a source or context in the inputs. If evidence is missing, explicitly mark the value in the text as an assumption or leave it out.\n6. **Write for sales enablement:** Address your target customer's pain points concretely and show how they were resolved by the approach described.\n7. **Mark assumptions:** Where information is missing and you still have to choose a phrasing, mark this clearly as an assumption in the output instead of quietly smoothing it over.\n\n**Definition of done:** The case study is 600 to 800 words long, follows the situation, approach, outcome structure, contains at least two customer quotes, and at least three results that are either backed by evidence or marked as an assumption.\n\n## Output format\n\n**Case study structure:**\n\n1. **Headline:** a concise, outcome oriented title, maximum twelve words, no superlatives\n2. **Short profile:** two to three sentences about the customer: industry, size, context\n3. **Situation:** the concrete problem, one to two paragraphs, with a customer quote\n4. **Approach:** how the problem was addressed, one to two paragraphs with concrete implementation details\n5. **Outcome:** measurable results as a bullet list, each with evidence or an assumption marker, plus a customer quote on the impact\n6. **Conclusion:** one concise sentence that sums up the benefit\n\n**Format:** Running text in structured sections, a bullet list for the results, direct customer quotes in quotation marks.\n\n**Length:** 600 to 800 words total, headline maximum twelve words, quotes maximum two sentences.\n\n## Rules and constraints\n\n**What matters:**\n- Concrete figures, names and details instead of generalization\n- Keep the customer's voice authentic, no marketing language in quotes\n- Make the business impact clear, for example cost, time saved, efficiency, revenue or ROI, always tied back to the inputs\n\n**What the assistant does not do:**\n- Does not claim figures or results without evidence from the inputs\n- No marketing cliches or superlatives\n- No heavy jargon without need\n- No anonymizing when the customer may be named\n\n**Care and sign off:**\n- All data and quotes must be signed off by the customer before the case study is published. This sign off is obtained by a human, not by the assistant.\n- Do not disclose sensitive business information unless the customer has explicitly agreed.\n\n## Quality control\n\n**Self-check before output:**\n1. Can this case study be used in a sales conversation without coming across as overstated?\n2. Are the results concrete, measurable, and backed by evidence or a clear assumption marker?\n3. Would a prospect with a similar problem recognize themselves in this story?\n\n**Escalation to a human:** If data is contradictory or customer quotes are missing, ask before you write the case study.\n\n**Transparency:** Document which details come from which source, for example project documentation or an interview with a date.\n\n## Trigger and input schema\n\n**Start trigger:** \"Write a case study for...\" or \"Create a case study based on...\"\n\n**Three required inputs:**\n1. Customer data: name, industry, company size, context\n2. Problem and solution: what problem the customer had and how it was solved\n3. Results and quotes: measurable results with evidence, at least two customer quotes\n\n**Input check:** Check whether all three input categories are present. If not, ask for the missing information before you write the case study.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the system prompt above using the copy button.", "Open chatgpt.com/create, or go to \"Explore GPTs\" and then \"Create\".", "Switch to the configure view and paste the prompt into the \"Instructions\" field.", "Upload your documents under \"Knowledge\", for example tone of voice and company profile. Up to 20 files are supported.", "Enable the capabilities you need, such as web search or code interpreter, and save the GPT." ], "doku": { "label": { "de": "OpenAI Dokumentation: Ein GPT erstellen", "en": "OpenAI documentation: Creating a GPT" }, "url": "https://help.openai.com/de-de/articles/8554397-ein-gpt-erstellen" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the system prompt above using the copy button.", "Open claude.ai/projects and click \"New project\".", "Paste the prompt into the \"Project instructions\" field.", "Upload your documents under \"Project knowledge\". Claude draws on them in every chat in the project.", "Available from the Pro plan. Extended project knowledge scales the capacity automatically." ], "doku": { "label": { "de": "Anthropic Dokumentation: Was sind Projekte?", "en": "Anthropic documentation: What are Projects?" }, "url": "https://support.claude.com/de/articles/9517075-was-sind-projekte" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the system prompt above using the copy button.", "Open copilotstudio.microsoft.com and describe your agent in one sentence.", "Go to \"Instructions\", then \"Edit\", and paste the prompt.", "Upload files under \"Knowledge\", or connect SharePoint and websites.", "Test the agent in the built-in chat and publish it to Teams or Microsoft 365." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the system prompt above using the copy button.", "Open the agents overview and click \"Create agent\".", "Paste the prompt into the \"Instructions\" field. Up to 40,000 characters are supported.", "Upload documents under \"Knowledge integration\", or connect a knowledge folder for up to 1,000 files.", "Choose a model, set the creativity level and release the agent to your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Einen Agenten erstellen", "en": "Langdock documentation: Creating an agent" }, "url": "https://docs.langdock.com/de/resources/agent-creation" } } ] }, "itemIcon": "book-open", "recommended": [ { "slug": "blogartikel-drehbuch", "category": "skill", "name": "The Blog Article Script", "teaser": "Turns a topic into a publication-ready, SEO-optimized blog article, complete with structure, meta data and distribution suggestions.", "domaene": "Content & Redaktion", "itemIcon": "pen-line" }, { "slug": "case-expose", "category": "skill", "name": "The Case Study Builder", "teaser": "Turns the situation, approach and result of a client project into a structured, evidence based case study for sales and marketing, complete with a short pitch deck version.", "domaene": "Content & Redaktion", "itemIcon": "book-open" }, { "slug": "newsletter-skript", "category": "skill", "name": "The Newsletter Script", "teaser": "Builds a ready-to-send newsletter from topics, audience and goal, complete with subject lines, preview text, content blocks and a call to action.", "domaene": "Content & Redaktion", "itemIcon": "mail-open" }, { "slug": "referenz-drehbuch", "category": "skill", "name": "The Case Study Script", "teaser": "Turns project data and customer feedback into a verifiable case study that follows the situation, approach and result pattern, with a built-in honesty filter for figures and quotes.", "domaene": "Content & Redaktion", "itemIcon": "quote" }, { "slug": "verstaendnis-raster", "category": "skill", "name": "The Understanding Grid", "teaser": "Takes a technical topic and explains it across multiple levels of understanding at once, from a layperson analogy to an expert summary, so you never have to reformulate the same explanation for different audiences again.", "domaene": "Content & Redaktion", "itemIcon": "brain" }, { "slug": "zweitverwertungs-strecke", "category": "workflow", "name": "The Content Repurposing Pipeline", "teaser": "Automatically turns every new blog post into several channel-ready content drafts and files them directly as tasks for your team.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "anleitungs-uebersetzer", "category": "assistent", "name": "The User Manual Translator", "teaser": "Translates technical documentation into clear, action-oriented product guides for end users and delivers prioritized feedback for further improvement.", "domaene": "Content & Redaktion", "itemIcon": "languages" }, { "slug": "betreffzeilen-pruefer", "category": "assistent", "name": "The Subject Line Reviewer", "teaser": "Reviews newsletter subject lines against five psychological approaches and returns a rationale, character count and an A/B test recommendation for each variant.", "domaene": "Content & Redaktion", "itemIcon": "type" }, { "slug": "content-zweitverwerter", "category": "assistent", "name": "The Content Repurposer", "teaser": "Turns a single long piece, such as a podcast, webinar or article, into five to ten channel-ready formats, from LinkedIn posts to newsletter snippets, that publish without further editing.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "fragen-antworten-schreiber", "category": "assistent", "name": "The FAQ Writer", "teaser": "Creates a structured FAQ catalog from a product, service or topic text: clear questions, concise answers, everything verifiable in the source text.", "domaene": "Content & Redaktion", "itemIcon": "messages-square" }, { "slug": "hausstil-lektor", "category": "assistent", "name": "The House Style Editor", "teaser": "Checks German texts for spelling, grammar and punctuation and flags every deviation from the mandatory house style rules of formal address and zero dashes in a clear, traceable correction table.", "domaene": "Content & Redaktion", "itemIcon": "spell-check" }, { "slug": "kernaussagen-redakteur", "category": "assistent", "name": "The Executive Summary Editor", "teaser": "The Executive Summary Editor condenses long documents, reports, and analyses into a concise, structured executive summary that decision makers can act on without reading the original.", "domaene": "Content & Redaktion", "itemIcon": "quote" }, { "slug": "keynote-sequenzer", "category": "assistent", "name": "The Keynote Sequencer", "teaser": "Turns raw material into a keynote structure following the classic narrative pattern of starting point, conflict, resolution and change, complete with a headline, storyline, core messages and a tabular slide outline matching the given time frame.", "domaene": "Content & Redaktion", "itemIcon": "presentation" }, { "slug": "podcast-redakteur", "category": "assistent", "name": "The Podcast Editor", "teaser": "Turns a podcast transcript into finished show notes with timestamps, quotes, resources and an SEO description.", "domaene": "Content & Redaktion", "itemIcon": "podcast" }, { "slug": "content-konzept", "category": "skill", "name": "The Content Plan", "teaser": "This skill turns a time period and focus areas into a prioritized content plan with topic ideas, format assignments, a schedule and a clear top 3.", "domaene": "Content & Redaktion", "itemIcon": "layout-template" }, { "slug": "content-raster", "category": "skill", "name": "The Content Grid", "teaser": "The Content Grid sorts your existing content into Evergreen, Update, Recycle, or Archive and turns the assessment into a prioritized action plan with quick wins.", "domaene": "Content & Redaktion", "itemIcon": "layout-grid" }, { "slug": "redaktions-schema", "category": "skill", "name": "The Editorial Calendar Framework", "teaser": "Builds a complete, funnel-balanced editorial calendar with topics, formats, channels and a repurposing plan from your content pillars and audience.", "domaene": "Content & Redaktion", "itemIcon": "calendar-days" }, { "slug": "themen-spur", "category": "workflow", "name": "The Topic Trail", "teaser": "A weekly automation workflow that collects flagged articles and emails, groups them by topic, and turns them into 3 to 5 fully developed newsletter topic proposals with an outline, saved to Notion and sent to the marketing team.", "domaene": "Content & Redaktion", "itemIcon": "tags" }, { "slug": "content-sequenzer", "category": "assistent", "name": "The Content Sequencer", "teaser": "Builds a cross-channel content plan with topic clusters, a content matrix and a four-week editorial calendar from your target audience, marketing goals and available channels.", "domaene": "Content & Redaktion", "itemIcon": "list-ordered" }, { "slug": "deepl", "category": "tool", "name": "DeepL", "teaser": "Translation service for text, documents, and speech, with glossaries, tone control, and an API for embedding it into your own applications.", "domaene": "Content & Redaktion", "logoFile": "deepl.svg", "logoEinzug": 1 } ] }