You have hit the no-code ceiling
The Zap works until it needs a loop, a lookup table, a real retry or a 900-step run, and then the task bill grows faster than the value. Rebuilt on self-hosted n8n or as a small service, the per-task meter stops.
Business process automation is the work of taking the manual steps between the systems you already run — CRM, ERP, accounting, marketplaces, spreadsheets — and replacing them with APIs, webhooks and scheduled jobs. One engineer scopes it and builds it: in self-hosted n8n where a workflow is enough, in Python or TypeScript where it is not. Your existing software stays where it is.
The Zap works until it needs a loop, a lookup table, a real retry or a 900-step run, and then the task bill grows faster than the value. Rebuilt on self-hosted n8n or as a small service, the per-task meter stops.
Someone re-keys an order from the store into the ERP, then into a spreadsheet, then into the invoicing tool. Four entries of the same data, four places it can drift, and one person who cannot take a week off.
A vendor changes an endpoint, the sync stops, and nobody notices until month-end numbers refuse to reconcile. Every integration we ship carries a health check and an alert, so a failure surfaces the same day.
Off-the-shelf connectors move standard objects and then stop at your custom fields, your routing rules and your statuses. We keep the connector where it earns its keep and write code only for the gap it leaves.
Workflows built by whoever had time end up in a personal account, undocumented, with credentials no one can rotate. Ours live in your repo and your accounts, with a runbook that says what breaks and where to look.
We go through one process end to end on a call: who touches what by hand, where data is re-keyed, where it stalls. Scoping is free, and you keep the map whether or not we build anything.
You get the integration points in build order, with an hour estimate and a price for each. Start with one, see how it goes, decide on the rest afterwards — nothing here requires committing to the whole programme.
We ask for a service account scoped to the objects in play, never an admin login. The first build runs against a copy or in read-only mode; nothing writes to production until you have seen it work.
One integration at a time, tested on real data before writes are enabled. A sequential rollout means that when something misbehaves you know exactly which piece to roll back.
Health checks, alerts and a run log for every workflow, plus a runbook: what it does, what to do when it fails, where the logs live. Code, workflow exports and credentials are yours.
The tool follows the process, not the other way round. If an n8n workflow covers it you get an n8n workflow — cheaper to change and readable by your own team; when it needs state, queues, real volume or logic a node graph cannot express, it becomes a small service in Python or TypeScript.
One system talking to another: two-way sync, error handling, retries, run log and an alert. Around 20 hours of work. Undocumented APIs, exotic formats and on-prem legacy systems move the number up.
Several integrations, a service layer of your own, scheduled jobs and a small dashboard showing the state of every sync. This is also the tier for moving a pile of Zapier or Make scenarios onto self-hosted n8n.
A named engineer on your automations: fixes when a vendor changes an API, changes when your process changes, and someone who already knows the system. Hourly from $30 / 3 000 ₽ works too if the volume is uneven.
Prices are indicative and do not constitute a public offer. The final cost, scope and timeline are fixed in a contract or invoice after we have discussed the task.
The closest thing we have built to this is an accounting system for a HoReCa chain on AppSheet with Google Sheets as the database: 20+ sheets, 5 access roles, 0 servers. Manual bookkeeping became a structure the whole chain works in, with no ERP purchase and no infrastructure to run. Same instinct applies here: exhaust the tools already in place before adding new ones.
Read the AppSheet caseTell us where your team re-keys data by hand and you will get back what to automate first, what it costs and how long it takes. Scoping is free, and inbound requests get a reply within 2 hours.
Discuss your task