Talk to us about your process automation.
A half-hour first conversation, no obligation. Tell us about the processes that cost you and what they deliver, and we will advise you on approach, choice of tools and a realistic sequence for automation.
Service · Consultancy & custom development
Automating business processes with advice and custom software.
From quote-to-order to HR onboarding and compliance flows: we first look at which processes create volume and pain, and only then choose between iPaaS, RPA, BPM, low-code or a custom build. Independent advice, followed by implementation in sprints.
Process automation isn't a tool choice, it's a chain choice.
Many organisations start with "we'll buy Zapier" or "we'll deploy UiPath" and then get stuck on the first real exception: a form that deviates, an ERP field that changes, an approval step that requires human judgement. Process automation only works when you first map out the chain, then quantify the pain points, and only then choose the tools.
We are an independent implementation partner. We don't build a platform of our own that we are keen to sell. For each process, we choose between low-code, iPaaS, a BPM engine such as Camunda, RPA bots or a custom build. For the complex, industry-specific and deeply integrated parts, we do the custom work ourselves. For the simple work, we use standard platforms efficiently.
We mainly work with mid-market SMEs, industry associations, healthcare providers, cooperatives and scale-ups that have moved beyond the Excel stage. That's where the gains are usually greatest: manual quote flows, email ping-pong about invoices, approvals sitting in a shared mailbox, and data retyped across three different systems. Not because the teams are doing it wrong, but because the systems were never meant to work together.
The common thread in our approach: measure first, then model, then build. A process that hasn't been measured first (manual time, volume, error rate, lead time) can't be automated honestly, because nobody knows whether the business case stacks up. We'd rather spend an extra week on analysis than three months building plumbing for a process that in reality only runs ten times a month.
Three types of process automation.
The umbrella term breaks down roughly into three flavours. In practice we combine them: an iPaaS integration that handles the standard data, a BPM engine for human approvals, and custom logic for the industry-specific rules.
System-to-system automation
The plumbing between your existing applications. An order from your webshop to your ERP, an invoice from your accounting system to Peppol, a lead from your form to your CRM. Often via iPaaS (Workato, Make, Zapier) or direct API integrations where volume or latency demands it. See also our API and integration approach.
iPaaSWebhooksETLEvent-driven
Process orchestration with a human in the loop
When a process runs across several departments, includes escalations, or requires a four-eyes principle, you need a process engine that tracks status and assigns tasks to people. We work with BPM platforms such as Camunda and Flowable; for industry organisations we often build a custom BPM platform with BPMN/DMN as its backbone.
BPMNDMNEscalationAudit trail
RPA, document automation and AI classification
For flows that process unstructured input (incoming invoices, complaint letters, contracts, forms), we combine document AI (OCR plus LLM classification) with RPA bots that operate legacy applications where no API is available. For the entire paper flow we offer a dedicated document workflow service.
UiPathDocument AIOCRLLM classification
What an automation project delivers.
No loose reports and no vague transformation story. At the end of the project you have working, monitored processes plus the documentation to develop them further yourselves.
- Process landscape mappedAn overview of the processes generating the most volume and pain, quantified by time, errors and lead time. This tells you where to invest next.
- Make-buy-build advice per processIndependent advice on which process belongs in iPaaS, which in a BPM engine, which requires RPA and which needs custom development.
- Working automated processesLive in production, with monitoring dashboards, error handling and escalation routes. No demos or pilots that never make it further.
- Documentation and runbooksBPMN diagrams, decision tables, API contracts and operations manuals. Your team can change, extend and troubleshoot independently.
- Compliance trailProcess-level audit log for GDPR, DORA, NEN 7510 or the AI Act, depending on your sector. Who did what, when, with which model or data.
- Continuous improvement loopProcess metrics that show where the next gain lies, plus an approach for continued iterative improvement rather than a single big bang.
Who we do automation for.
Not every organisation needs custom process automation. Four profiles where we make the difference; if you recognise yourself, we'd be happy to talk further.
Mid-market businesses
Beyond the spreadsheet stage
Organisations with manual quoting, order and invoicing flows that, with 30+ employees and growing volume, are hitting the limits of spreadsheets and shared mailboxes. Early gains usually lie in the quote-to-order chain and the incoming invoice flow.
Industry & cooperatives
Multi-tenant flows
Industry organisations and cooperatives that must run the same process chain for dozens of members: member onboarding, claims, certification. We almost always build custom solutions here because standard platforms cannot handle the multi-tenant role model.
Healthcare & public sector
Reducing administrative burden
Healthcare providers and government organisations with heavy administrative flows (intake, referrals, claims, permit issuing) where GDPR and NEN 7510 apply strictly. Standard low-code platforms often struggle with these compliance requirements.
Multi-BU concerns & scale-ups
Scaling beyond the system
Concerns with multiple business units that run the same process differently in each unit, and scale-ups that are outgrowing their first tooling layer. Both need a process engine that supports variation without the governance falling apart.
How an automation project works.
1
Process analysis
Together with your team, we map out the current state of your key processes. For each process we record the steps, lead time, volumes, error frequency, waiting times, systems involved and pain points. No abstract transformation talk, just concrete measurements.
2
Prioritisation
We score processes on three axes: volume (how many transactions per month), effort to automate (technical complexity, number of systems) and strategic value. This produces a ranked list, so you decide which process is tackled first.
3
Make, buy or build per process
For each prioritised process, we assess: can an iPaaS handle this? Does low-code such as Power Automate fit? Do we need a BPM engine? Or does this need custom development? We are honest when a standard platform is sufficient. We have no incentive to build everything from scratch.
4
Implementation in sprints
We build in short iterations. Each sprint delivers a working process or a working part of a chain, not weeks of plumbing with no visible output. You test along the way, and so do your end users. This takes you through a multi-sprint programme from a first process to a mature process landscape.
5
Monitoring and ongoing development
After go-live we keep measuring: which processes deliver value, where new bottlenecks emerge, and which exceptions need human attention. Based on this, we plan the next round of improvements. Process automation is a continuous programme, not a project with an end date.
Concrete use cases.
These are the flows we most often encounter. This is not an exhaustive list. Usually an organisation combines three or four of them, and we build the process landscape around those.
Quote-to-order (CPQ)
From configuration and pricing calculation through to quote, contract, order and invoice. Central product logic, a rules engine for discounts, e-signing and integration with your ERP. We have a dedicated service for this: custom CPQ and product configurator.
CPQPricing rulesE-signingERP sync
Invoice flow with Peppol and accounting
Incoming invoices are read via OCR, VAT numbers are validated, a cost centre is suggested, and the approval route determines who is asked to sign off. Outgoing invoices are sent via Peppol to government bodies and large customers. Postings flow back into the accounts automatically.
PeppolOCR + AIVAT validationFour-eyes principle
HR onboarding, complaint and ticket flows
A new employee triggers an SSO account, payroll registration, IT asset assignment and training invitations, multiple systems, one process. On the customer side: complaints and tickets arriving by email, form or web chat are classified, routed and monitored against SLAs, linked to the CRM.
SSO & provisioningPayroll integrationComplaint routingSLA monitoring
When to build custom and when to use a platform.
An honest comparison. For most automation needs, a combination of standard platforms is enough. Custom development pays off in four specific situations.
Choose platform
Standard integrations between SaaS
For SaaS-to-SaaS flows with common connectors (HubSpot, Stripe, Slack, Google Workspace), an iPaaS is almost always faster and cheaper than a custom build. In that case, we help you with the setup rather than building something of our own.
Choose platform
Simple form-based flows
Simple request or approval flows with linear sign-off work perfectly well in Microsoft Power Automate or another low-code platform. That's often enough for a first layer of process automation in many small and mid-sized businesses.
Choose custom development
Complex, multi-system, industry-specific
Once a process runs across more than four systems, is subject to sector-specific regulation and can't be squeezed into a standard connector, custom development is often cheaper in the long run than stretching a layer that was never designed for the job.
Choose custom development
Multi-tenant and AI-augmented
Industry organisations with multi-tenant role models, or processes in which LLM classification and document AI are interwoven with human approval, call for custom enterprise software that treats these concepts as first-class citizens.
Tools we work with.
We're platform-agnostic. The right choice depends on your existing landscape, the type of processes involved and how much of the management you want your own team to handle.
UiPath, Blue Prism, Automation Anywhere
For screen-scraping flows and legacy applications without a proper API. RPA bots work well for repeatable data entry tasks, but they're brittle when the user interface changes. We use them where they're the only option, and build a proper API layer over them wherever that's possible.
UiPathBlue PrismAutomation Anywhere
Workato, Make, Zapier, Power Automate
iPaaS platforms for SaaS integrations and low-code for lightweight workflow automation. We have senior experience with Workato and Make for mid-sized integration landscapes, and with Microsoft Power Automate for organisations that rely heavily on the Microsoft stack.
WorkatoMakePower AutomateOutSystems
Camunda, Flowable, custom Node/Python
For process engines with BPMN/DMN at their core, we typically choose Camunda or Flowable. Around that we build custom front ends, integrations and rules modules. For multi-tenant industry platforms, AI flows and deep integrations, this is the combination where we deliver the most value.
CamundaFlowableBPMN/DMNNode.jsPython
Compliance and governance.
Process automation almost always involves sensitive data: staff records, financial flows, client communications. Auditability of a process isn't an extra — it's a design decision we build in from sprint one.
- GDPR and privacy by designData minimisation, purpose limitation and data processing agreements built into the process design. A DPIA for every larger automation programme.
- DORA for the financial sectorFor financial institutions, we design processes with DORA-compliant logging, incident reporting and third-party risk management embedded in the process chain.
- NEN 7510 and healthcareIn healthcare, we design process flows that respect the NEN 7510 information security controls: role-based access, encryption and logging at patient level.
- ISO 27001 and BIOFor the public sector and organisations working within an ISO 27001 framework, we deliver processes with the corresponding security controls, logging and risk assessment.
- AI Act complianceFor AI-augmented process automation (LLM classification, document AI), we follow the requirements of the AI Act on risk classification, human-in-the-loop oversight, transparency and logging of model output.
Frequently asked questions.
The questions clients ask before starting an automation project.
What exactly does automating business processes cover?
It is an umbrella term covering a number of disciplines in practice: workflow automation (quotes, invoices, complaints), document automation (contracts, forms, incoming post), RPA (bots in legacy systems without an API), process orchestration via BPM platforms using BPMN and DMN models, SaaS integrations via iPaaS, AI-augmented automation (LLM classification, document AI), data pipelines (ETL and event streaming), and setting up approval and escalation routes. A mature programme almost always combines several of these categories. Pure RPA without integrations is no longer the norm in 2026, and iPaaS alone is too limited for most mid-market organisations.
What is the difference between RPA, BPM and iPaaS?
RPA (UiPath, Blue Prism, Automation Anywhere) imitates human user actions in applications without an API, making it a temporary bridge to systems that do not support integration. BPM (Camunda, Flowable) is a process engine that tracks the status of long-running processes, assigns tasks to people, and orchestrates approvals, escalations and deadlines. iPaaS (Workato, Make, Zapier, Power Automate) connects SaaS applications using ready-made connectors and is best suited to relatively simple event-driven flows. They are not mutually exclusive; in a mature process landscape you will see them side by side for different types of flow, often with a BPM engine as the orchestrator that calls iPaaS and RPA bots.
When should you choose low-code and when custom development?
Low-code (Power Automate, OutSystems, Mendix) suits linear flows built from standard components, a limited number of exceptions and a reasonable volume. Custom development pays off when a process runs across many systems, is subject to industry-specific regulation, must be multi-tenant for a cooperative or industry body, or combines AI components with human decisions. A second signal: once you spend more than forty percent of your time in low-code building workarounds to get around its limitations, you have lost the cost advantage and custom development may well be cheaper. When in doubt, we often start with low-code for the first tier and migrate to custom development if complexity later demands it. That is almost always a healthier sequence than the reverse.
What determines the cost of an automation project?
The biggest cost drivers are: the number of systems to integrate and the quality of their APIs, the level of exceptions and industry-specific regulation, the number of manual approval steps, the requirements for auditability and compliance (GDPR, DORA and NEN 7510 each have their own impact), the choice between platform licences and a custom build, and the extent to which your own team takes over management after go-live. We work with fixed sprint budgets so you can steer scope and investment per iteration, and at the end of each sprint we give an honest estimate of expected ongoing costs. No open ends, no surprises afterwards.
How long before we see results?
A first automated process typically goes live in production after a number of sprints. A mature process landscape with multiple flows, monitoring and ongoing development requires a programme of several sprints and continues thereafter as a programme. We deliberately avoid hard figures in weeks, as these depend heavily on scope, the number of systems involved, your team's availability and the degree of organisational change the process brings with it. What we can promise is that after the first sprint you will have visibility of the first working automation or a tangible part of the chain, not just documentation.
How do we calculate the ROI of process automation?
In the analysis phase we measure each process per step: manual time per transaction, transaction volume per month, error rate and rework costs, throughput time, and the cost of waiting times (think late invoices, delayed quotes). That gives you a baseline. After automation we compare the same metrics over a comparable period. Additional value, such as shorter throughput times, a better customer experience, compliance assurance and scalability without extra staff, we quantify where possible, but these are harder to express in euros. We present the business case on a sound basis rather than as a marketing promise, so you can decide for yourself where the next investment will pay off.
What role does AI play in process automation?
AI is mainly used in three areas: classifying incoming documents (invoice, complaint, contract, permit), extracting structured data from unstructured input such as emails, scans and PDFs, and suggesting follow-up actions to human reviewers based on historical data. We never deploy AI fully autonomously for decisions with a major impact; a human is always kept in the loop, especially for financial, medical or legal decisions. For every AI component we also build in the logging and audit trail that the AI Act requires for risk classification and transparency.
Do you work together with our internal IT department?
Almost always. We transfer knowledge throughout the entire project, not just at the end. We deliver BPMN diagrams, DMN decision tables, API contracts and runbooks so that your own team can manage and further develop the processes. For ongoing management we offer an optional SLA contract with four response-time levels, but we prefer that your team handles primary management while we are available for escalations and larger changes. This way you build your own capability instead of depending on us.
Can you connect to our existing ERP, CRM and HR systems?
As a rule, yes. We have experience with the common ERP suites (SAP, Microsoft Dynamics, Exact, AFAS, Unit4), CRM platforms (Salesforce, HubSpot, Microsoft Dynamics), HR suites (AFAS HR, Visma, Workday) and accounting packages (Exact, Twinfield, Moneybird). For industry-specific systems, such as EHRs in healthcare or specialist applications in logistics, we first look at the available API or integration layer. If there is none, we fall back on structured file exchange or, as a last resort, an RPA bot. We do not make "shadow copies" of your data unless this is strictly necessary for performance.