# DropD., Für Geschäftsführer, die KI richtig nutzen wollen.

Source: https://dropdigital.de/en
Language: en
Site: DropD., https://dropdigital.de

Sections on this page:

- #kap-versprechen, Versprechen: Der Einstieg: das Betriebssystem, das nirgends aufgeschrieben steht.
- #these, These: Was wir bauen: Systeme, die manuelle Arbeit abnehmen, unter Ihrer Kontrolle.
- #vorgehen, Vorgehen: So entsteht Ihr System: aufnehmen, umsetzen, optimieren.
- #problem, Was möglich ist: Agenten, Workflows, Automatisierung, Telefon, Wissen und Schulung, die in einem Betrieb stehen können.
- #kap-versuche, Hebel: Was manuell läuft, lässt sich erleichtern, automatisieren und skalieren.
- #system, Der aufgeschriebene Betrieb: Wie aus einem Ablauf im Kopf ein System wird, das Software beschleunigen kann.
- #process, Ablauf der Zusammenarbeit: Die Etappen von der Analyse bis zum Betrieb.
- #scale-offer, Leistungen und Pakete: Was wir anbieten, von der Klarheit bis zur vollständigen Umsetzung.
- #datenhoheit, Datenhoheit und Einwände: Die Daten bleiben im Haus, wenn Sie das wollen. Server in Deutschland oder On-Premise.
- #entscheidungsmatrix, Entscheidungsmatrix: Wo KI im Betrieb sinnvoll ist und wo ausdrücklich nicht.
- #cases, Referenzprojekte: Wer wir sind, und fünf anonymisierte eigene Projekte: Branche, Größe, Ergebnis.
- #werte, Woran Sie uns messen: Vier Zusagen vor dem Preis: Kontinuität, Abnahme, Übergabe, kein Katalog.
- #founder, Wer das gebaut hat: Lucas Koch und Can Tillmann, Herkunft des Ansatzes aus dem Echtbetrieb.
- #team, Operating Agent Officers: Lena und die Officers, die dropd. führen. Zwei Menschen bleiben verantwortlich.
- #ressourcen, Wissen: KI-News, DSGVO und Praxis: die letzten Artikel vor den Fragen.
- #kap-schritt, Der erste Schritt: Fünf Einwände: Zeit, Versuch, ChatGPT, Mitarbeiter, Daten.
- #faq, Häufige Fragen: Die kurze Fragenliste der Startseite.

## The promise

What runs by hand, the AI takes on for around 80 percent. The remaining 20 percent stay with people: check, sign off, decide. The firm scales with the system, not with extra headcount.

Advice alone will not move your company forward. We build your scalable system. What runs by hand, the AI takes on for around 80 percent. The remaining 20 percent stay with people: check, sign off, decide. The firm scales with the system, not with extra headcount. Request an on-site appointment Book a strategy call Reports end up in a drawer. What is not built as a process does not change the day-to-day. Software only automates what is written down. That is why most tools fail at the step before the software. The costliest place: between two heads. Every handoff runs by calling across, email, and phone.

Link: https://dropdigital.de/en#kap-versprechen
Id: home-versprechen

## What we build

We build tailored systems that take the manual work off your people and automate the processes. Secure, and under your control. Across more than fifty scenarios. We think with you instead of working a list: early results first, measurable progress within weeks.

We build tailored systems that take the manual work off your people and automate the processes. Secure, and under your control . Across more than fifty scenarios. We think with you instead of working a list: early results first, measurable progress within weeks.

Link: https://dropdigital.de/en#these
Id: home-these

## How your system is built

How a process becomes a system that can grow. Map, build, tighten. Not a tutorial, the work in your firm.

This is how your system is built. How a process becomes a system that can grow. Map, build, tighten. Not a tutorial, the work in your firm. Map, build, tighten. Process 01 Map Not the tool. The process. What lives in heads, mail and slips comes onto the table, in an order someone in the firm already recognises. Where time is lost, and which AI makes sense there. A report and an order of work, in two to three weeks. No slide deck. The process your people already know. 02 Build The first process, until someone in the firm uses it. In your stack, documented, no lock-in. One area first, where the bottleneck costs the most. Your people stay the ones who can do it. The routine goes. Not a one-shot that withers after handover. 03 Tighten Measure, sharpen, next area. What runs, stays. What snags, gets tighter. The same people, less shouting across the room. The next process sits on the one that already holds. We stay until it holds in the day-to-day. Quote Follow-up Sign-off File Bring-forward The manual work sits in the middle. Day-to-day and sign-off stay with people. Day-to-day What your people see and do face AI layer reads, sorts, proposes machine Flow the rail that runs after machine Store stays with you, not in the model machine Sign-off a person says when it leaves gate Measure Sharpen Next

