Ten services that make everyday workflows leaner
From mapping the current state through automation and interfaces to ongoing operations: we look at how your business actually works, remove duplicate data entry and media breaks and connect the systems that currently run side by side.
Entry point and delivery · net plus VAT
- Measure first, build second: the analysis comes before any delivery
- A fixed price per measure instead of an open-ended estimate
- Every stage delivers its own visible benefit
- Operations, adjustments and a named contact after the rollout as well
The process analysis starts at 1,900 € net and covers the on-site review, a written report and a prioritised list of measures. Each automation or interface in the delivery phase starts at 4,900 € net as a fixed price that is set once the analysis is complete. Ongoing support starts at 190 € net per month. All prices are net plus VAT; third-party licences and fees are shown separately. The full breakdown is on the pricing overview.
Prices as of September 2026. Ongoing services are booked individually and can be cancelled monthly; there is no minimum term.
In most mid-sized companies the software is not the problem. The problem sits in the gaps between the systems: a job is noted during a phone call, copied into a list, typed into the scheduling software, emailed to the workshop and looked up again at month end for invoicing. Every one of those steps costs time, and every handover creates errors. Our ten services start exactly there: we map the workflow, remove the unnecessary handovers and connect the systems that already know the work.
Ten services in six layers
All services at a glance
The ten service areas interlock, yet each can be commissioned on its own. Projects usually begin with the process analysis, because it sets the order of play: which workflow costs the most time, which one can be improved fastest, and which measure carries the next one. Only then does it become clear whether an automation, an interface or a clean data foundation is the right next step.
Process analysis
A review of how work is really done: where data is entered twice, where the chain breaks, where people wait for each other. The result is a report with prioritised measures.
Learn moreProcess automation
Technology takes over the repetitive work: passing on documents, sending confirmations, creating appointments, transferring data. Exceptions stay in human hands.
Learn moreInterfaces
Connect systems instead of retyping: through programming interfaces, a mediating layer, webhooks or a controlled file exchange, depending on what the system offers.
Learn moreData integration
Scattered lists, folders and isolated tools are merged into one shared data foundation, with clear ownership per record and without competing versions.
Learn moreDocument digitisation
Paper, scans and grown folder structures become searchable and linked to the case they belong to: job, customer, project or piece of equipment.
Learn moreMetrics and reporting
Figures come out of the systems instead of being collected by hand each month. Utilisation, lead times, open items and contribution margin are available day by day.
Learn moreLegacy replacement
Programmes nobody maintains any more are replaced step by step. Migrate data, run in parallel, switch over, shut down, without stopping the business.
Learn moreProcess documentation
Workflows put in writing so that cover, onboarding and audits work: written in plain language, kept current and linked to the systems involved.
Learn moreOperations and maintenance
Automations and interfaces keep running even as systems change. Monitoring, fault clearing, adjustments to new requirements, one named contact.
Learn moreTraining and rollout
A well-designed workflow is worthless if nobody uses it. We support the rollout on site, train the people involved and stay reachable during the first weeks.
Learn moresince 2013
experience with business IT
50+
delivered projects (project experience)
10
service areas from one source
2-6 weeks
typical duration per stage (project experience)
The ten services in detail
For each service you will find the starting situation, our approach and the result that actually arrives in day-to-day work. The detail pages go further into method, typical systems and effort.
Process analysis: understand first, change second
Almost every improvement project that goes wrong started with the tool rather than with the workflow. We take the opposite route: we sit with the people who run the workflow every day, note every step, every handover and every waiting period, and work out how much working time the workflow ties up over a year. The outcome is a written report with a list of measures sorted by benefit and effort. You can use that report without us as well. More on the process analysis page.
- Problem: nobody knows the complete workflow from start to finish
- Approach: on-site observation, workflow mapping, time estimate per step
- Result: a report with prioritised measures and a defensible effort estimate
| Step | Handover | Time per case |
|---|---|---|
| Order taken by phone | Notepad | 6 min |
| Entered in the scheduling software | Retyping | 9 min |
| Added to the planning list | Duplicate entry | 7 min |
| Query about the delivery date | Waiting time | 11 min |
| Preparing the invoice | Searching the mailbox | 8 min |
Process automation: hand over the typing, keep the decisions
Repetitive work is the most expensive item in many workflows: copying data from one screen to the next, writing standard emails, reconciling lists, sending reminders. We automate exactly the steps that run the same way every time and leave the decisions where experience is needed. Every automation gets a traceable log and a defined route for exceptions, so that nobody has to guess what the system just did. More on the process automation page.
- Problem: skilled staff spend hours transferring data and chasing up
- Approach: define the rules, name the exceptions, automate and log the workflow
- Result: the standard case runs on its own, the special case lands on the right desk
Interfaces: connect systems instead of retyping
In companies that have grown over time there is rarely one system that does everything, but several that each do part of it well. The effort sits in between. We connect those systems through the routes they offer: programming interfaces, a mediating layer, event-driven calls or a controlled file exchange where an older programme offers nothing else. Before we build, we clarify which system is authoritative for which piece of information, so that no two versions of the truth appear. More on the interfaces page.
- Problem: the same information is maintained in two or three programmes
- Approach: clarify ownership per field, choose the route, safeguard the failure cases
- Result: one entry is enough, the other systems pick up the current state
Data integration: one foundation instead of many lists
Customer addresses in the scheduling software, contacts in a spreadsheet, prices in a document on the file server, notes in a mailbox: that is the normal state, not the exception. We merge these scattered stocks, clean up duplicates and define who maintains which record. The old lists do not disappear overnight; they are retired step by step as soon as the shared foundation holds up in daily use. More on the data integration page.
- Problem: four sources for the same information, none of them complete
- Approach: review the stocks, clean duplicates, assign ownership per record
- Result: one shared foundation that sales, operations and accounting all refer to
Document digitisation: filing that knows the case
A scanned document in a folder is not yet digitisation. The benefit only appears once the document is searchable and linked to the case it belongs to: the delivery note with the job, the test record with the machine, the contract with the customer. We set up capture, text recognition, filing structure and retention periods so that searching takes seconds rather than minutes, and we tie the archive into the workflows where the documents are created. More on the document digitisation page.
- Problem: paperwork is scattered across folders, mailboxes and file servers
- Approach: set up capture and text recognition, define filing logic and retention
- Result: documents are searchable and attached to the right case
| Document | Attached to | Retention |
|---|---|---|
| Delivery note 4188 | Job 4188 | 10 years |
| Test record | Machine 7 | 10 years |
| Framework contract | Customer 2043 | Term + 10 years |
Metrics and reporting: figures from the system, not from rework
Many companies only learn their key figures weeks later, because they are collected from several programmes at month end. We pick the metrics up where they arise anyway and make them available continuously: utilisation, lead times, open items, rework, contribution margin per job type. What matters is not the number of charts but the question of which decision a figure is meant to trigger. More on the metrics and reporting page.
- Problem: reports are built by hand and are out of date by the time they appear
- Approach: define the metrics, connect the sources, automate the refresh
- Result: current figures that lead to a decision rather than to follow-up questions
Legacy replacement: move on without stopping
Some programmes have been running for many years, know every quirk of the business and are no longer maintained by anyone. A complete switch over a single weekend carries a high risk in such cases. We replace step by step: migrate and verify the data, convert one clearly bounded area first, run both routes in parallel for a while, then switch over and shut the old system down in an orderly way. Daily work stays possible throughout. More on the legacy replacement page.
- Problem: a central programme is outdated, yet the business depends on it
- Approach: data migration, one area first, parallel operation, controlled shutdown
- Result: a maintained system without the work coming to a halt
Process documentation: knowledge that does not sit with one person
If a workflow only exists in one person's head, every holiday cover and every onboarding becomes a risk. We put the important workflows in writing, in the language of the business rather than the language of a manual: what happens, who is responsible, which system is used, what to do when things deviate. The documentation is placed where it is needed and carried along whenever something changes. More on the process documentation page.
- Problem: workflows live in people's heads, not in a readable form
- Approach: map the workflow, describe it plainly, name owners and exceptions
- Result: cover, onboarding and evidence for audits become considerably easier
Operations and maintenance: so it still runs in two years
An interface is not a piece of furniture. Systems get updated, formats change, credentials expire and workflows keep developing. We monitor the automations and connections we have set up, step in when something fails and adjust them when things change. You have a named contact who knows your system landscape and does not need briefing again with every call. More on the operations and maintenance page.
- Problem: after the rollout nobody notices when a transfer fails to run
- Approach: set up monitoring, handle faults, plan adjustments in advance
- Result: deviations are noticed before they reach day-to-day business
Training and rollout: the part where projects fail
A new workflow does not catch on because it is better, but because the people involved understand it and trust it. We support the rollout on site: short training sessions on real cases rather than sample data, a brief written guide for the workplace and a reachable contact during the first weeks. Feedback from that phase feeds straight into improvements while they are still inexpensive. More on the training and rollout page.
- Problem: the technology is in place, but people still use the old route
- Approach: training on real cases, short guides, support after the start
- Result: the new workflow is genuinely used and sustains itself
How a project runs with us
First conversation
On the phone or on site we clarify which workflow costs you the most time and which systems are in use. Afterwards you know whether an analysis makes sense and what it costs.
Process analysis
A review on site, at the workplaces where the workflow actually happens. The result is a report on media breaks, duplicate entry and prioritised measures, from 1,900 € net.
Fixed price and order of play
For every measure we state a fixed price and a benefit. You decide which stage comes first. Nothing is built before scope and price are set out in writing.
Delivery in stages
We build the first stage, test it with real cases and hand it over together with you. Only then does the next one begin, so daily work remains possible at all times.
Rollout and operations
Training for the people involved, support during the first weeks, then ongoing care from 190 € net per month with monitoring, fault clearing and adjustments.
On the phone or on site we clarify which workflow costs you the most time and which systems are in use. Afterwards you know whether an analysis makes sense and what it costs.
A review on site, at the workplaces where the workflow actually happens. The result is a report on media breaks, duplicate entry and prioritised measures, from 1,900 € net.
For every measure we state a fixed price and a benefit. You decide which stage comes first. Nothing is built before scope and price are set out in writing.
We build the first stage, test it with real cases and hand it over together with you. Only then does the next one begin, so daily work remains possible at all times.
Training for the people involved, support during the first weeks, then ongoing care from 190 € net per month with monitoring, fault clearing and adjustments.
What you hold in your hands at the end
The scope depends on the project, but the following results are produced in almost every engagement. They belong to you and remain usable even if you later continue with someone else.
- A map of the current workflow with all steps, handovers and waiting periods
- A list of media breaks and duplicate entries with an estimated time cost
- A prioritised list of measures ranked by benefit and effort
- A fixed-price offer per measure with a clearly bounded scope
- A description of the target workflows, understandable for the people involved
- An overview of data ownership: which system is authoritative for what
- Automations and connections in place, with logging
- Short working instructions for the workplaces affected
- Monitoring of the running transfers with alerts when something fails
- Handover documentation for your own IT team or a future service provider
Typical starting points in mid-sized companies
How such projects typically unfold
Illustrative scenarios from typical project journeys (project experience), anonymised and without client details.
Where we deliberately work differently
| Aspect | Introducing the tool first | Our approach: analysis first |
|---|---|---|
| Project start | Software is selected, the workflow adapts to it | The workflow is mapped, then the means is chosen |
| Scope | Everything at once, benefit only visible at the end | Bounded stages, each with its own benefit and fixed price |
| Data | A new island next to the existing lists | Ownership per piece of information clarified up front |
| People | Rollout by announcement | Training on real cases, support after the start |
| After the rollout | The project ends with the handover | Monitoring, fault clearing and adjustments from 190 € net per month |
Three ways to improve your workflows
The order of play determines risk and how much budget is tied up. A factual comparison of the common approaches.
New software for everything
- Included: One system, one contact, one contract
- Included: The target state is described from the outset
- Not included: The benefit only becomes visible after many months
- Not included: Hard-won quirks of the business are easily lost
- Not included: The entire budget is tied up before anything runs in production
Individual tools as needed
- Included: Ready to use immediately, low entry cost
- Included: Each department can decide for itself
- Not included: New islands appear alongside the old ones
- Not included: The same data is maintained differently in several places
- Not included: Subscription costs grow without manual work disappearing
Analysis, then stages
- Included: The order follows from measured time spent
- Included: Every stage has a fixed price and a visible benefit
- Included: Existing systems stay in use for as long as they hold up
- Included: Process analysis from 1,900 € net, delivery from 4,900 € net per measure
- Not included: The analysis takes time before the first measure starts
What delivery costs
We state prices before you have to ask. The entry point is as a rule the process analysis, because without it any estimate would be guesswork. After that you receive a fixed price per measure with a clearly bounded scope. Third-party licences, fees or access charges required for a connection are shown separately, so that you can see which share covers our work and which covers running costs.
Prices at a glance
All prices are net plus VAT. The final fixed price for delivery is set once the process analysis is complete.
Process analysis
The entry point: review, report and order of play.
- Observation at the workplaces concerned
- A map of the current workflow with all handovers
- Media breaks and duplicate entries named
- A written report with prioritised measures
- An effort estimate per measure
Delivery
A fixed price per automation or interface.
- Automation of one recurring workflow
- Or a connection between two systems via an interface
- Fixed price after the analysis, scope in writing
- Testing with real cases before hand-over
- A short working instruction for the people involved
Ongoing support
So the solution stays stable in daily use.
- Monitoring of the transfers in place
- Alerts when a run fails to happen
- Fault clearing and error analysis
- Adjustments when your systems change
- A named contact who knows your landscape
All prices are net plus VAT. Third-party licences, access charges and fees are shown separately. You receive a binding offer after the process analysis.
Scope: retail systems and the online shop
Which workflow costs you the most time?
Tell us briefly where things get stuck. We will say whether an analysis makes sense and which measure we would start with.