StackLift
Cost guide · 2026

How much does it cost to build an AI chatbot in 2026?

In 2026, an AI chatbot typically costs $15k – $21k on the recommended Standard plan (~2 months), or $6k – $8k as an MVP-first launch (~1 months). These are the free estimate's own numbers for a typical scope; the biggest drivers are the features in the first version, the integrations and the user roles.

Delivery options

What an AI chatbot costs, by delivery plan

The same four options, prices and timelines the free estimate shows for this scope. Prices include design, build, testing and project management.

MVP First

Lowest cost

$6k – $8k

Validate fast, iterate with data

Core features only. Launch in weeks, not months. Remaining scope delivered in Phase 2 based on real user feedback.

Timeline
~1 months
Team
12 people
Effort
~370 hours

Phases: Discovery & Architecture Planning (1 wk) · UX / UI Design (1 wk) · Database Design & API Architecture (1 wk) · Backend Development & Integration (2 wk) · Frontend UI / UX Development (1 wk) · AI / Agentic Workflow Development (1 wk) · QA, Testing & Bug Fixes (1 wk) · Deployment, DevOps & Launch (1 wk)

Standard

Recommended

$15k – $21k

Best value — full scope, sustainable pace

Complete scope delivered across balanced parallel tracks. Optimal quality-to-cost ratio with a stable, proven team.

Timeline
~2 months
Team
13 people
Effort
~597 hours

Phases: Discovery & Architecture Planning (1 wk) · UX / UI Design (1 wk) · Database Design & API Architecture (1 wk) · Backend Development & Integration (3 wk) · Frontend UI / UX Development (3 wk) · AI / Agentic Workflow Development (2 wk) · QA, Testing & Bug Fixes (1 wk) · Deployment, DevOps & Launch (1 wk)

Fast Track

30% faster

$18k – $25k

30% faster — expanded parallel teams

Larger teams working in parallel across all tracks. Dedicated frontend, backend, and QA running simultaneously from day one.

Timeline
~2 months
Team
13 people
Effort
~597 hours

Phases: Discovery & Architecture Planning (1 wk) · UX / UI Design (1 wk) · Database Design & API Architecture (1 wk) · Backend Development & Integration (2 wk) · Frontend UI / UX Development (2 wk) · AI / Agentic Workflow Development (1 wk) · QA, Testing & Bug Fixes (1 wk) · Deployment, DevOps & Launch (1 wk)

Priority / Rush

Fastest

$20k – $29k

Maximum speed — all hands, dedicated team

Every resource fully dedicated to your project. Daily standups, dedicated PM, maximum parallel execution. For critical launches.

Timeline
~1 months
Team
15 people
Effort
~597 hours

Phases: Discovery & Architecture Planning (1 wk) · UX / UI Design (1 wk) · Database Design & API Architecture (1 wk) · Backend Development & Integration (2 wk) · Frontend UI / UX Development (1 wk) · AI / Agentic Workflow Development (1 wk) · QA, Testing & Bug Fixes (1 wk) · Deployment, DevOps & Launch (1 wk)

The typical scope these prices are for

Starting point
Customer Support AI Bot
Platforms
Claude (Anthropic) and OpenAI GPT (ChatGPT)
10 features
AI Customer Support Bot, RAG Vector Database, Public REST API, Admin Dashboard, Activity Feed / Audit Log, Voice AI Integration, AI Content Generation, Real-Time Chat (1-on-1), Interactive BI Dashboards and Data Import (CSV / Excel)
Integrations and tools
Knowledge from your website and docs, Answers with sources (RAG), Hand-off to a person and Actions: orders, bookings, account lookups
User roles
2, standard complexity
AI running cost
about $420 a month at today's model prices

Pick the same in the free estimate and you get these numbers. Add or remove features, integrations or roles and the price moves with them.

What drives the price

Five things that move the number most

  1. 1. Features in version one

    The biggest driver. Ship the workflow that proves value first; phase the rest.

  2. 2. Integrations

    Payments, CRM, maps, messaging or AI providers each add build and testing time.

  3. 3. User roles and permissions

    Every role (customer, admin, partner…) adds screens, rules and tests.

  4. 4. Design detail

    Standard components are faster; a custom design system and motion take longer.

  5. 5. Security, scale and compliance

    Audit logs, data residency, HIPAA or PCI work add effort up front.

Questions

How much does it cost to build an AI chatbot?

In 2026, an AI chatbot typically costs $15k – $21k on the recommended Standard plan (~2 months), or $6k – $8k as an MVP-first launch (~1 months). These are the free estimate's own numbers for a typical scope; the biggest drivers are the features in the first version, the integrations and the user roles.

