"AI chatbot" covers a huge range of actual builds
A chatbot that answers FAQs from a document set and a chatbot that takes multi-step actions across several internal systems are both called "AI chatbots" in casual conversation — but one is a weekend-scale RAG implementation and the other is a serious engineering project. Cost only makes sense once you know which one you're actually building.
What drives the cost
- Knowledge scope — a single document set is far simpler than continuously syncing multiple live data sources
- Conversation complexity — single-turn Q&A vs. multi-turn conversations that need to track context and state
- Actions vs. answers — a chatbot that only answers questions is simpler than one that takes actions (booking, updating records, triggering workflows) via tool use
- Integration surface — connecting to your CRM, support platform, or internal APIs adds real engineering time beyond the conversational layer itself
- Evaluation and guardrails — testing for hallucination, defining what the assistant should refuse to answer, and monitoring quality post-launch is real, often underestimated work
Rough ranges
General market context, not a quote — actual scoping determines the real number:
- Simple RAG-based FAQ/document assistant: the fastest and most cost-effective AI build, typically weeks rather than months
- Multi-source knowledge assistant with integrations: a meaningfully larger build, given the data pipeline and sync work involved
- Agentic workflow with tool use across systems: the most complex tier — real software engineering on top of the AI layer, priced accordingly
See How Much Does Software Development Cost? for the general cost framework this fits into, and Custom Software Development Cost in India for market-level pricing context.
Ongoing cost, not just build cost
Unlike a typical web feature, a live AI assistant has a real ongoing cost line: model API usage, and continued evaluation as usage patterns evolve. Budget for this as an operating cost, not a one-time expense.
Scope it properly before you price it
Tell us what you want the assistant to actually do — answer questions, take actions, or both — and we'll give you a real estimate against that, not a guess off the word "chatbot."