Chatbot development cost depends on what the bot has to do behind the chat window: the systems it connects to, the state of your content, the channels and languages, and how much assurance a wrong answer calls for. We do not publish a price list, because two chatbots with the same interface can differ widely in the work behind them.
A bot that sits in the left column on every row is a small project. Each move to the right adds engineering and testing.
What drives the build cost of a chatbot | Cost driver | Lower cost | Higher cost |
| Knowledge | One clean help center | Many sources, scans, tables and per-user permissions |
|---|
| Actions | Answers only | Reads and changes records in your systems |
|---|
| Channels | One website widget | Web, in-app, messaging apps and phone |
|---|
| Languages | One | Several, each with its own test conversations |
|---|
| Handover | A transcript sent by email | Live transfer into your help desk with context |
|---|
| Assurance | Internal use, low stakes | Public use, sensitive topics, full audit trail |
|---|
Running cost is a separate line: model usage per conversation, hosting, any messaging or telephony fees, and upkeep of the content and the tests. We estimate cost per conversation from measured token counts during the prototype, before you commit to the full build. Reducing it later is covered under LLM cost optimization.