Link: https://dropdigital.de/en#vorgehen
Id: home-vorgehen

## What can run

Agents, workflows, automation, phone, knowledge and on-site training that can stand in a company.

What can actually run in a company like yours. No industry drawers. The things that can stand in a firm: agents, workflows, automation, phone, knowledge, training on site. Scroll through the areas, or pick one. What can run in a company Previous area Next area AI agents Roles that work in your house and hand off to a person. Chat Phone Bookkeeping Workflows Runs that know the order. A person decides at the points that count. Quotes Follow-up Approvals Automation What is retyped today runs without a hand. Classic automation where AI would only get in the way. Receipts Invoices CRM Phone AI The phone picks up. After 5pm too. A handoff when it gets serious. Pickup Appointments Follow-up Knowledge in the house What only lives in heads becomes queryable. Before it leaves with retirement. Runs Rules Onboarding AI workshop Training on site, in your rooms or in Ratingen. Not a remote course, no exam. Foundations Specialist modules Workshop day Get found In Google, and in the answers models give. Visibility is a run, not a one-off text. Google ChatGPT Answers

Link: https://dropdigital.de/en#problem
Id: home-problem

## What one absence costs

What happens when the one person who knows the process is away.

If one person is out, a piece of the company is out. Experience lives nowhere except in people. And people get sick, retire, quit. Nothing explodes. Everything just gets slower. Quotes take longer. Enquiries sit. At quarter-end, two quotes are missing that nobody noticed. New people need months instead of weeks. Because nobody writes down what everyone takes for granted. Onboarding happens on the side, with your best people. And the question nobody asks out loud. What is your company worth if the knowledge leaves with the people? Anyone who wants to hand over or sell will be asked exactly that. Almost everyone has this. The difference is who takes it on. Getting sick is the catastrophe. Since 1998 knows every customer For 20 years does the billing The master tradesman knows which supplier delivers The site foreman knows why it was decided that way Costing hangs on one person

Link: https://dropdigital.de/en
Id: home-ausfall

## Ease, automate, scale

Almost every process in the firm can be eased, automated and scaled. Not with a chat seat for everyone. Not with another licence. With the process itself.

What runs by hand does not have to stay by hand. Almost every process in the firm can be eased, automated and scaled. Not with a chat seat for everyone. Not with another licence. With the process itself. Almost every process in the firm can be eased, automated and scaled. Not with a chat seat for everyone. Not with another licence. With the process itself. Ease, automate, scale. Request Check Sign-off Do File 01 Ease Less searching, less shouting across the room. The process is there before anyone has to ask. The place where time is lost today becomes visible. Your people stay the ones who can do it. The friction goes. No new tool first. The process they already know. 02 Automate What repeats, runs. What has to be decided stays with you. The routine moves out of heads and into the process. One area first, where the bottleneck costs the most. Not a chat that answers everyone something different. 03 Scale The same process, more throughput, no extra headcount. What holds becomes the next area. Growth does not hang on one more seat. We stay until it holds in the day-to-day. Your company has an operating system. Almost none of it is written down. 10 100 written down, software can speed this up in heads, no software reaches there Who decides what, how each exception is handled, why it runs this way and not another. Schematic illustration, not a measured figure.

Link: https://dropdigital.de/en#kap-versuche
Id: home-versuche

## The written-down operation

How a process in someone's head becomes a system software can speed up.

