Automation
Automation and system integration, so data moves by itself
Most companies use five to ten tools that do not talk to each other, so people join them by hand: copying, exporting, importing and watching that nothing gets lost. I connect them into one process that runs by itself and raises a flag when something fails.
Who it is for: For companies with a CRM, an e-shop, invoicing or accounting software, spreadsheets and email, moving data between them by hand. Typically 3–100 people.
- From
- CZK 25,000
- Typical timeline
- 3–4 weeks
- You get
- Running scenarios, alerts, a guide
- Ownership
- You own the scenarios and access
01
This is probably what hurts.
- A new order has to be carried by hand from the e-shop to invoicing and the warehouse.
- Leads from a form end up in email and someone enters them into the CRM when they remember.
- Reports are assembled every week from spreadsheet exports.
- When someone is ill, nobody knows how the process works.
- At peak times mistakes creep in because the steps repeat and nobody checks them.
If you nodded at least twice, it is worth a conversation.
02
What we actually solve.
Typical cases clients bring. Yours may look different; we always start from what you need.
Order → warehouse → invoice
A received order is written to stock automatically, a document is issued and the customer gets a confirmation. If an item is missing, a task is created for a person.
Lead → CRM → task for sales
An enquiry from a form or ad is written to the CRM, enriched with basic data and assigned to a salesperson who gets a Slack or email alert.
Automated reports
An overview of revenue, enquiries or campaign performance assembles itself from your systems and arrives by email or in a sheet at an agreed time.
Reminders and dunning
Overdue payments, expiring contracts or unanswered enquiries trigger a reminder at the right moment, with no one having to remember.
Data synchronisation
Prices, stock, contacts or products stay identical across systems, so the numbers can be trusted.
03
How it works, step by step.
For each step you see what I do, what I need from you and what you hold afterwards. No black box.
- 01
Audit of the current process
Week 1I do
I walk through how data travels today, who does what manually and where errors arise. I check which APIs and connectors your tools offer.
You do
Show the process live and share an overview of the tools you use.
You get
A data-flow map and the order in which automating pays off.
- 02
Workflow design
Week 1I do
I design the scenarios, triggers, rules and failure behaviour. I choose the tool (Make, n8n, custom code) by complexity and running cost.
You do
Approve the design and the exceptions.
You get
An approved design and an estimate of running costs.
- 03
Build
Week 2–3I do
I build the integrations, set up data validation and exception alerts and show finished steps as I go.
You do
Provide accounts and test data.
You get
Working scenarios in test operation.
- 04
Test and go live
Week 3–4I do
I test on real cases including error cases, launch and watch the first days.
You do
Confirm that the results match what you expect.
You get
Production operation and monitoring.
- 05
Handover
Week 4I do
I hand over documentation, access and a short guide to managing or changing the scenarios.
You do
Decide who will watch the scenarios.
You get
Documentation and a short training.
04
What it can look like in practice.
Model situation: an e-shop with four tools
A small e-shop uses a sales platform, accounting software, a stock spreadsheet and Slack. Orders are retyped between them by hand.
Before
- Every order means several manual steps.
- The stock sheet drifts from reality.
- Mistakes show up only when a customer complains.
Process
- A new order triggers the scenario.
- It is written to accounting and deducted from stock.
- Low stock sends a Slack alert.
- The customer gets a confirmation and tracking.
After
- An order passes through without manual work.
- Stock matches reality.
- People handle only what falls outside the norm.
An illustrative scenario, not a specific client and not a promised result. I estimate the real saving in the audit, based on how much manual work the process takes today.
05
What I build with, and why.
- Make and n8n
- Quick, readable scenarios your team can edit later. Make is hosted; n8n can run on your own server.
- APIs, webhooks and custom code
- TypeScript where a ready connector is missing or too limiting.
- The systems you already use
- CRM, e-shop platforms, invoicing, Google Workspace, Slack, email, spreadsheets.
- Validation and alerts
- Bad data stops before it spreads. You hear about exceptions immediately.
What you get at the end.
- Data-flow map and workflow design
- Working integration scenarios
- Data validation and exception alerts
- Documentation and access
- A short training for the owner
- Support during the first weeks of operation
06
What it costs and how long it takes.
from CZK 25,000
Typical timeline: 3–4 weeks
Make, n8n or cloud-service licences are paid directly to the vendors. You get a monthly cost estimate in the design.
Full price listWhat moves the price
- Number of systems to connect
- Quality and availability of their APIs
- Number of exceptions and branches in the process
- Reliability and monitoring requirements
When it does not make sense.
I would rather say so now than have you pay needlessly.
- The process changes every week. Settle it first; otherwise automation keeps being rewritten.
- You do a few steps a month. Doing it by hand costs less than building and maintaining a scenario.
- You want to connect a tool with no interface or export. We check feasibility first so you do not pay needlessly.
07
What people ask most.
Can you connect the tools we already use?
In most cases, yes. I first check the availability of APIs or connectors and the limits of each service and tell you honestly what is and is not possible.
Make, n8n or custom code?
I choose by complexity and running cost. Make and n8n are fast and readable for a team; custom code makes sense for demanding or high-volume work. I am not tied to one tool.
What if one service goes down?
Scenarios expect errors: they stop, record what happened and alert you. When the service recovers, processing can be completed so nothing is lost.
Can I edit the scenarios myself later?
Yes, the scenarios and access are yours. Handover includes documentation and a short training on managing or adapting them.
How big a saving can I expect?
It depends on how much manual work the process takes today. That is why I start with an audit where we work it out. Promising figures up front would be dishonest.
Is it safe to give access to our systems?
I use dedicated accounts with minimal permissions that you can revoke at any time. Credentials are kept in a secure store, not inside the scenarios.
Do you offer maintenance after launch?
Yes. After handover we can agree ongoing care, monitoring and changes, or your team manages the scenarios.
08
Let’s talk it through.
Write a few lines about what you are dealing with. I will reply within 24 hours with a view on whether and how it makes sense, before you commit to anything.