How Much Does an AI Chatbot Cost? Every Build Route, Priced Honestly

How much does an AI chatbot cost? Any single number is a lie, because “AI chatbot” covers four different products: a DIY bot wired together from free tools, a no-code platform bot, a developer-built custom bot, and an enterprise suite. Each sits in a different cost band, driven by different things. This post prices each route, names what moves the price inside it, and matches each band to the business it fits.

Route 1: DIY — free in money, expensive in hours

The DIY route uses free tiers of general AI tools and open-source frameworks, wired together by the owner. Cash cost: near zero. Real cost: the owner's evenings — setup, prompt writing, testing, fixing the breakages when an API changes. It fits a hobbyist or a technical owner with more time than budget, and it breaks the moment the business needs reliability: no support line, no uptime promise, and every fix is another evening. DIY is the cheapest route only if your time is free, and it stops being cheap the week it is not.

Route 2: no-code platforms — the small-business band

No-code platforms charge a flat monthly plan for a bot you build by uploading documents and writing instructions — no developer, live in an afternoon. This is the band most small businesses should compare in, and the price driver inside it is volume: how many AI replies, conversations, or contacts the plan includes, and what happens past the quota. On Neksio the band is explicit: Free at 100 AI replies a month on WhatsApp, Starter $8.99 for 5,000 replies, Growth $11.99 for 15,000 including Facebook and Instagram, Scale $29.99. WhatsApp bots carry one extra line other channels do not — Meta's per-message fees, billed separately, covered in the

WhatsApp total-cost breakdown. Compare no-code plans on included volume and overage behaviour, not headline price — the

hidden-costs guide lists the traps.

Route 3: developer-built — a project, not a subscription

A custom build is priced as a project: design, development, integration with your systems, testing, and then ongoing maintenance — because a custom bot is software you now own, and software rots without upkeep. The price driver is scope: one channel with a document base is a small project; multi-channel, multi-system, compliance-reviewed is a large one. It fits businesses with requirements no platform covers — unusual integrations, strict data rules, or a workflow that is genuinely unique. For everyone else it is the most expensive way to get the same answers a no-code platform gives from uploaded documents.

Route 4: enterprise suites — priced for procurement, not owners

Enterprise suites price by seats, contacts, or custom contracts, with onboarding, security reviews, and account management bundled in. They fit companies with procurement processes, compliance teams, and thousands of monthly conversations. For a small business they are the wrong band entirely: the floor price alone exceeds a year of no-code plans, and the features — SSO, multi-workspace governance, dedicated managers — solve problems a five-person team does not have.

What actually moves the price inside any band

Four drivers, in order: volume (replies, conversations, or contacts per month — the unit differs by vendor, so compare units, not prices); channels (each added channel is a new surface to configure and often a new fee); integrations (CRM, calendar, store — native versus custom-built); and AI usage depth (simple FAQ answers versus long agentic workflows that consume far more model usage per conversation). A bot answering price questions from a price list is cheap in every band; a bot booking, rescheduling, and updating your CRM is dearer in every band, for the same reason: it does more work per conversation.

Owner: “We got quotes from free to five figures — for the same bot.” They were not the same bot: one was a no-code plan, one was a custom project, one was an enterprise suite. The route was the price.

Which band fits you

Solo owner, under a few hundred chats a month, answers from your own documents: no-code, starting free. Growing team, multiple channels, integrations: no-code's upper plans, or the developer route only if an integration truly does not exist. Regulated enterprise with procurement: the suite band. And a final scope note for the WhatsApp slice: Neksio is not a bulk or broadcast tool, so if your chatbot plan is built around sending to lists, you are shopping in a different category with different pricing — this post's bands assume bots that answer customers, not blast them.