AI Development Services

AI Chatbot Development Services: Scope, Cost, Timeline

By the UXreviewer.io team4 min read

AI chatbot development services cover scoping, conversation design, knowledge integration, building the chat interface, connecting business systems, testing and ongoing tuning. Cost and timeline depend less on the chat window itself and more on how many knowledge sources and systems the bot must use, how many languages and channels it serves, and how much quality assurance and compliance work your context requires.

Modern LLM-based chatbots can be impressive within days, which is exactly why scope creeps. This guide helps you define a realistic first version, understand the cost drivers and plan a timeline you can defend internally.

Three tiers of chatbot scope

Most chatbot projects fall into one of three tiers. Being explicit about which tier you are buying is the single best way to align budget and expectations.

  • Tier 1, knowledge assistant: answers questions from your website, help center or documentation. No access to customer accounts. Lowest risk and fastest to launch.
  • Tier 2, connected assistant: looks up orders, bookings or account details after authentication and answers personal questions. Requires secure integrations and stronger privacy controls.
  • Tier 3, transactional agent: changes things on behalf of the user, such as rebooking, cancelling or issuing refunds. Needs permissions design, confirmations, audit logs and human escalation; see our guide on custom AI agent development.

What drives chatbot development cost?

We do not publish fixed prices for chatbot builds because the spread between tiers is large. Instead, here are the factors that move the budget most, so you can compare offers on substance.

Running costs matter as much as build costs. Model usage is billed per token by most providers, so long conversations, large retrieved contexts and expensive models add up. A good partner estimates running costs at your expected volume and designs to keep them predictable. Our AI development cost guide explains this in more detail.

  • Number and quality of knowledge sources, and how often they change.
  • Number of system integrations (CRM, shop, ticketing, booking) and their API quality.
  • Channels: website widget, mobile app, messaging apps, voice.
  • Languages and tone requirements.
  • Authentication and data protection requirements.
  • Depth of testing: evaluation sets, red-teaming, accessibility checks.
  • Analytics, reporting and admin tooling for your team.

A typical chatbot project timeline

As a rule of thumb, a Tier 1 knowledge assistant can go live in a few weeks, while Tier 2 and Tier 3 bots take longer because integrations, security reviews and stakeholder sign-offs add time. The phases themselves are similar across tiers.

  1. Scoping: top user intents, out-of-scope topics, escalation rules, success metrics.
  2. Knowledge preparation: cleaning and structuring content, often the most underestimated step.
  3. Conversation and UX design: greeting, suggested prompts, fallback answers, handoff to humans.
  4. Build: retrieval pipeline, integrations, chat interface, logging.
  5. Evaluation: test against real questions from support tickets, fix gaps, test edge cases and abuse.
  6. Soft launch to a share of traffic, review transcripts, tune, then full rollout.

Want an expert opinion on your product?

Talk to a UX expert or AI Code Engineer — 30 minutes, free, no obligation.

Book a call for free

Chatbot UX details that decide adoption

Many chatbots fail not because the model is weak, but because users do not understand what the bot can do or cannot get to a human when they need one. These details cost little to get right during development and a lot to fix later.

For a deeper review approach, see our article on conversational UX and chatbot reviews.

  • Say clearly that users are talking to an AI, and what it can and cannot help with.
  • Offer suggested starting questions instead of an empty input field.
  • Show sources or links for factual answers so users can verify.
  • Make the path to a human visible, not hidden behind repeated failed attempts.
  • Handle the bot not knowing with an honest answer and a next step.
  • Keep answers short and scannable, especially on mobile.
  • Make the widget keyboard accessible and readable by screen readers.

Compliance checklist for EU-facing chatbots

Under the EU AI Act, transparency obligations from Article 50 apply from 2 August 2026: users must be informed that they are interacting with an AI system unless it is obvious. Late-2025 EU digital omnibus proposals may adjust parts of the timeline, so check the current status. Our article on EU AI Act transparency obligations for chatbots goes deeper.

GDPR applies to chat transcripts that contain personal data, which is almost all of them. Define retention periods, inform users in your privacy notice and check where your model provider processes data. If you serve consumers in the EU, the European Accessibility Act, applicable since 28 June 2025, may also cover your chat interface. This is general information, not legal advice.

Build, buy or review?

Off-the-shelf chatbot platforms are a sensible choice for standard Tier 1 use cases. Custom development pays off when you need deep integrations, specific UX, data residency control or a bot that is part of your own product.

UXreviewer.io's team offers both directions: AI development services for custom chatbots and agents, and UX audits of existing chatbots with commented screenshots and concrete improvement ideas, delivered within 10 business days. Book a call for free to discuss which tier fits your goals.

Frequently asked questions

How long does it take to build an AI chatbot?

A focused knowledge assistant can often launch within a few weeks. Bots that access customer accounts or perform actions take longer due to integrations, security reviews and testing.

Why do chatbot quotes vary so much?

Vendors often quote different tiers without saying so. Compare offers by asking which integrations, channels, languages, evaluation work and post-launch tuning are included.

Can a chatbot replace our support team?

It can take over repetitive questions and speed up the rest, but complex or emotional cases still need people. The best results come from bots that hand over smoothly with context, so agents do not start from zero.

How do we keep the chatbot's answers up to date?

Connect it to the sources your team already maintains and re-index on a schedule or on change. Review transcripts regularly to find questions the bot cannot answer yet.

Book a call for free

From UX audits and Agentic UX reviews to AI development, agentic coding workshops and publishing your AI-built app on the App Store and Google Play — we help you ship. 24/7 call support in English and German.

Related insights