AI Development Cost in 2026: What Drives It and What to Budget
AI development cost in 2026 runs from about $15,000 for a narrow proof of concept to several hundred thousand dollars for a custom model or an agent wired into many systems — and that spread is the honest answer, not a dodge. The question underneath "how much does AI cost?" is usually sharper: what will my project cost to build, what will it cost every month after launch, and how do I know the quote in front of me is sane? Most price guides answer only the first part, with ranges that disagree by an order of magnitude and no workings shown.
This guide does the rest. It lines up what seven published price guides actually say, explains the variables that move the number, does the run-cost maths with October 2026 list prices from OpenAI and Anthropic, and walks through a first-year budget you can re-run with your own figures. It is written for a founder, CTO or COO who has to decide whether an AI project is worth funding — and wants to know what they are paying for.
TL;DR:
- Build cost: published 2026 price guides put a chatbot or RAG assistant at a median of roughly $25K–$100K, an AI agent with integrations at $45K–$150K, and a custom machine learning model at $55K–$250K. These are vendors' ranges, not quotes.
- Run cost: for a business assistant, model tokens can be the smallest monthly line. The same workload costs about $7, $144 or $720 a month depending on the model tier — and in the worked example below, maintenance costs about 11× the model bill.
- What moves the number: integrations, data readiness and the quality bar (evals) — far more than the choice of model.
- The cheap path: one job, one metric, a proof of concept on your real data, then an MVP with evals. Gartner expected at least 30% of generative AI projects to be abandoned after proof of concept by the end of 2025 — over data quality, risk controls, escalating costs and unclear value.
How much does AI development cost in 2026?
AI development cost for a scoped business project typically lands between $15,000 and $250,000, depending on the type of project: chatbot and RAG assistants toward the low end, custom machine learning toward the high end, computer vision and enterprise platforms often above it. To get past single-vendor numbers, we read the 2026 price guides of seven development firms that rank on Google's first page for "ai development cost", "ai app development cost" and "how much does it cost to build an ai agent", and lined up what each one says per project type:
| Project type | Lowest published figure | Median published range | Highest published figure | Guides that price it |
|---|---|---|---|---|
| Proof of concept | $15K | $15K–$80K | $80K | 3 |
| Chatbot or RAG assistant on a hosted model | $15K | $25K–$98K | $180K | 6 |
| AI agent with tool integrations | $15K | $45K–$150K | $690K | 6 |
| Custom machine learning model | $40K | $55K–$250K | $400K | 6 |
| Computer vision system | $50K | $60K–$325K | $500K+ | 4 |
Source: build-cost ranges published by Coherent Solutions, Azilen, Upsilon, Redwerk, Uvik, Netguru and ProductCrafters, read on 14 October 2026. "Median published range" is the median of the guides' low figures and the median of their high figures. US dollars. Vendor-published ranges — not independent data, and not a quote.
Three things to take from the table:
- The spread inside one row is the real finding. The chatbot row runs from $15K to $180K — a 12× gap for what is nominally the same deliverable. The label doesn't set the price; scope, integrations and the quality bar do. The next section is about which end of the row your project lands on.
- These are agency prices. A freelancer or an in-house team prices the same work differently — the hourly rates are further down — and the guides rarely say which rates or team sizes sit behind their ranges.
- Enterprise is a different scale entirely. Gartner put the cost of generative AI deployment approaches at $5 million to $20 million (July 2024). That is the scale of enterprise deployments, not an SME's first project — don't let enterprise headlines size your budget.
What actually drives AI development cost?
Seven variables decide where your project sits inside those ranges — and the model is rarely the expensive one. Score your own project against this table before you ask anyone for a price; most of the variance between quotes lives here.
| Driver | Cheaper end | Expensive end |
|---|---|---|
| Scope | One job, one metric ("draft replies to refund emails") | "An assistant for the whole support team" |
| Data | Clean, digital, in one system you control | Scattered across PDFs, scans and spreadsheets; needs labelling |
| Integrations | A documented API, read-only | A legacy system with no API, or writing back into systems of record |
| Quality bar | A person approves every output | Acts on its own on money, customers or regulated decisions |
| Model approach | A hosted model with prompts and retrieval | Fine-tuning, or training your own model |
| Volume and latency | Hundreds of requests a day, answer within seconds | Millions of requests, real-time responses |
| Compliance | Internal tool, no personal data | Sensitive personal data, or a high-risk use under the EU AI Act |
Three of these do most of the damage.
Integrations are the most underestimated line. Reading from a documented API is days of work. Writing into an ERP that has no sandbox — with validation, a dry-run mode, an audit trail and a way to roll back — is weeks. That AI integration work is often the majority of the engineering on a project, not an add-on, so make sure every quote prices it explicitly, system by system.
Data readiness decides whether you are building or cleaning. Poor data quality is the first reason on Gartner's list of why generative AI projects are dropped after proof of concept. If the answers your AI needs live in email threads, scanned PDFs and three spreadsheets, the first weeks go to getting that data into a shape a model can use. Budget it as its own phase, so it doesn't eat the build.
The quality bar sets the evals budget. A system that drafts for a person can be wrong now and then; a system that sends emails, moves money or decides about a person cannot. That difference is paid for in evaluation sets, guardrails and human-review flows — the work that separates a demo from a system you can leave running. We break down that gap in why AI agents aren't reliable enough to scale.
How much does each type of AI project cost?
Each project type has one cost that dominates — retrieval quality for an assistant, integrations for an agent, data and labelling for a custom model. Knowing which one dominates tells you where to push on a quote.
AI chatbot or RAG assistant over your documents
Median published range: about $25K–$98K. This is the most common first project: an assistant that answers questions from your policies, manuals or knowledge base, citing where each answer came from. You are paying for document ingestion, retrieval tuned so the right paragraph is actually found, an answer layer with citations, access control so people only see what they're allowed to see, and an eval set of real questions with known answers.
AI chatbot development cost climbs with the number and messiness of sources, with permissions (a different answer for different roles), and with live lookups — "where is my order?" needs an integration, not just documents. The pitfall: shipping a demo that answers the 20 questions you tested and invents an answer to the 21st. The eval set is not optional; it is how you know when it's wrong.
AI agent that takes actions in your systems
Median published range: about $45K–$150K — and the widest row in the table, because "agent" covers everything from a single tool-calling workflow to multi-agent platforms. So how much does it cost to build an AI agent? The number tracks two things: how many systems it touches, and whether it writes to them. Every write action needs input validation, a dry-run mode, an audit trail and a stop condition. A single agent scoped to one job on one or two systems sits at the bottom of the band; one that orchestrates several systems with write access sits at the top.
Agents also multiply the run cost, because one task becomes many model calls (the maths is below). The pitfall: building an agent where a fixed workflow with one model call would do the job — cheaper and more reliable. Our guide on how to build an AI agent covers that decision, and AI agent development shows the agents we build.
AI features inside an app: what drives AI app development cost
When the AI is a feature inside a web or mobile product, the cost has two parts that follow different rules. The app itself — screens, accounts, payments, admin — follows ordinary software economics, and the method for estimating it is in our guide to software development cost estimation. The AI feature adds its own line: prompts and retrieval, evals, a fallback for when the model is slow or down, and a ceiling on run cost per user.
The pitfall: budgeting only for the AI part. In a new product, the AI feature can be the smaller line — the accounts, data model and integrations around it are what take the weeks.
Custom machine learning model
Median published range: about $55K–$250K. This is prediction from your own structured data — churn, demand forecasting, fraud, pricing — where no hosted model already knows your business. You are paying for data extraction and cleaning, feature engineering, training and validation, and the pipeline that retrains and monitors the model once it is live (MLOps).
The model code is the small part. Google engineers' NeurIPS paper on hidden technical debt in machine learning systems found it is common for real-world ML systems to incur massive ongoing maintenance costs — data dependencies, feedback loops and configuration that the first build never budgets. The pitfall: no plan for drift. Our guide to deploying AI models to production covers what that plan needs.
Computer vision system
Median published range: about $60K–$325K, and only four of the seven guides price it separately. The cost sits in image collection and labelling, camera or edge hardware, and accuracy under real conditions — lighting, angles, dirt on the lens, a new product variant on the line. The pitfall: a model that scores well on a clean test set and degrades on the factory floor. Collect test images where the system will actually run, before anyone quotes accuracy.
How much does AI cost to run each month?
For a business assistant handling a few thousand requests a month, model tokens are a small monthly line — from single digits to hundreds of dollars, depending on the model — while hosting, monitoring and the people who maintain the system make up most of the bill. Model providers charge per million tokens of input and output, so the bill is volume × tokens per request × price. Here is one workload priced at three tiers:
Workload: 3,000 jobs a month (for example, customer emails), 3 model calls per job, 5,000 input and 600 output tokens per call — 45 million input and 5.4 million output tokens a month.
| Model tier | Example models | List price per 1M tokens (input / output) | Monthly token cost |
|---|---|---|---|
| Small | Claude Haiku 5.5, OpenAI gpt-6-luna | $0.10 / $0.50 | ~$7 |
| Mid | Claude Sonnet 5.5, OpenAI gpt-6-sol | $2 / $10 | ~$144 |
| Top | Claude Fable 5.1, OpenAI gpt-6-astra | $10 / $50 | ~$720 |
List prices from OpenAI and Anthropic, checked 14 October 2026. Prices change often — re-check before you budget.
Four things move that number:
- Model choice per step. The same tokens cost 100× more on the top tier than on the small one. Classification and extraction steps rarely need the top tier; route each step to the cheapest model that passes your evals.
- Agents multiply calls. Run the same 3,000 jobs through an agent that takes 8 steps per job, averaging 8,000 tokens of context and 500 of output per step, and the mid-tier bill goes from ~$144 to ~$504 a month — 3.5× for the same work. Cap steps and spend per task in code.
- Caching and batching. On Claude Sonnet 5.5, cached input is billed at $0.10 per million tokens instead of $2. If 4 of every 5 input tokens are the same instructions and policy text, caching takes that part of the input bill down by about 95% (plus a small premium to write the cache). Both providers bill non-urgent batch work at half price.
- Prices keep falling. Stanford's 2025 AI Index found the inference cost for a system performing at GPT-3.5's level dropped over 280-fold between November 2022 and October 2024, with hardware costs falling 30% a year. Build so you can swap the model without rewriting the application, and your run cost improves on its own.
The other monthly lines are usually modest, but they are not zero:
- Retrieval. A managed vector database such as Pinecone starts at a $50 monthly minimum on its Standard plan; the pgvector extension in a Postgres you already run adds little beyond storage. Embedding your documents is cheap: at OpenAI's $0.02 per million tokens for text-embedding-3-small, 10 million tokens of documents cost about $0.20.
- Observability. You need traces of every model call to debug and to measure quality. Langfuse, for example, charges $29 a month for its Cloud Core plan and is open source if you self-host.
- Hosting. The application, database and queues — your normal cloud bill.
- People. The largest line, covered next.
What costs does nobody put in the budget?
The lines that break AI budgets arrive after launch: evals, model churn, data upkeep, security and the people who keep the system working. None of them shows up in a demo, which is why they rarely show up in the first quote.
- Evals and human review. An eval set is a few hundred real cases with the right answer, scored automatically on every change. Building it takes domain experts' time — usually your people, not the vendor's — and it has to grow every time a new failure appears. Without it, every prompt tweak is a gamble.
- Model churn. Providers retire and replace models on their schedule, not yours. In October 2026, Anthropic's pricing page lists ten legacy models alongside four current ones. Every migration means re-running your evals and often re-tuning prompts — budget it as recurring work, not a surprise.
- Data upkeep. Policies, prices and documents change. The index has to follow them, and so do the permissions on who can see what.
- Monitoring and incidents. Someone has to watch quality and cost, triage the bad answers and fix them. This is the ongoing maintenance the technical-debt paper warns about.
- Security testing. Prompt injection — user input that alters the model's behaviour in unintended ways — is LLM01 in OWASP's Top 10 for LLM applications. Anything that reads emails or web pages and can take actions needs to be tested against it.
- Adoption. Training, changed workflows and someone who owns the metric. A system nobody uses costs the full build and returns nothing.
- Exit cost. If the vendor owns the code, the prompts or the eval set, changing vendor means paying for the build twice. Ownership written into the contract costs nothing up front.
A worked example: the first-year budget for an AI assistant
A worked budget beats any range, because it shows which assumption decides the project. The example: an assistant that reads incoming customer emails, pulls the order from your order system, retrieves the relevant policy and drafts a reply that a support agent approves or edits before sending. Every figure in the "Example input" column is an assumption — replace it with your own.
| Line | Example input | How it is calculated |
|---|---|---|
| Build | ||
| Engineering effort | 11 engineer-weeks | Scoping and eval set 1.5 · retrieval 2 · two read-only integrations 3 · drafting and guardrails 2 · evals in CI and monitoring 1.5 · deployment and handover 1 |
| Blended rate | $100/hour | An example inside Upwork's $50–$200 median range for machine learning engineers; agencies usually bill more |
| One-off build | $44,000 | 11 × 40 hours × $100 |
| Run (per month) | ||
| Model tokens | $144 | The mid-tier row in the run-cost table above |
| Vector store | $50 | Pinecone Standard minimum (close to $0 on an existing Postgres) |
| Observability | $29 | Langfuse Cloud Core (or self-hosted) |
| Application hosting | $150 | Example — use your cloud bill |
| Maintenance and improvement | $1,600 | 2 engineer-days a month × 8 hours × $100 |
| Monthly run cost | $1,973 | Sum of the five lines |
| Value (per month) | ||
| Time saved per email | 5 minutes | 8 minutes today → 3 minutes reviewing a draft (measure your own) |
| Hours saved | 250 | 3,000 emails × 5 minutes ÷ 60 |
| Loaded cost of support time | $35/hour | Salary, employer taxes and overhead |
| Monthly value | $8,750 | 250 × $35 |
| Decision | ||
| Net monthly gain | $6,777 | $8,750 − $1,973 |
| Payback on the build | ~6.5 months | $44,000 ÷ $6,777 |
| First-year net | ~$37,300 | ($6,777 × 12) − $44,000, assuming 12 months live |
Two things the table shows that a price list never will:
- Tokens are 7% of the run cost. The model bill is $144 of $1,973 a month; human upkeep is about 81%. If a quote obsesses over model pricing and says nothing about maintenance, it is pricing the wrong line.
- The decision hinges on one assumption — minutes saved. At 2 minutes saved per email instead of 5, monthly value drops to $3,500, the net gain to $1,527 and payback stretches to about 29 months — well past the first year. That project needs rescoping (a bigger share of emails, fewer steps for the agent) or shouldn't be built. Measure the baseline before anyone writes code.
Build, buy or call an API — which is cheapest?
Buying is cheapest when the problem is generic, building on a hosted model's API is cheapest when the workflow is yours, and training your own model is rarely cheapest for an SME. The four options, side by side:
| Option | Up-front cost | Running cost | Choose it when | Watch out for |
|---|---|---|---|---|
| Buy a SaaS tool | Setup and configuration | Per seat or per conversation | The job is generic — meeting notes, a standard help-desk bot | Your data leaves your stack; you can't change the workflow; per-seat costs grow with headcount |
| Build on a hosted model's API | The build ranges above | Tokens + hosting + upkeep | The workflow, data or integrations are specific to your business | Lock-in if the code and prompts aren't yours; uncapped token bills |
| Fine-tune or self-host an open-weight model | Higher build + GPU infrastructure | GPU time, used or not | Strict data residency, very high steady volume, or the API can't reach the accuracy you need even with good retrieval | You run the infrastructure; utilisation decides the cost |
| Train a model from scratch | The highest | The highest | Almost never for an SME | Months of data and compute before the first useful result |
The same build-or-buy question applies to the team. If you're weighing hiring against a partner, our comparison of in-house vs outsourced AI development walks through the costs that don't show on a job ad: hiring time, ramp-up and retention.
How much do AI developers and AI consultants charge per hour?
On Upwork, AI developers' typical rates run from $30 to $150 an hour and machine learning engineers' from $50 to $200; AI consultancies and agencies bill more, roughly $150 to $500 an hour. Upwork publishes typical ranges from historical contracts worldwide:
| Role (Upwork) | Typical hourly range |
|---|---|
| Chatbot developers | $30–$61 |
| AI developers | $30–$150 |
| Machine learning engineers — beginner | $50–$80 |
| Machine learning engineers — intermediate | $80–$120 |
| Machine learning engineers — advanced | $120–$200+ |
The consultancy figure comes from development firms' own price guides that rank for the same searches: Sphere puts traditional AI consultancies and agencies at $150–$500 an hour, and Uvik puts senior engineers at top-tier US AI consultancies at $200–$450. Treat both as vendor claims.
The hourly rate is the wrong unit to optimise, though. Total cost is rate × hours, and the hours depend on whether the person has taken this kind of system to production before. An engineer at half the rate who needs three times the hours — and still can't close the gap between demo and production — is the most expensive option on the list.
The same goes for the AI consultant hourly rate. Strategy work is better bought as a fixed-price deliverable — a defined assessment with a costed roadmap at the end — than as an open meter, where the incentive is to keep the meter running.
What does EU regulation add to the cost?
For most SME projects — internal assistants, document processing, drafting tools — EU rules add design and documentation work, not a new budget tier; high-risk uses are the exception. Under the AI Act, which became applicable on 2 August 2026 with some exceptions, the cost follows the risk level:
- Minimal risk (the Commission's examples are spam filters and AI-enabled video games): no new rules.
- Transparency risk: when people use a chatbot, they must be made aware they are interacting with a machine. That is a design requirement — cheap if planned, annoying if retrofitted.
- High risk (the Commission's examples include CV-sorting software for recruitment, credit scoring and exam scoring): from 2 December 2027, these systems must meet obligations including risk assessment, high-quality datasets, activity logging, detailed documentation, human oversight, and high levels of accuracy, cybersecurity and resilience to errors. That is a real budget line — logging, documentation and oversight flows built in from the start, not bolted on later.
- AI literacy: obligations on AI literacy have applied since 2 February 2025, which in practice means training the people who use and run these systems.
GDPR adds its own line. A data protection impact assessment is required when processing is likely to result in a high risk to people's rights — including systematic evaluation of people (profiling among it) and large-scale processing of sensitive data. If your AI scores people or reads health data, budget the assessment before processing starts. And decide where inference runs: pinning it to a region can carry a premium (Anthropic lists 1.1× pricing for US-only inference), so price the region you need, not the default.
This is general information, not legal advice — confirm your classification with qualified counsel.
How do you reduce AI development cost without ending up with a demo?
Spend in stages that each answer one question: a proof of concept shows it works on your data, an MVP shows people use it, production shows it holds up under real traffic. Every reason Gartner gives for projects dying after proof of concept — poor data quality, inadequate risk controls, escalating costs, unclear business value — is cheaper to discover in a small first stage than in a full build.
- Proof of concept. One job, your real data, an eval set and a run-cost estimate at real volume. The guides above put a PoC at $15K–$80K and 4 to 10 weeks. Exit criterion: the metric is hit on the eval set, or you stop.
- MVP. The smallest version that real users run every day — with the integrations, guardrails and monitoring it needs to be trusted. This is where MVP development services earn their keep: scope cut to what proves value, nothing that doesn't.
- Production. Hardening, a cost ceiling enforced in code, a runbook and a handover your team can operate.
Inside each stage, the levers that cut cost without cutting reliability:
- Narrow the scope to one job and one metric. Breadth comes after the first version is reliable.
- Start with a hosted model and retrieval before fine-tuning anything. Fine-tune only when evals prove you need it.
- Route by task: a small model for classification and extraction, a bigger one only where the reasoning is hard.
- Use what you already run — pgvector in your Postgres, your existing cloud account and identity provider.
- Buy the commodity parts (OCR, speech-to-text, e-signature) and build only the workflow that is specific to you.
- Write the evals before the features. It is the cheapest place to find out something doesn't work.
- Own the code, the prompts and the eval set, so the next phase doesn't start from zero.
How do you get an AI development estimate you can trust?
Send a one-page brief, ask for ranges with their assumptions written down, and judge the proposal on how it will measure quality — not on the day rate. What to send:
- The one job you want done and the metric that says it worked.
- The volume: requests, documents or transactions per month.
- The systems involved, and whether each has an API or a sandbox.
- 20–50 real, anonymised examples of inputs and the right outputs.
- Constraints: personal data, EU hosting, deadlines, a budget band if you have one.
What a credible estimate contains: phases with a range for each (the three-point method from our cost-estimation guide works for AI too), every assumption written down, an eval plan, the run cost at your volume with a ceiling, code ownership and handover terms, and an explicit list of what is out of scope. The red flags are the reverse: a single number with no assumptions, no word on how quality is measured, vague ownership, and a yes to every idea.
That is the shape we use for our own custom AI development services: fixed price per scoped phase, with the evals and the run-cost ceiling defined before production code is written. If you don't yet know which project to estimate first, an AI readiness assessment ranks the candidates by payback before anyone writes code.
Frequently asked questions
How much does AI cost for a small business?
Two numbers, not one: a one-off build and a monthly run cost. For a scoped project — one assistant or one agent on one or two systems — published 2026 price guides put the build at a median of roughly $25K to $150K, depending on type. Monthly run cost depends on volume; in our worked example, tools cost under $400 a month and maintenance about $1,600. Off-the-shelf SaaS starts far lower, as a subscription. Decide by the monthly value, not the price tag.
Can I build my own AI for free?
You can build a prototype for close to nothing: open-weight models are free to download, and tools such as Pinecone and Langfuse have free tiers. What isn't free is the production part — the evals, integrations, security testing, monitoring and upkeep that make a system trustworthy. That is where most of the cost of AI development sits, and why a free prototype is a good way to learn and a poor way to estimate.
Is building an AI agent worth it?
It is worth it when the monthly value clears the build and run costs within the first year, on a narrow, high-volume task where a mistake is recoverable. Gartner predicts over 40% of agentic AI projects will be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls. Run the worked-example maths on your own baseline first; if it doesn't pay back inside a year, build something narrower.
How long does AI development take?
The published guides put a proof of concept at 4 to 10 weeks and a first production version of a focused project at roughly 2 to 4 months; multi-system platforms take quarters. Integrations and data preparation decide where you land in those ranges far more than the model does. Ask for working software in your environment early and at every milestone, not a reveal at the end.
Why do AI development quotes vary so much for the same project?
Because they price different projects under the same name. One quote assumes read-only access to clean data and a person approving every output; another assumes write-back to a legacy system, an eval set and monitoring. Some include upkeep, most don't. Compare quotes on their assumptions — scope, integrations, quality bar, run-cost ceiling and code ownership — rather than on the total.

