The short answer
One workflow automation costs $2,500 to $12,000 to build with Lumeor and goes live in one to three weeks. A “new form submission goes to the CRM and a Slack channel” workflow sits at the bottom. An “invoice arrives, AI extracts the fields, a manager approves, it posts to QuickBooks Online and anything odd lands in a review queue” workflow sits near the top.
If you have five or more workflows to build, pricing them together as a program is usually cheaper per workflow because shared pieces get built once. See what an n8n automation program costs.
Where the money goes
| Phase | Share of effort | What happens |
|---|---|---|
| Process mapping | 10–15% | Walk through the manual process, list the exceptions, agree what “done” looks like |
| Access and setup | 5–15% | Credentials, API keys, test accounts, permission scopes |
| Build | 30–40% | Triggers, mapping, branching, any AI step and its prompt |
| Error handling | 10–20% | Retries, alerts, failed-record queue |
| Testing with real data | 15–20% | Run historical examples, fix edge cases, confirm totals match |
| Handover | 5–10% | Documentation, walkthrough, who to call when it fails |
The exceptions list drives the price more than the happy path. Most processes are easy to automate for the cases that look normal. The work is in what happens to the credit memo, the duplicate contact or the email in Spanish.
What it costs to run
The build is a one-time cost. The running costs depend on the platform and on volume:
- Platform usage. Zapier counts each successful action step as a task, so a workflow with eight action steps that runs 2,000 times a month uses about 16,000 tasks. Make bills by the operations or credits each module run consumes. n8n Cloud counts the whole run as one execution, so the same workflow is about 2,000 executions. Self-hosted n8n replaces usage billing with server costs. Check each vendor’s current plans.
- Model usage. An AI step is billed per token by the model provider, so the cost tracks how many documents or messages go through it and how long they are.
- App plan tiers. Some apps only open their API on higher plans. Check this before you build, because it can cost more than the automation platform.
- Monitoring. Failure alerts are usually built in. A separate log store is only worth it for high-volume or regulated workflows.
The n8n vs Zapier comparison walks through how the billing models play out at different volumes.
How to keep the cost down
- Fix the process first. Automating a messy approval chain just makes the mess faster.
- Start with the most common path. Route rare exceptions to a person and automate them later if they turn out to be frequent.
- Filter early. Drop irrelevant records at the trigger so they do not burn tasks or operations downstream.
- Use built-in connectors. Choosing an app with a ready connector over one that needs custom API work can move a workflow down a tier.
When not to pay for a build
Some workflows do not need a studio. If your CRM or help desk already has a native automation that does the job, use it. If a template exists in Zapier or Make and the process is low stakes, set it up yourself. If the process runs a few times a month and takes five minutes, automation may never pay back. For a look at when custom code beats no-code tools, see no-code vs custom-code automation.
How Lumeor prices a workflow
We price each workflow as a fixed fee after a 30-minute walkthrough of the current process and a look at sample records. The quote names the trigger, every app touched, the exceptions handled, the failure path and who maintains it afterward. We build in your accounts, so you own the workflow and can change it later. A worked example of a higher-tier build is our guide to automating invoice processing with AI.