Service · Web development

System integration specialist in the Netherlands.

Adviser and implementer for organisations with a growing system landscape. From inventory and architecture to iPaaS selection, custom integrations and long-term management. Vendor-independent, with the code in your own hands, and a team that both thinks along and builds.

Architecture & strategyiPaaS & customMaster dataCompliance overlay

A system integration specialist is something different from an integration builder.

Many organisations have let their stack grow along the way: a CRM for sales, an ERP for finance, three SaaS tools for marketing, a custom tool for operations, and on the fringes some shadow IT from a department that wanted to solve things itself. At some point it stops working as the sum of separate parts.

At that point, an integration between two systems is no longer the question. The question becomes: which landscape do you want in two years, which systems will then be the source for which type of data, how does information flow between those systems, and which layer sits in between to orchestrate and control it? That is the work of a system integration specialist: strategy plus execution, not one or the other.

We do this work for mid-market organisations, scale-ups with a fast-growing stack, post-merger projects where two IT landscapes need to come together, groups with multiple business units each running their own ERP, industry associations, government and the public sector (Common Ground), financial institutions with a multi-vendor stack, and healthcare providers with the familiar EHR–portal–payroll chain.

Our positioning is a deliberate choice. We have no reseller relationships with iPaaS vendors, so the toolchain choice follows from your situation and not from a sales agenda. The code we write goes into your own repository and remains your property — no lock-in, no contractually dependent licences on the work itself. Our team combines builders with consultants, so advice and delivery sit with the same people. We work from Amsterdam with a permanent team, and we deliver pragmatic work: a working integration landscape with the accompanying documentation, not a report that disappears into a drawer. Our approach to smart API integrations describes the delivery side of this work in more detail.

Three ways we take on integration projects.

Depending on the stage your landscape is at, we choose a different starting point. An audit is something different from implementation, and managed support is something else again from an embedded engineer.

Discovery project · fixed sprint budget

Integration audit and roadmap

We map your entire systems landscape: sources, data flows, integrations, field-level ownership, and where the pain is. From that follows an architecture choice (point-to-point, hub-and-spoke, event-driven) and a multi-year roadmap with priorities. Not a two-hundred-page report — a working document your team can run with.

InventoryArchitectureToolchain selectionRoadmap
Implementation project · iterative sprints

Building the integration landscape

The hands-on work: integrations, data pipelines, event streams, master data management, monitoring. We use iPaaS where it fits (Workato, Make, Boomi, MuleSoft, Frends, Zapier for lighter flows) and build custom where the specifics demand it. For data volumes, ETL via dbt, Airflow or Fivetran. For event-driven architectures, Kafka or Confluent. The choice depends on your stack, not on our preference.

iPaaSETLEvent streamingMDM
Ongoing support or embedded engineer

Managed integrations or an embedded integration engineer

Two models for the long term. Managed integrations means we keep managing, monitoring and further developing your integration landscape, and keep it compliant. An embedded integration engineer is one of our people who becomes part of your team — contributing to architecture, building alongside you and passing knowledge on to your own people. Both models scale up and down.

MonitoringOngoing developmentKnowledge transferCompliance

What you're left with.

A working integration landscape, under your control, with a team that knows it in detail. Vendor-independent, code in your own repo, and an audit trail you can rely on.

Over the past few years we've integrated landscapes in manufacturing, healthcare, financial services, agri-food, recruitment and the public sector. The patterns differ; the work doesn't fundamentally.

  • Architecture documentA workable overview of your landscape: systems, integrations, master data per field, owners, and the chosen integration style per project.
  • Working integrations in productionThe actual implementation for each project — iPaaS flows, custom services or event streams. Including retry logic, dead-letter queues and alerting.
  • Master data governanceFor each core domain (customer, product, order, employee), a chosen source of truth, a synchronisation strategy and the agreements that go with it.
  • Compliance overlayGDPR flows per dataset, DORA for financial services, NIS2 for essential services, NEN 7510 for healthcare, BIO for the public sector, and the evidence needed for audits.
  • Observability stackMonitoring of all your integrations in one place, with an audit trail showing what was synchronised, when, by whom and with what result.
  • Knowledge transfer to your teamDocumentation, runbooks and sessions with your IT and data people, so your team can carry on without being tied to us.

