How much to charge for a chatbot
How much to charge for a chatbot comes down to one question: what is it wired into? A scripted FAQ bot that answers from a fixed set of responses, an AI bot that answers from the client's own documents and site content, and a bot connected to live systems - booking, orders, a CRM - are three different products at three different prices, even if the client calls all of them "a chatbot." Price the tier as a fixed project fee, add a monthly fee on every AI tier, and never quote hours.
This is the CCC Chatbot Pricing Ladder: three tiers a client can point at, each described by what the bot can do rather than how it works. It kills the vague "how much for a chatbot" conversation, because the client stops pricing a mystery and starts choosing a deliverable - and most will talk themselves up a tier once they see what the next rung does.
The three tiers, and what moves a quote
The tiers are separated by capability, and capability is separated by integrations. That is the honest cost driver: wiring a bot into a booking system or a CRM is where the real scope lives, so it is where the price moves.
The CCC Chatbot Pricing Ladder
| Tier | What the bot does | How to price it |
|---|---|---|
| Scripted FAQ bot | Answers a fixed set of questions with pre-written responses, hands off to a human or a contact form | Low fixed fee - an entry product, priced to close fast and open the relationship |
| Grounded AI bot | Answers naturally from the client's own content - site, docs, policies - and captures leads | Mid fixed fee plus monthly - this is the default tier most small businesses actually need |
| Integrated AI bot | Everything in tier two, plus live actions: check availability, book, look up an order, write to the CRM | Highest fixed fee plus monthly - price per integration, because each one is its own scope |
- Integrations move the price most. Each connected system is a scoped line item with its own fee. Name them individually in the quote so adding one later is an upsell, not an argument.
- Content volume moves the mid tier. A bot grounded in ten pages and a bot grounded in three hundred support articles are different setup jobs - ask how much content exists before you quote.
- Channels multiply surface area. Website widget only is the default; the same bot on WhatsApp or Instagram is an add-on per channel, not a freebie.
- Who keeps answers current moves the monthly. If you update the bot's knowledge when their prices and policies change, that maintenance is priced in the monthly fee - never bundled silently into the build.
Why every AI tier carries a monthly fee
A chatbot is not a website - it costs money every day it runs. Every conversation on an AI tier consumes API usage, and every change to the client's business quietly makes some answer stale. If you hand over an AI bot for a one-time fee, you have either signed up to pay its running costs yourself or handed the client a bot that is slowly going wrong with your name on it.
So the rule is simple: every AI-powered tier ships with a monthly fee that covers usage within a stated conversation volume, a monthly review of what people actually asked, and knowledge updates when the business changes. Put the volume number in the agreement so a traffic spike becomes a plan upgrade conversation instead of a margin leak. This is the same recurring logic as [how to price a maintenance retainer](/blog/how-to-price-a-maintenance-retainer) - the chatbot version just has a hard cost floor underneath it, which makes the monthly fee easier to defend, not harder.
Quote the outcome, not the technology
The client is not buying a chatbot. They are buying questions answered at midnight, leads captured while they sleep, and fewer repetitive emails in their inbox. Every line of the quote should be written in that language. "Your visitors get instant answers from your own content, 24 hours a day, and every conversation that looks like a buyer gets captured with contact details" closes. "AI-powered conversational agent with retrieval over your knowledge base" gets you a confused pause and a price objection.
And keep the build mechanism out of the pricing conversation entirely. Claude Code compressing a chatbot build from weeks to days is your margin story, not the client's discount. Anchor the price against what the bot replaces - hours of answering the same questions, missed after-hours leads, a part-time hire they were considering - and the fixed fee sounds small next to the problem. If they push on price anyway, that conversation is handled in [the "can you do it cheaper" objection](/blog/can-you-do-it-cheaper-objection).
The pricing mistakes that kill chatbot margin
- Quoting before you have seen the content. The number one source of underwater chatbot projects is discovering after signing that the client's "docs" are forty contradictory PDFs. Ask for the content before the number leaves your mouth.
- Leaving integrations vague. "Connects to your systems" in a quote means every system they think of later is included. Name each integration as its own line with its own price.
- Skipping the scope document. A chatbot deal has more assumption gaps than most builds - channels, volume, who updates knowledge, what happens when the bot cannot answer. Put it on one page using [the statement of work format](/blog/how-to-write-a-statement-of-work-for-an-ai-project) before you start.
- Treating the FAQ tier as beneath you. The scripted bot is a fast, low-risk yes that opens the account - and the upgrade conversation to the AI tier starts the first time the client sees a question the scripts cannot handle.
- Unlimited revisions on the bot's personality. Tone and wording tweaks are the scope creep vector on chatbot projects. Include a set number of revision rounds, then bill per round.
Put the ladder in front of a real client
Pricing structure only earns money when it is in front of someone with a problem. The pitch is one paragraph: three tiers, each described by outcome, each with a fixed price and a clear monthly where it applies - sent as [a one-page proposal](/blog/one-page-ai-proposal-that-closes), not a menu of technologies. Local service businesses, coaches, and small e-commerce shops are the natural first market, because they feel the repeated-questions problem daily and nobody has offered them a straight answer on price.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How much should I charge for a chatbot?
Price by tier, not by hours. A scripted FAQ bot is a low fixed fee priced to close fast. An AI bot grounded in the client's own content is a mid fixed fee plus a monthly. A bot integrated with live systems - booking, orders, CRM - is the highest fixed fee, priced per integration, plus a monthly. The tier is set by what the bot is wired into, because integrations are where the real scope lives.
Should a chatbot have a monthly fee?
Every AI-powered tier should. The bot consumes API usage each day it runs, and the client's business changes make answers stale over time. The monthly covers usage within a stated conversation volume, a review of what people asked, and knowledge updates. A one-time-only AI bot deal means you own the running costs and the reputation risk for free.
What makes a chatbot project more expensive?
Integrations first - each connected system (booking, orders, CRM) is its own scoped line item. Then content volume for grounded bots, extra channels beyond the website widget, and who is responsible for keeping the bot's knowledge current. Build difficulty is not the driver; what the bot is wired into is.
Should I tell clients the chatbot is built with Claude Code?
Keep the pricing conversation on outcomes - answered questions, captured leads, fewer repetitive emails - and price against what the bot replaces. The build tooling is your margin story, not the client's discount. If asked directly, be honest about your stack, but do not lead the quote with technology the client cannot evaluate.
What should be in a chatbot project scope document?
The tier and what the bot can do, the named integrations with individual prices, the channels included, the conversation volume the monthly fee covers, who updates the bot's knowledge, what happens when the bot cannot answer, and a set number of revision rounds on tone and wording. One page, agreed before the build starts - chatbot deals have more assumption gaps than most projects.
Last reviewed by Duncan Rogoff on September 22, 2026