How long does it take to build an AI chatbot?

About 5 weeks as an MVP-first launch and 9 weeks for the full scope on the Standard plan, with a team of 12–13. Fast Track and Priority shorten that with a larger team, at a higher price.

Why is there a range and not one price?

The range covers how the scope settles in discovery: the exact features in the first version, the integrations (payments, CRM, maps…), the user roles and the design detail. The free estimate replaces the typical scope with yours.

What does it cost to run each month?

Besides hosting, the AI usage of this scope runs about $420 a month at today's model prices, paid to the AI providers. See current model prices at /llm-pricing.

How do I get an exact price for my project?

Answer a few questions in the free StackLift estimate: it scopes an AI chatbot feature by feature and returns cost, timeline and team, with no signup.

The complete guide

What it costs to build an AI chatbot: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

AI chatbot cost depends on the channels it runs on (website, WhatsApp, voice), the size and quality of the knowledge it answers from, whether it takes actions like bookings or order lookups, how it hands off to people, and the testing behind it. Model and messaging fees are billed separately. The free estimate prices your scope in about five minutes.

What does an AI chatbot include?

A modern AI chatbot reads a question, finds the right information in your content, and writes an answer in plain language, with a way to pass the conversation to a person when it cannot help. Behind the chat window sit the pieces that make it dependable: a knowledge pipeline, guardrails, hand-off, analytics and an admin area.

The typical scope on the estimate above covers the support bot, retrieval over your knowledge (RAG), a REST API, an admin dashboard and audit logs. Voice, content generation, team chat, dashboards, import, roles and privacy controls are optional.

  • Knowledge: your website, help center, policies and product documents, kept current.
  • Answers with sources, so customers and staff can check them.
  • Hand-off to a person with the conversation attached.
  • Actions: order status, bookings, account lookups and lead capture.
  • Analytics: what people ask, what failed, and what to fix.

What drives the cost of an AI chatbot?

AI chatbot cost drivers
DriverWhy it moves the priceHow to keep it down
ChannelsWebsite, in-app, WhatsApp, Slack, Teams, SMS and phone each have their own setup and rulesLaunch on the channel where most questions arrive
Knowledge size and qualityMessy or outdated content needs cleaning; many sources need ingestion pipelinesStart with your top questions and the content that answers them
ActionsLooking up an order or booking a slot means secure integration and error handlingBegin with answers only, then add one action
Hand-off designRouting to staff needs queues, hours and context transferConnect to the help desk you already use
LanguagesEach language needs testingSupport the languages your customers actually use
Quality testingEvals on real questions are the main safeguard against wrong answersCollect real conversations before you build
VoiceSpeech in and out adds latency and telephony workTreat voice as phase two

How does cost break down by feature and integration?

Typical chatbot modules
ModuleSimple versionComplex version
Knowledge from website and docsCrawl a small, stable siteMany sources, access rules, frequent updates; see RAG
Answers with sourcesLink to the page usedCitations at passage level with confidence rules
Hand-off to a personEmail the transcriptLive transfer into Zendesk or another help desk with context
ActionsOrder status lookupBookings, returns and account changes with identity checks
Lead captureCollect name and emailQualify and sync to HubSpot or Salesforce
WhatsApp and messagingBasic replies; see WhatsAppTemplates, media, opt-in handling, Twilio routing
AnalyticsConversation countsUnanswered-question reports and quality scoring
GuardrailsTopic limits and tonePersonal data redaction, policy checks, abuse handling

The model list includes Claude, GPT, Gemini, Azure OpenAI, AWS Bedrock, Vertex AI, Mistral and open models. See Claude vs. GPT when choosing.

AI chatbot or AI agent: which do you need?

If people mainly need answers and the occasional simple lookup, a chatbot fits. If the assistant must complete multi-step work across several systems, such as processing a refund end to end, you are describing an agent, which needs more testing and approvals.

Chatbot compared with agent
ChatbotAgent
Main jobAnswer and guideDecide and act
AutonomyLowHigher, with approvals
Testing effortModerateHigher
Typical useSupport, FAQs, lead captureProcessing tasks across tools

Read AI agent vs. chatbot and the AI agent cost page if your needs lean toward action.

Should you launch a small chatbot first?

Yes. Launch on one channel with answers from your top content and a clear hand-off. Real conversations then show what to add: more content, a lookup, a second language. This follows the MVP approach; see MVP vs. full build.

