Off-the-Shelf Chatbot or Custom Build: Three-Year Cost
By CodexierPublished 5 min read
Comparing a chatbot subscription with a custom build on the first invoice is misleading: one is a low monthly fee, the other a larger one-off. The honest comparison runs over three years and includes the parts nobody quotes, such as per-conversation charges, the hours spent keeping answers current and the cost of leaving. This guide lays out both options side by side and gives you a rule for choosing.
What each option includes
A subscription chatbot is a hosted product: you paste a script onto your site, upload documents or point it at your pages, and pay monthly. The vendor handles the model, hosting and updates. A custom build is software made for you, usually on top of a commercial AI model, with its own knowledge base, rules for handover to a human and integrations with your systems. You pay for the build and then for hosting, model usage and maintenance.
Three-year cost side by side
| Cost item | Subscription chatbot | Custom build |
|---|---|---|
| Start | Low or none; setup is often self-service | One-off build fee |
| Monthly base | Plan fee, often per seat or per bot | Hosting and monitoring, usually small |
| Volume | Per-conversation or per-resolution charges above the plan limit | AI model tokens, paid directly and visible |
| Integrations | Limited to the vendor's connectors, sometimes on a higher plan | Built to your systems as part of the project |
| Content upkeep | Your hours in the vendor's editor | Your hours, or a maintenance agreement |
| Leaving | Rebuild content and flows elsewhere | You keep the code and data; move hosting if needed |
Add up each column for 36 months at your expected conversation volume, including one year of growth. The lines that decide the outcome are usually volume and integrations.
The pattern is consistent. At low volume with no integrations, the subscription wins clearly over three years because the build fee is never earned back. As volume grows, per-conversation pricing on the subscription side climbs in steps, while the custom build's model cost grows smoothly and is usually lower per conversation, since you pay the model provider directly without a margin on top. For typical cost ranges on our side, see what an AI chatbot costs.
Data ownership and lock-in
Every chatbot collects conversations, and conversations contain personal data: names, email addresses, order numbers and sometimes health or financial details that customers type in unprompted. Under GDPR you are the controller, and the vendor is your processor, so you need a data processing agreement, to know where the data is stored and to be able to delete it. Check whether the vendor hosts in the EU, whether conversation data is used to train its models, and whether you can export the logs.
- Can you export all conversations and the knowledge base in a usable format?
- Can you change the AI model, or are you tied to the vendor's choice and its price changes?
- Are the flows and rules readable outside the vendor's editor?
- What happens to your data the day you cancel, and how quickly is it deleted?
Customisation limits
Subscriptions are built for the common case: answer questions from your content, collect contact details, hand over to a human. They struggle when the bot must act in your systems, such as checking a specific order in your webshop, booking a slot in your own calendar logic, or following rules that differ per customer segment. Custom builds also give you control over the fallback: what the bot says when it does not know, which is the difference between a useful assistant and one that makes things up.
Subscription is enough when
Questions are general, answers live on your website, and a human takes over anything specific.
Custom pays off when
The bot must read or write in your booking, order or CRM data, or follow business rules the vendor cannot express.
Hybrid option
Start on a subscription to learn what customers ask, then build custom for the flows that matter once you have real conversation data.
Which one fits your volume
- Count current support contacts per month by channel: email, phone, chat, social messages.
- Estimate the share of those a bot could fully answer, and be conservative.
- List the systems an answer depends on. If none, lean subscription.
- Price both options over 36 months with growth, including your own hours for upkeep.
- Check the exit: what it would cost to leave each option in year two.
When not to buy a custom build from us: if your volume is low and your questions are general, a subscription or even a better FAQ page will serve you well and we will say so. Our chatbot setup is for businesses where the bot must connect to real systems. See the pricing page, or book a call with your monthly contact volume and we will run the three-year numbers with you.
Frequently asked questions
Is a custom chatbot always more expensive?
In year one, usually yes, because of the build fee. Over three years it can be cheaper at higher volumes, since you pay the AI provider directly per use and avoid per-conversation charges from a vendor.
Can we move from a subscription to a custom build later?
Yes, and it is often the smart route. Export your conversation logs and knowledge base before switching; the logs show what customers really ask and make the custom build better and cheaper to scope.
Who owns the chatbot if you build it?
With us, you own the code and the content, as agreed in the contract. You can host it yourself or with another supplier. The AI model itself is licensed from its provider under their terms, as with any AI product.
Do we need a data processing agreement for a chatbot?
Yes. The chatbot handles personal data on your behalf, so the vendor or developer who hosts it is your processor and GDPR requires a written agreement covering storage, security and deletion.
Run the three-year comparison with us
Bring your monthly contact volume and the systems a bot would need to reach. We will tell you which option is cheaper for you, including when that is a subscription.
Book a free 15-minute call