The AI chatbot pitch is almost always built on impressive numbers: '40% reduction in support tickets.' '24/7 customer service without additional headcount.' 'Answers customer questions in under 3 seconds.'
These outcomes are achievable. They are also achievable only with the right use case, the right knowledge base, and a properly scoped implementation. Before committing to an AI chatbot investment, it is worth building an honest cost-versus-savings model for your specific situation.
IBM research on AI in customer service found that chatbots can handle up to 80% of routine customer queries without human intervention — but also confirmed that the gap between that ceiling and what most implementations actually achieve comes down to knowledge base quality and use case scoping.
What a Business-Grade AI Chatbot Actually Costs
There are three cost categories: build, run, and maintain.
Build: a RAG (Retrieval Augmented Generation) chatbot trained on your knowledge base, deployed on your website or internal tool, with an admin interface to update content, runs from £8,000 at the lower end of scope. This covers scoping, data preparation guidance, build, testing, deployment, and 60 days of post-launch support.
Run: ongoing LLM API costs (OpenAI or Anthropic) depend heavily on usage. For a business chatbot handling 500 queries per day at moderate token counts, expect £80–£250/mo in API costs.
Maintain: prompt performance degrades as your content evolves. A monthly maintenance retainer from £600/mo covers monitoring, content updates, model upgrades, and performance optimisation.
Year 1 total: approximately £8,000 build + £3,600 maintenance + £1,800 API = £13,400 fully loaded for a well-scoped SMB chatbot.
What It Saves
The savings calculation depends on what the chatbot handles. The most common use case: first-line customer support.
Assume your support team currently handles 200 inbound enquiries per week. 60% of these are answerable from your knowledge base (product questions, pricing, process queries, FAQ). Each currently takes 8 minutes to respond to.
200 enquiries × 60% = 120 automatable queries per week × 8 minutes = 960 minutes = 16 hours of support time per week.
At a fully-loaded support cost of £20/hour: £320 per week, £16,640 per year saved from support team time alone.
Against a £13,400 Year 1 cost, that is a positive ROI in Year 1 — with the maintenance cost dropping to recurring API + support fees from Year 2.
Where Chatbot Projects Fail
- Knowledge base quality: a chatbot can only answer questions as well as the information it has been trained on. If your internal knowledge is unstructured, outdated, or incomplete, the chatbot will hallucinate or deflect. Data preparation is the most underestimated phase of any AI chatbot project.
- Use case misalignment: chatbots excel at answering structured queries from known knowledge. They struggle with complex negotiations, nuanced complaints, and any situation requiring human empathy and judgment. Deploying a chatbot to handle the wrong type of query is worse than no chatbot.
- No feedback loop: a chatbot without a mechanism to identify unanswered questions and improve the knowledge base will degrade over time as your business evolves.
Is It Right for Your Business?
The clearest signal that a chatbot is a good investment: you have a support team spending 30%+ of their time answering the same 50 questions repeatedly, you have a knowledge base or FAQ that could serve as training data, and you have the operational infrastructure to maintain the system after launch.
If those conditions are not met yet, the right first step is an AI Readiness Audit — which will tell you exactly what is needed to reach them.
Related: Why 'We'll Figure Out AI Later' Is Becoming a Competitive Liability