Automation · on your server · Fixed price
Your team copies data by hand from one system to the next. We make that run on its own. On your server, no fee per transaction.
Typing orders into the inventory system. Forwarding invoices by email. Reconciling customer data between CRM and accounting. Building the same report from five sources every week. Those are invisible costs that grow with revenue and create errors.
We build workflows that take that over: a trigger happens, a rule decides, the systems get written. With the tool n8n on your server in Germany. No fee per transaction, no volume limit, no data with a US provider. And the workflows belong to you.
Short conversation, fixed-price quote, two to six weeks to handover. Operation by us on request.
By hand against automated
- Cost per transaction
- EUR 4.50 against 0.002
- Transactions per day
- 150 against unlimited
- Available
- 8 hours against 24
- Error rate
- 1 to 5 % against near zero
At EUR 60 full cost per working hour. 40 hours of copying per month is EUR 28,800 a year, before the follow-up cost of errors.
What we do differently
-
No fee per transaction
Zapier and Make bill every step. On your server nobody counts. A million runs cost the same as a hundred.
-
Data stays with you
Customer data, credentials and content do not leave your server. No contract with a US provider needed.
-
The tool is not a dogma
n8n covers most workflows. Where it is not enough, we write code and attach it to the same system.
-
You own the workflows
You can change, extend and move them. With us, with your team or with anyone else.
What doing nothing costs
The three most expensive manual processes.
Processes usually break between five and ten million euros of revenue. What worked with five people creates chaos with fifty. The costs were there all along, just invisible.
-
Moving data between systems
CRM into inventory. Shop into warehouse. Accounting into banking. Every day by hand because the systems do not talk to each other. Typically 15 to 25 hours a month.
-
Typing standard messages
Order confirmations, shipping notices, reminders, follow-ups. Always the same message, instead of work only people can do. Typically 10 to 20 hours a month.
-
Rebuilding reports
Collecting data from five sources, merging it in a spreadsheet, building charts. The same every week, and the numbers are outdated as soon as the report is done. Typically 8 to 15 hours a month.
Add the error rate: with a thousand orders a month and one to three percent typos, that is ten to thirty cases someone has to find and fix. Some cost a customer.
How it works
One trigger, one rule, one result.
Every automation consists of the same three parts. The trigger can be a form, an incoming email, a schedule or a new record. The rule decides what happens. The result lands in the systems you use anyway.
n8n is the tool we build this with: you connect systems, databases and AI models visually into a workflow and can extend every step with your own code. Unlike Zapier or Make it runs on your own server.
-
Trigger
Form submitted, payment received, order created, email arrived, time reached.
-
Rule
Enrich, check, branch, wait for approval by a person, retry on error.
-
Result
Record in the CRM, invoice in accounting, message to the customer, row in the report.
-
When something goes wrong
The workflow retries, sets the case aside and gets in touch. Nothing is lost because a system happened to be unreachable.
The difference
Zapier and Make against n8n on your server.
Zapier and Make bill every single step. n8n counts a whole run as one transaction, and on your server nobody counts at all.
| Point | Zapier or Make | n8n on your server |
|---|---|---|
| Billing | Per step. A workflow with ten steps that runs 10,000 times is 100,000 billed steps | No counter. You pay the server, about EUR 5 to 20 per month |
| Cost at medium volume | EUR 500 to 800 per month, permanently. Over three years EUR 18,000 to 28,800, and in the end you own nothing | One-off build plus hosting |
| Where the data runs | Through US servers, contract with a US provider needed | On your server in Germany |
| Volume limit | By plan | None |
| Own code per step | Limited | Yes, in JavaScript or Python |
| AI features | Limited, cloud models only | Over 70 ready-made building blocks, including local models where nothing leaves the server |
For small, static setups with a few hundred runs a month the existing tool can stay. We say so then too.
What we automate
Recurring, rule-based, across several systems.
These are the workflows that give you hours per week back.
-
Enquiries and CRM
Capture enquiries from forms, enrich, score and route them to the right person or segment. In seconds instead of hours. Plus duplicates and data hygiene.
-
Invoices and documents
Create invoices, read data from PDFs, obtain approvals, archive, hand over to accounting.
-
Syncing systems
Keep CRM, inventory, shop, marketing and databases at the same state, in both directions, with rules for conflicts.
-
Messages
Email, Slack, SMS and push, triggered by events instead of someone remembering. Timed right, logged.
-
Scheduled reports
Daily numbers, weekly summaries, monthly reconciliations. From one source, sent automatically.
-
AI in workflows
Pre-sort emails and enquiries, summarise texts, structure data from free text. On request with models on your server where no document leaves the house.
When the tool is not enough
Then we write the code.
Some workflows outgrow a visual editor: millions of records, answers in milliseconds, deeply custom rules. Same server, same ownership, different tool.
-
Custom logic
Decision rules, custom building blocks and AI routing in Python or Node when the editor reaches its limit.
-
High throughput
Data processing in Rust or Go when milliseconds and memory decide.
-
Events instead of polling
A messaging system that reacts the moment something happens, with queues, replay after an outage and nothing lost.
-
One interface for everything
A unified connection point across your tools so every system has one place to turn to.
From the work
What automation gives back.
500 to 1,200 saved working hours a year is the normal range. The build usually pays for itself after 12 to 18 months, after that it runs at server cost.
-
Online retailer, Germany
Order handling from start to finish
- Before
- Three employees, 120 hours of manual work a month: shop into inventory, into warehouse, to the carrier, message to the customer.
- Built
- One workflow that takes over everything. Exceptions land with a person.
- After
- About 850 working hours a year saved, around EUR 51,000 at EUR 60 an hour. Error rate down 87 percent.
-
Agency, Austria
Sync between tools
- Before
- Customer data in several tools, reconciled by hand, constant errors.
- Built
- Two-way sync with conflict rules.
- After
- Sync error rate down 94 percent, about 1,200 working hours a year saved.
-
Software company, Switzerland
Replacing rented tools
- Before
- Several automation services billed per step, costs grew with volume.
- Built
- All workflows moved to a server of their own.
- After
- Around EUR 78,000 annual saving. Figures released by the client.
How it runs
From analysis to handover
-
one or two meetings
Analysis
We map your processes and systems and find the ones that cost the most time and money. Result: a map with an order.
-
within five days
Fixed price
Which workflows, in which order, what it costs. We calculate the comparison with your real volumes.
-
two to six weeks
Build
n8n on your server in Germany, the workflows with versioning, error handling and logging. Where code is needed, we write it.
-
one to two weeks
Test
Every workflow with real data and error cases. What happens when a system does not answer, when a field is empty, when a thousand transactions arrive at once.
-
controlled
Launch
With monitoring. The old way stays until the new one is verified.
-
your choice
Handover or operation
Access, manual, training on request. Or we run it: updates, security, monitoring, intervention on errors.
Prices
Build once, own permanently.
We quote a fixed price per project and compare in advance, with your real numbers, what the existing tool costs over three years.
What you get
- by quote
Build at a fixed price
Server, n8n, the agreed workflows, error handling, logging, test, handover.
- EUR 5 to 20 per month
Hosting
A small server at Hetzner in Germany, paid directly to the provider. No fee per transaction.
- EUR 0
Licence
n8n is free for internal use in your company. Only if you pass access on to third parties is a licence from the maker needed.
Afterwards, optional
- monthly, cancellable
Operation by us
Updates, security, monitoring, backups, intervention on errors. The solution stays yours.
- by effort
Further workflows
New workflows you build yourself, with your team or with us. No technical upper limit.
All prices net. The build usually pays for itself after 12 to 18 months.
Related
Automation rarely stands alone.
-
Connecting systems
Connecting interfaces, databases and legacy systems cleanly. The foundation of every reliable workflow.
See interfaces -
Custom software
When a process needs more than an editor: services, portals and tools made to measure.
See custom software -
Monitoring
We notice when a workflow stops before the cases pile up.
See monitoring -
What does the rented tool really cost?
The calculator compares subscription costs over years with a one-off build.
Compare costs
Common questions
Tool, cost, privacy and operation.
What is n8n?
A tool that connects systems, databases and AI models visually into a workflow without programming every step. Every step can still be extended with your own code. The difference to Zapier and Make: it runs on your own server.
What if n8n does not fit a process?
Then we do not force it. n8n is strong on workflows with triggers, branches and approvals. Very high throughput or deeply custom rules are better placed in code of their own. We write it and attach it to the same system.
Is it privacy-compliant?
The tool is just a tool. On your server in Germany customer data, credentials and content do not leave your infrastructure and you need no contract with a US provider. Whether a specific workflow is permissible depends on the data and recipients. You check that with your advisers.
Is switching from Zapier or Make worth it?
Almost always when volume grows or privacy matters. For small, static setups with a few hundred runs a month the existing tool can stay.
Do we need technical knowledge to run it?
No. Error handling, retries, monitoring and alerts are part of the build. Most customers never open the editor again after the handover. Anyone who wants to can at any time.
What happens when we need new workflows later?
You own the workflows. You add them yourself, with your team or with us. There is no upper limit on the number of workflows or runs.
Is n8n open source?
Not in the strict sense. The code is visible and internal use in your company is free. Only if you offer n8n as a service yourself or pass access on to third parties is a licence from the maker needed.
Next step
Which processes cost you the most time right now?
In a short conversation we map your processes and say which ones pay off first. Then a fixed price.
On your server in Germany. No fee per transaction. You own the workflows.