Sales and orders
- orders from your store and Allegro in one place
- confirmations and status updates sent on their own
- orders handed off to production or the courier
- a reminder about an unpaid cart
Copying data between programs, issuing the same documents, assembling the report every Monday. Work that comes back every week can usually be done once and left to a machine. I connect the programs you already use and arrange them so the data moves between them on its own.
Scope
Below are the things people ask about most often. If your task isn't here, tell me about it — one conversation is usually enough to know whether and how it can be handed to a machine.
Examples from real implementations
Everything below runs in my own products and at my clients', continuously, for years.
A motor store sells on its own site and on Allegro at the same time. A sale in one channel immediately removes the item from the other — and the other way round.
The risk of selling something no longer on the shelf disappears.
Two sites pull data from the main store and rebuild themselves after every stock or price change, double-checking every half hour on top of that.
The offer stays current everywhere, without a single click on your side.
Smart-Copy publishes a public API and webhooks, which lets it run in Zapier, n8n and WordPress. Customers wire it into their own processes without my involvement.
Your product starts working with the tools your customers already use.
My servers run dozens of scheduled jobs: database backups with a week of retention, availability checks, domain renewals, reports. Each has a watchdog that reports problems.
You learn about a fault from a notification, before a customer notices it.
Tools
I match the tool to the task and to how long it is meant to run. For simple flows the ready-made platforms come out cheapest, while for jobs meant to last years a custom script pays for itself within a few months.
The largest library of ready-made connections between popular apps. A good fit for simple flows and a quick start. Billed monthly by the number of operations.
A tool I can host on your own server. Suited to elaborate scenarios, and the fee does not grow with the number of operations.
A comfortable visual editor with good support for branches and loops. A solid choice when a process has many conditions.
Code written for one job, run on a server at a set time. The cheapest to maintain for tasks meant to run for years.
I give my recommendation with the quote, along with each option's monthly cost. The choice stays with you.
Integrations
Below are the connections I configure most often. If your program isn't here, it can usually be connected through an API or file exchange — I check that at the quoting stage.
Calculator
Mark how much time the work you want to hand over takes today, and what the automation should do. The calculator works out the savings, the implementation quote and the month the cost pays for itself.
Control
The automation works on your accounts and your server. Nothing passes through middlemen you don't know about.
Every run leaves a trace: what was fetched, what was sent and with what result. You can always check what happened.
If an external system changes its rules or stops responding, I get a notification and fix it before you notice.
The automation can be stopped with a single switch, and the process returns to manual handling with no data lost.
Process
You tell me what you do by hand and how long it takes. Fifteen minutes in, it is usually clear what to automate first.
I write down, step by step, how the work runs today and where the data will flow after the change. You approve it on paper.
Scope, price and deadline. Plus a calculation of how many hours a month you get back.
I set up the connections and test them on a copy of your data, so nothing in your systems is at risk.
The automation runs alongside the current routine and we compare results until everything matches.
Documentation, access and oversight. I adjust the scenarios when your needs or the external systems change.
After launch
You get a drawing of the whole flow and a description of what happens at each step. A new person at the company will understand it without my help.
You see the run history and the results, so you can check at any moment that everything went through.
For the first month after launch I tune and fix as much as needed, within the implementation price.
Monitoring, reaction to changes in external systems and scenario development — from 200 zł a month.
Price
That is the price for one process: mapping it, building the connections, testing on a copy of your data and launching. Elaborate flows tying several systems together usually land between 6,000 and 15,000 zł.
from 3,000 złnet, one-off
What affects the price:
Oversight of running automations costs from 200 zł a month and covers monitoring, reaction to changes in external systems and small scenario adjustments.
Questions
With the one task that eats the most time and repeats every week. We pick it during the first conversation, I implement it first, and only once it is running do we take on the next one. This approach shows the savings immediately and spreads the cost over time.
No. Automation means connecting what you already have. If you work with Subiekt, a Google sheet and a Gmail inbox, those are exactly the three things I connect. Switching systems is a separate decision you make independently.
A single process starts at 3,000 zł net. An elaborate flow tying several systems together with conditions and exceptions usually lands between 6,000 and 15,000 zł. On top of that comes the tool's fee, if we use Zapier or Make.
For a task taking five hours a week at 60 zł per hour, you recover about 1,300 zł a month, so a 3,000 zł implementation pays for itself in under three months. The calculator above runs the numbers for your case.
I get a notification that something stopped working and I fix the scenario. For implementations under my oversight this happens before you notice the problem. Without oversight, you report it to me and I quote the fix separately.
Every run leaves a record of what was fetched and sent, so a mistake can be traced and reversed. Before launch I test everything on a copy of your data, and for the first days the automation runs alongside the manual routine so we can compare results.
Not to use it. You get a diagram, documentation and a view of the run history. If you do have a technical person, I will gladly hand them full access and pass the project over for independent development.
Yes, and increasingly that is the whole point: reading the content of an email, summarizing a document, assigning a case to a category, or drafting a reply based on your materials. I bill this by actual model calls and set limits so the invoice stays predictable.
Related services
Projects rarely stop at one thing — here is the rest of what I do, each with its starting price.
Get a quote
A few sentences are enough: which task keeps coming back every week and roughly how long it takes. I'll reply with a proposal, a quote and a calculation of when it pays for itself — usually the same day.