How much does building a chatbot cost?

From a simple FAQ bot to fully integrated conversational AI that lives inside your business systems: costs range from a few thousand to tens of thousands of euros. This article explains where those differences come from, so you can set a realistic budget.

Not a standard price, but a spectrum

The question "what does a chatbot cost?" is like asking "what does a car cost?": it depends entirely on what you need. A chatbot that answers frequently asked questions based on a fixed decision tree is a fundamentally different product from an AI assistant that consults your order system, CRM and knowledge base in real time.

The biggest cost variable is not the technology itself, but the depth of integration with your existing systems. A standalone chat widget on your website can be delivered within a limited budget. As soon as the chatbot has to look up orders in your ERP, schedule appointments in your calendar or update customer data in your CRM, the complexity grows, and with it the investment.

The chosen AI approach also plays a role. Older chatbots work with predefined flows (intent-based). Modern conversational AI uses large language models (LLMs) that understand natural language and generate contextual answers. The second route requires more knowledge of prompt engineering, RAG (Retrieval-Augmented Generation) architecture and vector databases, but delivers a better-quality product.

Three typical budget levels for chatbot development

The breakdown below gives a realistic picture of what you can expect at each budget level. The amounts are indicative: every project is custom, and the final investment depends on your specific requirements and technical environment.

Basic

FAQ chatbot or decision tree

A chatbot that answers frequently asked questions from a fixed set of answers. Well suited to easing the load on customer service for repetitive questions about opening hours, delivery terms or product information.

  • Fixed question-and-answer flows
  • Web chat widget on your site
  • Simple fallback to email
  • Basic analytics dashboard
  • Training on your content
Most popular

AI chatbot with system integration

A chatbot that, besides free-text conversation, also consults your business systems. Think of checking order status, scheduling appointments, or searching a knowledge base using RAG technology.

  • LLM-based (GPT-4, Claude, Gemini)
  • RAG with your own documentation
  • API integrations with CRM/ERP
  • Multichannel (web, WhatsApp, email)
  • Handoff to a live agent
  • Extensive analytics and logging
Enterprise

Fully autonomous AI assistant

A conversational AI that carries out tasks independently within your processes: processing orders, generating contracts, escalating tickets. Includes a compliance layer, audit trail and on-premise or private cloud hosting.

  • Agentic AI with tool use
  • Deep integration into business processes
  • Custom fine-tuning or private LLM
  • RBAC and audit logging
  • On-premise or private cloud option
  • Availability SLA
  • Ongoing management and optimisation

Seven factors that determine the cost

Every chatbot project is unique. Still, there are seven factors that affect the budget in almost every project. Below, we explain how each one comes into play.

Conversation complexity

A linear decision tree with ten questions is fundamentally simpler than an open conversation in which the bot has to remember context across several messages. The freer the conversation, the more NLU logic is needed.

Number of channels

A web chat widget alone is simpler than a bot that also has to be active on WhatsApp, Facebook Messenger, Teams and email. Each channel has its own API requirements and UX constraints.

System integrations

Every integration with an external system (CRM, ERP, ticketing system, knowledge base) requires API development, authentication handling and error handling. Two integrations don't double the cost, but they do add substantially.

Compliance and security

Does the chatbot process personal data? Then GDPR requirements apply: data minimisation, retention policy, right to erasure. In sectors such as finance and healthcare, sector-specific requirements come on top (DNB, NEN 7510).

AI model choice

A chatbot built on a commercial LLM (OpenAI, Anthropic, Google) has lower development costs but ongoing API costs per conversation. A self-hosted open-source model (Llama, Mistral) requires more initial work but can work out cheaper at high volume.

Knowledge base size

Does the chatbot need to search ten FAQ pages or thousands of product sheets, manuals and contract documents? In RAG implementations, the volume of source data determines the complexity of indexing, chunking and retrieval tuning.

Three routes: SaaS platform, custom or hybrid

There are roughly three ways to build a chatbot. Each has its own pros and cons in terms of cost, flexibility and management.

Aspect SaaS chatbot platform Custom development Hybrid approach
Initial budget Low — subscription costs High — one-off build Medium: SaaS core + custom layers
Ongoing costs Fixed monthly fee + per-conversation fees Hosting + AI API costs + maintenance Subscription + maintenance of custom layers
Flexibility Limited to platform features Fully custom Flexible where it counts
Time-to-market Fast — weeks Longer — months Average
Integration depth Standard integrations Unlimited Extensible
Suited to Simple customer service Complex business processes Growing organisations