Knowledge first. Then the tools. We make your company writable before we automate it. In that order, never the reverse. 01 We collect what nobody has written down. Conversations with the people who know. Old quotes, minutes, exceptions. At the end stands what until now was only thought. 02 We anchor it with you, not with the vendor. The knowledge sits in a store that your team can search and maintain. If a document is wrong, it is corrected, and from then on the system answers differently. It stays with you. Who can take it over is written down with it. 03 Now you ask, instead of searching. "How did we solve this at the Nordstraße property?" gets an answer with a source. Your best people become specialists again instead of a reference library. And if the answer is not there, it says so. 04 Then what today runs by calling across starts running. Requesting documents, chasing, reminding. Requesting documents from the client, chasing, reminding. Taking defect reports, assigning them, chasing the tradesperson. Reconciling orders between shop, marketplace and warehouse. Capturing time sheets, finding variations before they expire. Pre-checking invoices against the quote. Pre-sorting the post. Every run produces the same result, and a person makes the binding decision. Anonymised from a live operation. How did we solve the heating failure at the Nordstraße property in 2024? Emergency call-out Kessler, approval up to €800 by Ms Albers, invoice checked against quote. Repeat failure in January, cause expansion vessel. Source: case 2024-0871, minutes of 14 Nov 2024 Which documents are still missing for Berger's 2024 tax return? Q3 bank statements, mileage log, donation receipts. Requested 4 Jul, reminded 18 Jul, bank statements received 21 Jul. Two items still open. Source: case ESt-2024-Berger, client file Which variations on the Weststraße site have been delivered but not claimed? Three: extra excavation 14 Mar, additional shaft 22 Mar, winter construction measure 2 Apr. Per time sheets, total €11,400. Claim deadline expires 30 Apr. Source: time sheets weeks 11 to 14, Weststraße site diary What discount applies from 20 pallets? 8 percent from 20 pallets, 12 from 50. Approval by sales leadership from 12. Source: 2026 price list, section 4.2 Four stages, each with a result. Better something that runs in four weeks than something perfectly planned in a year. Exception: data protection, co-determination and access rights come first. 01 The on-site appointment One day at your site, on your real material. At the end there is a number with the calculation. The number, with the calculation, usable even without us 02 What we build, what we do not, what it costs. Where AI helps, where only a process is missing, and what both cost. Decision paper with sequence 03 Delivery in stages A visible piece every week. Done means: it runs without us. Weekly result 04 Handover. Then operations, if you want. Trained, documented, access with you. If you want, we stay on and report every month what it has taken off. Documentation and access What a knowledge store cannot do. AI is an eager apprentice. He assists, he replaces nobody, and you do not leave him alone. The four limits, written out He does not fix permissions. He makes findable what is accessible. Approvals that sat without consequence for ten years become visible on day one. Access rights are therefore phase zero. Without them we do not start. He does not separate current from outdated on his own. Every store gets an owner, every answer names the status of its source. Contradictions he shows both. He is not a source for personnel matters. We do not index personal mailboxes. Only functional mailboxes, each approved individually. And "I don't know" is an allowed answer. A system that always answers is unusable. 45 minutes, then you know where we start The one superpower of language models Turning unstructured into structured. Everything else is automation. Unstructured Emails, PDFs, notes, voice memos AI layer Structured Tables, JSON, database From here, classic automation takes over Rail vs. driver The line is not smart versus dumb, but structured versus unstructured. Automation (the rail) The path is known in advance. Same input, same output. Extremely reliable, but only goes where you laid tracks. AI (the driver) The path cannot be written down in advance. Gets to the destination even via detours, but takes a wrong turn occasionally. Needs control. Good systems are both: rail for ninety percent of the way, driver for the junction in the middle. AI step A realistic process Invoice arrives by email Extract attachment and file it Read line items and amounts from PDF Enter data in accounting Message to the team Document arrives by email File attachment in client record Read line items and amounts from PDF Suggest booking entry Approval by the clerk Defect report by email Create and assign case Evaluate photos and description Commission tradesperson Report to owner Time sheet from site manager Capture photo and position Read variation from handwritten note Notify client Approval by site management Order from the shop Reconcile with marketplace and warehouse Check delivery discrepancy Adjust stock Trigger shipment We open the black box. No magic wand, but clearly defined layers. Scroll to pull them apart. Daily operations Your team's interface AI layer Language model, knowledge base, tools Middleware Automation and routing Data source DMS, accounting, archives Human-in-the-loop Control and approval

Link: https://dropdigital.de/en#system
Id: home-mechanismus

## Data sovereignty and objections

Where the data sits, and that it does not leave the house if that is what you want.

