Skip to content
8 min read

Telegram bot development in Tashkent: scope, timeline and cost

Telegram bot development in Tashkent is more than writing code: first you need to be clear on what the bot is for, and only then pick the technology. In Uzbekistan Telegram has long been a working channel for sales and support, so mistakes at the start are expensive. Below: where to start, what the project consists of, how long it takes and what to check before signing.

Where to start when creating a Telegram bot

Start with the task, not with BotFather. Write in one sentence what the bot must do: take requests, sell items from a catalogue, book appointments, answer typical questions or send notifications. If the sentence holds more than two tasks, pick the main one and leave the rest for version two.

Next, define the audience and the language. Customers in Uzbekistan usually need Russian and Uzbek interfaces: decide in advance which language the bot offers by default and where users can switch. Also decide who on your side receives requests — a manager, the sales team or a shared work chat.

Technically, creating a bot is simple: in the official @BotFather you register a name and receive a token, the access key to the Bot API. Never send the token through messengers or store it in plain sight, because it gives full control of the bot. Register the bot under a company account rather than an employee's personal number, or you will lose access when that person leaves.

Choosing an approach. A no-code builder suits a simple business card or FAQ: it is quick and cheap, but logic and integrations are limited and your data sits on someone else's platform. Custom development is needed when you have a catalogue, payments, a CRM or logic of your own. If unsure, launch a minimal version and watch how people use it.

Telegram bot development in Tashkent: what the project consists of

The script. This is a map of the conversation: what the bot asks, which buttons it shows, and what it does on unexpected input or a /start command in the middle of an order. A good script fits on 3–5 pages and is agreed before any code, because reworking logic after development costs more than designing it upfront.

Backend and storage. Even a simple bot must keep users, orders and dialogue state somewhere. Usually this is a small database and a panel where a manager reviews requests and changes statuses.

Integrations. CRM, payment providers (for example Payme or Click), inventory, Google Sheets, notifications into a work chat. Integrations most often consume half the budget despite looking trivial from outside: each system has its own rules, test environments and approval times.

Testing and launch. Check the bot on different devices and with different behaviour: users press buttons out of order, type text instead of choosing, block the bot and come back. Before launch, agree who monitors errors and how quickly they are fixed.

Timelines by bot type

Indicative timelines: a business-card bot with a menu, contacts and a request form — 3–7 working days; an order bot with catalogue, cart and manager notifications — 2–4 weeks; a bot with payments, user accounts and CRM — 4–8 weeks. These are guidelines; the exact figure depends on the scope of the script.

What usually stretches deadlines is content approval, not code: product descriptions, button copy, payment provider details, CRM access. Gather materials in parallel with development instead of waiting until it ends.

What the price is made of

Number of script branches. A bot with five buttons and a bot with a tree of forty states differ in effort several times over, though both look like just a bot. Admin panel: if the client, not the developer, must edit content, the panel is a separate mini-project. Bilingual support is more than translating strings: notifications, buttons and errors need separate texts, plus language selection and storing the choice.

Market guidance (not an offer): a business-card bot roughly 2,000,000 – 5,000,000 UZS, an order bot with catalogue 7,000,000 – 18,000,000 UZS, a bot with payments, CRM and admin panel from 20,000,000 UZS. Budget hosting and support separately: about 300,000 – 1,500,000 UZS per month depending on load.

An unmaintained bot breaks at the first change in a payment provider or CRM API, so discuss support before launch, not after.

Common mistakes and questions before signing

Common mistakes: starting with a huge bot that does everything; not thinking through what happens when a user leaves mid-order; not keeping request history; leaving the token exposed; not setting a default language; launching without a test group of real users.

Questions for a contractor: who owns the source code and where is it stored? Who holds the payment provider account? Whose server runs the bot and do you have database access? How do backups work? What does support include and how fast are bugs fixed?

A bot living on an agency server with no client access is common and turns into dependency. Agree on migration to your own hosting upfront, even if you never use it.

FAQ

Can I build a bot myself? Yes, a builder is enough for a simple menu or FAQ. Once you need a catalogue, payments or a CRM, custom development usually pays off.

How long does a simple bot take? Roughly 3 to 7 working days if the content is ready.

Do I need a separate server? The bot needs hosting that runs around the clock. It is better registered in your company's name.

Can features be added later? Yes, if the bot was built modularly. So start with a minimal version and expand based on usage.

Do I need Uzbek? If your audience speaks both languages, build both at once: adding a language later is usually harder.

If you need help launching

4 Digital builds Telegram bots for businesses in Uzbekistan; the profile service starts from 999,000 UZS. Tell us the task and we will advise which version to start with and which integrations are really needed.

Need a website or ads? Let’s discuss your project.

Telegram Bot Development · от 999000 сум

We reply within 15 minutes during business hours. No spam.