The quote came back at $8,000. The second came back at $45,000. The scope description was the same. Ranges like this are not unusual for AI agent implementation, and the gap is almost never about one service overcharging. The gap comes from what each quote does and does not include.
Most quotes name the build. Few include integration work. Almost none include ongoing maintenance. Those three things are different costs with different timelines, and confusing them is how implementation projects end up over budget and under-supported.
Why implementation quotes vary so widely
Three variables drive the range from $5,000 to $80,000-plus for what can sound like the same project.
Workflow complexity determines how much logic has to be designed before any code is written. A workflow with two or three consistent inputs and one output is straightforward. A workflow with conditional branching, multiple escalation paths, and edge cases that each need separate handling multiplies the design time before the build begins.
Number of integrations matters because each connected system — a CRM, an inbox, a project tracker, a billing tool — adds setup, permissioning, data mapping, and error handling. Connecting to one system is a task. Connecting to four is a project.
Whether ongoing support is included creates the largest gaps between quotes. A quote that covers only the build will look cheaper than a quote that includes maintenance and support. These quotes are not comparable. One ends at launch. The other covers what happens next.
What the build cost actually covers
The build is the part most quotes name explicitly. The build covers designing the workflow logic: what the agent does, in what order, under what conditions. The build includes writing and testing the prompts, configuring approval flows, and connecting the agent to a staging environment.
For a well-scoped single workflow, a build typically runs $5,000–$20,000. For a multi-integration system with conditional logic and a control layer, $30,000–$80,000 is realistic. The build is the only cost with a defined endpoint.
The build is a one-time cost. The running is not.
What integration costs that most quotes skip
Connecting an agent to live business systems is where many quotes fall short. API access, data mapping, error handling, and permission scoping each require time that headline build quotes often exclude.
Most business software was not built with agent access in mind. Giving an agent access to the right records — and only those records — requires permissioning work that vendors rarely document cleanly. When an API changes (and they change), someone needs to catch the break and fix it before the agent starts producing bad outputs.
Budget an additional 20–40% above the build cost for integration work that many quotes leave unspecified. That number is not padding — it is the work of connecting the agent to how the business actually runs.
What maintaining a running agent actually costs
Most implementation quotes cover the build. None of them cover what happens when a process changes, a connected tool updates its API, or the agent starts misfiring on edge cases. That cost starts on day one after launch.
After the build and integration, the agent needs ongoing attention. Prompts need updating when business language shifts or processes change. Integrations need maintenance when connected tools update their APIs. Edge cases accumulate — inputs the agent was not designed for that pile up unhandled until someone reviews the logs.
Plan for 15–30% of the initial build cost per year in ongoing maintenance. A $20,000 build costs $3,000–$6,000 annually just to keep running correctly. An agent left without maintenance does not hold its performance level — the agent degrades, slowly and invisibly, until someone notices a pattern of bad outputs that have been going out for weeks.
How to evaluate any implementation quote
Three questions expose whether a quote covers the real cost of implementation.
Does the quote include integration work — specifically, which systems will be connected, what access each requires, and who handles breaks after launch? Is there a maintenance plan, and what does the plan cover: prompt updates, integration maintenance, edge-case handling? What happens when something breaks after go-live — is there a defined support process with a response timeline?
A quote that cannot answer these questions is pricing the easy part of the project. The rest shows up later, unbundled, on a separate invoice — or does not show up at all, and the team discovers why after the first missed client email.