The two objections we always hear If you want, not one byte leaves your house. Two variants, you decide: dedicated server in Germany or on your premises. No US cloud. No model that trains on your data. The server stands where you want it. No uneasy feeling when the data protection officer asks. Dedicated server in Germany or on-premise. In the self-hosted setup, no third-country transfer. AVV and TOM in writing before anything goes live. On request without internet access, updates via a path you approve. A model that serves only you. Fitted to your terms and your tone. Open-weight model on your infrastructure, connected to your own knowledge store. Fine-tuned are tone and format, not the domain knowledge. A switch to a newer base model is planned in. Your knowledge stays your knowledge. Nothing goes into training. Not even during the build. Login via your directory, groups unchanged. Filtering happens before retrieval: what someone may not see in the file system does not enter their context. Logging happens in your system, not ours. Technical datasheet Architecture diagram, list of outbound connections, sizing in three tiers with hardware and power draw, update and rollback path, backup with recovery times, failure behaviour per process, component list with licences, exit package. For every use case you receive an AI Act dossier: purpose, data types, model, degree of autonomy, intervention points, logging, retention. Your legal counsel then makes the classification. At no extra charge. We automate tasks, not people. The first thought in the team is the fear of being replaced. If that question is not answered honestly, nobody uses what we build. Workshops on site. On the departments' real tasks, not handbook examples. Training that starts with capability. No prompt course. What the tools can do, where they get it wrong, how you recognise it. One contact per department. So the first follow-up does not land with your IT. Side effect: the EU AI Act requires AI competence in the team (Art. 4). Our training supplies the evidence, with participant list, contents and date. Whether that is sufficient is for your legal counsel to judge. A system that logs questions and timestamps is subject to co-determination. We supply the technical description for the works agreement: processed data, access, logging, deletion periods, intervention points. We sit in the meeting, before the first conversation. I want to talk this through with my IT

Link: https://dropdigital.de/en#datenhoheit
Id: home-datenhoheit

## Decision matrix

Where AI pays off, where it does not, and where clean processes come first.

Not every department needs AI. Some areas need AI. Some only need clear rules and a cleaner process. Whoever does not make that distinction burns your money. Area Makes sense Does not make sense Tax firm Incoming documents Requesting, chasing, reminding, spotting duplicates Approving the booking itself Deadlines (VAT, recapitulative statement, payroll) Monitoring, reminding, requesting documents The tax return. Invented paragraphs are not a risk you take Client letters Draft in the firm's tone from the case Legal advice. Never without a qualified professional New client Document checklist, chasing Whether the mandate fits. That is your decision Trades and construction Costing Quote draft from your own past line items The price decision itself Site management Minutes and photo documentation from dictation Scheduling on the construction site Billing and variations Finding delivered, unclaimed variations Approval without a second person Procurement and yard Checking invoices against quote Supplier choice. Here a rule helps, not AI Property management and real estate Invoice checking Pre-check against quote and contract Payment approval Tenant communication Pre-sorting, preparing standard cases Answering complaints and termination notices Deadlines and inspection duties Monitoring and reminding in time Documenting the inspection itself Accounting Pre-capturing documents Year-end close. What is usually missing is a process, not AI Trade and e-commerce Order and stock data Reconciling between shop, marketplace and warehouse The price decision Customer enquiries Pre-sorting, preparing standard cases Deciding complaints and returns Product copy Drafts from your data Publishing without approval. Copy that sounds like AI costs trust Documents Assigning, checking against the order Year-end close. What is usually missing is a process, not AI We do not yet have a table of our own for your industry. This is the best-documented one, and the pattern is the same. You can also walk through this yourself: eight questions, result immediately, no appointment. Start the company check

Link: https://dropdigital.de/en#entscheidungsmatrix
Id: home-matrix

## Who we are, and what we built

Lucas and Can, then five anonymised own projects: industry, what was built, what came of it.

Not from theory We built it first, then offered it. No whiteboard. A Mittelstand firm, five departments, dozens of automations we ran ourselves. What breaks, we know from the day-to-day, not from a seminar. Only once it held did it become the offer. Industry Size What was built What came of it Service Time Who worked on it Volume Time back Live after Start with the on-site appointment Case film In progress Case film, still in progress Who we are Lucas Koch and Can Tillmann Founders and managing directors. Two operators. More than ten years in operations, building companies, and AI. Lucas put AI into a running Mittelstand firm, across marketing, sales, logistics and purchasing. Can scaled his own brands from a standing start and laid funnels so they are not rebuilt every month. We know the processes firms get stuck on because we ran them ourselves. Mapped, time taken out of the day-to-day, what holds built on. Not a demo pilot. Years of live operations, dozens of automations, a system that can grow.

