Telegram bot development in Tashkent: scope, timeline and cost
In Uzbekistan Telegram is no longer just a messenger — for many companies it is the primary sales channel. Here is how bot projects actually run.
What the project consists of
First comes the script: a map of the conversation covering what the bot asks, which buttons it shows, and what happens on unexpected input. It is agreed before any code, because reworking logic afterwards costs more than designing it.
Then the backend and storage. Even a simple bot must keep orders, users and dialogue state somewhere, usually with a small panel where managers review requests.
Finally integrations: CRM, payment providers, inventory, Google Sheets, notifications into a work chat. Integrations typically consume half the budget despite looking trivial from outside.
Timelines by bot type
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 integration: 4 to 8 weeks. What usually stretches deadlines is content approval, not code — product descriptions, button copy, payment provider paperwork.
Budget guidance
Business-card bot: roughly 2M – 5M UZS. Order bot with catalogue: 7M – 18M UZS. Payments, CRM and admin panel: from 20M UZS.
Budget hosting and support separately at 300,000 – 1,500,000 UZS monthly. An unmaintained bot breaks at the first payment provider API change.
Questions before signing
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?
Bots living on an agency server with no client access are common and create dependency. Agree on migration rights upfront even if you never exercise them.