Loading...
Workflow Automation · n8n

The handoffs nobody should still be doing by hand.

We automate the repetitive steps between your systems and your people, built on n8n and running where you decide.

Start a conversation How this works
Your process already exists. It just runs on people.
Somebody reads the order out of an email and types it into the system. Somebody exports a spreadsheet on Monday so that somebody else can paste it into a report. Somebody remembers to chase the invoice, most of the time.

None of that is difficult work. That is exactly the problem: it is the kind of work that gets skipped when the week gets busy, and nobody notices until a customer does.
Automation is not about replacing those people. It is about taking the copying, the chasing and the remembering off their desk, so the hours go into the part of the job that actually needs a person.

The systems you already run usually stay. We connect them rather than replace them.

What we automate

The four that come up in almost every company.

Quotes, orders and invoices

An enquiry arrives, and the quote, the order confirmation and the invoice follow from it without anyone retyping the same customer three times. Including the follow-up nobody enjoys sending.

Systems that don’t talk

Your shop, your accounting, your warehouse and your CRM each hold a piece of the truth. We move the right piece to the right place on a schedule or on an event, so the four of them stop disagreeing.

Reports and reminders

The Monday numbers, the stock warning, the contract that renews in thirty days. Assembled and sent on their own, to the people who need them, whether or not anyone remembered.

Documents and inboxes

Supplier PDFs, delivery notes, WhatsApp messages with an order buried in them. This is where AI genuinely helps: reading unstructured input and turning it into a record a system can use.

n8n, set up and run properly

The tool we build on, and why.

n8n is an open-source automation platform. A workflow is a chain of steps you can look at and understand: when this arrives, look that up, write it there, tell this person. It speaks to several hundred common systems directly and to anything else through a plain HTTP step.

We build on it because of what happens on the day you no longer want us. The workflows are yours, they export as files, and any developer who knows n8n can pick them up.
It runs on a server you own, in a data centre you choose, or on n8n’s hosted service. For companies in Paraguay that usually means a small server we set up and maintain; for clients in Switzerland and Germany, where the data is allowed to sit is normally the first question, not the last.

We do the installation, the hardening, the backups and the monitoring, and we hand over documentation written for whoever comes after us.
A workflow in four steps: an order email arrives, the customer is looked up in the CRM, a record is created in accounting, and the warehouse is notified in chat. TRIGGER Order email arrives CRM Look up the customer ACCOUNTING Create the record CHAT Notify the warehouse A workflow in four steps: an order email arrives, the customer is looked up in the CRM, a record is created in accounting, and the warehouse is notified in chat. TRIGGER Order email arrives CRM Look up the customer ACCOUNTING Create the record CHAT Notify the warehouse
One workflow, four systems, nobody retyping anything. The brighter box is the only step anything external touches.
  • Self-hosted installation on your infrastructure, or ours if you would rather not own a server.
  • Workflows built, tested and documented, not left as an undocumented canvas.
  • Connections to the systems you already run, including the ones with no official integration.
  • Monitoring and alerting, so a workflow that stops working says so instead of failing quietly.
  • Training for the person on your side who will own it.

How it works

Three steps. You can stop after any of them.

Three phases: mapping in one week, a pilot over two to four weeks, then ongoing rollout. You can stop after the first phase and again after the second. you can stop here or here 01 Mapping one week, fixed price 02 Pilot two to four weeks 03 Rollout and handover ongoing, cancellable Three phases: mapping in one week, a pilot over two to four weeks, then ongoing rollout. You can stop after the first phase and again after the second. you can stop here or here 01 Mapping one week, fixed price 02 Pilot two to four weeks 03 Rollout and handover ongoing, cancellable

Mapping

One week, fixed price. We follow two or three of your processes end to end and write down what actually happens, including the parts that only work because somebody is paying attention. You get a list of candidates ranked by hours saved against effort. If you stop here, the list is still yours.

Pilot

Two to four weeks. We build one workflow, usually not the biggest one, and run it alongside the manual process until you trust it. This is where you find out whether we understood your business, at a price where being wrong is survivable.

