S/03automation & integrations

A business process automation consultant who ships the integration, not a deck

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.

Discuss your taskFree scoping call, reply within 2 hours

What this solves

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.

Operations runs on copy-paste

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.

Integrations fail silently

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.

The connector almost fits

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.

Nobody owns the automations

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.

How the work runs

  1. Process walkthrough

    1–2 days

    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.

  2. Automation plan and quote

    1–2 days

    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.

  3. Access and a sandbox

    1–3 days

    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.

  4. Build and go live

    5–15 days

    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.

  5. Monitoring and handover

    2–3 days

    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.

Stack

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.

  • n8n (self-hosted)
  • Make
  • Zapier
  • Python
  • TypeScript / Node.js
  • PostgreSQL 16
  • Redis
  • Docker
  • REST & webhooks
  • Google Sheets API
  • Grafana + alerts

What it costs

Single integration

from $600 / from 60 000 ₽

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.

Process build

from $1,800 / from 180 000 ₽

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.

Retainer

from $400 / from 40 000 ₽ per month

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.

Related case study

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 case

Frequently asked questions

How much does business process automation cost?
A single integration between two systems starts at $600 / 60 000 ₽, and a full process build with several syncs starts at $1,800 / 180 000 ₽. Everything is quoted off a $30 / 3 000 ₽ hourly rate, so the estimate shows how many hours each integration point takes. Scoping is free; payment is 50% up front and 50% on acceptance.
Which processes are actually worth automating first?
Start with the step that runs most often and involves the least judgement — order or lead intake, re-entering data between two systems, a recurring report someone assembles by hand. Steps that need a human decision, and processes about to change anyway, should wait. On the scoping call we rank your list by hours saved per month against hours to build.
Should we use n8n, Make, Zapier, or custom code?
Zapier and Make are right when the workflow is short, low volume, and someone non-technical needs to edit it. Self-hosted n8n is right when task pricing starts to hurt, when data cannot leave your infrastructure, or when you need branching and retries a linear flow handles badly. Custom code wins when there is real state, real volume, or logic worth writing tests for — and mixing all three in one project is normal.
How long does an automation project take?
One integration takes 10 to 25 working days end to end, including the walkthrough, the sandbox and go-live; the build itself accounts for 5 to 15 of those. A multi-step process build runs 3 to 6 weeks, but integrations go live one at a time, so the first is already saving work while the second is being built. The usual delay is not development — it is getting API access approved on your side.
What happens if an integration breaks or an API changes?
We fix it. Every workflow ships with a health check and an alert, so a failed sync surfaces the same day instead of at month end. The first month after release is covered by warranty at no cost; after that it is either the retainer from $400 / 40 000 ₽ a month or hourly work, whichever suits the volume.
Can you automate a process without replacing our existing software?
Yes, and that is the default. We build on top of what you run, through APIs, webhooks and exports, and we do not open with a proposal to replace your CRM or ERP. The only case where replacement comes up is software with no way to get data out at all — and you will hear that during scoping, not three weeks into the build.
Do you work with our internal IT team or independently?
Both, and independently is the more common one, since most companies at this size have no internal team. Where there is one, we work to their rules: their repo, their review, their infrastructure, their service accounts. What we need from IT is access and someone to answer questions, not their engineers' time on the build.
How do you measure the ROI of an automation project?
Before the build we count how long a step takes today and how often it runs; that is the number the quote gets compared against. After go-live the run log shows how many times each automation executed and how many records it moved, so the comparison is against recorded runs rather than a promise. We will not hand you a percentage — we do not know your labour costs, and an invented figure is worse than none.

Send the process, not a spec

Tell 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
Business Process Automation Consultant — Corexy