References and competence areas in process optimisation
Instead of invented case studies, we show what we actually do: competence areas, typical scenarios from mid-sized companies and how we run a project. Specific results and matching references are discussed in person.
50+
delivered projects (project experience)
10
service areas from analysis to operations
6
sector focuses (project experience)
since 2013
experience in systems integration (project experience)
We do not publish client names or embellished case studies. What we can show is the craft itself: process analysis, automation of repetitive work, interfaces between systems, data integration and the ongoing operations that follow. This page sets out our competence areas, typical scenarios from trades, manufacturing, wholesale, logistics and administration, our project approach and the technology we work with. Which of those projects relate to your situation is something we place in a conversation.
Four patterns that show up in almost every project
Our competence areas
Companies differ in size, sector and software, yet the bottlenecks look alike: data is captured several times over, paper and files sit beside the systems, and reports are assembled by hand. The following nine areas cover the path from stocktaking to stable operations. In most projects several of them interlock, because automation rarely holds up without a clean data basis underneath it.
Process analysis
Recording the workflow along the actual work: who captures what, where media breaks occur, which steps repeat. The result is a written report with prioritised measures. Learn more
Process automation
Technology takes over repetitive work: pulling in documents, setting statuses, triggering notifications, producing lists. Approvals and exceptions stay in human hands. Learn more
Interfaces
Connecting systems via REST interfaces, webhooks, middleware or file exchange, depending on what the existing software offers. With retry logic and a full log. Learn more
Data integration
Isolated tools, grown lists and spreadsheets are merged into one data basis. Duplicates cleaned up, data ownership settled per field, reconciliation documented. Learn more
Document digitisation
Paper and PDF archives become searchable and linked to the case: order, delivery note, invoice and proof sit in one place instead of four folders. Learn more
Metrics and reporting
Figures from your existing systems are brought together and kept up to date, instead of being collected by hand each month. Reports with traceable origin. Learn more
Legacy replacement
Step-by-step migration rather than a single cut-off date: take over the data, secure parallel operation, switch function by function and keep the old state as a fallback. Learn more
Process documentation
Workflows written down so that cover arrangements, onboarding and audits work without follow-up questions. Written to be read, not filed away. Learn more
Operations and rollout
After go-live, monitoring, error handling and adaptation to software updates continue, complemented by rollout and training within the team. Operations and training
Typical scenarios in mid-sized companies
Around 99 per cent (Federal Statistical Office of Germany) of companies in Germany are small and medium-sized enterprises. Their workflows have grown over years, often around one industry-specific application, supplemented by lists, forms and mailboxes. The four scenarios below describe starting points we meet regularly in projects, together with the question that needs answering before any technology is chosen.
Scenario 1: the same data is captured several times
An order arrives in a mailbox, is created in the industry-specific application, copied into a list for scheduling and prepared once more for accounting at month end. Every transfer costs time and creates discrepancies between the versions. In the analysis we first settle which system is authoritative for which field. Only then does the connection follow: an interface where the software offers one, a governed file exchange where it does not. After the change, data is captured once and every other version follows automatically.
Scenario 2: paper and files sit beside the case
Delivery notes arrive as photos from the van, test certificates as PDFs by email, timesheets on paper from the workshop. Later, people search through folders, mailboxes and drives. We link the archive to the case: incoming documents are recognised, assigned to the order or the customer and filed in a searchable way, including retention periods. The side effect usually matters more than the search function: queries from accounting and customer service can be answered without pulling colleagues away from their work.
Scenario 3: figures only appear at month end
Utilisation, outstanding items, material consumption and contribution margins sit in different systems. Anyone who wants the current picture waits for a report that somebody assembles by hand. We bring the required values together, put the calculation in writing and refresh it automatically. The definition behind it matters more than the dashboard: if two departments calculate differently, no chart will help. That is why the work starts with a metric definition both sides support.
Scenario 4: a legacy system no longer holds up but must not fail
An older application keeps the business running but is no longer developed, has no interfaces and runs on hardware for which spares are hard to find. Switching overnight is risky in that position. We replace such systems in stages: secure and take over the data, build an intermediate layer for the data exchange, move functions across one after another and keep the old state available for reading during the transition. Operations continue throughout, and each stage is signed off on its own.
Which scenario comes closest to your company?
Describe briefly which systems are in use and where work is done twice. We will place your project and tell you which step we would start with.
How we run a project
Initial conversation and assessment
Around 30 minutes, free of charge: we establish which systems are in use, where work is duplicated and what bothers you most. Afterwards we say openly whether we are a fit and which step is worth taking first.
Process analysis on site and in the systems
We follow the actual work, review data, interfaces and file archives and talk to the people who run the workflow every day. The result is a written report with prioritised measures and an effort estimate.
Fixed price and sequence
The report turns into a quote per measure so you can decide on each one separately. We begin with the step that noticeably eases daily work, not with the technically most appealing one.
Delivery in small steps
Every automation and every interface is first built and checked in a test environment with real data copies. You see interim results and can steer before anything reaches live operation.
Handover into daily work
Rollout with the team, short training on the parts that changed and written process documentation. During the first weeks we stay closer and adjust details that only surface in live operation.
Operations, monitoring, evolution
Interfaces are monitored, and errors land in a follow-up queue rather than nowhere. Before software updates we check compatibility in advance, and new requirements build on what already exists.
Around 30 minutes, free of charge: we establish which systems are in use, where work is duplicated and what bothers you most. Afterwards we say openly whether we are a fit and which step is worth taking first.
We follow the actual work, review data, interfaces and file archives and talk to the people who run the workflow every day. The result is a written report with prioritised measures and an effort estimate.
The report turns into a quote per measure so you can decide on each one separately. We begin with the step that noticeably eases daily work, not with the technically most appealing one.
Every automation and every interface is first built and checked in a test environment with real data copies. You see interim results and can steer before anything reaches live operation.
Rollout with the team, short training on the parts that changed and written process documentation. During the first weeks we stay closer and adjust details that only surface in live operation.
Interfaces are monitored, and errors land in a follow-up queue rather than nowhere. Before software updates we check compatibility in advance, and new requirements build on what already exists.
The technology we work with
REST interfaces and webhooks
Connections to documented programming interfaces, event-driven handovers via webhook, access protection through tokens and traceable logging of every call.
Middleware and queues
An intermediate layer decouples the systems: jobs are held in queues, retried after faults and processed in the correct business order, rather than being wired point to point.
Databases and data models
Relational databases for the shared data basis, cleanly modelled master data, history for changes and reconciliation runs that surface discrepancies instead of overwriting them.
File import and export
Where software offers no interface, we use governed file exchange: CSV, XML, JSON or sector formats, with validation rules, quarantine for faulty records and a resume point.
Inventory systems and accounting
Handover of documents, payments and master data between inventory management, accounting and the tax firm, including structured invoice formats for electronic document exchange.
Operations and monitoring
Automatic checks that transfers are running, notification on failures, retention of logs and regular review of runtimes and error rates. Hosting and data in Germany.
Sectors we have worked in
Trades and crafts
Orders, scheduling, material withdrawal and time recording belong together. We connect site, office and accounting so that paper slips and re-entry disappear.
Manufacturing
Bills of material, production orders, feedback from the shop floor and stock levels. The aim is one continuous state from purchase order to dispatch without interim lists.
Service providers
Quote, project, service recording and invoicing in one chain. A frequent case: time recording that does not match invoicing, and variations that get lost along the way.
Wholesale
Keeping item data, prices, volume tiers and stock consistent across several channels. For trade with an online shop focus, we work alongside a dedicated sister offering.
Logistics
Shipment data, status messages, route planning and proof of delivery. Interfaces to clients and carriers, including file formats that have to be processed reliably every day.
Administration
Application, review, decision and filing as one continuous case. Traceability, deadlines and retention rank alongside the time saved, not below it.
Anonymised project outlines
What typical projects look like
Anonymised, generalised project outlines (project experience). No client names, no promised savings. Results depend on the starting point and the systems involved.
How to recognise process work that holds up
| Aspect | Tool first | Our approach |
|---|---|---|
| Starting point | Software is selected, the workflow adapts to it | The workflow is recorded, then the technology decision follows |
| Data ownership | Left open, every system writes as well | Settled in writing per field before any connection is built |
| Failure case | Transfers break off silently | Retry, follow-up queue and notification are part of the build |
| Knowledge in the company | Sits in the heads of a few people | Process documentation and rollout are part of the project scope |
| After go-live | The project ends at handover | Monitoring, update checks and evolution during live operation |
Specific results on request
Starting the collaboration
- Stocktaking along the actual work
- Written report with an effort estimate per measure
- Fixed-price quote per delivery step, decided one at a time
Process analysis as the entry point: stocktaking of your workflows, a written report and prioritised measures. Delivery per automation or interface from 4,900 € net plus VAT at a fixed price after the analysis. Ongoing support from 190 € net plus VAT per month.
Prices as of September 2026. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.