Most "how much does a bot cost" conversations go wrong in the first minute. The client asks for a number, the contractor gives a range, and both leave slightly annoyed: the range is either suspiciously cheap or obviously out of budget.
The gap between a $150 bot and a $1,500 bot is almost never in the code. It is in five things.
1. The number of integrations
Every link to an existing system — CRM, ERP, spreadsheets, payments, inventory — is separate work: access, tests, error handling, edge cases. One integration is a few days. Three or four integrations can eat half the budget before the first screen exists.
2. The state of your records
A configured CRM with clear fields integrates in days. "Everything is in spreadsheets and everyone has their own format" means agreeing on the data structure first — and that is separate work that nobody wants to pay for, but it decides whether the bot works in production.
3. Who writes the scenario and the copy
A prepared scenario from the client saves money. A well-designed scenario earns it back: the sequence of questions and messages affects conversion more than the visual design does. A bot with beautiful buttons and a vague flow converts worse than a plain one that asks the right questions.
4. Rights and personal data
If the bot collects phone numbers and addresses, you need a processing policy and a sane storage plan. Medicine and finance have higher requirements — that is a separate budget line, not a formality.
5. Deadlines
"By Monday" usually means a 20–30% surcharge or a trimmed scenario. Moving the date by a week is almost always cheaper than cutting the steps the user actually needs.
What it costs after launch
A bot is not a one-off purchase. It lives: server, updates, fixes.
- Server or hosting — $3–12/month: a VPS, a home Raspberry Pi, or shared hosting;
- Domain, if needed — only for webhooks and a web admin panel;
- Support — from $40/month for fixes and supervision; hourly if changes are rare;
- Updates — once or twice a year: Telegram and VK change their APIs and the bot must survive it.
Total: roughly $60–180 a year without support, $600–1,000 with it, plus your time for scenario changes.
If the bot brings 10–20 requests a month, support usually pays for itself. One lost request costs more than a month of maintenance.
So how much does a bot cost?
The honest answer is "show me the scenario". Two tasks that look identical can differ threefold — one needs a database and a payment provider, the other needs three messages and a notification.
A useful habit: ask for a breakdown by stage, not a single number. It shows what is actually included, and it makes the estimate comparable with other bids.
This is a cross-post. The full version, with price ranges by bot type and a sample budget, lives on my site: How much does a business bot cost in 2026. I also wrote about estimating a project and about local AI without the cloud.
Top comments (0)