Rollout and handover

We work down the list, set up monitoring, and train the person on your side who will own the system. You keep the server, the workflows and the documentation. We stay reachable, on a support arrangement you can cancel.

A worked example

Not a client story. A shape you will recognise.

An exporter receives orders by email and WhatsApp. Someone reads each one, types it into the accounting system, creates a folder on the shared drive, and adds a row to the shipment spreadsheet. Three people do this, slightly differently. Twice a month something is entered twice or not at all.

Automated, the message is read once, the fields are extracted, and a person confirms them on one screen instead of retyping them on three. The accounting record, the folder and the spreadsheet row are created from that single confirmation. The shipment status then updates itself from the carrier, and the Friday summary writes itself.

Today, three people each type the same order into accounting, the shared drive and the spreadsheet: nine paths. Automated, an incoming order is confirmed once and that single confirmation updates all three. TODAY Sales Order desk Owner Accounting Shared drive Spreadsheet nine ways in, three of them slightly different AUTOMATED Order arrives Confirm once Accounting Shared drive Spreadsheet Today, three people each type the same order into accounting, the shared drive and the spreadsheet: nine paths. Automated, an incoming order is confirmed once and that single confirmation updates all three. TODAY Sales Order desk Owner Accounting Shared drive Spreadsheet nine ways in AUTOMATED Order arrives Confirm once Accounting Shared drive Spreadsheet
Same three destinations either way. What changes is how many people have to remember to reach them.

Nobody lost their job. The order desk stopped being a bottleneck, and the double entries stopped, which is usually the part the accountant notices first.

Who this is for

This is for you if

  • You run a company of roughly 10–200 people and you make the decisions.
  • The same information gets typed into more than one system every day.
  • You already have the software you need, and the problem is that none of it talks.
  • You want to own what gets built, on a server you can point at.

Probably not, if

  • You are looking for someone to click together a Zapier flow for one afternoon.
  • Your process is not written down anywhere and nobody has time to walk us through it.

Questions we get asked

What is n8n?
An open-source automation tool. You draw a workflow as a chain of steps: when this arrives, look that up, write it there, notify this person. It then runs unattended. It connects to several hundred common systems out of the box, and to anything with an API through a generic HTTP step. The reason we build on it rather than on a closed platform: you can read the workflows, export them, and run them yourself.
Does it have to run in the cloud?
No. n8n can run on a server you own, in a data centre you pick, or on n8n’s own hosted service. Where it runs is usually decided by where your data is allowed to live, which is a question we ask in the first week rather than the last.
How long before the first automation is running?
The mapping week comes first, then the pilot. In practice the first workflow is doing real work two to four weeks in. It is deliberately a small one, because the point of the pilot is to find out whether we understood your process, not to impress you.
What does it cost to run?
Self-hosted n8n is free software; what you pay for is a small server, which for most companies is in the tens of euros per month. Our work is quoted per phase, fixed price. There is no per-workflow or per-execution fee from us.
What happens if we stop working with you?
The workflows, the server and the credentials are yours, and they keep running. n8n workflows export as JSON and any developer who knows the tool can pick them up. We write the documentation on the assumption that somebody else will read it.
Do we need AI for this?
Mostly no. Most of what slows a company down is moving known data between known systems, and that is ordinary automation. AI earns its place where the input is unstructured, such as reading a supplier’s PDF, sorting an inbox or summarising a thread, and we use it there and not as decoration.

Tell us what’s slowing you down.

Call the office nearest you. We’ll tell you whether we can help and roughly what it would take. No sales sequence.

Office Paraguay

Call Us
+595 98 65 21 088
Nicolas Krisvoschein 384
1767 Asuncion

Office Switzerland

Call Us
+41 44 586 90 96
Bahnhofstrasse 10
CH-5630 Muri

Office Germany

Call Us
+49 36 25 96 30 70
Hinter den Höfen 6
99880 Waltershausen

Or write instead

We use your details to answer you and nothing else. No list, no newsletter, no third party.