What does business process automation cost for a small company?

There are four different costs

A single project price hides decisions that matter later. Separate the work of understanding the process, building it, paying the providers and caring for the live system.

A small connection between two standard tools may cost hundreds. A client-facing process with several systems, permissions and recovery routes can cost many thousands. The number of boxes in a workflow diagram is a poor pricing unit.

• Process definition and system design
• Implementation, testing and launch
• Software licences, hosting and usage
• Monitoring, maintenance and recovery

What I charge for a bounded process

My Systemisation Blueprints usually cost €1,500 to €3,000. A Blueprint covers one process and leaves you with a usable design and build boundary, even when the right recommendation is smaller than automation.

A Process Build usually costs €4,500 to €12,000. The fee rises when the process crosses more systems, needs custom integration, handles sensitive data or has exceptions that require careful recovery. Several connected workflows are scoped separately.

Ongoing Process Care usually costs €350 to €950 per month for each live process. A system I did not build starts with a €900 to €1,800 review before I accept responsibility for it. Prices exclude VAT where applicable and third-party provider costs.

Why a Blueprint has its own fee

The mapping work settles what the business is buying. Without it, a builder must price uncertainty into the Build or discover the real process after implementation has started.

A paid Blueprint also leaves room for an honest stop. If the best answer is a clearer handoff, a permission change or a simple tool configuration, you should be able to take that answer without being pushed into a larger build.

The factors that move a Build price

Two processes with six steps can be entirely different jobs. One moves approved fields between modern services. The other interprets attachments, calls a legacy system and must resume safely after partial failure.

• Quality and availability of existing APIs
• Number of accounts, roles and permission boundaries
• Variation in incoming data
• Financial, legal or customer impact of a mistake
• Volume and the need to handle duplicate or concurrent cases
• Monitoring and response expected after launch

Provider costs belong in the decision

Workflow platforms may charge per task or execution. AI providers charge by use. Email, document, hosting and database services can add their own fees. These costs should sit in the client’s accounts where possible, so usage remains visible and the process is not tied to a hidden margin.

Ask what happens when volume doubles. A low initial licence can become the largest recurring cost. A more technical build can cost more upfront and less to run. There is no universal winner.

Maintenance and additions are different

Care keeps the agreed process working inside expected parameters. It covers the watch points, routine upkeep and recovery named in the agreement. A provider outage still belongs to the provider, although the process may need a fallback or safe recovery around it.

A new service line, business rule, integration or process branch changes what the system does. That is a new engagement. Keeping this boundary explicit prevents a monthly care fee becoming an undefined development retainer.

A simple investment check

Estimate the current hours, but add delay, interruption and error recovery. Compare the annual cost with the Build, provider fees and realistic care. Then ask what the process makes possible: more capacity, quicker starts, fewer dropped cases or less dependence on one person.

Use conservative assumptions. A strong case should still make sense when adoption takes time and only part of the administrative load moves.