A typical AI chatbot for a small business costs between $4,000 and $12,000 to build, before connecting it to your other systems. Each integration (your CRM, booking calendar, help desk or store) typically adds $1,500 to $4,000. These are typical US ranges for a senior team, and a fixed quote comes after a short call about what you need.
That is a wide range, so the rest of this guide explains what moves a chatbot toward the low or high end, what the price includes, and how to tell whether you need a custom build at all.
What you are paying for
A chatbot project is not just the chat window. The work usually falls into five parts:
- Scoping. Deciding what the bot should answer, what it should refuse, and when it hands a person the conversation.
- Knowledge. Preparing your FAQs, policies, product pages and documents so the bot answers from your material instead of guessing.
- Build. The conversation logic, the chat interface on your site or app, and the connection to the AI model.
- Integrations. Pulling data from, or sending data to, the tools you already use.
- Testing and launch. Trying hundreds of real questions, fixing wrong answers, and setting up a way to review conversations after launch.
The last part is the one cheap projects skip, and it is where most chatbot failures come from.
Typical price ranges
| Item | Typical range |
|---|---|
| AI assistant or chatbot (build) | $4,000 to $12,000 |
| Each integration (CRM, calendar, store, help desk) | $1,500 to $4,000 |
| Example: chatbot plus two integrations | $7,000 to $20,000 |
| A second language | $2,000 to $5,000 |
The example row is simple arithmetic: the build range plus two integrations at the low and high end. Your own number depends on the factors below.
What moves the price
- How many questions it must handle. A bot that answers 30 common questions about hours, pricing and shipping is far cheaper than one that must handle account-specific questions.
- Where its knowledge lives. Clean FAQ pages are quick to use. Scattered PDFs, old emails and a spreadsheet of exceptions take preparation time.
- Integrations. A bot that only answers questions needs none. A bot that books appointments, looks up an order or creates a lead in your CRM needs one per system.
- Handoff to a person. Passing a conversation to your team, with the history attached, takes extra work but saves your customers from repeating themselves.
- Languages. Each additional language needs its own testing, not just translation.
- Safeguards. Limits on what the bot may say about prices, refunds or medical and legal topics add design and testing time.
Costs after launch
Building the bot is not the only cost. Plan for these as well:
- AI usage fees. Most chatbots call an AI model from a provider that charges based on usage. The more conversations you have, the higher this goes. Ask for an estimate based on your expected traffic.
- Hosting and tools. Small recurring costs for the servers and services the bot runs on.
- Review and improvement. Someone should read a sample of conversations each month and fix wrong answers. This can be your own team after a short handover.
We do not quote a flat monthly figure here because it depends on your traffic and the model you use. A good builder will give you an estimate before you sign.
Do you need a custom chatbot?
Not always. If you get fewer than a few inquiries a day and the questions are repetitive, a well-written FAQ page and a contact form may serve you better. A ready-made live chat tool is also fine when you have staff watching it during business hours.
A custom AI chatbot starts to make sense when:
- You get the same questions repeatedly, and your team's time goes to answering them.
- Customers write in outside business hours and you lose leads.
- The answer lives in your own documents, and generic tools cannot use them.
- You want the bot to take an action, such as booking a visit or creating a lead.
Questions to ask any builder
Use these to compare quotes on equal terms:
- Which questions will the bot answer, and what happens when it does not know?
- Where does it get its answers, and how do we update them?
- How do you test it before launch, and how many real questions do you try?
- Who owns the code, the prompts and the conversation data?
- Which AI provider does it use, and what will usage cost at our volume?
- Can a person take over a conversation, and does the history come with it?
A builder who can answer these plainly has done this before. One who answers with a flat price and no questions of their own has probably not.
How to get a fixed quote
Before you talk to anyone, gather three things: the 20 questions customers ask most, the tools the bot would need to connect to, and where you want it to live (website, app, or messaging). With those, a developer can scope the work in one call and give you a fixed price instead of an hourly estimate.
If you want a rough number for a wider project first, try our website cost calculator. For comparison on how we price other custom software, see how much a custom CRM costs.
Ready to scope yours?
Our AI solutions service covers support chatbots, answers over your own documents, and automations. To talk through your case, book a 30-minute call. If your needs are simple, we will tell you so.