An AI agent costs an expertise-led practice three ways: the build, the month, and the owner's own hours training and supervising it.
You've heard AI agents can take real work off your plate. So you go looking for what one costs and how to get one.
What you find is build prices. Twenty thousand dollars. Six figures.
That's a strange place to land. You wanted work off your plate, and when you want work off your plate, you hire someone. A build is not what you buy when you hire a worker.
An agent is custom software, and it costs you three ways. What it takes to build. What it costs to run each month. And your own hours, training it and reading what it did. Price all three before you sign anything.
A build is not what you buy when you hire a worker.
What it costs to build an AI agent
Cleveroad builds agents for a living and publishes its prices, so I'll use theirs. A simple agent runs $20,000 to $35,000 USD. An enterprise one, six figures.
Coder Band doesn't dress it up: "Very little rigorous public data exists on AI build costs. Most published numbers are agency marketing, so treat them as directional."
I build agents too. I call them digital employees, and I'll get to why. So count me in that group. Every build price is a starting point, mine included.
What it costs to run one each month
Innovation Insight published what it costs them to run a support assistant handling thousands of conversations: $750 to $3,650 USD a month, hosting and monitoring included.
Most small businesses will never get near that. For one small job, the month is mostly model calls. The agent sends each request to a model, and a hard request costs more than an easy one.
What I ask first
When someone asks me what an agent costs, I ask what they'd pay a person to do that job for a month. A real job. The role, the goals, the standards, the KPIs. What you'd pay a person for a month is about what you'd pay a digital employee for a year.
That's the part that lands. People go from skeptical to curious. "I'm not sure this will work for us, but I want to know more." Then they book a call.
They also tell me they'd never hire a person for the job. The role needs doing, and it's outside what they can staff. Nobody running a small business hires someone to post on LinkedIn and Facebook, write for search, or run the Google Ads. That is exactly what makes the best digital employees: the jobs nobody would ever staff.
If you can staff it, staff it. What I build is for the work you can't.
The word agent doesn't get anyone over the line. An employee with a job description and KPIs does. The KPIs get met, and then they set new ones.
Ask whether the job needs an agent at all
Gartner says most firms selling agentic AI have put the label on something older, and its analyst Anushree Verma says many of those use cases never needed an agentic build.
That's a price question, not a tech one. If a chatbot can answer it, get a chatbot quote.
Your hours are the third cost
Coder Band says the first set of test cases eats days of the domain expert's time. Not an engineer's. Yours. They put no dollar figure on it, so put one on your own.
Then there's the reading. Nobody hires for it and you can't bill it, but you're the one who can tell when the work is wrong, and telling means reading. When the agent gets something wrong, you answer for it.
What I say when someone plans to use ChatGPT
People tell me they'll just use ChatGPT. I did that, before I had digital employees, and I went down rabbit holes. The tool writes your email, then offers to fix the copy on your site, and you say sure. A chatbot is built to keep you in the chat. The work gets done and your hours go up instead of down.
What to ask for when you want a quote
Ask for two prices, separately. The build and the month. Then ask how many hours a week the seller expects from you once it's live, and get that line into the quote before the model name goes in.
Then do the sum. If the hours are yours to spare, do it. If either number is a guess, wait.