A chatbot as a service bill has two possible parts: the hosted software and the work of setting up and running it. If your team manages the bot, you pay the platform and account for your own time. If an agency manages it, ask for its setup fee, monthly labor, and underlying platform charges separately. There is no useful single "CaaS price" until you know who owns the work and what the vendor counts as usage.
Use the editable chatbot budget worksheet to put both options on the same first-year basis. Leave unquoted charges as unknown. This article is Agentkit-authored desk research, and we sell one of the products mentioned. We checked vendor pricing pages on October 21, 2026; we did not run a comparative product test or survey business spending.
What a hosted plan pays for
The subscription usually pays for access to the vendor's software and a defined allowance. Read the plan's unit before comparing prices. A visitor message, an AI conversation, a model credit, a human seat, and a billed outcome answer different questions.
| Published offer | Charging unit to budget | A limit or extra charge to check |
|---|---|---|
| Agentkit Hobby | $29.99 per month on monthly billing, with 2,000 visitor messages | One chatbot and one team seat. Agent replies do not count as separate visitor messages. |
| Chatbase Hobby | $40 per month on monthly billing, with 700 message credits | Credits are not Agentkit messages. Measure your workload's credit use and check recharge settings. |
| Intercom with Fin | Helpdesk seats plus Fin outcomes, or a separate Fin arrangement with an existing helpdesk | Fin lists $0.99 for a resolution, procedure handoff, disqualification or self-serve routing, and $9.99 for a full sales qualification. At most one outcome is billed per conversation. |
| Crisp Free | $0 for a website chat widget and two seats | No AI credits are included. A free live-chat widget is not a recurring free AI-agent allowance. |
Those are named offers, not a market average or a ranking. Check each checkout or order form before buying; prices and limits can change. For a broader plan-by-plan comparison, use the chatbot pricing guide.
An agency fee buys a different service: someone to prepare sources, configure the bot, connect it to your site, review answers, and fix failures. It may sit on top of one of those subscriptions. A quote that says "AI chatbot, $1,500 per month" leaves the most important questions unanswered: whose platform account is it, what usage is included, and what work happens every month?
Turn traffic into a billable workload
Start with observed conversations if you have them. For each vendor, translate the same sample into that vendor's billed unit. Do not divide one vendor's credits by another vendor's messages.
Suppose your planning case is 300 conversations in a month, with an assumed average of six visitor messages in each. That illustrative workload is 1,800 visitor messages. It fits Agentkit Hobby's listed 2,000-message allowance if one chatbot and one seat also meet your needs. There is little headroom: seven messages per conversation would use 2,100. At 400 conversations with the original six-message average, the workload is 2,400 messages and exceeds that allowance. Agentkit's usage guide explains what counts and how to monitor the billing cycle.
The same 300 conversations do not tell you the Chatbase credit bill. Run representative prompts with the models you intend to use, read the credit usage, and price a normal and busy month. For Intercom, estimate the number and type of Fin outcomes, then add the seats and other contracted charges. For a managed service, add the provider's labor and any platform pass-through in both months. The example establishes only the arithmetic and questions to ask; it is not measured customer traffic or a vendor benchmark.
Ask a managed provider for an itemized quote
Send the same short scope to each provider. A quote you can audit should answer every line below:
We need one website chatbot trained on [number and type of sources] for [languages]. Expected monthly volume is [normal conversations] and [busy conversations], with [sampled visitor messages per conversation, if known]. Please itemize one-time setup, the platform subscription and account owner, the billable unit and included allowance, overage or hard-stop behavior, human seats, integrations, and recurring review hours. State who updates sources, who checks failed answers, response times for incidents, contract length, renewal terms, and how we export data and take over the account if we leave.
Replace the brackets with your own figures. If you do not know a usage figure, say so and ask for a pilot with a spending or usage limit. The worksheet keeps setup, subscriptions and labor in separate rows. It does not estimate a vendor's credit use or prove that a quoted service will resolve questions.
Watch for these common omissions:
- Platform pass-through. Ask whether the agency's fee includes the software bill and whose card is charged for add-ons.
- Source upkeep. Ask how changed hours, prices, policies and documents reach the bot. Check whether the provider refreshes uploaded files as well as web pages.
- Answer review. Ask for a named owner, a review cadence and an example of the report or change log you receive.
- Handoff and exit. Ask whether you own the platform workspace, training sources, lead data and conversation exports. Require a practical transfer step, not just a contractual promise.
- Limits. Ask what visitors see after the allowance runs out and whether the provider buys more usage automatically. Confirm any alert or cap in the actual account.
These questions matter more than a low headline price. A provider can sell competent setup at a fair fee. You should still know what work you are buying and how to operate the bot if that relationship ends.
Compare first-year cost without guessing market averages
Add the one-time setup to twelve months of subscription, expected usage charges and recurring labor. If the contract is annual, use its actual annual charge and renewal terms. Repeat for a busy month and show any extra capacity purchase or required tier change. Keep taxes, custom integrations and unquoted support as separate unknowns until the vendor answers them.
For example, consider an illustrative quote of $2,000 setup, $120 monthly software and $300 monthly review labor. At unchanged usage, first-year spending is $2,000 + 12 × ($120 + $300) = $7,040. If the $120 plan cannot handle the busy month, this is an incomplete budget. Request the busy-month price and the rule that triggers it. The figures are chosen to demonstrate the calculation, not to describe a typical agency or platform.
Your own team's time belongs in the self-managed column too. Preparing content, testing answers and maintaining integrations do not disappear because the software is self-serve. The implementation-cost guide helps scope that work. If the alternative is a custom build, include engineering, hosting, model use, security and maintenance in its quote instead of comparing only the launch project with a subscription.
Which buying route fits?
Choose a self-managed hosted plan when your team can own content and answer review, and the required website workflow is already supported. A managed provider makes sense when you need someone accountable for configuration and ongoing operation, especially across several sources or teams. A full support suite can be the better purchase when your existing inbox, ticketing and human routing matter as much as the bot. A custom build deserves consideration when a verified requirement cannot fit a hosted product and you can fund long-term maintenance.
Before committing, test your own questions on the intended plan and confirm how one unit appears in the usage screen. Then get the account ownership and monthly service duties in writing. If a self-managed website chatbot fits, compare Agentkit's current plans. Its free plan includes 50 visitor messages per month for a small trial; measure that usage before forecasting a paid month.
