Service · Software development

Data integration consulting for fragmented data landscapes.

We advise on and build data integrations. From APIs and ETL pipelines to iPaaS choices, data warehouses and streaming architectures. Pragmatic advice, followed by working integrations, with no vendor dogma.

Data integration is much broader than API integrations.

Many providers sell "integration" as if it were purely about linking two systems via a REST API. That is one flavour of data integration, but certainly not the only one. A mature integration approach covers synchronous API integrations for real-time use cases, batch ETL for nightly data warehouse loads, streaming architectures for data in motion, file-based drops via SFTP for partners who have no other option, and iPaaS platforms that bring all those patterns together under one dashboard.

Above that sits the strategic level: which data lives where, what the source of truth is, which quality issues block consolidation, and which master data management approach suits the organisation. We guide that strategic level and build the implementation. Also read about our approach to smart API integrations if you are looking specifically for the tactical side: real-time integrations between SaaS systems.

What sets us apart from pure consultancy firms: we don't hand you a PowerPoint that you then have to execute yourself. We design the architecture and build the pipelines, configure the warehouse, model the dbt layer, or select an iPaaS platform and set up the first flows. No black-box handover, no "advice delivered, good luck".

What data integration consulting involves in practice.

Discovery
Mapping sources, targets and data flows
Architecture
Choosing per use case: API, ETL, streaming, iPaaS
Implementation
Pipelines, integrations or platform configuration
Governance
Monitoring, data quality and ownership per flow

Three types of data integration engagement.

Depending on where your organisation stands: fragmented with no overview, running on an iPaaS that is reaching its limits, or ready for a serious data warehouse.

Engagement 01

Integration architecture and vendor selection

For organisations without a clear approach

You have ten SaaS tools that barely talk to each other, if at all. We map the landscape and choose the right pattern per use case (real-time API, nightly batch, event-driven streaming or file-based), and advise on build vs buy: do we build point-to-point integrations, choose an iPaaS platform such as MuleSoft, Boomi, Workato or Azure Logic Apps, or build a custom middleware layer? An independent assessment based on data volumes, latency requirements, management capacity and TCO. We don't represent any platform: our profit is in the solution, not the licence.

Landscape auditPattern selectioniPaaS comparisonTCO analysis
Engagement 02

Custom integrations and middleware

For industry-specific flows that off-the-shelf tools can't handle

When iPaaS platforms reach their limits — for example with high volumes, industry-specific messaging protocols or complex transformation logic — we build custom integrations. Real-time integrations between custom ERP systems, financial platforms, production MES or foreign suppliers with idiosyncratic formats. Custom middleware with proper logging, retry mechanisms, idempotency and version management. Suitable for organisations that have already considered an iPaaS platform and dropped out over pricing or expressiveness.

Custom middlewareEvent-drivenIndustry protocolsIdempotent flows
Engagement 03

Data warehouse and analytics foundation

For those who want to become data-driven

You want proper reporting across the whole organisation, but your figures come from six different systems that each claim their own truth. We build a data warehouse on Snowflake, BigQuery or Redshift, set up ETL pipelines from all your sources, model the data with dbt and lay the foundation for your KPI dashboards. This includes attention to data quality, master data management, historisation and governance. For some clients that also means a data lake on S3 or Delta Lake as a landing zone for raw data and machine learning use cases.

Snowflake / BigQuerydbt modellingData lakeMDM & quality

What you take away from an engagement.

Not loose pieces of advice, but working integrations plus the documentation and runbooks to keep them running.

Integration blueprint

For each data flow, the choice (API, ETL, streaming, file) justified by latency, volume and cost.

Working pipelines

Configured iPaaS flows, custom middleware or dbt models, in production and staging.

Monitoring & alerting

Health checks, error alerting and data quality rules on critical flows.

Runbook and docs

Who owns what, what to do when something fails, how to roll out a change.

Management (optional)

Monitoring, incident handling, ongoing development and quarterly reviews of data quality.

When data integration consulting really makes a difference.

Four patterns in which we most often get involved with mid-market and larger organisations.

Fragmented SaaS landscape

Ten tools that don't talk to each other