Link: https://dropdigital.de/en#cases
Id: home-beweis

## How you measure us

Four things that apply before anyone names a price. No slide deck. The yardstick for the meeting.

How you measure us. Four things that apply before anyone names a price. No slide deck. The yardstick for the meeting. 01 The same result on every run. Not one good pass. The next one and the one after that have to do the same. If ChatGPT gets you the same result in a morning, you do not need us. 02 Done is defined before anyone builds. Acceptance is on paper before the first line. No almost-there, no slide deck. You check yourself whether what was agreed was delivered. 03 Your team runs it without us. After three months the process is yours. If we keep operating it, that is your choice, not our condition. If after handover you can only reach your system through us, you bought the wrong thing. 04 Nothing we do not use ourselves. No licence we earn a cut on. No catalogue tool that does not run here. We sell the process we run ourselves, not the one that pays a commission.

Link: https://dropdigital.de/en#werte
Id: home-werte

## Operating Agent Officers

Lena and the officers that run dropd. Two humans remain liable.

OAO · Operating Agent Officers The team that never clocks off. Eight AI agents run dropd. The portraits are personas, not staff. Lena talks to you. The others take the work that would otherwise sit. Two people remain liable. Talk to Lena 24/7 Live Internal All Operating Agent Officers Lucas Koch Founder Can Tillmann Technology and AI architecture Lena CXO Chief eXternal Officer Writes in this chat. Books a slot when you want one. Answers what the page actually says. Does not invent prices. Around the clock. No pause, no holiday. Mira COO Chief Operating Officer Lena's counterpart, inside the house. Keeps what was decided: handoffs, briefings, the current state. So the knowledge does not live in one head. Runs 24/7, including when nobody is in the office. Nora CCO Chief Controlling Officer Reads DATEV and the ERP before anyone has to ask. Marks the deviation. Not the essay about it. One page on the table. No dashboard nobody opens. Does not approve. The number waits for a human. Vera CLO Chief Legal Officer Reads contracts before anything goes live. DPA, TOMs, AI Act dossier. Prepares, does not sign. Knows the line between engineering and legal counsel. No clocking off, because deadlines do not either. Jule CKO Chief Knowledge Officer Writes the knowledge section and the AI radar. Researches sources, rulings, numbers. Every line with a citation. Publishes nothing without Lucas signing off. Runs 24/7 so the picture is never older than the week. Kai CISO Chief Information Security Officer Access, logs, what may leave. Checks before anyone connects. Does not sleep. Attacks do not either. Reports. Does not reach into your operation on its own. Ada CFE Chief Frontend Engineer Writes the frontend. Components, states, what someone actually touches. Ships surfaces, does not speculate about your business. On the code 24/7, without sprint theatre. Hands off to a human when taste has to be decided. Beck CBE Chief Backend Engineer Writes the backend. APIs, data, the server in Germany. Holds up what Ada shows. No service that falls over at night because nobody is there. Changes nothing in your system until a human releases it.

Link: https://dropdigital.de/en#team
Id: home-team

## What we write down before anyone asks

AI news, GDPR, practice. The radar and the guides, without going through the hub page first.

Knowledge What we write down before anyone asks. AI news, GDPR, practice. The radar and the guides, without going through the hub page first. Everything under Knowledge

Link: https://dropdigital.de/en#ressourcen
Id: home-wissen

## The first step

Five objections: time, a failed first attempt, ChatGPT, replacing people, and the cloud.

Around 45 minutes, an honest assessment. Three things: We listen to how your company actually runs. We say where there is potential and where there is not. And we name a frame for the next step. If AI currently brings you nothing, we will tell you. Not a sales trick, but arithmetic: a project that delivers nothing costs us the reference. What we are often told. I don't have time. What comes after that costs your people time, and we quantify it beforehand: which person, which week, how many hours. We've already tried this once. Then you know what to ask this time: for the acceptance criterion, before you ask for the price. We write down before the build how you will recognise that it is done. I'll do this myself with ChatGPT. If your morning with ChatGPT produces the same result, our calculation has not added up. We build what still holds on the second run, and on the third as well. Then you'll replace our people. That is exactly what we do not do. We automate tasks, not people: the same people, less chasing, more time for the work only they can do. My data is not going into the cloud. Then it does not. A dedicated server in Germany or at your site, you decide. No US cloud. No model trained on your data. Who we do not work for. Under about 20 employees. If management does not take part themselves. And if the goal is to cut positions: then we are the wrong people. Request an on-site appointment Or pick a time directly /lucas-training.jpg

