Automation & integrations
I'll build you custom middleware that connects your CRM, warehouse, accounting and legacy systems. Data flows on its own, an event in one system triggers actions in all the others. People handle only the exceptions.
Who it makes sense for
- Your team re-types data between two or more systems by hand
- Re-typing errors cause delays, claims or customs problems
- Growing volume means hiring more people just for admin work
What you get
- Event-driven orchestration: event → validation → writes to downstream systems
- API connections; a safe RPA layer for closed software
- An exceptions dashboard, the team sees only cases that need a decision
- Monitoring and alerting; I know about an integration outage before you do
What it looks like in production
Monitoring dashboard preview (illustrative data).
What gets connected most often
Almost every job is different, but the same three pairings keep coming back.
Online shop or order portal and ERP
An order lands in the shop and has to appear in stock, in accounting and with the courier. Without integration somebody retypes it, or it gets handled by a spreadsheet export that eventually gets forgotten. An integration layer does it in under a minute and asks when a case is ambiguous.
CRM and invoicing
A closed deal should generate a proforma invoice, the status should change once it is paid, and the salesperson should get a notification. Three systems, three places somebody watches by hand today.
Legacy system with no API
Accounting or production software that cannot be changed and nobody wants to replace. There you can build a layer that works with it the way a person would, only reliably and at night. Not elegant, but it works and it is cheaper than a migration.
When I will talk you out of it
- When configuration would fix it. Plenty of systems do more than their users realise. Before I build middleware, I check whether it can simply be switched on.
- When you are about to change the system. Integrating something that will be gone in six months is wasted budget. Wait and do it once.
- Under a few dozen cases a day. Retyping twenty rows a week will not pay to automate. I will say so up front.
- When nobody knows what the process should look like. Automating chaos produces faster chaos. The process has to be described first, and I can help with that too.
Parameters
FAQ
Our system has no API. Is that a problem?+
No. For closed software I deploy a safe RPA layer that works with the system like a human would, just reliably and around the clock. Once an API appears, I swap the layer out.
What happens when the pipeline goes down?+
Every transaction is idempotent and the queue catches up on its own after an outage. Monitoring alerts me immediately; a response SLA is part of ongoing care.
What does connecting two systems cost?+
From CZK 25,000 for one bounded integration, delivered in 3 to 4 weeks. The price is driven mainly by whether both systems have a usable API, how many event types flow across, and what should happen with exceptions. Full pricing is on a separate page.
Do we have to change our ERP or accounting software?+
No, and that is the point of this service. The integration layer sits on top of what you have and talks to it over APIs. For software without an API an RPA layer works. Replacing an ERP just to make two systems talk is almost always a needlessly expensive route, as I write in Automation without replacing systems.
Who runs it after you build it and leave?+
You do, because after handover and final payment you have the code, the documentation and the access. Handover includes a walkthrough and a description of what to do during an outage. If you want someone else watching it, we can agree on ongoing care, but it is not a condition and you are not dependent on me.
Related
- AI automation, when the input cannot be described by a rule
- Data, RAG & backend, when search over company documents is part of it
- Automation without replacing systems, what middleware can do
- Pricing, prices and lead times in one place
Send me two systems you re-type data between today, and I'll write back with how I'd connect them.
Write to me, I'll reply within hours.