How Much Does It Cost to Develop a Chatbot? A 2026 Pricing Breakdown

Chatbot development cost by project type

Most custom chatbot projects fall into one of three tiers. The price differences track scope: how much the bot knows, how many systems it touches, and how much it is allowed to do on its own. These are the same ranges we publish for our AI chatbot development services.

Tier	Scope	Cost Range	Build Time
Basic FAQ / Knowledge Base Bot	Your docs, Q&A, web embed	$5,000–$15,000	2–5 weeks
Integrated Workflow Bot	CRM/help desk/ERP connections, multi-step workflows	$15,000–$50,000	4–12 weeks
Custom Conversational AI Agent	Multi-channel, domain-grounded, tool use, advanced analytics	$50,000–$150,000+	3–9+ months

Monthly operating costs are separate from these build prices and are covered below. Large enterprise deployments can exceed $250,000.

Basic knowledge-base bot ($5,000–$15,000). The bot answers questions from your existing documentation, FAQs, and help articles, and hands off to a person when it is unsure. Most of the work is preparing your content, designing the conversation, and testing answers against real questions. Expect a web embed and basic reporting, but no deep system connections. It suits teams whose support inbox is dominated by repeat questions.

Integrated workflow bot ($15,000–$50,000). Here the bot takes action, not just answers. It creates tickets, qualifies and routes leads, checks order status, or books appointments by talking to your CRM, help desk, or ERP. Every integration adds design, build, and testing work, which is why this tier takes 4–12 weeks and why the top of the range is so much higher than the basic tier.

Custom conversational agent ($50,000–$150,000+). This tier covers multi-channel deployment, domain-specific behavior, advanced analytics, and often regulated data. The bot may run multi-step processes with several systems and operate within strict guardrails. Projects at this level run 3–9+ months and can exceed the top of the range when compliance or integration complexity is high.

---

What drives chatbot development cost

Two chatbots with the same name can differ by an order of magnitude in price. These six factors explain most of the difference. The effects below are directional, not measured.

1. Integrations

This is usually the biggest lever. A handoff that emails a transcript or calls a webhook is a few days of work. A two-way CRM integration that creates and updates records is often several weeks. Older ERPs, scheduling systems, and electronic health record systems with limited APIs can take up a large share of the budget on their own. Count the systems the bot must read from and write to, and check which have a documented API.

2. Data preparation

The bot is only as good as the content behind it. If your knowledge base is current and well organized, preparation is light. If answers are scattered across PDFs, old tickets, and people's heads, expect real effort to gather, clean, and structure them. This is often the most valuable work in the project, and the one teams underestimate most.

3. Channels

A web widget is the baseline. Adding WhatsApp, SMS, email, voice, Slack, or Microsoft Teams means extra connectors, channel-specific formatting, and more testing. Voice is usually the most expensive addition because it adds speech handling and tighter response-time requirements.

4. Languages

Supporting a second language is more than translation. Retrieval, prompts, test sets, and escalation scripts all need to work in each language, and quality has to be checked by someone who reads it natively. Each added language increases testing and content work, though the core engine is shared.

5. Compliance and security

Handling health, financial, or other sensitive data (HIPAA, SOC 2, or GDPR requirements, for example) adds access controls, audit logging, data retention rules, vendor agreements, and review time. This is the factor most likely to push a project from the middle tier into the top one. If you need a SOC 2 or HIPAA posture, say so at the start, because it affects architecture, not just paperwork.

6. Custom UI

An off-the-shelf chat widget with your colors is inexpensive. A fully branded interface, an in-app assistant embedded in your product, rich cards, file uploads, or a custom agent console for your support team add design and front-end work that can rival the conversation engine itself.

---

Ongoing chatbot costs after launch

The build fee is not the whole bill. Running costs fall into two categories that are easy to confuse, and they scale differently.

Infrastructure and usage

This covers LLM API calls, hosting, the vector or search database, storage, messaging and voice channels, and logging. It runs from under $100 a month for a small, low-volume bot to thousands of dollars a month at high volume. Model usage for a low-volume text bot can be a few dollars to tens of dollars a month. Your cost per conversation depends on the model you choose, how long conversations run, and how much of your content is sent with each question. Because model prices change often, we don't quote per-token prices here. Ask any vendor to estimate cost per conversation from your real transcripts and to show how it scales if volume doubles.

Managed monitoring and optimization

This is the human side: reviewing conversations, improving prompts and workflows, reviewing failed answers, updating content, fixing integrations, and handling QA and support. It typically costs roughly $500–$5,000+ a month. Someone has to watch for wrong answers, unanswered questions, and drift as your products and policies change, and dashboards for resolution rate, escalation rate, and abandoned conversations make that measurable. A chatbot that is never updated becomes a liability within months, so budget for this from day one. A small bot you manage yourself may need little beyond your own time.

---

Build vs. buy: SaaS chatbot builders vs. custom development

A subscription chatbot platform is often the right first step for simple needs. A custom build makes sense once the bot has to fit your systems, your data, or your compliance requirements. For a deeper look at choosing a vendor, read our guide to AI chatbot development services.

	SaaS chatbot builder	Custom development
