Pricing
What things cost, and why
Fifteen cost breakdowns, each denominated in delivery days rather than in a headline figure. Days are arguable and a headline number is not: you can tell us that four days for a CRM integration seems high, and we can show you the field mapping behind it. That is the whole point of publishing it this way.
Telegram bot cost breakdowns: what this section covers
- Cost pages
- 15, each with a line-item effort breakdown and year-one running costs
- Unit of estimation
- Delivery days. Money is computed from one signed day rate, so no two pages can contradict each other
- Regional comparison
- What the money buys in each market and what it risks — not a quoted competitor rate
As of 2025-10-01, Telegram Bot API 13.4
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.
The reason days rather than dirhams is partly honesty and partly arithmetic. A day rate multiplied by an effort estimate produces the same figure on every page, which means these fifteen breakdowns cannot drift into contradicting each other — a failure that is invisible in review and obvious to a buyer who reads two of them. It also means a client can check our estimate against a quote from anyone else on the substance, which is the comparison worth having.
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. 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.
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 is there no price list on this page?
Because a price without a scope is a number designed to start a conversation rather than to answer a question. Each bot type in the catalogue carries an exact fixed price and an exact delivery time; these pages explain how those numbers are arrived at, which is the part that lets you check them.
How do days convert into a figure?
One blended delivery day rate, applied identically across every page here. That single rate is what stops fifteen breakdowns from quoting different money for the same work, and it is why the arithmetic on any two of these pages agrees.
Are the estimates on these pages binding?
They are honest ranges for typical projects, not a quote for yours. A quote is fixed against a written scope after a conversation, and once fixed it does not move because the work turned out harder than we thought. What is quoted separately is scope added afterwards.
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
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.