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 generate 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 analysisMake-buy-buildWorkflow & RPADocument AIMid-market & enterprise

Process automation is not 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 if you first describe 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 organisations, cooperatives and scale-ups that have outgrown their Excel phase. This is usually where the gains are greatest: manual quote flows, email ping-pong around invoices, approvals in a shared mailbox, and data that gets retyped into three different systems. Not because the teams are doing it wrong, but because the systems were never designed 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 holds up. We would rather spend an extra week on analysis than three months building plumbing for a process that actually only runs ten times a month.

Three types of process automation.

The umbrella term roughly splits into three flavours. In practice, we combine them: an iPaaS integration that picks up the standard data, a BPM engine for the human approvals, and custom logic for the industry-specific rules.

Integration & data flow

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 via direct API integrations when volume or latency demands it. See also our API and integration approach.

iPaaSWebhooksETLEvent-driven
Workflow & approvals

Process orchestration with a human in the loop

When a process runs through several departments, involves escalations, or requires a four-eyes principle, you need a process engine that tracks the status and assigns tasks to people. Here we work with BPM platforms such as Camunda and Flowable; for industry associations we often build a custom BPM platform with BPMN/DMN as its backbone.

BPMNDMNEscalationAudit trail
Document & data bots

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 click through legacy applications where no API is available. For the entire paper flow we have a separate document workflow service.

UiPathDocument AIOCRLLM classification

What an automation programme delivers.

No standalone reports and no vague transformation story. At the end of the programme you have working, monitored processes plus the documentation to keep developing them yourself.

  • Process landscape mapAn overview of the processes that generate the most volume and pain, quantified in time, errors and lead time. This shows you where to invest next.
  • Make-buy-build advice per processIndependent advice on which process belongs in an iPaaS, which in a BPM engine, which calls for RPA and which need custom development.
  • Working automated processesLive in production, with monitoring dashboards, error handling and escalation routes. No demos or pilots that never get any further.
  • Documentation and runbooksBPMN diagrams, decision tables, API contracts and management guides. Your team can change, extend and troubleshoot on its own.
  • 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 which data.
  • Continuous improvement loopProcess metrics that show where the next gains lie, plus an approach for improving iteratively rather than stopping after a single big bang.

Who we do automation for.

Not every organisation needs custom process automation. Here are four profiles where we make a difference. If you recognise yourself, we'd be glad to talk further.

Mid-market SMEs

Beyond the Excel phase

Organisations with manual quote, order and invoice flows that, with 30+ employees and growing volume, are hitting the limits of spreadsheets and shared mailboxes. The first gains usually come in the quote-to-order chain and the incoming invoice flow.

Trade associations and cooperatives

Multi-tenant flows

Trade associations and cooperatives that need to support the same process chain for dozens of members: member onboarding, expense claims, certification. Here we almost always build custom, because standard platforms can't handle the multi-tenant role model.

Healthcare and public sector

Reducing administrative burden

Healthcare providers and government organisations with heavy administrative flows (intake, referral, claims, permit processing) where GDPR and NEN 7510 play a major role. Standard low-code platforms often get stuck on the compliance requirements.

Multi-BU groups and scale-ups

Scaling beyond the system

Groups with multiple business units that each run the same process differently, and scale-ups growing beyond their first layer of tooling. Both need a process engine that supports variation without management getting out of hand.

How an automation programme works.

1

Process analysis

Together with your team, we map the current state of your most important processes. For each process we record: 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 ranking that lets you decide which process is tackled first.

3

Make-buy-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 to be custom? We're honest when a standard platform is enough. We have no incentive to build everything custom.

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 with us, and so do end users. Over a programme of several sprints, you move from a first process to a mature process landscape.

5

Monitoring and further development

After go-live we keep measuring: which processes deliver, where new bottlenecks appear, which exceptions need human attention. On that basis we plan the next round of improvements. Process automation is an ongoing programme, not a project with an end date.

Concrete use cases.

These are the flows we most often end up with. The list isn't exhaustive: most organisations combine three or four of them, and we build the process landscape around those.

Sales & order

Quote-to-order (CPQ)

From configuration and pricing to quote, contract, order and invoice. Central product logic, a rules engine for discounts, e-signing and an integration with your ERP. We have a dedicated service for this: custom CPQ and product configurator.

CPQPricing rulesE-signingERP sync
Finance & compliance

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 the invoice is sent to for sign-off. Outgoing invoices go via Peppol to government bodies and large customers. Postings are written back to your accounting system automatically.

PeppolOCR + AIVAT validationFour-eyes principle
HR & customer service

HR onboarding, complaint and ticket flows

A new employee triggers an SSO account, payroll registration, IT asset allocation and training invitations: multiple systems, one process. On the customer side: complaints and tickets from email, forms or web chat are classified, routed and monitored against SLAs, and linked to your CRM.

SSO & provisioningPayroll integrationComplaint routingSLA monitoring

When to go custom and when to use a platform.

An honest comparison. For most automation needs, a combination of standard platforms is enough. Custom pays off in four specific situations.

Choose a platform