When you need a system integration specialist.

A few patterns in which we support organisations. If you recognise one of these situations, we'd be glad to talk further.

Stack fragmentation

Five or more SaaS tools side by side

You've reached the mid-market stage where several tools overlap, the same customer data lives in multiple places, and nobody can say which system is the source of truth. Sales, marketing and operations are working from different versions of the truth.

Post-merger

Combining two IT landscapes

After an acquisition or merger, two complete stacks sit side by side. The question isn't only which systems stay, but also how data will flow between them until the migration is complete, and that usually takes longer than expected.

Group structure

Business units with their own ERP and CRM

A group in which every operating company has its own systems, but which still needs group-level reporting, consolidation and shared services. The integration layer becomes the place where the group comes together.

Scale-up

Stack growing faster than the IT team

A fast-growing organisation in which every department adds tools that don't talk to each other. For the IT team, continuously building integrations is no longer something that can be done on the side; it needs a strategy and a dedicated team alongside it.

Industry bodies and public sector

Cooperatives or government bodies with multiple members

Industry organisations with affiliated members, cooperatives with many participants, or government bodies that want to open up data under the Common Ground principle without central storage. The integration layer is then the real product.

Regulated sectors

Financial services, healthcare or energy

Financial institutions with a multi-vendor stack and DORA requirements. Healthcare organisations that need to integrate their EHR, patient portal and payroll in a NEN 7510-compliant way. Energy and grid operators with BIO and NIS2 requirements. Compliance is then a design variable, not an afterthought.

How an engagement typically runs.

1

Introduction

An initial conversation in which we get to know your landscape, your growth stage and the reason for the engagement. No sales pitch: we check whether there is a match in working style and in the substance of the challenge.

2

Integration audit

A discovery phase of a few sprints in which we map the system landscape: which systems, which data flows, which integrations, which shadow IT, and where the pain points are. We interview key people from IT, the business and compliance. At the end we deliver a working document with an architecture recommendation.

3

Roadmap and toolchain selection

Based on the audit, we choose an approach for each integration: iPaaS for what is lightweight and standard, custom development for the specific work, ETL for data volume, event streaming for real time. The result is a multi-year roadmap with priorities and dependencies. In our knowledge base you can read more about the trade-off between direct APIs and an integration platform.

4

Implementation in sprints

We build iteratively, one integration at a time. Every sprint delivers something that works, with monitoring, retry logic and an audit trail from the start. Your team works alongside us: we stand next to you, not in front of you. Alongside the build, we also work on master data governance and the compliance overlay.

5

Managed service or embedded engineer

After go-live, you choose: managed integrations, where we keep looking after the landscape, or an embedded integration engineer who works as part of your team. Both models scale up and down as your landscape matures and your own team can take on more.

6

Ongoing development

An integration landscape is never finished. Systems are added, systems are retired, business logic changes, compliance requirements get stricter. We keep the overview, flag when an integration needs revisiting, and monitor the health of the landscape as a whole. For your own team, that means a fixed point of contact who knows the landscape, so you don't have to hold the full picture in your head.

Frequently asked questions.

Questions clients ask before starting a project.

