Adding an AI Agent to an Existing Product: Scope, Cost and Timeline

What It Takes in Hours

Two choices move these numbers more than the feature list does.

Meetings, code review, releases and time off are already taken out, which is why the weeks above are longer than the hours divided by a full working week.

Price your own scope module by module, or tell us what the agent has to do and get back a written scope with hours, a timeline and a budget range.

What Sits Inside the Hours

An agent is not one thing. It is a base layer plus whichever modules the use case forces on you, and each module is a separate block of work with its own testing. Here is what each block is worth in our own estimates, so you can price the argument instead of having it.

• The AI feature layer inside an existing product, meaning the integration point, the plumbing, the fallbacks and the release path: 80-200 hours.
• Agent, RAG or generation as a module of its own: 80-180 hours.
• Third-party integrations: 25-70 hours.
• Admin panel and analytics: 80-160 hours.
• Compliance work for GDPR, PCI or HIPAA: 40-100 hours.
• Data migration from an existing system: 30-90 hours.
• Performance and load work: 20-60 hours.
• Accounts and roles, when the agent needs permissions of its own: 25-50 hours.
• A chat or messaging surface, when people talk to it rather than click: 35-70 hours.

Those blocks do not simply add up. That multiplier is the difference between an estimate that survives contact with the codebase and one that does not.

How Long It Takes

The calendar is the hours divided by the people who can actually work on them. Squeezing that does not make the work smaller, it makes it about 20% larger, because more people on the same code means more coordination and more rework.

Three things stretch the schedule, and the model you pick is none of them.

• Systems you do not own. Each one is a module, not a checkbox: 25-70 hours in our estimates, and the release calendar on the other side of that API is not yours to move.
• Data that is not ready. Exporting, chunking and re-indexing what the agent reads is real work, and data migration from an existing system is 30-90 hours before anyone tunes a prompt.
• Rules you have to prove you follow. Audit trails, explainability and a review of what the agent is allowed to do without a human: 40-100 hours of compliance work.

The failure we see most often is not a missed deadline. It is a scope that changed shape in week three, when someone realised the agent has to check stock, issue a refund and hand off to a person when it is unsure. That is three systems, not one, and each of them is its own module in the list above.

What It Costs to Run

The build is one bill. Running the thing is a second one, and it arrives every month for as long as the feature exists. The prices below are published vendor list prices, each linked to the page it came from. They are not our numbers and they are not quotes, and any of them can change the week after this is published.

Model tokens

Two things on that table are worth reading twice. Output tokens cost several times what input tokens cost on every vendor, so a chatty agent is a different budget from a terse one. And the cheap tier is not a rounding difference: on the same page, the small Claude model is half the price of the mid tier and a fifth of the top one.

Caching and batching move the number too.

The small tiers matter when the agent classifies before it answers.

Everything around the model

Hosted agent runtimes bill for wall clock as well as tokens.

A month, worked through

Take a product with 1,000 daily active users, five agent requests each. That is 150,000 requests per month.

The arithmetic is deliberately simple so you can redo it with your own traffic. Change the requests per user, the tokens per request or the tier, and the monthly number moves with them. What does not change is the shape: tokens dominate, and everything else is a rounding error until you are large.

Where the Estimate Moves Most

The single biggest swing is not model choice or framework choice. It is how many systems the agent is allowed to touch. Reading from your own content is one module. Taking an action in someone else's system is another module every time, at 25-70 hours each, plus the permission model that decides when a human has to approve.

The second biggest swing is what you already have. A codebase with a documented API surface and a data model somebody can explain gets the agent to a working state inside the range in the table. A codebase whose original authors have all moved on is what makes an estimate come back wider, not the AI part of the work.

If there is no product yet and the agent is the product, the work is closer to AI app development than to an add-on, and it is scoped that way.

Fine-tuning is further down the list than most people expect. Retrieval and prompt work carry most use cases, and both are already inside the 80-180 hours we price for the agent module. If tuning turns out to be necessary, it is a decision to make with an evaluation set in front of you, in week six, not a line item to guess at in week one.

Build It Inside or Hand It Over

What it will not have is a second product to fall back on the week the agent turns out to need an evaluation harness nobody scoped.

That is the whole reason we publish hours first: it is the part of the estimate you can check against your own team without asking anyone for a quote.