Standard integrations between SaaS tools

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 a platform

Simple form flows

Simple request flows with linear approval work perfectly well in Microsoft Power Automate or another low-code platform. That's enough for the first layer of process automation in many SME organisations.

Choose custom

Complex, multi-system, industry-specific

When a process runs through more than four systems, is subject to industry-specific regulations and can't be squeezed into a standard connector, custom is often cheaper in the long run than stretching a layer that wasn't built for it.

Choose custom

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-independent. The choice depends on your existing landscape, the type of processes and how much of the management your team wants to handle itself.

RPA

UiPath, Blue Prism, Automation Anywhere

For screen-scraping flows and legacy applications without a decent API. RPA bots work well for repeatable data-entry tasks, but they're brittle when the UI changes. We use them where they're the only option, and build a proper API layer on top wherever possible.

UiPathBlue PrismAutomation Anywhere
iPaaS & low-code

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 run heavily on the Microsoft stack.

WorkatoMakePower AutomateOutSystems
BPM & custom build

Camunda, Flowable, custom in Node/Python

For process engines with BPMN/DMN at the core, we usually choose Camunda or Flowable. Around that we build custom front ends, integrations and rule 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 touches sensitive data: employee records, financial flows, customer communications. The auditability of a process is not an extra — it is a design choice 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 the healthcare contextIn healthcare, we design process flows that respect the NEN 7510 information security controls: role-based access, encryption, patient-level logging.
  • ISO 27001 and BIOFor the public sector and organisations with an ISO 27001 context, we deliver processes with the corresponding controls, logging and risk assessment.
  • AI Act complianceFor AI-augmented process automation (LLM classification, document AI), we follow the AI Act requirements for risk classification, human-in-the-loop, transparency and logging of model output.

Frequently asked questions.

The questions clients ask before we start an automation project.

What does automating business processes actually cover?
It is an umbrella term that covers many disciplines in practice: workflow automation (quotes, invoices, complaints), document automation (contracts, forms, incoming mail), RPA (bots in legacy systems without an API), process orchestration via BPM platforms with 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 project almost always combines several of these categories — pure RPA without integrations is no longer the norm in 2026, and iPaaS-only is too limited for most mid-market organisations.
What is the difference between RPA, BPM and iPaaS?
RPA (UiPath, Blue Prism, Automation Anywhere) mimics 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 we see them side by side for different types of flows, often with a BPM engine as the orchestrator that calls iPaaS and RPA bots.
When do you choose low-code and when custom?
Low-code (Power Automate, OutSystems, Mendix) suits linear flows with standard building blocks, a limited number of exceptions and a reasonable volume. Custom development pays off when a process runs through many systems, is subject to industry-specific regulations, needs to be multi-tenant for a cooperative or trade organisation, or has AI components intertwined with human decisions. A second signal: as soon as you spend more than forty per cent of your time in low-code building workarounds for its limitations, you lose the cost advantage and custom development can work out cheaper. When in doubt, we often start with low-code for the first tier and migrate to custom development if the complexity eventually demands it — that is almost always a healthier order than the other way round.
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 number of exceptions and the extent of sector-specific regulation, the number of human 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 you an honest estimate of the expected follow-on costs — no open-ended commitments, no surprises afterwards.
How long before we see results?
A first automated process usually goes into production after a handful of sprints. A mature process landscape with multiple flows, monitoring and ongoing development takes a programme of several sprints and continues afterwards as an ongoing programme. We deliberately avoid hard week counts — 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 do promise: after the first sprint you will see the first working automation or a tangible partial flow, not just documentation.
How do we calculate the ROI of process automation?
In the analysis phase we measure, per process: manual time per transaction, monthly transaction volume, error rate and recovery costs, lead time and the cost of waiting times (think late invoices, delayed quotes). This gives us a baseline. After automation we compare the same metrics over a comparable period. Additional value — shorter lead times, a better customer experience, compliance assurance, scalability without extra staff — we quantify where possible, but it is harder to express in euros. We present the business case with supporting evidence rather than as a marketing promise, so you can decide for yourself where the next investment will pay off.
What is the role of AI in process automation?
AI is used mainly in three places: 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 use AI fully autonomously for decisions with a major impact — there is always a human 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-category classification and transparency.
Do you work with our internal IT department?
Almost always. We transfer knowledge throughout the entire engagement, not just at the end. We deliver BPMN diagrams, DMN decision tables, API contracts and runbooks so your own team can manage and further develop the processes. For ongoing management we offer an optional SLA contract with four response-time tiers, but we prefer your team to handle primary management, with us available for escalations and larger changes. That way you build your own capability instead of dependency.
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 sector-specific systems — think EHRs in healthcare or specialist applications in logistics — we first look at the available API or integration layer, and if there isn't one, we fall back on structured file exchange or, as a last resort, an RPA bot. We don't make "shadow copies" of your data unless that is strictly necessary for performance.

Talk to us about your process automation.

A no-obligation first conversation of half an hour. Tell us about the processes that cost you more than they deliver, and we'll give you direction on approach, tool choice and a realistic order of automation.

Edit content