What exactly does a systems integration specialist do?
A system integration specialist is not just someone who builds individual integrations. The work covers mapping your system landscape, choosing an integration strategy (direct API, iPaaS, ESB, event-driven or hybrid), architecture choices (point-to-point, hub-and-spoke), toolchain selection between iPaaS vendors and custom builds, the actual implementation, master data management, a compliance overlay (GDPR, DORA, NIS2, NEN 7510), observability and knowledge transfer to your own team. It is strategy plus execution, not one or the other.
How does this differ from an iPaaS vendor itself?
An iPaaS vendor (Workato, MuleSoft, Boomi, Frends, Make) supplies a platform. We are vendor-independent and choose the right tool for each situation: sometimes that is one of those platforms, sometimes ETL via dbt or Airflow, sometimes event streaming via Kafka, sometimes custom code. An iPaaS vendor has a commercial interest in putting more flows on its platform; we have a commercial interest in a landscape that works for you. On top of that, iPaaS tools have fundamental limitations, and then custom work is needed alongside them.
What does vendor-independent mean in practice?
We have no reseller deals with iPaaS suppliers, no kickbacks, and no partner status that steers us towards a particular platform. That means that if your situation calls for Frends because you run on Microsoft, or Workato because you are strongly SaaS-oriented, or custom code because the business logic is too specific, we make that choice in your interest. We document the trade-offs so you can see for yourself why we favour one direction.
When do you choose iPaaS and when custom?
iPaaS is strong for fairly standard SaaS-to-SaaS integrations, for business users who want to maintain flows themselves, and for lighter data flows. Custom becomes attractive when business logic is complex, when performance or latency matters, when you have large data volumes, when iPaaS licence costs at some point exceed the cost of building, or when you want to weave an integration deeply into an existing system. Almost every landscape we work in is a mix, and that is usually the right mix.
Roughly what does an integration project cost?
The cost depends on the number of systems, the number of integrations, the complexity of the business logic, the compliance regime and the choice of toolchain. An audit is usually a well-defined piece of work with a fixed scope. For implementation we use sprint budgets, so you stay in control of what we take on each period. In an initial conversation we give an order of magnitude based on what you describe, without having to commit to an exact figure before we know your landscape.
How does a project start in practice?
Almost always with an audit. Not because it sells, but because otherwise we cannot know which approach fits. In the audit we interview key people from IT, the business and compliance, map the landscape and propose an architecture. Only then do we decide together which integrations to tackle first and in what order. Our integration pages give an idea of the kinds of integrations we typically build.
How do you handle GDPR and DORA in the integration layer?
The integration layer is precisely where personal data and financial data flow through your landscape, so it is where GDPR and DORA take shape in practice. For each data flow we document which data is involved, which legal basis applies, how long it is retained and who can see it. For DORA-regulated organisations we record operational resilience: monitoring, incident response, third-party risk and exit strategies. We work alongside your DPO, security officer or CISO; we do not replace those roles.
How does this compare with the Big 4 consultancies?
Accenture, Capgemini and similar firms mainly work with enterprise organisations and deliver large-scale programmes. We focus on mid-market, scale-up and specialty organisations: smaller teams, shorter lines of communication and a stronger build component alongside advice. For an organisation with ten integrations, a Big 4 engagement is often overkill; for a programme worth tens of millions, we are not the right partner. The work we take on sits between those extremes. We see ourselves as an IT modernisation partner that actually builds.
How does your approach differ from a staffing agency or freelancer?
A staffing agency supplies individual engineers, who often rotate out again after a few months. A freelancer is one person with no team around them. We provide a team that stays involved with an engagement for the long term: the same architect who carries out the audit stays involved in implementation and management. That gives continuity in knowledge and in accountability. For your team, it means you don't have to explain every two months why an earlier design decision was made.
Which iPaaS platforms and tools do you know?
For iPaaS we work with Workato, MuleSoft, Boomi, Frends (a Dutch player), Make and Zapier. For ETL and data orchestration we use dbt, Airflow and Fivetran. For event streaming, Kafka and Confluent. For master data management, Reltio or custom MDM depending on scale. For observability, Datadog, New Relic or your cloud provider's own monitoring stack. We have no fixed preference, but we do have firm opinions per situation, which we share openly in the audit phase.

Talk to us about your system landscape.

A no-obligation introductory call of half an hour. You tell us about your stack, your growth stage and what prompted you to get in touch. We ask questions, sketch a possible approach and give you direction you can use, even if we don't end up working together.

Edit content