Custom AI Agent Development Cost: Where the Money Goes
Ask what a custom AI agent costs and you will get quotes that are hundreds of times apart. That is not because someone is making prices up. The quotes are for different things. Break "an AI agent" into its parts and it becomes clear where the money goes.
What the cheap tier actually builds
At the low end you usually get a prompt written on an existing platform, a few documents uploaded, and a chat box. It can answer general questions the documents already cover: product descriptions, FAQs, how-to steps. If that is what you need, it is not a rip-off. The platforms are good at this, and you can often build it yourself.
What it cannot do is touch your business systems. It cannot check the status of one specific order, it does not know this customer already wrote three times, and it cannot change an address or open a ticket for a person. Most of the labour companies actually want to remove sits exactly there.
Where the expensive part goes
- Connecting systems. Orders, shipping, inventory, tickets, mailboxes: each one needs an integration, permissions, and handling for failed lookups. A lookup has to tell the model whether it found the record, confirmed there is none, found part of it, or could not check. Otherwise the model treats a failed lookup as "does not exist" and gives a confident wrong answer. This is usually the largest piece of work.
- Turning raw material into facts. You cannot pass a whole email thread or a full ticket history to the model. It first has to be distilled into a few lines of key facts, each with its source. This step sets the ceiling on quality; the reasons are in why AI agents fail in production.
- Writing down how your business answers. Which things the AI may answer directly, which must be logged for a person, and how to talk to customers all have to be pulled out of how your team already works. That comes from reading your real case history, not from prompt-writing tricks.
- Acceptance testing. Replay a few hundred real historical cases and compare outputs one by one. Test questions you invent yourself hide the real problems.
- Running costs after launch. Model calls are billed by usage. Business rules change and the answers have to change with them, and every change needs another replay. Quotes often leave this out, yet over a year it is one of the biggest lines.
When you should not spend much at all
Low-volume work is not worth it. A task that happens a few times a month saves little once automated and still needs someone to maintain it. Work where the information needed to decide lives only in an experienced employee's head, and nowhere in a system, should also wait. Without the facts, the AI can only guess. Neither case turns out well, whatever the quote.
Pricing models you will see
- Per day or per hour. You pay for effort. Simple to compare, but the risk that it never works is yours.
- Fixed project price. You know the cost up front, but the scope is frozen at signing, and real processes rarely stay frozen.
- Subscription or per seat. Common for platforms. Fine for the cheap tier, less useful when most of the value is in your own integrations.
- Outcome-based (per completed task). You pay for work that actually got done. The vendor carries the risk, so this only works when "done" can be counted and checked.
Five questions to ask before you sign
- Will it connect to our existing systems? Which ones, and what does the AI say when a lookup fails?
- How will it be tested before launch? Will you replay our real historical data?
- Which things will the AI do on its own, and which will always be left for a person to approve?
- When rules or the business change after launch, who updates it, and how is that charged?
- What is the billing unit: days, the project, or the volume of work actually completed?
How we charge
We bill for completed work, not for days and not as a fixed package. The plan is free. We then connect to your existing systems and run real work for two to four weeks; you can see every record the AI handled, and your people review all of it at first. Once the pilot shows how much it handled and how accurately, we agree a unit price together, and after that you pay monthly for completed volume and can stop at any time. Your up-front risk stays small, and if we cannot deliver results, we do not get paid.
We are a small team based in Shenzhen, China, and we work with clients remotely. Before deciding between an agent and a plain workflow, read AI agent vs workflow; it often changes the scope, and therefore the cost.