How Much Does an AI Chatbot Cost to Build?

The short answer: $500–$1,800 for most builds

The band is wide because chatbot covers three genuinely different products. At the bottom, a lead-capture bot greets website visitors, answers common questions and collects contact details. In the middle, a retrieval-based support bot answers from your actual documentation. At the top, one assistant serves several channels and reads or writes data in your other systems.

All three are quoted fixed before work starts, run on your own infrastructure with code in your GitHub, and carry a bug-fix warranty. What you are buying in each case is the same thing: fewer repetitive conversations handled by humans, and no enquiry left waiting overnight.

What each budget buys

Here is the band as three tiers. Read the third column closely — the jumps are about knowledge and integration depth, never about a fancier chat bubble.

What drives the price up or down

Four factors explain nearly every quote we send, and three of them are in your control before the project starts.

• Knowledge base shape — fifty clean FAQ pages are quick to ingest; a decade of PDFs, scanned forms and contradictory policy versions takes real preparation work.
• Number of channels — each additional channel (WhatsApp, Instagram, Messenger) brings its own API, message formats and approval process.
• Integrations — a bot that reads order status from Shopify or writes leads into HubSpot costs more than one that only talks, and is usually worth far more too.
• Handoff design — routing hard conversations to a human, with full context attached, is the feature that separates bots customers tolerate from bots they appreciate.

Running costs: the honest monthly picture

A custom chatbot has two ongoing bills. Hosting is small — these are lightweight services, typically $5–15 a month on a small server or serverless plan. LLM usage scales with conversations: at typical small-business volume, token costs usually land between $10 and $50 a month in your own API account, and sensible engineering (smaller models for routing, caching for repeated questions) keeps it at the low end.

Compare that with per-seat or per-resolution pricing on hosted platforms, which commonly grows with exactly the metric you are trying to increase. The custom bot's costs grow gently with volume; you own the whole stack; and no vendor can reprice your support channel from under you.

Chatbot builders versus custom: a straight answer

Subscription builders — the drag-and-drop tools with free tiers — are the right choice more often than a development studio should probably admit. If your bot needs scripted answers to a fixed question list, no access to your systems, and you are comfortable inside the builder's template, spend $0–50 a month and skip custom development entirely.

Custom earns its price in three situations: your answers live in your own documents and change often; the bot must read or write other systems — bookings, orders, CRM records; or the conversation itself is a product experience you want full control over. If you are unsure which side you fall on, that is precisely a scoping-call question, and the honest answer is sometimes the cheaper one.

Next step: a fixed quote in one working day

Tell us what the bot should answer, where the answers currently live, and what systems it should touch. That is enough for a written fixed quote within a working day — free, and never above $2,500 for a single phase.

The AI customer support chatbot use case has the full deliverable list if support is your pain point, and the website lead-capture chatbot page covers the sales side. Or book the free 30-minute call and bring your messiest support questions with you.