Germany
AI automation for companies in Germany
We build automations, internal tools and AI agents for German teams, with GDPR, the works council and the e-invoicing rules planned into the design. We deliver in English, and the automations, templates and documents your staff use can be in German.
SBD builds AI automations and internal tools for companies in Germany with 1 to 1,000 people. Work starts with the $500 audit credited to the build, builds are fixed price from $1,000, and everything runs in your own accounts. We plan for GDPR and the BDSG, works council co-determination, e-invoice formats and the EU AI Act. Project delivery is in English, and the outputs can be in German.
Data protection law in Germany
German companies work under the GDPR, the Federal Data Protection Act (BDSG) and, where there is a works council, the Works Constitution Act. The EU AI Act adds duties that phase in over the next two years.
GDPR and the BDSG
Every use of personal data needs a lawful basis and a record of processing. We document what each automation reads, writes and keeps, so it can go straight into your records of processing and any impact assessment.
Works council (Betriebsrat)
Under section 87(1) no. 6 of the Works Constitution Act, the works council has a say in technical systems that are able to monitor employees’ behaviour or performance. Most automations log who did what, so we plan works council review into the timeline and write a plain description of what is recorded and who can see it.
EU AI Act
Bans on certain practices have applied since February 2025 and duties for general-purpose AI models since August 2025. The 2026 amendment moved obligations for high-risk systems listed in Annex III, which include recruitment and employee management, to 2 December 2027. We tell you in the audit if a use case may fall into that category.
Transfers to India
India has no EU adequacy decision, so where our team accesses personal data our data processing addendum uses the EU Standard Contractual Clauses.
How we handle it
Builds run in your accounts, and where you want data kept in the EU we choose EU hosting regions for every tool that offers them. We sign our data processing addendum and publish our sub-processors. We do not hold ISO 27001 or SOC 2, and we answer security questionnaires instead. See our data processing addendum, sub-processors and AI use policy.
Software we connect in Germany
German finance teams work with their tax adviser through DATEV, and invoicing rules changed on 1 January 2025. We do not have integration pages for DATEV, SAP Business One or lexoffice yet, so we scope those connections in the audit.
E-invoicing (XRechnung and ZUGFeRD)
Since 1 January 2025 every business in Germany must be able to receive structured e-invoices in the EN 16931 format. Issuing them becomes mandatory from 2027 for companies with prior-year turnover over €800,000, and for everyone from 2028. We build intake that reads XRechnung and ZUGFeRD files into your accounting system.
DATEV
Bookings and receipts prepared in the format your tax adviser imports, so month-end does not depend on a folder of PDFs.
SAP Business One and lexoffice
Orders, stock and invoices connected to your CRM or shop through their APIs.
Microsoft 365 and Business Central
Common in German mid-sized firms for documents, approvals and ERP.
HubSpot and Pipedrive
Sales pipelines with double opt-in consent handled before any email sequence starts.
Channels and language
Email is the main business channel in Germany, and people expect formal written German with a proper imprint and signature.
Email first
Customer updates, reminders and approvals go by email, written in German where your customers expect it, with templates your team can edit.
Consent for marketing email
Marketing email generally needs prior consent, usually collected by double opt-in. We record the confirmation with a timestamp.
Teams for internal alerts
Internal notifications go to Microsoft Teams or Slack, with the works council agreement in mind for anything that tracks individual work.
Working hours
Our team works from India (IST, UTC+5:30), three and a half hours ahead of Germany in summer and four and a half in winter. Your morning and lunchtime overlap with our afternoon, so calls usually sit between 9am and 1pm German time. The team is available about sixteen hours a day, so calls can usually be booked at a time that suits you.
| Your time | Our time |
|---|---|
| 9:00 CET | 13:30 IST |
| 13:00 CET | 17:30 IST |
| 9:00 CEST (summer) | 12:30 IST |
Common first automations
- 01
E-invoice intake
Incoming XRechnung and ZUGFeRD invoices are read, checked against the order and posted for approval.
- 02
Receipts to the tax adviser
Receipts and bookings are collected, named and exported in the form your adviser imports into DATEV.
- 03
Quote to order
Enquiries become quotes from your price list and, once accepted, orders in your ERP without retyping.
- 04
Documentation search
An AI assistant answers staff questions from your own manuals and policies in German, citing the page it used.
What it costs
Every engagement starts with the audit, which ends in a fixed price for the build. You own the accounts and the code.
| Automation Audit | $500 | One to two weeks, credited in full to a build within 90 days |
|---|---|---|
| Workflow automation | from $1,000 | One process connected across your tools |
| Internal tool | from $3,000 | An app your team works in every day |
| Multi-module system | from $5,000 | Several connected tools and agents |
| Micro-SaaS | from $10,000 | A product you can sell or license |
| Care plan | from $50/mo | Monitoring, fixes and small changes |
| Automation team | $999/mo | A standing team for ongoing builds |
Our work
Our published case studies do not name a client in Germany yet. One of them, a request-for-quotation to quotation flow on SAP, is close to the order work many German manufacturers ask us about.
Read the RFQ to quotation on SAP case study · All case studies
Questions
Do you work in German?
Project calls and our own documentation are in English. The automations, email templates, forms and staff guides we build can be in German, and we have them checked by a native speaker on your side before go-live.
Do we need works council approval?
If you have a works council and the system can monitor employees’ behaviour or performance, co-determination usually applies. We give you a plain description of what the system records so the discussion can start early. Your employment lawyer decides what is required.
Can our data stay in the EU?
For hosting, yes, where each tool offers an EU region, and we pick those by default. Our team in India may need access during the build, which is covered by Standard Contractual Clauses in our data processing addendum.
Does the EU AI Act affect our automation?
Most operations automations are not high-risk. Uses in recruitment, employee management or credit decisions can be, and those obligations now apply from 2 December 2027. We flag them in the audit.
How can we pay you?
However suits you. We hold bank accounts in several currencies and take bank transfer and card payments through Stripe, PayPal, Wise, Razorpay, Infinity and others. The statement of work fixes the price and the currency before any work starts.
Sources: BDSG (gesetze-im-internet.de); BetrVG section 87; Federal Ministry of Finance, e-invoicing FAQ; EU AI Act, Regulation (EU) 2024/1689; Addleshaw Goddard on the AI omnibus adoption. Checked 15 November 2026. This page explains how we build and is not legal advice.
Other locations: United States, United Kingdom, United Arab Emirates, France, Netherlands, Ireland, Saudi Arabia, Canada, Australia, Singapore, Sweden, Denmark, Norway, Finland, Switzerland, Qatar, Spain, Italy, Belgium, Austria, Portugal, Poland, New Zealand, India. All locations.
Tell us what your team in Germany does by hand
On a discovery call we look at the work your team repeats each week and tell you which parts are worth automating first and what the audit would cover.
Book a discovery call














