How much does AI automation cost?
Short answer
A first automated workflow starts around $5,000 for a small or mid-sized business and rises with the number of systems it touches. Diagnostics should cost you nothing. Enterprise transformation programmes from large consultancies are a different market — six and seven figures. If a vendor will not price a first project, the scope is not defined yet.
What actually drives the price
Almost all of the variance comes from integration surface, not from the AI. Automating a process that lives in one system is cheap. The same process spread across a CRM, a mailbox, a spreadsheet, and a messenger costs several times more, because most of the work is making four systems agree on what a record is.
The other three multipliers: data that has to be cleaned before anything can run on it, decisions that need a human approval step wired in, and whether you need monitoring and documentation at the end or just something that works today.
What should be free, and what should not
Diagnostics should be free. Any competent vendor can map your manual operations and estimate ROI on the top candidates without charging for it — that is a sales activity, not a deliverable. Paying four or five figures for a discovery phase that ends in a document is the single most common way automation budgets get spent without anything shipping.
What you should expect to pay for: the build, the integrations, and the handover. Those are real engineering.
How to sanity-check a quote
Ask for the ROI arithmetic behind the number — hours saved per week, multiplied by loaded cost, against the build price. If a vendor cannot produce that on one page, they have not scoped the process, they have scoped a budget.
Then ask what happens after handover: who can change the automation in six months, and what it costs. A cheap build with no documentation is the expensive option on a two-year view.
Related questions
Is there a minimum budget for AI automation?
Practically, yes. Below roughly $5,000 there is not enough engineering time to integrate, test, and hand over a process that revenue depends on. Under that threshold you are buying a script, which can be the right call for a single isolated task.
Why do quotes for the same project vary so much?
Usually because the two vendors scoped different things. One priced a working integrated process with monitoring and handover; the other priced a proof of concept. Compare what is in production at the end, not the headline number.
Should we pay for a discovery phase?
Not as a separate purchase before anything is built. A short scoping sprint inside a build engagement is reasonable. A standalone discovery contract that ends in a strategy deck is how months disappear.
The free diagnostics puts a number on your own processes — hours lost per week and what recovering them is worth — before you commit to anything.
Start free diagnostics