"How much does a chatbot cost" doesn't have one answer, because a chatbot that answers FAQ questions and a chatbot that qualifies leads, checks order status, and hands off to a human are completely different projects wearing the same label.
What actually drives the cost
- Integration depth — a bot that only talks is cheap; one that reads and writes to your CRM, order system, or calendar costs more because those integrations are the real work.
- Knowledge grounding — a bot answering from a handful of FAQ pages is simple; one grounded in thousands of documents needs a real RAG pipeline.
- Conversation design — how many distinct flows does it need to handle, and how gracefully does it fail when it doesn't know the answer?
- Channels — supporting web chat only is simpler than web plus WhatsApp plus in-app, each of which has its own constraints.
- Ongoing tuning — a bot's accuracy in month one is rarely as good as month six, once it's been tuned against real conversations.
The ongoing cost people forget
Model API usage scales with conversation volume, and it's worth estimating early rather than being surprised later. It's usually a modest, predictable line item — but only if someone accounted for it upfront.
How to scope it sensibly
Start with the highest-volume, most repetitive questions your team currently answers by hand — that's usually where a chatbot pays for itself fastest. Resist the urge to scope every possible feature into version one; a focused bot that handles 70% of a specific queue well beats a broad one that handles everything poorly.
Want this built for your business?
We design and ship exactly this kind of system — tell us what you're trying to solve.
Book a Free Consultation