If you are considering automation, you need more than a promise of time savings. You want to know what the build costs, which recurring costs apply and which assumptions the calculation uses.
This article provides indicative ranges and worked scenarios. They help you compare the build, ongoing costs and expected return for the same scope and period.
A warning upfront: some processes are not worth automating. You will find those below too.
Start with what the process already costs you
“What does automation cost?” is the second question. The first is: what does not automating it cost you every week?
That amount is not recorded anywhere. It is not on an invoice, in your accounts or in your profit and loss statement. It is hidden in the evenings you spend retyping invoices and in the quote you forgot to follow up. Invisible costs feel free. They are not.
The basic formula
Hours per week × 52 × internal hourly rate = annual cost of this process
For the internal hourly rate, divide gross pay including employer costs by productive hours. For office work in Dutch small and medium-sized businesses, this often comes to €45–€75 per hour. If you do the work as the owner, use your billable rate, because that is what you are actually missing out on.
Scroll sideways to view all table columns.
| Process | Hours/week | × 52 | At €60/hour | Annual cost |
|---|---|---|---|---|
| Manually following up quotes | 2.5 | 130 hours | €60 | €7,800 |
| Retyping supplier invoices | 2.0 | 104 hours | €60 | €6,240 |
| Copying order data between systems | 1.5 | 78 hours | €60 | €4,680 |
| Putting together weekly reports | 1.0 | 52 hours | €60 | €3,120 |
| Customer questions already answered before | 3.0 | 156 hours | €60 | €9,360 |
Illustrative calculations. Enter your own hours and rate; the result surprises almost everyone.
Notice what happens when you add two or three rows together. You reach the point where hiring someone comes into consideration. But staff are currently hard to find, and an employee who retypes information will keep having to do so.
We will calculate it for you
During a free scan, I map your processes, measure the hours and put a figure on them. You receive the calculation, even if you want to take it forward yourself.
Book your free automation scanFree · no obligation · always a short advisory report
So what does the build cost?
Below are our own ranges for Dutch small and medium-sized businesses, based on projects with a defined scope. They are indicative: the exact price depends on your systems, exceptions and data quality.
Scroll sideways to view all table columns.
| Project type | One-off cost | Recurring costs | Typical delivery time |
|---|---|---|---|
| One flow, two systems; for example, form → CRM → follow-up email | €750–€3,000 | Budget separately for hosting, storage, licences and API usage | 1–2 weeks |
| A process chain across three to five systems; for example, order → inventory → accounting | €3,500–€8,000 | Budget separately for hosting, storage, licences and API usage | 3–6 weeks |
| An AI agent with human review; for example, email triage with a draft reply | €5,000–€12,000 | Budget separately for hosting, storage, licences and API usage | 4–8 weeks |
| Optional technical maintenance: fixed maintenance, with changes covered by included work hours or separately agreed additional work | — | From €250 per month | Ongoing |
Indicative ranges, excluding VAT. Current package prices are on the pricing page.
The build price is separate from recurring services. You choose self-management (€0 per month for AIAgentCycle maintenance services) or a maintenance package from €250 per month. External usage costs still apply. Technical Maintenance includes no included work hours. See pricing and package limits and the maintenance terms.
Scroll sideways to view all table columns.
| Assumption | Amount / calculation |
|---|---|
| Assumed manual work avoided | 2 hours per week × 52 × €60 = €6,240 per year |
| One-off build | €3,000 |
| Maintenance and external costs in this scenario | €315 per month = €3,780 per year |
| Remaining manual work, as assumed | €0; measure this separately in practice |
| Net value of time after recurring costs | €2,460 per year = €205 per month |
| Simple payback period | €3,000 / €205 = approximately 14.6 months |
Fictional calculation, not a quote or a supplier price list. Technical Maintenance €250 + hosting €35 + external backup storage €10 + estimated operational AI usage €20 = €315 per month (€3,780 per year), excluding VAT. Package selection is provisional: complexity, a maximum of 3 named workflows, 1 production environment and a maximum of 20 GB of source data must fit the package in advance. Actual scope and external costs are budgeted separately. Expected time savings do not automatically translate into a financial return.
The three costs that are almost always missing
- Budget separately for fixed technical care, external usage costs and any additional work. A percentage of the build price does not determine which maintenance or recovery work is included. See pricing and package limits and the maintenance terms.
- Exceptions that only appear after going live. The process in your head has three steps. The real process has those three plus seven “except when” cases. These often take more time to build than the main route itself.
- Your own time during the project. Arranging access, reviewing work, testing and making decisions. Allow four to ten hours of your own time for a medium-sized project. No more, but not zero either.
We include these three as standard in the quote. A project that becomes more expensive halfway through is a project that costs you trust.
When automation does not pay off
This section is missing from almost every article on the subject, even though it can save you the most money. Here are four situations where our advice is: not now.
- The process takes less than one hour per week. At €60 per hour, the maximum annual value of that time is €3,120. The fictional scenario with €315 in monthly costs already costs €3,780 per year, before the build and remaining work. In that scenario, time value alone does not produce a positive payback. A different setup, self-management or demonstrable error reduction may change the outcome.
- The process still changes every quarter. You would be automating a snapshot. Settle the process first, then automate it.
- The process relies heavily on judgement. If the outcome depends on what someone knows about a customer, you can automate the preparation at most, rather than the decision.
- The underlying data is wrong. Duplicate customers, empty fields and three spellings of the same supplier. Automation does not fix that. It exposes the problem faster and makes it more expensive.
The fourth is the most common. Automating a disorganised process only creates disorder faster. That is why analysis comes first in how we work, and why we sometimes simply say no.
How do you choose the first process?
Score each candidate process on four points. A process that scores highly on all four is your starting point.
- Frequency. How often does this happen each week? Frequent matters more than frustrating.
- Consistency. Can you write it as a sequence of if-then steps? If not, it is still a skill rather than a process.
- Error costs. What does it cost when something goes wrong: money, a customer or a fine?
- Waiting time. How long is someone waiting for you? Speed often matters more than the hours saved.
That last point needs some explanation. In lead follow-up, speed is central to the outcome. Harvard Business Review studied 2,241 companies and found that responding within an hour made lead qualification substantially more likely than waiting longer, while average response times in the same study ran into tens of hours. A flow that sends a personalised reply within a minute can help win work as well as save time.
About the claim that “78 per cent buy from whoever replies first”
The frequently repeated figure of 78 per cent is not supported here by a verifiable primary source. We therefore do not use it as evidence of your potential return. Calculate that using your own response times, conversion rate, order value and costs; the example below makes its assumptions explicit.
Which process should you tackle first?
That is exactly where the scan begins. We look at frequency, the risk of mistakes and how many people handle the process, then put the candidates in order. You decide what to do next.
Book your free automation scanFree and without obligation. You always receive a short advisory report.
Key points
- First calculate what the process costs you today. Without that figure, every quote is a guess.
- One flow with a defined scope: €750–€3,000 as a one-off cost. A process chain: €3,500–€8,000.
- Budget separately for fixed maintenance, external usage costs and additional work. Our maintenance packages start at €250 per month, excluding VAT and external costs. Self-management remains an option.
- Less than one hour per week: usually leave it alone.
- If the process is wrong, you automate the mistake. Put it in order before building.
Want to know which tools are used and why the choice affects your bills as usage grows? Read what n8n is and AI agent or workflow — Dutch-language article.
Three complete calculations
Here are three worked examples, each based on a workflow structure you can open and explore in the official n8n library. The hours are typical small-business figures; substitute your own.
Case 1: accounting firm, 12 employees, invoice processing
FLOW A
Extract, check and post supplier invoices
Who it is for: accounting firms and wholesalers handling approximately 100 or more supplier invoices per month.
Scroll the diagram sideways to see everything.
What it delivers: from six hours per week to approximately twenty minutes of review.
Watch out: expect an exception rate of ten to twenty per cent during the first quarter. That rate falls as you refine the rules, but it never reaches zero.
Working template to explore: n8n template library.
Scroll sideways to view all table columns.
| Item | Amount | Explanation |
|---|---|---|
| Current value of time | €18,720 per year | 6 hours per week × 52 × €60 |
| One-off build | €5,500 | Accounting integration, extraction and approval |
| Maintenance and external costs | €3,780 per year | Scenario of €315 per month |
| Remaining work | €1,040 per year | 20 minutes per week × 52 × €60 |
| Net value of time in year 1 | €8,400 | 18,720 − 5,500 − 3,780 − 1,040 |
| Net value of time from year 2 | €13,900 per year | 18,720 − 3,780 − 1,040 |
| Simple payback period | Approximately 4.7 months | 5,500 / (13,900 / 12) |
Fictional calculation, not a quote or a supplier price list. Technical Maintenance €250 + hosting €35 + external backup storage €10 + estimated operational AI usage €20 = €315 per month (€3,780 per year), excluding VAT. Package selection is provisional: complexity, a maximum of 3 named workflows, 1 production environment and a maximum of 20 GB of source data must fit the package in advance. Actual scope and external costs are budgeted separately.
Case 2: consultancy, 8 employees, lead follow-up
Here, the gain comes from the work you currently miss because you do not reply until the following morning. The number of hours saved is modest.
FLOW B
A personalised reply to a lead within a minute
Who it is for: B2B service providers receiving form submissions or quote requests.
Scroll the diagram sideways to see everything.
What it delivers: response times drop from hours to seconds, with a CRM that stays up to date automatically.
Watch out: let AI write the draft and keep sending it yourself, particularly during the first few months. Gaining speed at the expense of tone is no gain.
Working template to explore: n8n template library.
What an extra 0.8 projects per month could mean for revenue
Assume 40 enquiries per month, a current conversion rate of 12 per cent and an average project value of €4,500. That gives 4.8 projects per month.
If faster follow-up raises conversion to 14 per cent, a modest assumption, that means an extra 0.8 projects per month: €3,600 per month, or €43,200 per year, against an investment of around €3,500.
Additional revenue is not additional profit. Deduct delivery costs, remaining work and ongoing automation costs before quoting a payback period. The stated conversion increase is a fictional assumption, not a promise of results.
Case 3: online shop, 25 employees, keeping systems in sync
This is the least exciting case, and the one where error costs matter more than hours. Incorrect inventory can cost you an order and a review, rather than just time.
Scroll sideways to view all table columns.
| Item | Amount | Explanation |
|---|---|---|
| Retyping work | €4,680 per year | 1.5 hours per week × 52 × €60 |
| Assumed error costs avoided | €6,000 per year | Assumption: all 10 mistakes costing €600 each are avoided |
| One-off build | €6,500 | Connecting three systems |
| Maintenance and external costs | €3,780 per year | Scenario of €315 per month |
| Net value in year 1 | €400 | 10,680 − 6,500 − 3,780 |
| Net value from year 2 | €6,900 per year | 10,680 − 3,780 |
| Simple payback period | Approximately 11.3 months | 6,500 / (6,900 / 12) |
Fictional calculation, not a quote or a supplier price list. Technical Maintenance €250 + hosting €35 + external backup storage €10 + estimated operational AI usage €20 = €315 per month (€3,780 per year), excluding VAT. Package selection is provisional: complexity, a maximum of 3 named workflows, 1 production environment and a maximum of 20 GB of source data must fit the package in advance. Actual scope and external costs are budgeted separately. Remaining manual work is set to zero here; measure it and the genuinely avoidable error costs in advance.
In this fictional online-shop example, the simple payback period is approximately 11.3 months. Costs and capacity requirements can grow with order volume. Measure error costs and the actions you can genuinely avoid before investing.
Scroll sideways to view all table columns.
| Example | Year 1 after the stated costs | From year 2 | Simple payback period |
|---|---|---|---|
| Invoice processing | €8,400 in expected time value | €13,900 per year | Approximately 4.7 months |
| Lead follow-up | Not calculated: margins and costs are missing | Additional revenue is not net profit | Not determined |
| Online shop | €400 in expected net value | €6,900 per year | Approximately 11.3 months |
Overview of the fictional assumptions above, excluding VAT; not a quote or a guarantee of results.
Would you like the numbers worked out for your three cases?
That is exactly what the scan does: we measure the hours, estimate error costs and calculate a payback period. You receive the spreadsheet.
Book your free automation scanFree · no obligation · always a short advisory report
The question to ask every provider
Requesting quotes from several providers? These four questions help you assess them. A provider who avoids them now may charge you for the consequences later.
- “What happens if you stop operating?” Do I receive the flows? Do they run in my own environment? Can someone else take them over? A vague answer means you are buying dependency.
- “What does maintenance cost each year?” Anyone who says “nothing” has never seen an API phased out.
- “Which exceptions have you found in my process?” A good provider maps them before quoting. A poor one discovers them during the build and charges for additional work.
- “What would you advise against?” Anyone who advises against nothing will sell you anything. Ask explicitly which process they would not automate and why.
We answer these four as standard in every quote; the fourth even has its own heading. Our approach to each phase is explained in how we work.
Frequently asked questions
What does it cost to automate one business process?
The one-off build, optional maintenance and external usage costs are separate items. AIAgentCycle maintenance starts at €250 per month, excluding VAT. Self-management remains possible. Hosting, storage, licences and operational AI usage are additional, separate costs.
How quickly will automation pay for itself?
Calculate the payback period from the expected net monthly return after remaining manual work and all ongoing costs. With an assumed €6,240 in annual time savings, a €3,000 build and monthly costs of €315, this is approximately 14.6 months if no manual work remains. This is a calculation scenario, not a guarantee.
What are the hidden costs of automation?
Budget for fixed maintenance, external hosting, storage, licences and operational usage, plus possible changes and your own staff’s time. Human triage and the included work hours have defined limits; additional work is agreed in advance. A percentage of the build price does not determine which maintenance or recovery work is included.
Is automation cheaper than hiring someone?
That depends on the tasks, staffing and full costs. Automation can reduce repetitive work, but freed-up time does not automatically reduce payroll. Compare the build, maintenance, external costs and remaining work with staff costs that can genuinely be avoided. Work requiring judgement, creativity or customer contact still requires people.
Which process should you automate first?
The process with the highest frequency, clearest rules and fewest exceptions. Choose the process that recurs most often, rather than the one that irritates you most. Frequency matters because it determines the value.
The ranges are based on projects with a defined scope for small and medium-sized businesses and are indicative. The HBR research is “The Short Life of Online Sales Leads” (Oldroyd, McElheran & Elkington, Harvard Business Review, 2011).