Link: https://dropdigital.de/en#kap-schritt
Id: home-erster-schritt

## How we work

Four steps from discovery to running operation.

01 Audit Where time is lost, which AI makes sense, which does not. A report and an order of work, in two to three weeks. 02 Implementation The first process, until someone in the firm uses it. In your stack, documented, no lock-in. 03 Optimisation Measure, tighten, next area. Not a one-shot project.

Link: https://dropdigital.de/en#process
Id: section-prozess

## What is going wrong out there

Most AI consultants can do one thing: one can do n8n, another Copilot, a third runs prompt courses. Nobody looks at the company as a whole.

Most AI consultants can do one thing: one can do n8n, another Copilot, a third runs prompt courses. Nobody looks at the company as a whole. What happens Companies buy Copilot or ChatGPT licenses for everyone. After two weeks nobody uses them anymore, or five-figure sums go into software that solves a problem nobody had. What is missing Someone who understands that some departments have to develop with AI and some simply use it. Sales needs different tools than purchasing, marketing different workflows than management. Some departments do not need AI at all. They need clear rules and clean processes. Anyone who does not understand that burns your money.

Link: https://dropdigital.de/en#problem
Id: fact-problem-lage

## What sets DropD. apart from other AI consultants?

What sets DropD. apart from other AI consultants?

What sets DropD. apart from other AI consultants? Three points. First, vendor-neutral: no commission agenda. Second, practice instead of theory: dozens of AI applications in live operation at a mid-market company, across five departments. Third, department logic: we understand that sales needs different tools than purchasing, and the office needs different workflows than the job site. Some departments do not need AI at all. They need clean processes.

Link: https://dropdigital.de/en#faq
Id: faq-home-1

## How long does an AI implementation take in a mid-market company?

How long does an AI implementation take in a mid-market company?

How long does an AI implementation take in a mid-market company? The operations check delivers a report with prioritized starting points after two to three weeks. Ready-made workflows are usable from the moment they are provided. A full implementation across several areas runs in stages over three to six months, with a visible result each week. Where personnel data or your ERP are involved, the review of access rights and co-determination comes first, and that takes longer.

Link: https://dropdigital.de/en#faq
Id: faq-home-2

## Do I need technical prior knowledge?

Do I need technical prior knowledge?

Do I need technical prior knowledge? No. Everything is built for users, not for developers. And your people are trained before anything goes live.

Link: https://dropdigital.de/en#faq
Id: faq-home-3

## What do I actually get, and does it belong to me? Does it keep running if DropD. is no longer there?

What do I actually get, and does it belong to me? Does it keep running if DropD. is no longer there?

What do I actually get, and does it belong to me? Does it keep running if DropD. is no longer there? You do not get a black box. You get a documented setup: workflows, agents and, where we develop ourselves, the adapted system plus handover. Where we build on your infrastructure or a dedicated server in Germany, what runs there belongs to you, including data and configuration. No lock-in: we document so your IT or another provider can take over. What you get in hand (license, workflow files, your own server) depends on the package and is set in writing before we start.

Link: https://dropdigital.de/en#faq
Id: faq-home-4

## Where is DropD. based, and do you work across Germany?

Where is DropD. based, and do you work across Germany?

Where is DropD. based, and do you work across Germany? DropD. is based in Ratingen in Kreis Mettmann, in the Düsseldorf region. We work remotely across Germany for mid-market companies in the DACH region, and we come on site for workshops in Düsseldorf, Essen, Cologne, the Ruhr area, and to you nationwide.

Link: https://dropdigital.de/en#faq
Id: faq-home-5

## Do you build your own AI, or do you only sell third-party tools?

Do you build your own AI, or do you only sell third-party tools?

Do you build your own AI, or do you only sell third-party tools? Both, depending on which path is cheaper to the goal. Where a standard tool is enough, we save you the custom build. Where data protection, specialist knowledge or independence matter, we develop ourselves: a strong open-source model on your infrastructure or on a dedicated server in Germany, connected to your own knowledge store. Tone and format are adapted. Your expertise stays in the store. That is exactly why a single document remains deletable.

Link: https://dropdigital.de/en#faq
Id: faq-home-6