Appfront often works with the hybrid approach: we use proven AI platforms as the foundation (OpenAI, Google Gemini) and build custom integrations and business logic around them. That gives you the best of both worlds: a solid AI core with the flexibility to integrate deeply into your systems.

Ongoing costs: don't forget operating expenses

The build cost is only the beginning. A chatbot running in production comes with monthly operating costs, which are often underestimated in the initial budget.

Fixed costs

  • Hosting and infrastructure (cloud compute, vector database)
  • LLM API costs per conversation (tokens in/out)
  • Monitoring and logging tooling
  • SSL certificates and domain management

Variable costs

  • Knowledge base updates for new products or policy
  • Prompt optimisation after analysing failed conversations
  • New integrations as your system landscape changes
  • LLM version upgrades (GPT-4 → newer model)

A good rule of thumb: expect monthly running costs equal to a fraction of the initial build cost. The exact proportion depends on conversation volume and the complexity of your integrations. Alongside the initial build, Appfront also offers ongoing management, so your chatbot keeps performing at its best.

What does a chatbot project involve?

A typical chatbot project goes through five phases. Each phase has a clear go/no-go moment, so you stay in control of the budget.

1

Discovery and scope definition

We map out your use case: which questions the chatbot answers, which systems it communicates with, and which channels are needed. The result is a functional design with a clear scope and budget range.

2

Proof of concept

A working prototype that handles the core conversations. Often built with a limited knowledge base and one or two system integrations. This lets us test whether the chosen approach delivers the quality you want.

3

Full development

The chatbot is built out with all integrations, channels and business logic. This includes edge-case handling, fallback flows and the integration with your live systems in a staging environment.

4

Testing and optimising

User tests with your team and a select group of end users. We measure success rate, average handling time and customer satisfaction. Prompt engineering is fine-tuned based on real conversations.

5

Go-live and further development

Rollout to production with monitoring. After go-live, a period of intensive analysis follows in which we review conversation logs and continuously improve the chatbot. This is not a one-off task but an ongoing process.

Frequently asked questions about chatbot costs

What are the ongoing costs of a chatbot after delivery? +

After delivery, you pay for hosting, LLM API usage (per conversation/per token) and, optionally, maintenance. At low volumes, API costs are negligible. With thousands of conversations a month, they can add up. A management contract for knowledge base updates and prompt optimisation is recommended for the best results.

Can I start with a simple chatbot and expand later? +

Absolutely. Many of our clients start with an FAQ chatbot or a limited RAG solution and gradually expand it with system integrations and additional channels. A phased approach limits risk and lets you use real usage data to decide which extensions deliver the most value.

What is the difference between a chatbot and conversational AI? +

A traditional chatbot works with predefined flows: if the user says X, answer Y. Conversational AI uses a language model that understands natural language and responds in context. The difference lies in flexibility: conversational AI can handle unexpected questions, synonyms and complex sentence structures. The cost is higher, but the result is a significantly better user experience.

How long does it take to build a chatbot? +

A simple FAQ chatbot can be live within a few weeks. An AI chatbot with multiple system integrations and channels usually takes a few months. The lead time depends heavily on the availability of API documentation for the systems to be integrated and how quickly your organisation provides feedback during the testing phase.

Can a chatbot be made GDPR-compliant? +

Yes, provided you take privacy by design into account from the start. That means clearly defining which data the chatbot processes, where it is stored, how long it is retained and how users can access or delete their data. When using commercial LLM APIs, it is important to choose providers that offer European data processing, or to consider a self-hosted model.

Can the chatbot also work in multiple languages? +

Modern LLMs support dozens of languages out of the box. The challenge isn't the language model itself but the knowledge base: if your documentation is only available in Dutch, we either need to add translations or implement cross-lingual retrieval. This adds cost, but it is technically very feasible.

Cost estimate for your chatbot project?

We're happy to help you think through the right approach and the budget that goes with it. In a no-obligation conversation, we map out your requirements and give you a realistic estimate, with no strings attached.

A chatbot is just one channel among several. On applatenmaken.com you'll find the broader overview of customer contact and service software.

Edit content