Upfront cost	Low or none	$5,000–$150,000+
Ongoing cost	Subscription that typically grows with seats or conversation volume	Infrastructure from under $100 to thousands a month, plus roughly $500–$5,000+ a month for managed optimization
Time to launch	Days to a few weeks	2–5 weeks to 9+ months
Integrations	Prebuilt connectors for popular tools; limited beyond them	Built to your systems
Control over answers	Template-level; limited access to retrieval and prompts	Full control of logic, guardrails, and testing
Data ownership / hosting	Governed by the platform's terms and hosting model	Can be deployed in your own cloud accounts and structured around your ownership requirements
Compliance fit	Depends on the vendor's certifications	Designed around your requirements
Best for	Simple FAQ coverage, quick pilots	Workflows, sensitive data, differentiated experiences

The two are not exclusive. Many teams pilot with a SaaS tool, then commission a custom build once they know which conversations and integrations matter. If you are working around the tool's limits, that is the signal to go custom.

What buying costs today (as of September 2026)

• Chatbase: Hobby $40, Standard $150, Pro $500 per month (monthly billing).
• Botpress: Plus $150/month and Team $750/month, billed annually; AI usage beyond the included credit is billed per conversation.
• Intercom Fin: from $0.99 per Fin outcome, plus Intercom seats from $29 per seat/month billed annually.

Prices change often; check each vendor's page before you budget.

With SaaS plans at these prices, it rarely makes sense to spend $20,000 on custom development just to answer 30 FAQs. Custom development pays off when the assistant needs proprietary workflows, integrations, business logic, security requirements, or a differentiated product experience.

---

Three sample chatbot budgets

The scenarios below are illustrative examples we constructed to show how line items add up, not real client projects or quotes. Your scope and prices will differ. The line items in each scenario sum exactly to the stated total.

Scenario 1: SaaS customer support bot (knowledge-base tier)

A software company wants a bot that answers product questions from its help center and hands anything complicated to its existing help desk.

Line item	Estimate
Discovery and question audit	$1,500
Knowledge-base cleanup and retrieval pipeline	$3,500
Conversation design and escalation rules	$1,500
Web widget and handoff to the existing help desk by email or webhook	$2,000
Test set and QA	$1,500
Launch, analytics dashboard, and handover	$1,000
Total build	$11,000

Illustrative timeline: about 3 weeks. Illustrative managed operating budget: about $600/month, including infrastructure, monitoring, and light ongoing tuning, assuming roughly 1,000 conversations a month.

Scenario 2: B2B lead-qualification bot (integrated workflow tier)

A B2B company wants a website assistant that asks qualifying questions, scores the lead, books a meeting with the right rep, and writes everything into its CRM.

Line item	Estimate
Discovery and qualification-criteria workshop	$3,000
Conversation design, including objection handling	$4,000
Product and pricing content retrieval	$5,000
CRM integration: lead creation, scoring fields, routing	$9,000
Calendar booking and sales handoff	$4,000
Testing and QA, including integration tests	$4,000
Analytics and launch	$3,000
Total build	$32,000

Illustrative timeline: about 8–10 weeks. Illustrative managed operating budget: about $1,200/month, including infrastructure, monitoring, and light ongoing tuning, assuming roughly 3,000 conversations a month.

Scenario 3: Healthcare patient-intake bot (custom agent tier)

A provider wants a bot that collects intake information over web and SMS, in two languages, checks it against scheduling, and operates within strict privacy controls.

Line item	Estimate
Discovery, compliance scoping, and risk review	$10,000
Conversation design with clinical guardrails and escalation	$12,000
Intake workflow and scheduling-system integration	$30,000
Security controls, access management, and audit logging	$18,000
Web and SMS channels in two languages	$12,000
Testing, adversarial testing, and review support	$14,000
Launch, monitoring dashboard, and staff training	$9,000
Total build	$105,000

Illustrative timeline: about 4–5 months. Illustrative managed operating budget: about $3,000/month, including infrastructure, monitoring, and light ongoing tuning, assuming roughly 10,000 conversations a month across both channels. Legal review, business associate agreements, and compliance sign-off are handled by your own counsel and compliance team and are not included in this estimate.

Large healthcare deployments involving EHR integration, enterprise security reviews, or complex clinical workflows can substantially exceed this example, often into the $150,000–$300,000+ range.

---

How to lower chatbot development cost without cutting corners

• Start with your highest-volume questions. A bot that handles the top five to ten use cases well is cheaper than one that attempts everything, and it will usually perform better.
• Fix your content first. Consolidating and updating your knowledge base before the build shortens the project and improves accuracy.
• Integrate one system at a time. Launch with the single integration that removes the most manual work, then add others once the bot is proving its value.
• Run a proof of concept on your real data. A few weeks testing against actual tickets or FAQs exposes scope problems early, when they are cheap to fix.
• Plan for maintenance up front. Budgeting for tuning from the start costs less than rebuilding a bot that went stale.