Service
Connecting the systems that do not talk to each other
Most companies do not have too few tools, they have disconnected tools. The thing acting as the cable between them is a person. That is fixable.
What it solves
What system integration will do for you
- 01
E-shop and invoicing
An order creates the document, the document is matched to the payment, the customer gets what they should, without you touching it.
- 02
CRM and email
An enquiry from the website lands in the CRM with its context, not in a crowded inbox. The history of the conversation sits with the contact.
- 03
Stock and reporting
Levels and movements are written through to wherever you need to see them, in the same shape and at the same time.
- 04
Forms, bookings, payments
The website collects data and passes it on into your systems, instead of generating more email for you to retype.
What it runs on
What it will run on
Where an official API exists, I use it. Where it does not, I look for the most stable route available, sometimes a script of my own, and I tell you up front what that means for the future.
Tools
REST API · n8n · Make · Python · Google Workspace · webhooks · CSV and XML exports
What it costs
Not VAT registered, so these prices are final.
The price and what drives it
| Item | Price |
|---|---|
| System integrationI do not publish a price for system integration. The scope varies with how many systems are being joined and how open they are, so a number on the website would be a guess, not a price. It comes out of the analysis and then it does not change. |
The consultation is free. The analysis starts at 10,000 CZK. With integrations the analysis matters especially, because the price is set by what each side can do, not by how many systems there are.
How long it takes
The timeline and where it comes from
Connecting two tools with a decent API tends to be a matter of a few weeks. Where there is no API, or where synchronisation has to run both ways, count on a month or longer.
Common questions
Common questions: system integration
- 01What if one of the systems has no API?
- I solve it another way, for instance through a scheduled export, through email or through browser automation. It is more fragile than an API, so I tell you in advance what the limits are and what happens if the supplier changes something.
- 02Is there a risk that data gets duplicated or overwritten?
- That is the main risk in integration, which is why the analysis decides which system is the authority for which piece of information. Without that decision I do not build the integration.
- 03Can it synchronise in both directions?
- Yes, but it is considerably harder than one direction and it does not always pay off. Often one direction plus an exception for a few fields is enough. I recommend based on how you actually work with the data.
- 04What if we replace one of the tools later?
- I build integrations in parts, so that one side can be swapped without rebuilding everything. The swap is then handled under support or as a separate smaller job.
Get in touch
Free consultation, up to 30 minutes.
Tell me what still runs by hand
Send me a few sentences about what slows you down most. I will tell you whether it can be automated and how.