AI workflow automation: what it costs to run and what it saves

Ask three suppliers what an AI workflow costs and you will get three numbers that cannot be compared, because each covers a different scope and none of them covers what the workflow costs in year two. The useful question is not the price. It is which cost areas exist, which of them scale with your volume, and which savings survive a finance review.

What are the cost areas in an AI workflow automation project?

An AI workflow automation project has five cost areas, and missing one is how a project comes in on budget and over cost.

Two of the five cost areas are frequently absent from a quote. The first is your own team's time: process owners in workshops, subject experts labeling test cases, IT running security reviews. The second is the change work after launch, when people run old and new processes in parallel and throughput temporarily drops.

For a broader view of how these cost drivers fit into the work, read the practical guide to AI workflow automation.

What does AI workflow automation cost for a company of 20 to 200 people?

AI workflow automation cost for a company of 20 to 200 people depends on how many workflows are in scope and how many systems they touch, so the honest answer is a set of drivers, not a price. The tiers below show what changes as scope grows. They are illustrations of scope, not prices, and a discovery call is the place to turn them into a number for your situation.

How does model usage scale with volume?

Model usage is billed per token, a unit of text of roughly four characters of English, counted separately for what you send and what the model produces. That makes cost a function of three things: how many items you process, how much text each item carries, and which model you choose.

The spread between models is wide enough to matter. Anthropic publishes Claude Haiku 4.5 at $1 per million input tokens and $5 per million output tokens, Claude Sonnet 5 at $2 and $10, and Claude Opus 5 at $5 and $25 (Anthropic). Newer models are listed on the same page at different prices. Two mechanisms reduce the bill further: the Batch API applies a 50 percent discount on input and output tokens for work that does not need an immediate answer, and prompt caching charges a cache hit at a fraction of the standard input price, which suits workflows that resend the same policy document or instructions on every item.

Long documents change the arithmetic quickly, because a hundred page contract carries far more input tokens than a short support message, and server side tools carry their own charges, for example web search at $10 per 1,000 searches (Anthropic).

Three rules help control AI model usage cost. Choose the model per task rather than per company, since classification and field extraction often run well on a smaller model. Estimate at your real document length rather than a sample. Then double the estimate in your business case, because volume and document length both tend to grow.

What do the licenses around the model cost?

The software surrounding a workflow is frequently the larger recurring line, and published list prices give a sense of scale. All prices below were checked against the linked pages on 22 October 2026 and change often, so confirm them before you budget.

Per task and per seat pricing behaves differently as you grow. Task based platforms are inexpensive at low volume and climb steadily with it, which is one of the clearest signals that a workflow has outgrown a no code tool. Watch for license tiers too, since the API or connector a workflow depends on is sometimes only available on a plan above the one you currently pay for.

Which AI automation costs get missed?

Four cost lines cause most of the overruns, and none of them appear on a build quote.

• Data cleanup. Duplicate supplier records, inconsistent product codes and missing customer IDs cause wrong matches. You do not need a company wide data program, but you do need the specific fields this workflow depends on to be trustworthy, and someone has to do that work.
• Exception handling. Every workflow routes some share of items to a person. If nobody owns that queue, items pile up and staff quietly return to the old process. Budget the time as an ongoing operating cost, not a launch task.
• Adoption. Training, documentation, running both processes in parallel and slower throughput while people learn. Real, temporary and almost always underestimated.
• Monitoring and retesting. Suppliers change invoice layouts, a CRM field gets renamed, a model version is retired. Without monitoring, quality declines quietly and the first person to notice is a customer.

Where do the savings actually come from?

Three kinds of AI automation savings are defensible, and one common claim is not.

Hours returned, valued at loaded cost. Loaded cost means wages plus benefits, payroll taxes and overhead. The US Bureau of Labor Statistics reports private industry employer compensation costs averaging $46.89 per hour worked in June 2026, of which wages and salaries were $32.82, or 70.0 percent, with benefits making up the remaining 30.0 percent (BLS). Using an hourly wage alone leaves out that 30.0 percent. The full method for valuing hours is in how to calculate the ROI of AI automation.

Fewer errors and less rework. Price each error by what it costs to fix: staff time plus direct costs such as credit notes, redeliveries, late payment fees or missed early payment discounts. Count only the error types the workflow prevents, and subtract any new ones it introduces.

Faster cycle times, where speed changes money. Invoicing two days sooner improves cash timing. Capturing early payment discounts is cash. Answering quote requests faster may raise win rates, but only count it once you can measure the effect.

The claim that does not survive scrutiny is hours saved treated as cash by default. Returned hours become money in three ways only: a hire you planned and no longer make, reduced overtime or outside spend, or capacity redeployed to work with measurable output. Name which applies and agree it with the manager of the team before the case is written.

Illustrative example: Consider a professional services firm automating supplier invoice intake. Roughly 600 invoices a month take 12 minutes each to key in and code. After automation, about 70 percent go through with a three minute check and the rest take 10 minutes as exceptions, giving an average of about 5 minutes. That returns around 70 hours a month. At a loaded cost of $40 an hour, that is about $2,800, plus perhaps $500 of avoided rework. Against it sits a recurring bill made up of model usage, document processing per page, the automation platform license, hosting and a support agreement, along with the finance lead's time on the exception queue. Every figure here is a hypothetical input chosen to show the shape of the calculation. None of them is a benchmark, and none is a quote.

How do you build an AI automation business case finance will accept?

A defensible AI automation business case is short and testable. Six things belong in it.

1. A measured baseline. Two to four weeks of volume, handling time, cycle time and error rate, with the data source and the dates named.
2. Every cost line, split by type. One time and recurring, including your own team's time and the exception queue.
3. A three year view. Build plus three years of running cost, not a project price.
4. A named route to cash. Which hire, which overtime line, which contract.
5. Three scenarios. Expected, conservative and downside. The downside should assume exceptions run higher than planned and usage costs double.
6. Stop conditions. The results that would pause or end the project, agreed before it starts.

To run the arithmetic on your own figures, use the AI automation ROI calculator, and how to calculate the ROI of AI automation explains the method behind it in more detail. If you have not settled on a workflow yet, start with which business processes to automate first.

How Kastling approaches cost and scope

We do not publish a price list, because a number quoted before anyone has seen your process is a guess. What we can be clear about is the structure. A discovery call is free and carries no commitment. For AI and operations work a separately scoped paid audit is common, though not required for every project, and a well defined brief can move straight to a proposal. Implementation is scoped and quoted against agreed deliverables. Infrastructure and usage are billed according to where the solution runs, in your own AWS or Azure account or in ours. Maintenance is a separate agreement that states what is included.

Keeping those four areas distinct is deliberate. It lets you compare suppliers on scope rather than headline numbers, and it means nobody discovers a recurring cost after go live. Read more about our AI Integration & Automation service, or bring us a workflow and we will tell you what would drive its cost.