System integration for systems that were never designed to meet

Retyping is an integration too. An expensive one.

Webshop orders someone retypes into the accounting package. An export that runs every Friday and travels by e-mail. Customer data that lives in three systems and is correct in none of them. Every business has integrations; the only question is whether they are made of software or of human patience.

Manual work between systems costs more than hours. It makes the kind of errors that surface at year-end close, and it depends on the one colleague who knows how it is done.

What we do

We build integrations between the systems you already have. Your accounting software to your webshop. Your CRM to your invoicing. Your POS to your inventory. Which package it is does not matter to us: anything with an API, a messaging interface or an export capability can be connected.

Including the hard cases. Some systems do not answer right away, but only after hours or even days. Our integrations wait patiently, lose nothing, and pick the work back up the moment the answer arrives. Systems that do not answer immediately are, for us, simply systems to integrate.

Every integration we deliver keeps a record of what it did. When something goes wrong it can be traced, and our monitoring catches it before you notice it in your administration.

The common combinations are described on the integrations page: accounting and webshop, CRM and your other systems, webshop and inventory and custom API integrations.

What a project looks like

1. Inventory. Which systems, which data, which direction. We request the API documentation for your packages, or dig it up ourselves.
2. Fixed proposal. What the integration does, what it costs, and when it runs. Integrations can be scoped sharply, so here we work with a fixed price.
3. Build and verify. First alongside your current way of working, so you can check the numbers match before the manual work stops.
4. Go-live and monitoring. The integration runs, we watch it. If something gets stuck we fix it, usually before you see it yourself.

We do this work from Ede, the Netherlands, for clients at home and abroad; an integration project rarely requires us to be in your office.

What it costs

As an indication: an integration between two systems with a standard API starts around €500. More involved cases, slow or asynchronous systems, several packages, many exceptions in the process, usually land between €1,500 and €5,000. Always with a fixed scope agreed up front, so the price holds no surprises.

Frequently asked questions

Which systems can you integrate with?

Anything with an API, a messaging interface or an export capability: your accounting software, your CRM, your webshop, your POS system, your ERP. Which package it is does not matter to us. Systems that do not answer right away, sometimes only after hours or days, are integrations we handle as a matter of course.

What does an API integration cost?

As an indication: an integration between two systems with a standard API starts around €500. Integrations with slow or asynchronous systems, or across several systems at once, usually land between €1,500 and €5,000. You get a fixed scope and price up front.

What happens when an integration breaks?

A good integration reports its own failure instead of stopping silently. Our integrations record what they did and where they got to, and we monitor them. If something goes wrong, we see it before you notice it in your books.

Our system sometimes answers only after days. Can you work with that?

Yes. Our integrations wait patiently, lose nothing, and pick the work back up the moment the answer arrives, whether that takes a second or three days. This is exactly the kind of work we specialise in.

Our vendor says no integration is possible. Is that true?

Often not. Many packages do have an API or an export capability, just not a ready-made connector to your other system. That gap is what we build. We will look at it with you, free of charge.

More on how we keep long-running processes reliable is on the agentic workflows page.

Which of your systems should be talking?

Name the packages and what happens by hand today. Within two working days we tell you whether and how they can be connected.