Over the past few years you have bought separate SaaS tools: CRM, marketing automation, helpdesk, e-commerce, ERP, HR. Each department works in its own system, nobody has the full picture, and manual Excel bridges just about hold everything together.

Legacy replacement

From monolith to modern via an integration layer

You're replacing an old core system, but you can't do it in one big bang. An integration layer between old and new makes phased migration possible. See also our approach to enterprise software development, where this pattern often appears.

Reporting pressure

CSRD, ESG or management reporting

You need to report on matters whose data is spread across financial, operational and HR systems. Without a central warehouse, every report remains a manual exercise. We build the pipelines and the data model to make reporting repeatable.

Multi-site

Groups with fragmented administrations

Different operating companies, countries or sites each run on their own systems or versions. Consolidated insight is missing. We design an approach that preserves local autonomy while letting the group steer on a single set of figures.

How we differ from pure data consultancies.

There are several firms that call themselves data integration consultants. Broadly, they fall into two camps. On one side are strategic advisory firms that deliver excellent slides on data strategy, governance frameworks and data maturity models, but don't build anything themselves. On the other side are implementation partners for one specific platform: a MuleSoft shop, a Boomi partner, or a Snowflake implementation firm. They have commercial incentives to sell their tooling, even when it isn't the best fit.

We deliberately sit in the middle. We have no platform partnerships that earn us revenue or margin. Our profit comes purely from the engagement itself. That means we can advise honestly: for some clients an iPaaS is the right choice, for others point-to-point or custom middleware. For one organisation Snowflake is overkill and PostgreSQL with good modelling is enough; for another, a data lakehouse on Databricks or Delta Lake is exactly the answer.

And crucially: because we build the pipelines ourselves, we know where the complexity hides in quotes and vendor claims. We recognise which "out-of-the-box" iPaaS connector takes three weeks of custom work in practice. We know which warehouse can actually handle which data volumes. Advice that grows alongside the implementation stays realistic, and therefore sharper.

How a data integration engagement works.

01Introduction→ 02Discovery→ 03Architecture→ 04Build & run
First conversation

Introduction

Which systems, which pain points, which use cases. No obligation.

Workshops & interviews

Discovery

Source inventory, data volume measurement, quality check, ownership per data flow.

Document & decisions

Architecture choice

The right approach for each use case. Build vs buy, iPaaS shortlist, warehouse choice.

Sprints & ongoing

Build & run

First flows live within a few sprints, then phased expansion plus maintenance.

Approaches we often combine.

No organisation needs just one type of integration. In practice, we combine several patterns per engagement. We use real-time API integrations where transactions need to go through immediately, such as a payment that must update the order status, or a lead that must land in the CRM straight away. We choose batch ETL where a latency of hours is fine, such as overnight financial consolidation or filling a warehouse from operational systems.

We use streaming and event-driven architectures (Kafka, RabbitMQ, Google Pub/Sub, AWS Kinesis) when data in motion is essential: events that must serve multiple consumers at once, or organisations looking to evolve towards a true event-driven architecture. File-based integrations via SFTP, EDI or CSV drops remain indispensable for partners, especially in logistics, financial services and government, who simply can't or won't work any other way.

At the strategic level, we advise on iPaaS platforms such as MuleSoft, Boomi, Workato and Azure Logic Apps: when they are worth their licence costs, and when they are not. We advise on API-first refactoring, in which a monolithic legacy application is gradually given a modern API layer, so that new applications and integrations come in through controlled endpoints. And we advise on master data management and data quality, because the most advanced pipeline solves nothing if the source systems use different customer numbers and product codes.

Technology we work with.

No dogma about a single platform. We choose what fits each situation based on volume, latency, management capacity and cost.

iPaaS & middleware
MuleSoftBoomiWorkatoAzure Logic Appsn8nCustom middleware
Warehouse & lake
SnowflakeBigQueryRedshiftPostgreSQLDelta LakeS3 + Athenadbt
Streaming & messaging
KafkaRabbitMQGoogle Pub/SubAWS KinesisWebhooksEDI / SFTP

Frequently asked questions about data integration consulting.

