Telegram bot development Telegram bot

A bot that takes orders, books appointments and collects payment where your customers already spend their day: in Telegram. From $1,500 and from 2 weeks, with a conversation flow, an admin panel and leads sent to your CRM. Price and deadline are fixed in the contract before work starts.

Price
from $1,500
Timeline
from 2 weeks

Price and deadline are fixed in the contract before work starts

Curtain. Steel

What is included

  • 01Conversation design: where the bot answers and where it calls a manager
  • 02Menu, FAQ base and leads posted to your team chat
  • 03Catalogue and cart with in-chat payment and receipts
  • 04Booking into free slots from your calendar
  • 05Admin panel: orders, products, customers, segmented broadcasts
  • 06Lead handoff to amoCRM, Bitrix24 or your own CRM
  • 07Multilingual interface with language choice on first launch

Who it is for

  • Cafés, delivery services and retailers taking orders in direct messages
  • Clinics, salons and schools that take bookings by phone
  • Service businesses where repeat questions eat up managers’ time
  • Multi-branch chains that need one bot and shared analytics

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

Start

Menu, answers to questions, lead capture, manager alerts

$1,500–3,000

≈ UZS 18M · from 2 weeks

Business

Catalogue, cart, payments, admin panel, broadcasts

$4,000–8,000

≈ UZS 48M · from 4 weeks

Platform

Branches, AI, integrations, analytics

$12,000–25,000

≈ UZS 144M · from 8 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

What drives the price

A bot’s price depends on what happens behind the buttons, not on how many there are. The Start level covers a menu, answers to common questions, lead capture and an instant alert to a manager: enough to stop losing enquiries at night and on weekends. Business adds a catalogue with a cart, payments, an admin panel and broadcasts, so the bot starts selling on its own. Platform is for chains: bots per branch, CRM handoff, funnel analytics and AI that answers from your knowledge base. Bookings, referrals, loyalty points, channel autoposting and voice-to-text can be added to any level. The configurator adds it up and the total goes into the contract.

How the work runs, week by week

Week one is the script. We map every step of the dialogue, including the awkward ones: a voice note, a change of mind at checkout, a typed question instead of a button press. You approve the flow and the copy in every language. Then we build on a test bot that your team uses from their phones as customers would. You get a working version every two weeks, so feedback lands on a live bot, not a document. Before launch we switch on live payments, run a real card through checkout and train managers on the panel. The timeline from 2 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract in total.

Payments, languages and local rails

In markets where Telegram is the everyday messenger, people expect a bot to behave like a good sales assistant: answer in their language and accept the payment method they already use. We build multilingual bots with a language picker on first launch. In Uzbekistan that means Uzbek and Russian, with payments through Payme, Click and Uzum: the customer pays without leaving the chat, gets a receipt, and the order is marked paid automatically. Digital goods sold inside Telegram use Telegram Stars, as Telegram requires. Voice messages can be transcribed to text, which matters wherever customers prefer talking to typing. Orders can flow into Excel, Google Sheets or your CRM.

Where cheap bots break

A bot can be assembled in an evening with a no-code builder or an AI assistant, and at first it may even work. Trouble arrives with real customers. The token sits in public code and a stranger reads your conversations. A payment confirmation is lost because the server answered late, or it is counted twice. The bot runs on someone’s laptop and silently stops replying. The admin panel has no proper login. We keep the token on the server only and process payment retries so a second charge never appears. Bugs are fixed free with no time limit, and your own engineer may audit the code against the contract: any unfulfilled item means a 10% refund.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does a Telegram bot cost?

From $1,500, with a timeline from 2 weeks: menu, FAQ, lead capture and manager alerts. Catalogue, payments and broadcasts are the Business level; branches, AI and CRM are Platform. The configurator gives the exact amount, which is fixed in the contract before work starts.

How long does it take to build a bot?

From 2 weeks for a bot with a menu and lead capture. A shop bot with payments or a multi-branch platform takes longer; the timeline for each level is in the table above. You see a working version every two weeks. Every day of delay cuts the invoice by 2%, up to 10% of the contract.

Can a Telegram bot work as an online store?

Yes. A catalogue with categories and a cart, in-chat payment, order status for the customer and an alert for the manager. If the catalogue is large and needs filters, a Telegram Mini App is more comfortable; the bot and the Mini App work together.

Who owns the bot?

You do. The bot is registered to your Telegram account; the token belongs to you and is kept only on the server. Handover of the source code and server access is written into the contract.

Can the bot speak several languages?

Yes. Multilingual support is part of the project: the customer picks a language on first launch and can switch it in the menu. Voice-to-text for those languages is an optional add-on.

Does a bot need a server, and what does support cost?

It does: a bot has to run around the clock and receive payment confirmations, so it lives on a server, not on an employee’s computer. Bugs are fixed free with no time limit; new features are priced separately in the configurator.

Other solutions

Practice: Bots & Messengers