When a vendor quotes you an AI agent, they quote the build. The number that actually decides your return on investment is the one almost no one puts on the page: what it costs to run for the next twelve months.
At Shanti Infosoft we build these systems, so this is not a warning against agents. It is the opposite. The teams that get real value from automation are the ones who go in with eyes open about the running bill, because that is what separates an agent that quietly pays for itself from one that becomes a line item finance keeps questioning. So here is the plain-English ledger we walk clients through before anyone signs anything.
1. The usage bill that arrives every month
Every action your agent takes calls a model, and models charge per use. A support agent handling a few hundred conversations a day, or a coding agent working through real tasks, consumes tokens continuously. This bill scales with success: the more your agent does, the more it costs, which is healthy, but it means you cannot treat it as a one-time purchase. Get a usage estimate at your real expected volume, not the demo volume, and ask what happens to the bill if usage triples.
2. The integrations that quietly rot
An agent that touches your CRM, inbox, payment system or database depends on those systems staying exactly as they are. They will not. APIs change, a tool gets upgraded, a permission gets revoked, a field gets renamed. Each of those can silently break the agent. Budget for ongoing integration maintenance the way you budget for keeping any connected software alive. It is small, but it is never zero, and skipping it is how a working agent becomes a broken one.
3. Monitoring and the cost of catching mistakes
A human employee tells you when something is wrong. An agent does not, unless you build it to. Someone has to watch its outputs, review a sample of its work, and catch the slow drift before customers do. That is real time from a real person, plus the tooling to make it visible. This is the cost most quotes skip entirely, and it is the one that protects you from the expensive failures.
4. Tuning after real users arrive
Your agent will meet inputs the build never anticipated. The first weeks of real use always surface edge cases that need correcting. This is not a defect; it is the normal break-in period. Plan for a few rounds of adjustment in the first quarter, and lighter ongoing tuning after that as your business and your data change.
5. The human who owns it
Even a well-behaved agent needs a person accountable for it: deciding when to widen its scope, approving changes, answering when it misbehaves. That is a slice of someone's job, not a full role for a single agent, but across a few agents it adds up to a real responsibility. An ownerless agent is the one that drifts into trouble, so this cost buys you reliability.
6. Compliance and the audit you hope you never need
If you operate anywhere near regulated data -- finance, health, anything with personal information -- you need logs of what the agent did and why, retention you can defend, and the ability to answer an auditor. Building this in costs a little up front and a little ongoing. Bolting it on after a problem costs far more.
So what does this mean for the decision?
None of these line items is large on its own. Together they typically mean the twelve-month cost of owning an agent is a meaningful multiple of the build quote, and that is exactly the number you should be comparing against the value it creates. The good news is that a well-scoped agent doing high-volume, repetitive work clears that bar comfortably. A vaguely-scoped "do everything" agent often does not, and now you can see why before you commit.
The honest test is simple. Take the full twelve-month figure, including everything above, and set it against the hours saved, errors avoided, or revenue captured. If the agent still wins, build it with confidence. If it only wins when you pretend the run cost is zero, you have just saved yourself a painful renewal conversation.
When we scope an agent, we put the run cost on the table next to the build cost, because a number that surprises you in month six is a number we should have shown you in week one.
If you would like a realistic twelve-month picture for an agent you are considering, that is a conversation worth having before the contract, not after.
About Shanti Infosoft: Shanti Infosoft is a CMMI Level 5 AI development company that has delivered 700+ projects across 16+ industries. We help teams move from AI ideas to dependable, production-grade software - shantiinfosoft.com | AI consulting services.
If you want a clear-eyed view of the 12-month run cost before you sign, we can put a realistic total-cost-of-ownership estimate in front of your team. Talk to our team.
Related reading: Automation Is a Trade-Off Nobody Quotes You On. Here's the Real Bill
Sagar Jain is a Director at Shanti Infosoft, where the team builds AI agents and automation for real business operations.
