Data is rekeyed
People copy the same information between systems, files or inboxes.
For process owners, Operations and IT
Business automation: find where automation genuinely pays off
If teams keep rekeying data, repeating checks or relying on one person to handle exceptions, start with the process. That shows whether automation deserves further investigation and what must be fixed first.
Not sure where to start? The scan stays local and does not ask for personal data.
Confirmed point of contactJoshua BoermansFirst point of contact
You do not need to know the solution yet
Start by discussing the recurring situation with Joshua Boermans. The conversation covers the purpose, day-to-day steps, exceptions and ownership, so there is a concrete starting point before any tool is considered.
See how an initial exploration worksA practical starting point
When is automation worth exploring?
Automation becomes a useful question when recurring work creates visible friction. These signals help you choose a process without pretending the answer is already known.
Checks keep returning
Routine controls and follow-up depend on manual reminders.
Exceptions rely on one person
Repair work or operational knowledge is concentrated with a small number of colleagues.
Process evidence
Make the question concrete before choosing a route
A first process view separates the normal route from exceptions, ownership and the next decision. This is an illustrative structure, not a customer case or promised outcome.
- Trigger
- A new request arrives
- Normal route
- Check → enter → confirm
- Exception
- Missing information requires manual repair
- Owner
- The process owner defines the standard
- Next decision
- Standardise first or explore automation?
Public practice evidence
How we separate source facts from our analysis →
What public cases do — and do not — prove
Boermans Digital uses public Korper/Fortra sources to test decision frameworks against practice. These are not Boermans Digital customer cases: source facts and published outcomes remain attributable to the original case; the surrounding interpretation is Boermans Digital's.
Top Bakkers: scale and central orchestration
Published: more than 1 million invoices per month with 1.5 FTE.
The case describes central data exchange, ETL, and order and invoice processing. The Boermans analysis focuses on why volume, repetition and central orchestration can combine into a strong automation candidate.
Variant: system friction and interface choice
Reported: 100% fewer manual errors and 75% fewer planning errors.
The source describes databases, web services, REST/API and file formats alongside manual hand-offs. The analysis shows why not every step automatically needs to become an RPA step.
House of Representatives: why controlled file transfer is more than SFTP
Evidence boundary: no realised KPIs or outcomes are published.
The public announcement names automated, secure and controlled exchange with third parties. Boermans uses only those facts to analyse the operating-model question and does not invent results.
Boundary: Boermans Digital does not present Top Bakkers, Variant or the House of Representatives as its own customers. This section uses public sources to explain which decisions and preconditions can be learned from practice.
From friction to direction
Four questions shape the next step
The outcome can be automation, but it can also be simplification, clearer ownership or better control first.
What must the process achieve?
Make the intended outcome and the people involved concrete.
Where does friction appear?
Mark where someone copies data, waits, checks or resolves an exception.
Is the foundation ready?
Check whether rules, data, access and ownership are clear enough to continue.
Which step comes first?
Choose between simplification, standardisation, better control or further automation exploration.
Specialist route
Is critical file transfer the real issue?
Explore scheduled transfers, access, logging, monitoring and recovery through the separate Managed File Transfer route.
Explore Managed File TransferAfter contact
What happens after you get in touch
The first step is not automatically a quotation or technical implementation. The question is defined before deciding what is actually needed.
Describe one concrete situation
Describe one process or file-transfer question. You do not need to know the solution, vendor or technology yet.
Define the question first
The first assessment looks at the objective, current way of working, exceptions, risk and missing information — not immediately at a tool or quotation.
Choose the appropriate next step
The route may be process improvement first, a scan or deeper assessment, a business case/technical discovery, or direct specialist discussion.
Bring in implementation only when it fits
If specialist technical delivery is needed, Korper ICT can be involved. This is not an automatic hand-off and no outcome is guaranteed in advance.
Bring one recurring process
Describe what keeps returning, where the work slows down and which decision you need to make next.