How Much Does Business Process Automation Cost in 2026?

Our catalogue starts at $1,200–$2,400 for a packaged Starter automation. That is an implementation estimate for a listed scope. Software and usage need their own budget decisions. So do support and your team's work. Don't merge them into one number.

The useful question is which listed workflow resembles the work you need done. The automation cost guide lets you compare actual catalogue scopes, add your own running-cost assumptions, and download a planning brief. It uses our published service catalogue, not an independent market survey or a collection of final customer invoices.

Start with a scope you can describe

Write down the trigger, the systems involved, the required outcome, and the person who accepts the result. Then name an exception: what happens if a required field is missing, an approval never arrives, or a downstream system is unavailable?

For example, our Refund Workflow listing describes an issued refund updating the CRM, notifying support, and updating entitlements. Its Starter estimate is $1,200–$2,400 for 6–12 implementation hours. The description does not specify the systems or how partial refunds should affect access. Those are questions to resolve before agreeing to the scope.

A workflow with several approvals and financial handoffs is a different listing. Our Quote-to-Cash Orchestrator connects quoting, approval, e-signature, a billing trigger, and CRM stage updates. Its Orchestration band is $8,000–$18,000 for 40–90 implementation hours. That comparison describes two scopes in our catalogue; it does not establish a universal price for those business processes.

Read the build estimate correctly

The catalogue assigns each entry a tier. Both price endpoints are the tier's estimated labor hours multiplied by our published $200 hourly rate.

Source: current catalogue evidence and methodology. Entries within a tier share the same band. These are not separately measured project costs, elapsed delivery times, or guaranteed spending caps. A band is useful only after the scope is specific enough to compare.

Custom engagements scoped from scratch have a separate $2,500 minimum. It is not a floor applied to packaged catalogue entries. Check the current pricing and engagement terms before committing to a build.

Compare what each quote makes someone responsible for

Two proposals can show the same system names and still describe different work. One may stop after a successful test record. Another may include duplicate handling, an exception queue, a person who accepts the result, and a handoff for the team that will run it. The higher figure isn't automatically more complete, but the lower figure is not comparable until those boundaries are written down.

Ask each provider to state the trigger, records and systems in scope, the acceptance cases, and what happens after an uncertain result. Then separate the implementation estimate from the recurring bill. List the software, hosting, usage, and support decisions on their own lines. Our n8n project-quote comparison walks through that exercise with two illustrative scopes. It does not set a market rate or turn an outline into a final quote.

Confirm the costs of running it

Use the operating-budget tool to record the cash assumptions that apply:

• Software and hosting: additional subscriptions, hosting, or plan upgrades needed for this workflow. Check what your existing plans already cover.
• API and AI usage: the billing unit, expected workload, and any overage charges. Get the unit rate from the provider and document how you estimated usage.
• Support and maintenance: the coverage you need, who monitors failures, and the terms of any support agreement. A shared support retainer should not automatically be charged in full to one workflow.
• One-time extras: costs outside the listed implementation scope, such as a separately quoted migration or data preparation task. Confirm what is already included to avoid counting it twice.

The tool adds 12 full months of stated operating costs to the build estimate. It does not guess a launch date or insert a maintenance percentage. A blank field stays unknown and produces an incomplete subtotal; enter zero only when you expect no cost. Tax is excluded. Keep unknown costs visible.

Keep internal effort visible

Someone still needs to explain the process, provide access, review test cases, and handle operational decisions. You can add setup hours, monthly operating hours, and your own hourly value in the guide. This time value stays separate from the cash budget. It is still real work.

That calculation does not show a saving. To explore potential time value, use the ROI calculator with your own measured task frequency, time per task, and assumptions about work that remains. The catalogue does not establish payback periods or realized customer savings.

Take the unanswered questions into scoping

Check whether your existing software's native features can cover the process. If ownership, access, or the accepted outcome is unclear, complete the requirements template first.

Then download your planning brief. It includes the selected listing, source version, your entered assumptions, and unresolved costs. Share it with the person who owns the process, or use it to prepare for a scope discussion. The final quote should follow the agreed requirements.