How much a Telegram bot costs in 2026 and what the price is made of

The floor

A Bot API bot costs from $125 with us. That buys a bot with a menu, a few flows, a simple admin panel and data storage. For example, a booking bot, a bot with a catalogue of 20-30 items, or a bot that takes requests and forwards them to a manager.

Bot builders and templates cost less. They work when the task fits what they can do: answer common questions, collect a contact, send a newsletter. As soon as you need your own logic, the builder gets in the way. From then on you pay for workarounds, and the bot often ends up rewritten from scratch anyway.

Almost any real bot ends up above the floor. The question is what exactly you pay extra for and whether you need it at the start.

What raises the price

The price grows with the number of things the bot has to know and remember, not with the number of buttons. These parts usually add the most work.

• Payments. Connecting a provider is easy. Thinking through refunds, failed payments and a client who closes the window mid-payment is harder.
• Integrations. A CRM, accounting software, Google Sheets, delivery services. Each has its own API, its own limits and its own ways to break.
• Roles. When a bot has clients, staff, admins and an owner, each needs their own screens and permissions.
• Schedules. Booking free time is harder than it looks: overlaps, cancellations, breaks, time zones.
• Admin panel. Managing the bot from inside the bot works while there are two or three settings. A catalogue of hundreds of products needs a web admin panel.
• Mini App. With many products or a need for a convenient interface, the bot gets a web interface inside Telegram. That is a frontend plus a backend: from $430.

Regular bot or userbot

A regular bot works through the official Bot API. It cannot message a person first, it does not see messages in chats it has not been added to, and it follows Telegram’s broadcast limits. For most business tasks that is enough.

A userbot works on behalf of a regular account through the MTProto protocol. It reads channels, works with chats and does almost anything a person does in the app. It costs from $300: the protocol is more complex, and the account has to be protected from bans. Telegram watches for automation on personal accounts, so a userbot is no tool for spam or mass messaging. We do not take such tasks.

How long it takes

We show a simple bot with a menu and requests as a demo in one or two weeks and launch it in two to four. A bot with payments, schedules and a CRM integration takes longer, usually a month to a month and a half. The timeline depends on you too: how quickly you answer questions and share access. Most often a project waits not for the developer but for payment provider keys or an export from the old system.

How we estimate

When we estimate a bot, we split it into parts and estimate the time for each.

1. 1 Flows. What the user writes, what the bot answers, what happens on an error. This is usually the biggest part.
2. 2 Data. Which tables are needed, what to store and for how long, what can be deleted.
3. 3 Integrations and payments. How many external services, and how clear their documentation is.
4. 4 Admin panel. Who changes texts, prices and schedules, and how.
5. 5 Launch. A server, a webhook address, backups, monitoring.

The hours for all parts add up and get multiplied by the rate. Our development rate is $20 per hour. We fix the price before work starts. If our estimate turns out too low, that is our problem, not yours.

What owning a bot costs

Besides development there are running costs. Count them up front, so that in six months the bot does not turn out more expensive than it seemed.

• Server. A bot with a small load runs on the simplest VPS. We help you pick one and pay for it in your name, so the access is yours from day one.
• Payment provider fees. They are charged on each payment, and the size depends on the provider and the payment method.
• External services. SMS, maps and AI models are paid separately if the bot uses them.
• Maintenance. Telegram changes its API from time to time, and so do other services. Every few months a bot needs small fixes.

For a month after launch we fix small things for free, as long as they add no new features. After that, fixes are billed by the hour.

How to save without losing quality

• Start with one flow. A bot that books clients well is more useful than one that does five things badly.
• Put off the web admin panel. For the first weeks prices and texts can live in a Google Sheet, and the admin panel comes once it is clear what it really needs.
• Describe the task in your own words. You do not need a spec, we will ask the questions. The more examples from your work, the more accurate the estimate.
• Do not pay for what you already have. If your CRM can send reminders, the bot can simply pass bookings to it.

Summary

Prices are a guide. We name the exact amount after a conversation and fix it before we start. You pay after a demo with about 40% of the functionality done.