System integration
Most businesses do not have a software gap, they have a translation gap: the shop, the warehouse, the CRM and the accounting system all know the same order under four different names. I connect them so each number is maintained in exactly one place.
What I connect
Anything with an interface, and a fair amount that officially has none.
- online shop and inventory
- CRM and accounting
- ERP and warehouse
- forms, email and helpdesk
- payment providers and invoicing
- legacy systems without a modern API
Why integrations fail
Almost never on day one. Almost always on what happens afterwards.
- nobody notices when the sync stops
- one edge case topples the whole run
- credentials expire silently
- duplicates appear after every restart
- two systems, two truths, no tiebreaker
- nobody in-house understands the setup
How I work
The one connection that removes the most manual work first, then the next.
- inventory of the systems involved
- one source of truth per fact
- first connection tested on real data
- error handling and retries built in
- monitoring that speaks up on its own
- documentation and handover
Working languages: English and Czech
I work from Czechia for clients across Europe and further out. Everything runs in English — calls, documentation and handover — or in Czech if that suits you better. Time zone is CET, which overlaps a normal working day almost everywhere in Europe and the morning in the US.
FAQ
- What if our legacy system has no API?
- There is almost always another route: a file export, direct database access, a scheduled report by email. Less elegant than a real interface, but reliable. I look at what the system actually offers before promising anything.
- What happens when a transfer fails?
- Every connection I build retries on failure, logs what happened, and raises an alert when it stays stuck. A silent failure is worse than a loud one, because it only surfaces once weeks of data are missing.
- Do you build this into our systems directly?
- Not if it can be avoided. The connection runs as its own layer between your systems, usually in n8n. That keeps every system independently upgradeable without breaking the integration, and it means you are not locked to me.
- How long does one integration take?
- A single, clearly scoped connection is typically one to three weeks. What drives it is not data volume but how well the systems are documented and how many edge cases your operation has.
Which two systems do not talk to each other?
Name the two where somebody retypes data today. I will tell you whether connecting them pays for itself, and if it does not, I will tell you that too.
Get in touch