System integration and BPM processes

Most companies do not need another system. They need the systems they already have to start talking to each other — reliably, with error handling and a record of what happened.

What we do

• Application integration — CRM, ERP, accounting software, payment gateways, marketplaces, data-provider APIs. REST, SOAP, webhooks, files, queues.
• BPM processes — long, multi-step processes (customer activation, reacting to declining activity, confirmations, approvals) modelled in BPMN and run on the Flowable engine. Human tasks land where the team already works — in the existing admin panel, not in yet another tool.
• Data migration — moving data between systems with validation, a discrepancy report and the ability to re-run.
• Custom systems — where off-the-shelf software does not fit the process. We have been doing this since the 1990s, from production planning to cost estimation.

Integration buses and data-flow automation

When the production system — where customers sign up, buy and pay — needs to feed the CRM, ERP and accounting, nobody should be doing it by hand, and not every connection needs to be written from scratch. That is what integration and workflow-automation tools are for. They let information from production systems flow automatically to where it is needed: a new customer appears in the CRM, an order in the ERP, a payment in the accounting system.

We see two classes of tools and pick the one that fits the job, not the other way round:

• Low-code automation — Make, Zapier, n8n. Good for quick flows between SaaS services that already have connectors: form → CRM, new customer → spreadsheet and a notification, invoice → archive. Setting one up takes hours, not weeks, and your team can adjust simple rules themselves. n8n can run on your own server, which matters when data should not leave the company. The limits show at high volume, with systems that have no ready-made connector, and wherever each kind of error needs different handling.
• Integration buses (ESB) and integration platforms — Apache Camel, Talend, MuleSoft. The right choice when volumes are high, the source is a custom system or a database, the integration runs on-premise, or reliability requirements are strict. This is where the problems that low-code tools only reveal in production get solved by design: idempotency (re-running a flow creates no duplicates), retries with proper handling of business errors, ID mapping between systems, and batch processing that does not load the production database.

Often the best answer combines both: the core flow — production system, CRM, accounting — on an integration bus, and small automations around it in a low-code tool.

Our deepest production experience is with Apache Camel. For example: an integration service connecting a SaaS platform's production system with its CRM and QuickBooks — every new customer appears in the CRM on their own, and their payments land in accounting.

How we work

We start with a map of the data flow: which system is the source of truth, what happens when one side does not respond, how retries work. An integration without answers to those questions only works on good days.

Speed comes from not rebuilding the source systems. For example, a BPM engine embedded in an existing admin panel reached production in 4 days, and full integration with the UI took 9 days.