OOmnistu

Blog / AI Development

AI Development

AI chatbot for your website: build, buy, or embed?

Who owns the answers, data and risk when you add an LLM assistant to a business site. Cost shapes, vendor questions and the risks that stay with you.

OOmnistu
Reviewed 2026-11-19 · 3 min read

"Add a chatbot to the website" now means something specific: an LLM-backed assistant that answers in natural language, not a scripted widget with three buttons. The build-or-buy decision for that assistant is less about technology fashion and more about who owns the answers, the data and the risk. This guide lays out the decision for a business site, checked against current vendor documentation and the OWASP GenAI Security Project on 19 November 2026.

What you are actually choosing

Buying means embedding a hosted chatbot product: a script tag or plugin, a monthly subscription, and the vendor's model, hosting and dashboard. Building means your own assistant: a model API (billed by usage), your own retrieval over your own content, your own UI, and your own guardrails. A middle path - a platform's embeddable assistant pointed at your documentation - behaves like buying for cost and like building for configuration effort.

The cost structures are different shapes

A bought assistant is a predictable subscription line item. A built assistant is usage-based: model API billing scales with traffic and answer length, and the engineering cost is front-loaded - retrieval, evaluation, safety handling and the UI all exist before the first visitor asks anything. API pricing is public and changes; check the model provider's current pricing page when you model costs rather than trusting any article, including this one. Unbounded usage is a real failure mode either way: our guide to unbounded consumption and cost abuse covers the caps to put in place.

The risks do not transfer with the invoice

Whether you build or buy, three risks stay with the site owner:

Buying moves the infrastructure work to the vendor; it does not move these answers-and-data questions. Ask any vendor how their product handles each one, in writing.

When buying is the honest choice

When building earns its cost

Questions that separate real vendors from demos

If you decide a custom assistant is the right shape, our generative AI development page describes how such engagements are scoped, and the project scoping guide helps write the requirement down first.

Sources

Drafted with AI assistance from these sources and Omnistu's own referenced guides. Pricing and product capabilities change; verify against current vendor documentation before committing.