What is process automation?
Process automation describes the shift from manual, rule-based activity to software-driven execution. This guide explains soberly what it covers, which methods and tools exist, which processes are worth automating in a mid-sized business, and how a project is actually set up in practice — no buzzwords, concrete numbers.
What is process automation?
Process automation refers to the use of software to execute recurring steps in a business process without manual intervention. Instead of an employee opening an invoice from the inbox, keying the data into a system, asking a colleague for approval and finally triggering the payment, a combination of workflow engine, data extraction and API integration handles these steps on its own — the employee only reviews exceptions.
The range stretches from simple data transfer between two systems (CRM to ERP, say) through rule-based workflows with approval stages all the way to AI-assisted decisions, where language models understand and classify unstructured content (emails, PDFs, images). The decisive factor is not the technology used but the outcome: a process that runs faster, with fewer errors and without permanent manual intervention.
In the German mid-market the term is often used interchangeably with business process automation, workflow automation or process automation. It is distinct from plain digitisation — which only means that information exists in digital form (PDF instead of paper) without the process itself getting any faster. Automation is the next step.
The terms RPA (Robotic Process Automation), BPM (Business Process Management) and AI automation are also frequently blurred. They are not synonyms but different layers: BPM is the architecture and modelling of the process, RPA a concrete execution technique (UI bots), and AI augments this architecture wherever understanding of unstructured data is required. A detailed description of the AI element is on our page about AI process automation.
For mid-sized businesses — typically companies with 30 to 500 employees — process automation is not an abstract IT topic but a business decision: which working time can be replaced by software, and what additional value can the same team deliver in the time freed up?
Methods and technologies of process automation
Six established approaches — usually combined in practice. Which one fits depends on the process, the systems already in place and the stability requirements.
| Approach | Character | Pros | Cons |
|---|---|---|---|
| RPA | UI-based automation | Works without APIs, fast visible impact, no change to legacy systems. | Breaks on UI changes, high maintenance, no true integration. |
| API integration / iPaaS | Data and system connection | Stable, fast, audit-friendly. Make, n8n, Workato as standard. | Requires available APIs, licence costs scale with volume. |
| BPM / workflow engines | Process orchestration | Clear models (BPMN 2.0), compliance-ready, well suited to multi-stage approvals (Camunda, Bonita). | Steeper learning curve, only pays off for complex processes. |
| AI-assisted automation | LLM, vision, classification | Understands unstructured data (PDFs, emails, images), decides in grey areas. | Cost per call, hallucination risk without guardrails, GDPR effort. |
| Low-code platforms | Citizen development | Business users build themselves (Power Platform, Mendix), relieves IT. | Shadow-IT risk, often hard to scale, lock-in. |
| Custom engineering | Tailored software solution | Full control, optimal fit, no platform limits. | Higher initial cost, own maintenance required. |
In practice these methods rarely appear in isolation. A typical back-office scenario combines iPaaS for the system connection, a small workflow engine for the approval logic and an LLM component for classifying unstructured inbound documents. Which method to choose comes down to three questions: are APIs available? How variable is the input data? How high is the volume, and which audit requirements apply? More on the concrete implementation in the back office under back-office automation.
A particular role is played by hyperautomation — the orchestrated interplay of multiple automation technologies across an entire business domain. For mid-sized businesses it is usually a distant prospect: a platform strategy only makes sense once ten to fifteen individual processes are running cleanly.
Which processes are worth automating?
Not every process is a good candidate. Five criteria help with prioritisation.
Frequency
The more often an activity occurs, the faster the investment pays off. Rule of thumb: from 20 cases per week the effort is almost always worthwhile.
Handling time
Long manual activities with a clear structure are the best candidates. Worked example: 15 minutes of manual input per case × 200 cases/month = 50 hours of reclaimed working time.
Rule clarity
Processes with unambiguous rules (whenever X, then Y) are technically straightforward. As soon as gut feeling decides, you need either a human in the loop or an AI model.
Data availability
Is the required data available digitally and machine-readable? If not, digitisation is the first step — automation comes after.
Strategic value
Processes at customer touchpoints often have higher leverage than pure back-office activity — shorter response times directly affect revenue and customer retention.
Typical first candidates in mid-sized businesses
- Invoice intake & document posting — extract the PDF from the email, OCR, match against purchase orders, post automatically into DATEV or SAP. Typical saving: 60–80 % of handling time.
- Lead routing & CRM creation — web form, phone call or trade-fair lead automatically into the CRM, with enrichment (company data, industry), assignment to the right sales rep and a reminder.
- Employee onboarding — from contract creation through IT account provisioning to the delivery of training material. Typically reduces lead time from weeks to a few days.
- Reporting aggregation — pull weekly or monthly KPIs from several systems, prepare and distribute them. Instead of half a day of Excel tinkering: one click, or none at all.
- Master data maintenance — synchronisation between CRM, ERP, email system and line-of-business software. Avoids the classic “maintained-three-times-and-still-wrong” effect.
- Classify & prioritise customer enquiries — categorise incoming emails with an LLM, route them to the right inbox, prepare reply drafts. Cuts response time substantially.
Process automation by business area
Depending on the department, process automation looks different. An overview of the focus areas and resources for the deeper topics.
Back office & finance
Invoice intake, document capture, dunning, expense reporting, DATEV interfaces. High frequency, clearly defined rules, fast payback. Detailed examples under back-office automation.
Sales
Lead routing, CRM creation and enrichment, proposal drafts, automated follow-up, pipeline reporting. Substantially reduces administrative load and gives sales more time for real customer contact — see sales automation.
Human resources
Applicant management, onboarding, contract creation, leave and sickness notifications, personnel file maintenance. Particularly with growing teams, automation noticeably relieves the HR department. Detailed topics under HR process automation.
Real estate
Listing creation, portal synchronisation, lead qualification, viewing coordination, tenant and owner reporting. More on the industry application under process automation in the real estate industry.
Industry & manufacturing
MES and ERP integration, maintenance planning, quality documentation, supplier communication. Here process automation meets classic industrial automation — see industrial automation.
Cross-functional (AI)
As soon as unstructured content enters the picture — analysing contracts, classifying emails, extracting knowledge from documents — language models come in. For more depth, see our page on AI process automation.
Tools and platforms for process automation 2026
An overview of the platforms widely used in the DACH mid-market — with their strengths and typical field of use.
Make.com
iPaaS, visualStrength: Fast start, more than 1,800 integrations, good pricing tiers.
Best for: SMEs up to 500 employees, many SaaS tools, IT-savvy business staff.
n8n
Self-hosted workflowStrength: Open source, on-premise possible, code extensions, EU hosting.
Best for: GDPR-sensitive industries, technically sound teams, no licence lock-in.
Zapier
iPaaS, entry-levelStrength: Easiest to use, many apps, good for simple trigger-action flows.
Best for: Very small teams, single workflows, no self-hosting needed.
Microsoft Power Automate
Microsoft ecosystemStrength: Deep integration with Microsoft 365, Dataverse, Dynamics, Teams.
Best for: Companies with a full M365 deployment and Power Platform licences.
UiPath / Automation Anywhere
RPAStrength: Mature RPA platforms for SAP, mainframes, legacy systems without APIs.
Best for: Enterprises and the upper mid-market with legacy load and high-volume processes.
Camunda
BPMN workflow engineStrength: Standards-conformant BPMN execution, highly scalable, audit-ready.
Best for: Banks, insurers and regulated industries with complex approval chains.
Tool choice is a means, not an end. In many projects a combination of n8n (for the workflows) and a lean database is enough — regardless of what the platform vendors' marketing slides promise. We recommend not committing to a platform too early: analyse the process first, then assign the tool. More on our approach and on concrete service packages under our services.
How do you approach an automation project? The 5-phase roadmap
A pragmatic approach we use as standard in mid-market projects — no concept-paper marathon, with the first productive process after 4 to 8 weeks.
Identify
Process inventory: which activities run how often, how long do they take, who performs them? Interviews with the people doing the work plus a compact process-mining or self-assessment exercise produce a long list of 20 to 60 candidates.
Prioritise
Assessment by frequency, effort, rule clarity and risk. The top three candidates move into detailed analysis — including data availability, system access and readiness for change in the business unit.
Pilot
A scoped pilot in 4 to 8 weeks with clearly defined success metrics. The goal is not the perfect process but a runnable comparison between the status quo and the automated flow.
Scale
After a successful pilot, further processes are automated using the same pattern. Architecture building blocks (data models, authentication, audit log) are reused so that each subsequent automation becomes cheaper and faster.
Optimise
Monitoring, adaptation to process changes, continuous improvement. An automation is not a project but an operation — with clear responsibilities and a backlog for further development.
This approach deliberately differs from classic large-project logic: no months-long concept phase, no complete business process analysis before the first line of code. Instead, a small productive start that informs the rest of the undertaking. If you want to know which process in your company makes the best entry point, a free ProcessCheck is the fastest route.
ROI and KPIs
Four metrics that show cleanly whether a process automation has succeeded — and which we let our projects be measured by.
Cycle time is the time from the start of a case to its completion. An illustrative example: an invoice intake that previously took several days on average typically runs through in a few hours after automation. Cycle time affects cash and early-payment-discount effects and is often the metric with the highest indirect business impact.
Manual effort is expressed as an FTE equivalent — how many full-time person-days does the automation free up? This figure makes the ROI tangible. A worked example: 1,500 hours of working time saved per year are weighed against the implementation and operating costs — as a rule with a clearly positive result. You receive the concrete investment costs as an individual quote.
Error rate is the number of cases requiring correction. With cleanly defined rules it is practically zero after automation — unlike manual processing, where typos, skipped steps and lapses in concentration are regular sources of error.
Time to value is the time from project start to the first productive process. It should be between 4 and 8 weeks — longer lead times usually mean the methodology is oversized.
Common mistakes in process automation
Seven typical patterns that bring projects to a standstill — and how each of them can be avoided.
Starting with the most complex process
Many projects fail because the first initiative is also the hardest process in the company. Recommended: start with a moderately complex process with a clear ROI so the team gains experience and can document success.
No measurement baseline
Without a before-measurement (cycle time, error rate, effort) success cannot be proven. The consequence: the project counts as “felt to be successful” and further investment becomes harder to push through.
Leaving the business unit out
IT-driven automations without close involvement of the people doing the work produce solutions that miss the real process. The best pointers to weak spots come from those who run the process every day.
Tool choice before process analysis
“We'll use Power Automate, we have it anyway.” — Wrong order. Understand the process first, then the tool. Otherwise you force processes into tool logic instead of the other way round.
No ongoing operation planned
An automation is never finished. Whoever plans no owner, no monitoring and no budget line for maintenance will have orphaned workflows in 12 months.
AI as an end in itself
An AI component does not automatically make a project better. If the process can be solved with rules, an API integration is cheaper, more stable and faster. AI belongs where unstructured data needs to be understood.
Data protection as an afterthought
GDPR assessment and data processing agreements should be settled before architecture decisions, not after. We have seen projects that had to be rebuilt shortly before go-live because the data flow was not permissible.
Funding and subsidies for process automation
For mid-sized businesses in Germany, several funding programmes exist that cover part of the consulting and implementation costs. Which funds come into question depends on size, industry and location.
- BAFA — Förderung unternehmerischen Know-hows: 50 % subsidy on consulting services, capped at a €3,500 subsidy (equivalent to €7,000 in fees). Suitable for the strategic analysis and concept phase.
- go-digital: Federal programme for digitisation in the mid-market, funding certain consulting services and implementation steps at up to 50 %. Suitable for AI components and digital business models.
- Digital bonus of the federal states: Bavaria, Saxony, Thuringia, Baden-Württemberg and other federal states have their own funding programmes, often with attractive rates for investments in software and training.
- ZIM — Zentrales Innovationsprogramm Mittelstand: For more ambitious undertakings with a research and development component; well suited to individually developed platforms.
A detailed overview of current AI and automation funding programmes including application notes can be found in our blog.
Frequently asked questions on process automation
Answers to the ten questions we hear most often in initial conversations.
Process automation means that recurring steps in a business process are taken over by software instead of being performed manually by employees. It spans from simple data transfer between two systems (e.g. CRM → ERP) through rule-based workflows (BPM, RPA) to AI-assisted decisions (LLM classification, document extraction). The goal is not headcount reduction but freeing your employees to focus on value-creating work while repetitive tasks run in the background.
Which of your processes carries the most leverage?
A free ProcessCheck — 30 minutes, no sales pitch on the phone. We identify the process with the highest ROI and outline how an automation can go into production in 4 to 8 weeks.
Reply within 24 h · 100 % no obligation