Systems that don't talk to each other, bridged by APIs and middleware.
Rewriting is not always the right move. Often the real problem is that current systems do not talk to each other: the ERP does not see e-commerce, the CRM does not see the warehouse, the production app lives in a silo. We build middleware and APIs that bridge the gap, without touching the existing systems.
What happens today.
Italian companies typically have 3-7 software systems in production, built by different vendors at different times: 2000s ERP, more recent CRM, modern e-commerce, vertical warehouse system, production software (MES). The problem is rarely the quality of each individual system: it is that they do not talk to each other.
Rewriting everything into a single ERP is too expensive and risky. The pragmatic path is middleware: an API layer that translates between systems, keeps data consistent (e.g. a single customer master), and enables cross-system workflows (e.g. e-commerce order → warehouse reservation → production order → invoice).
Not every legacy system has to be replaced. Most of them just want to be heard by the ones next door.
The solution, broken into parts.
-
Mapping of missing integrations
We map existing systems, identify the data flows that are not automatic today (and that travel via email, CSV files, copy-paste), and prioritize the ones with the largest operational impact.
-
Middleware + API gateway
We build a middleware layer (event-driven or request-response depending on the case) that translates between systems. Each system exposes its APIs; the middleware orchestrates the flows and handles error cases.
-
Monitoring + recovery
Central dashboard showing the state of all flows. Alerts on errors, automatic retry, low-confidence case handling. Structured audit trail of every cross-system transaction.
The typical profiles who benefit.
-
Companies with e-commerce + ERP that 'don't talk'
E-commerce is modern (Shopify, WooCommerce, Magento), the ERP is legacy or vertical. Today orders are re-entered by hand into the ERP (or via overnight CSV imports). The middleware automates the flow.
-
Manufacturing with separate ERP + MES + warehouse
ERP for planning, MES for production, warehouse software for logistics. Historically built separately, today they need to be synchronized. The middleware orchestrates the cross-system flows.
Transparency on what the client does.
Before we start we need a few accesses and decisions. All reasonable, no surprise asks.
-
System access
- API documentation of current systems (or access to vendors to obtain it)
- Test accounts and staging environments
-
Operational decisions
- Priority list of cross-system flows to automate
- Error-case policy (rollback, retry, human escalation)
- Latency constraints (real-time vs nightly batch)
Indicative numbers, not quotes.
- TIME
- First integrated flow in 4-8 weeks. Full middleware setup in 4-9 months depending on the number of systems and flows.
- COST
- Range €25,000-150,000 depending on complexity.
- MODEL
- Fixed milestones per flow. Time & material possible for subsequent evolutions.
Indicative numbers. For an accurate quote, let's talk.
Answers to the most common questions.
Our current systems have no API. How do you integrate them?
Three possible approaches: (1) build custom APIs on top of the legacy system if we have database access (safe read); (2) scraping/automation for cases without API (frequent with old software); (3) file-based integration (CSV, XML) for systems with no interface at all. The first is preferable, the third is a last resort but it works.
What happens if one of the systems goes down?
The middleware is designed with resilience: persistent queues, automatic retry, alert if the problem persists. If a system is down for hours, queued messages accumulate and are processed when it comes back up. No data loss, but higher latency on the flows that depend on the down system.
Can we use the middleware to later replace a legacy system?
Yes, very common scenario. The middleware becomes the stable "access point"; underneath, we can replace a legacy system with another (custom or commercial) without the other systems noticing. It is the first step of a multi-year progressive migration.
Recognize your case?
Write a couple of lines about your context. We'll reply within 24-48 hours with an initial assessment and a first orientation on time and cost.
Let's talk