The chatbot launch checklist lists what to confirm before you go live, and AI chatbot development describes the service.

How long does it take, and what happens in each phase?

Timelines vary by delivery plan; see the estimate above. In general, the timeline follows the scope and the plan you pick, and a one-channel answers-only chatbot sits at the short end.

  1. Scope: channels, content, actions and hand-off rules. A 3-day AI Scope Sprint documents them.
  2. Content preparation: gather and clean the knowledge the bot answers from.
  3. Build: retrieval, conversation design, channel setup, hand-off and admin tools.
  4. Evaluate: test on real questions, review wrong or missing answers, tune.
  5. Pilot: release to a small share of visitors with staff watching.
  6. Launch and improve: widen, then use analytics to fix gaps every week.

What does a chatbot cost to run after launch?

Ongoing chatbot costs
CostWhat it coversNotes
Model usageCharged for each question and answerGrows with conversation volume; see LLM pricing
Messaging feesWhatsApp, SMS and phone minutesBilled by the channel provider
Hosting and storageThe bot, its index and logsGrows with content
Content upkeepUpdating answers when policies and products changeThe most overlooked cost
Review and tuningReading failed conversations and fixing themWeekly at first, then less often
Staff for hand-offPeople answering escalated chatsOften falls as quality improves

How can you reduce the cost without cutting quality?

  1. Begin with one channel and your most common questions.
  2. Clean and trim your help content before ingesting it.
  3. Answer first, then add actions one at a time.
  4. Use a smaller model for routine questions and a stronger one for hard ones.
  5. Cache common answers to reduce usage fees.
  6. Reuse your existing help desk for hand-off instead of building one.
  7. Review failed conversations weekly and fix content, not just prompts.

What are the risks, and how do you control them?

Chatbot risks and controls
RiskControl
Wrong or invented answersAnswer only from your content, show sources, say "I don't know" and hand off; see hallucination
Personal data in chatsRedaction, retention rules and access limits
Off-topic or abusive useTopic limits, rate limits and moderation
Customers stuck with a botA clear route to a person at any time

If the bot touches regulated information such as health or financial data, ask your compliance team which rules apply before launch.

What should you ask before choosing someone to build your chatbot?

Chatbot demos always look good, so judge the builder on what happens after the demo. Ask for answers to these questions in writing and compare the replies.

  • How will you measure answer quality on our real questions before launch?
  • What does the bot say when it does not know, and how does it reach a person?
  • Which costs are ours (model usage, messaging, hosting) and which are in the price?
  • Who owns the prompts, the knowledge index and the code?
  • How do we update content, and who does it?
  • What do we see after launch: conversations, failures, cost?
  • How is scope change handled, and how do we approve it?

How does StackLift estimate and deliver a chatbot?

The free estimate scopes your chatbot feature by feature and returns cost, timeline and team in about five minutes, with no signup. A senior architect reviews every estimate before it becomes a commitment.

Pricing is by deliverable complexity (story points), not hours, with scope, budget and delivery path agreed before engineering begins. Agents work on feature branches and never touch production secrets, and CI/CD, observability, security review and rollback are in the plan from sprint one. The client portal shows live state, approvals, invoices and releases. You can also contact us.

Questions people ask

How much does it cost to build an AI chatbot?

It depends on channels, knowledge size, actions and hand-off. The estimate above shows ranges by delivery plan, and the free estimate tailors them to your scope. Model and messaging fees are billed separately.

Why do some chatbots cost so much more than others?

A bot that answers from a small FAQ is simple. A bot on several channels that looks up orders, speaks multiple languages and hands off with context needs integration, testing and analytics.

Can I build a chatbot for less?

Yes. Launch on one channel, answer from your best content, and use your existing help desk for hand-off. Add actions and languages once real conversations justify them.

What is the cheapest way to start?

A focused pilot on your website with answers from your help center and a clear hand-off. It proves value quickly before you widen the scope.

How much does it cost to maintain a chatbot?

Expect model usage, messaging fees, hosting, and time to update content and review failed chats. Content upkeep matters most because outdated answers hurt trust.

How do I stop the chatbot from making things up?

Ground answers in your own content, show sources, test on real questions, and let it say it does not know and pass the chat to a person. Weekly review of failed conversations keeps it accurate.

Can it work on WhatsApp and my website at once?

Yes, with one knowledge base behind both channels. Each channel adds its own setup, rules and fees, so many teams launch on one and add the second later.

Get your number

Your exact cost to build an AI chatbot

Pick your features, platforms and integrations; the estimate returns cost, timeline and team in about five minutes. Free, no signup.