What does custom automation cost a small business?
What drives the price of an automation, which costs come on top of the build, and how to judge up front whether a project pays off for you.
In short: A single, clearly defined automation costs a small business a low to mid four-figure amount, a whole internal system correspondingly more. With me, a single workflow starts at a fixed price from €1,500, custom software from €3,000. What you actually pay depends less on the tool than on your process.
Search for prices online and you mostly find tool subscriptions or vague answers like "it depends". This article explains what it depends on, so you can judge a quote.
What drives the price
| Factor | Why it matters |
|---|---|
| Number of steps and edge cases | A workflow with five steps is far more work than five workflows with one step each. Every exception ("except for customers from …") costs time. |
| Number of systems involved | Every program that gets connected brings its own access, data formats and sources of error. |
| Is there an interface? | If a program has an API, connecting it is cheaper. If not, you need workarounds, see RPA or API? |
| How clear the process is | A process that only exists in one person's head has to be mapped first. That saves money later but costs time up front. |
| AI share | Reading texts, classifying, drafting: it works, but needs testing to be reliable. |
| Human approvals | For important decisions (quote, payment) you build in a review step. That adds a little effort and cuts risk considerably. |
What costs come on top of the build
The build is only one part. Plan for these as well:
- Tool costs: Platforms like n8n or Make and the connected programs have their own subscriptions. How billing works is covered in n8n or Make?
- AI usage costs: When a model processes text, you pay per use. For small volumes this is usually low, but keep an eye on it.
- Running and maintenance: Programs change, access expires. Someone has to receive error alerts and make small adjustments.
- Rollout in the team: An automation nobody uses saves nothing.
Fixed price or hourly rate?
For a clearly bounded workflow, a fixed price is usually fairer: you know what you'll pay up front, and the provider has an incentive to work efficiently. For larger, evolving systems, a project frame with jointly defined scope fits better.
Be careful with fixed prices quoted without any process mapping. Either the scope is calculated very generously, or extra charges follow later.
Does it pay off? The simple calculation
The question isn't whether an automation is cheap, but whether it adds up:
hours per week × cost per hour × 52 = yearly cost of the manual work
Compare that number with the cost of the solution (build plus running costs).
Example with assumed numbers, not a client project: If a task costs your team three hours a week and you count €40 an hour, that's €120 a week, roughly €6,000 a year. If an automation replaces most of that, you can weigh the build against it. Use your own numbers, since they differ a lot from business to business.
For a first rough idea you can also use the AI check.
When automation probably doesn't pay off
- The task rarely comes up.
- The process changes constantly or isn't clearly defined.
- Every run needs an individual decision anyway.
In that case it's often better to clarify the process first, for example with BPMN, and decide later.
Frequently asked questions
Is there a minimum amount?
With me, a single workflow starts at €1,500. Smaller things can often be solved directly with the built-in features of your programs, no provider needed.
Do I keep paying monthly?
The tools usually have their own subscriptions. Maintenance and support are optional, on request as a monthly retainer. You own everything, including the documentation.
How long does a project take?
A single workflow is often live within a few weeks. How fast depends on the systems and on your feedback.
How this could look for you, we clarify in the free call. How such a start is set up is described on the automation page.