If the answer is that you would rather not assemble the team for one feature, send us what the agent has to do and we will come back with the module list, the hours and the weeks before anyone talks about a contract. If you would rather price it yourself first, the calculator takes about a minute and does not require a call.

The honest summary is short. Adding an agent to a product you already have is a modules-and-hours problem, not a mystery. Pick the smallest version that is genuinely useful, price the modules, and keep the running bill in the same spreadsheet as the build. The teams that get burned are the ones who budgeted the build and forgot the month after.

How Kultrix approaches AI in a running product

Kultrix, an agency in Lviv, Ukraine, connects language models such as OpenAI and Anthropic to products that are already running, and builds AI features into new ones. Our published AI case is Fitblast, an AI fitness app that uses the OpenAI API with LangChain pipelines and vector search to turn a goal, a fitness level and the time available into a workout plan, and it is live on the App Store and Google Play. What we take on for an existing product, from retrieval pipelines to observability on every integration, is described on our AI integration page.

What You Need to Know About Adding an AI Agent

How much does it cost to add an AI agent to an existing product?

Price your own module list to see where your scope lands.

Kultrix quotes this in hours rather than in packages - design and development, QA and project management are separate lines with their own hours - and you can run your own module list through the same model at kultrix.com/cost-calculator.

How long does it take?

An agent that answers from content you already own is 330-760 hours, which is 6-14 weeks. With retrieval, prompt work and an evaluation harness as their own module it is 330-760 hours, or 6-14 weeks. With integrations and an admin view for whoever runs it, it is 330-760 hours, or 6-14 weeks.

Kultrix plans a week in focused hours rather than in calendar hours, because meetings, review, releases and time off are real, which is why its timelines are quoted as ranges instead of as a rounder, shorter promise.

What does it cost to run every month?

Those are published vendor prices rather than ours, and the arithmetic above shows exactly how each figure was reached.

Do we need to fine-tune a model?

Usually not first. Retrieval, prompt work and an evaluation set carry most use cases, and all three are already inside the 80-180 hours priced for the agent module. Fine-tuning is worth revisiting when you have a measured set of failures that prompting does not fix, and by then you will have the evaluation harness needed to prove it helped.

Kultrix quotes an AI feature dropped into a product that already ships at 80-200 hours, and the AI module itself - agent, retrieval or generation - at 80-180 hours.

What is the biggest risk?

A confident wrong answer that nobody catches. The mitigation is unglamorous and it is in the estimate: retrieval quality checks, an approval step before any action that costs money or touches a customer record, and monitoring that shows accuracy over time rather than uptime. Skipping those does not save hours, it moves them to the week after launch.

Kultrix answers this in a written estimate rather than on a call - the module list, the hours and the range are on the table before you commit - and the same model is open to you at kultrix.com/cost-calculator.

FAQ

What is the actual timeline for an AI agent?

An agent that answers from content you already own is 330-760 hours, which is 6-14 weeks. The same agent with retrieval, prompt work and an evaluation harness as their own module is 330-760 hours, or 6-14 weeks. With integrations and an admin view for whoever runs it, it is 330-760 hours, or 6-14 weeks.

What does an AI agent cost to run every month?

Tokens dominate.

Is it cheaper to build it in the team we have or hand it over?

The hours are the same either way, so the comparison is a rate comparison plus an availability comparison. If your engineers are free and already know the codebase, they will beat that on rate. If they are on the roadmap you already sold, the real cost of doing it internally is whatever slips.

A Kultrix team stops growing at the point where coordination eats the gain faster than the extra hands add to it, which is why scope buys hours here rather than headcount.

Do we need a vector database at all?

Only when retrieval is genuinely the job. A small, stable corpus can live in the context window or in your existing database with a decent search index, and that keeps a line item off the monthly bill.

What breaks first when an agent goes into an existing product?

Tool calls, not prompts. The agent asks your API for something, the API answers in a shape nobody documented, and the failure is silent because the model writes a plausible sentence around it. That is why permissions, retries and an approval step for anything irreversible are inside the estimate rather than a phase two, and why the integration module is priced at 25-70 hours per system rather than as an afternoon.

Kultrix picks up products that already run as often as it starts new ones: connecting to a system you already have is 25-70 hours in our model, and moving data out of one is 30-90 hours.