Pricing
What a Telegram bot costs, and why
Every bot type in the catalogue has one exact price and one exact delivery time, listed on this page. The sixteen breakdowns below show where the days behind those prices go, so you can argue with them: you can tell us three days for a CRM system seems high, and we can show you the field mapping behind it.
Every catalogue price
| What you buy | Price | Delivery |
|---|---|---|
| Feedback and review bots | $2,900 | 14 calendar days from kickoff |
| Lead qualification bots | $3,400 | 16 calendar days from kickoff |
| Notification and dispatch bots | $3,400 | 16 calendar days from kickoff |
| Appointment booking bots | $3,800 | 18 calendar days from kickoff |
| Loyalty and referral bots | $3,800 | 18 calendar days from kickoff |
| Delivery tracking bots | $4,200 | 21 calendar days from kickoff |
| Document collection bots | $4,200 | 18 calendar days from kickoff |
| Restaurant ordering bots | $4,600 | 21 calendar days from kickoff |
| CRM-connected bots | $4,600 | 24 calendar days from kickoff |
| Multilingual support bots | $4,600 | 21 calendar days from kickoff |
| Real estate listing bots | $4,600 | 21 calendar days from kickoff |
| Car rental booking bots | $4,600 | 21 calendar days from kickoff |
| Price alert bots | $5,000 | 21 calendar days from kickoff |
| Community moderation bots | $5,400 | 21 calendar days from kickoff |
| Telegram Stars payment bots | $6,700 | 28 calendar days from kickoff |
| Trading signal bots | $6,700 | 28 calendar days from kickoff |
| Anti-scam bots | $6,700 | 28 calendar days from kickoff |
| Airdrop and quest bots | $7,100 | 28 calendar days from kickoff |
| KYC-gated access bots | $7,500 | 32 calendar days from kickoff |
| DAO governance bots | $8,000 | 32 calendar days from kickoff |
| Token launch bots | $8,400 | 32 calendar days from kickoff |
| TON Mini App storefronts | $9,200 | 35 calendar days from kickoff |
| AI assistants inside Telegram | $9,600 | 35 calendar days from kickoff |
| Crypto wallet bots | $11,800 | 45 calendar days from kickoff |
Every figure here is a published catalogue price or an add-on at the same day rate the calculator uses. The fixed quote confirms it against your scope.
Telegram bot cost breakdowns: what this section covers
- Cost pages
- 16, each with a line-item effort breakdown and year-one running costs
- Source of every price
- One published price table: a catalogue price per bot type, and one signed day rate for add-ons
- Regional comparison
- What the money buys in each market and what it risks — not a quoted competitor rate
As of 2026-09-19, Telegram Bot API 10.3
What these numbers rest on
Almost every agency pricing page in this market is a three-tier table with the middle column highlighted, and it tells a buyer nothing. The tiers are not comparable to anyone else's tiers, the inclusions are written to be flexible, and the only genuinely informative number — what drives the difference between the columns — is deliberately absent. It is a sales instrument rather than a pricing page.
These pages are built the other way round. Each one takes a cost question people actually search for, breaks the work into named line items with a day count against each, and states the factors that move those counts up or down with real numbers attached. There is no tier to be nudged toward and no configuration you have to ask about. If a breakdown says the calendar integration is two days, you can ask why, and there is an answer.
Every figure on these pages comes from one published table. A catalogue price is the price of that bot on its service page and in the calculator; anything added on top is costed at one signed day rate, identically everywhere. That is what stops these pages contradicting each other — a failure that is invisible in review and obvious to a buyer who reads two of them.
One thing these pages deliberately do not do is quote what other suppliers charge. Regional and competitor rate figures cannot be verified, they go stale inside a year, and publishing them invites a conversation about somebody else's number rather than about your project. Instead, each page ends with what the money buys in each alternative — an aggregator, an off-the-shelf product, your own team — and what you carry if you choose it.
What a build costs
Start here if the question is simply what a bot costs. If you meant what Telegram charges for the Bot API itself, that has its own page first: the API is free to call. After it, these four cover the full production build, the smallest defensible first version, the Mini App surface, and the enterprise variant where compliance rather than functionality drives the number.
If the question is what Telegram itself charges rather than what a build costs, the answer (the Bot API is free; paid broadcasts, Gateway codes and Stars are not) is in
For the head question, with every line item and the six factors that move it, read
To configure a build and watch the day count move rather than read a typical one, use
If the point is to learn whether anyone wants this at all, start with
Where a web view inside Telegram is part of the plan, the second interface is costed in
If a security review and a data residency requirement are involved, the honest calendar is in
What a capability adds
What a specific capability adds to a build you have already scoped. Payments, retrieval, chain verification, CRM depth and a second language each have their own economics, and each is the answer to "why is this quote higher than the last one".
For reconciliation, refunds and the underwriting question that decides the shortlist, see
Before buying an assistant, read what the corpus and the evaluation set really cost in
Where a mistake is irreversible rather than embarrassing, the shape of the estimate changes, as set out in
For field mapping, duplicate policy and the automations already running in your account, read
If Arabic or Russian is required alongside English, the real work is described in
What it costs in your industry
The same underlying build seen through three industries where the local detail decides the cost — clinics and salons, restaurants, and property brokerages. Each carries the specific constraint that makes it different from a generic estimate.
Clinics, salons and studios weighing a diary integration should read
For restaurants doing the aggregator commission arithmetic, the build is costed in
Property brokerages with inventory across two portals should start with
What it costs to keep running
The numbers that matter in year two rather than year one. Maintenance, infrastructure, and what it costs to take over a bot whose developer has gone — which is where a great many businesses first learn what maintenance was for.
For why a bot stops working eighteen months after launch, and what prevents it, read
The infrastructure is cheaper than anyone quotes, and the reason is explained in
If the developer has already gone and something has broken, see
Questions about how we price
Why one exact price per bot rather than a range?
Because a range is a number designed to start a conversation rather than to answer a question. Each bot type carries one fixed price and one delivery time for the scope its page describes; the breakdowns explain how those numbers are arrived at, which is the part that lets you check them.
How is an add-on priced on top of a catalogue bot?
In days, at one blended day rate applied identically across every page and the calculator. A card gateway is six days, an Arabic interface two, a second system the bot writes to three. That single rate is why the arithmetic on any two of these pages agrees.
Are the estimates on these pages binding?
The catalogue prices are what we charge for the scope each service page describes. Your quote is fixed against your written scope after one round of questions, and once fixed it does not move because the work turned out harder than we thought. Only scope you add afterwards is quoted separately.
Why do you not show what other agencies charge?
Because we cannot verify it and it would be stale within a year. Every page ends instead with what the money buys through each alternative route and what you carry if you take it, which is checkable and more useful than a number we invented.
Which page should I read if I have no idea what I need?
The full build breakdown, because it names every line item that appears in the others and explains what each one is for. Everything else on this page is that breakdown seen through a specific capability, industry or timeframe.
Do you do hourly work?
For maintenance inside a retainer and for work on an existing system, effectively yes. For new builds, no — a fixed price against a written scope puts the estimation risk on us rather than on you, and that is the arrangement we would want as a buyer.
Related reading
To turn one of these prices into a fixed quote for your own scope, send the five-question brief.
For an exact fixed price and delivery date against each bot type, see the priced catalogue.
Integration depth moves these numbers more than anything else, and each system is documented in the integration pages.
If the real question is whether to build at all, start with the comparison pages.
Several of these estimates turn on a hard Telegram limit, each documented in the Bot API reference.