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.