What is the difference between API integration and data integration?
API integration is one of the patterns within data integration. An API integration is usually synchronous and real-time: system A asks system B for something and waits for the answer. Data integration is a broader term that also covers batch ETL (nightly data loads), streaming (events via Kafka or Pub/Sub), file-based exchange (CSV/EDI/JSON via SFTP), and data warehousing (consolidating multiple sources in one place). Which pattern is the right one depends on latency requirements, data volume and how many systems are involved. See also our separate page on smart API integrations for the tactical side.
Do you replace iPaaS platforms such as MuleSoft or Boomi?
No, and that wouldn't be honest advice either. For many organisations, iPaaS platforms are an excellent choice: a standardised way to manage integrations, with reusable connectors, an audit trail and monitoring out of the box. We guide the choice between platforms, configure the flows and give independent advice on when iPaaS is the right investment and when it is not. We only build custom middleware where iPaaS platforms hit technical or commercial limits.
When do we choose iPaaS and when custom middleware?
iPaaS suits organisations with many relatively standard integrations between well-known SaaS systems, a moderate data volume, and a wish to hand management to a dedicated team of integration developers. Custom middleware is a better fit for high-volume situations, industry-specific messaging protocols (EDI, Peppol, HL7), highly complex transformation logic, or organisations that cannot or do not want to bear the licence costs of iPaaS. We often combine the two: iPaaS for the standard integrations, custom where needed.
Which data warehouse should we choose: Snowflake, BigQuery or Redshift?
There is no universal answer. Snowflake offers the most cloud-agnostic experience and is strong for workloads with many short-running queries. BigQuery integrates best within Google Cloud and excels at serverless and pay-per-query. Redshift fits best within AWS stacks and with predictable workloads. For smaller organisations, a well-modelled PostgreSQL is sometimes enough: you don't always need a warehouse. The choice depends on your existing cloud stack, data volumes, query patterns and budget. We make this assessment independently; we earn nothing from the licence.
Real-time or batch: which is the right choice for us?
Real-time is more expensive, more complex and harder to manage. It is only the right choice if the business case justifies it: an order status that must update within seconds because customers would otherwise call, fraud detection that cannot wait until midnight, a personalised experience that has to work at the moment of interaction. For a great many use cases, batch (nightly ETL, for example) is simpler, more robust and cheaper. We advise on each data flow individually and don't try to make everything real-time just because it sounds "modern".
What determines the cost of a data integration project?
The number and complexity of source systems, the chosen architecture (iPaaS licence costs, warehouse costs, custom build effort), the data volumes and the amount of data quality work required. It also depends on whether there are existing integrations we can reuse or whether we are starting from scratch. A well-defined integration between two systems is a different conversation from an organisation-wide data platform foundation with dbt modelling. After the discovery phase, we give you a substantiated scope estimate. We don't publish "from" prices on the website, because in practice the range is too wide to communicate honestly.
Do you combine consulting with actual implementation?
Yes, that is a deliberate choice and what sets us apart from pure consultancy firms. We don't just write the architecture and the roadmap; we also build the pipelines, configure the iPaaS platform, write the dbt models or set up the streaming architecture. That keeps our advice sharp, because we are directly confronted with the assumptions we make. For organisations that would rather have an external party do the build, we can also act purely as an adviser and vendor management partner, guiding a third party that handles the implementation.
How long does a project like this typically take?
A well-defined discovery with an integration blueprint is a short engagement of a few weeks. We then deliver the first working integrations within a few sprints. A full data platform with a warehouse, modelling and multiple integration flows is a project of several sprints, followed by an ongoing management and further development phase. We don't make firm timeline promises before we know the scope, as that would be irresponsible towards both sides.
Do you work with our existing IT suppliers?
Almost always. We are not out to replace what works. We often advise making further use of existing iPaaS licences or warehouse investments rather than replacing them. Collaboration with your own team and existing suppliers is part of almost every project. We see our role as a sounding board and catalyst, not as the sole ruler of your data landscape. For the broader strategic context, we often work from our role as a digital transformation partner.

Talk to us about your data integration.

A no-obligation conversation of about half an hour. We listen to your situation (which systems, which pain points, which ambitions) and give you direction. Even if the outcome is that another platform or provider is a better fit.

A complementary perspective on this topic can be found on applatenmaken.com: Building data integration software.

Edit content