Skip to content
Uzbyte
S-01 / AI automation

AI automation

You open Telegram and the hotel has already reported itself: who checked in, who checked out, which rooms are free tonight. Nobody assembled it by hand.

S-01.1Problem

What it looks like today

Every morning our accountant spends two to three hours pulling yesterday's sales out of 1C, pasting them into Excel and sending a screenshot to the owners' Telegram group. By the time it arrives it is 11:00, and one line is usually wrong.

Leads come in from Instagram, Uzum and the website, land in three different Telegram chats, and nobody replies until someone remembers. Invoices, contracts and delivery notes are typed by hand from the same numbers — we have five people doing work a system should do.

S-01.2Outcomes

What changes in your business

  1. Daily 1C / Excel / Sheets report in your Telegram group at 08:00 — instead of a 2–3-hour manual job (target for the pilot workflow)

  2. Every new lead answered and logged within 15 minutes in working hours, in the customer's language

  3. Invoices, contracts and delivery notes generated from one source of data, with the numbers checked before anyone signs

  4. Invoice-to-order matching that flags mismatches the same day, not at month-end

  5. A one-page AI usage policy and data rules, so staff know what may and may not go into a model

  6. Before-and-after numbers for every automated workflow — a one-page report you can forward to your director

S-01.3How it works

Three steps, in this order.

  1. 01Step 1

    Audit

    A 30-minute call plus one visit to your office. We map where the hours actually go — 1C exports, Excel, Telegram chats, paper — and pick the 1–2 workflows with the biggest return. You get a written scope, a price and an honest go/no-go.

  2. 02Step 2

    Pilot in 30 days

    We build the 1–2 workflows on your real data, with your accountant and manager in the loop every week. Week four is measurement: minutes saved, reply time, error rate — numbers you can show the owners.

  3. 03Step 3

    Scale on a retainer

    Once the pilot pays for itself, we add the next workflow each month, keep the bots monitored and train your team. The retainer is agreed with you; you can stop any month.

S-01.4Deliverables

What you sign off on

  • Automation audit report: process map, hours lost per week, priority list (PDF, UZ/RU)
  • 1–2 working automations connected to your 1C, Excel/Sheets and Telegram
  • AI usage policy + data rules (1 page, signed off by you)
  • Monitoring dashboard: runs, failures, cost per run
  • Runbook: what to do when something stops, in plain language
  • Measurement sheet: before / after numbers from week four
  • Handover session for your accountant and manager (2 hours, recorded)
  • A handover pack: scope, cost breakdown and acceptance criteria in one file
S-01.5Price

What it costs.

By agreement

Exact quote after the free 30-minute audit.

S-01.6Proof

We run what we build.

  • Fact 01

    Our own operations job at a professional football club — document generation, registrations, foreign-player paperwork — automated on top of the existing platform. Time saved is published only once measured.

  • Fact 02

    A Telegram-bot pipeline that generates and publishes channel content without a person in the loop — ours, running every day.

  • Fact 03

    Presidential data, August 2026: 25% of firms using AI-based management cut production costs, 54% saw a sharp rise in demand, and 40% raised wages by more than 10%.

S-01.7Questions

Questions we get on the first call.

Who owns the code, the data and the accounts?
All of it is yours. The code lives in your repository, the cloud and bot accounts are registered to your company, and the database is yours — we only hold operator access. When the work ends, or you decide to stop, there is nothing to ask us for: the system is already in your hands. The results should hold you, not the credentials.
Where does our data go? Our 1C has salaries and prices in it.
Your data stays in your 1C. The automation reads only the fields agreed in the data rules — the day's sales total, for example, not salaries. The model provider receives only anonymised fragments needed for the task. Personal data of citizens is minimised and, where the law requires it, kept on servers inside Uzbekistan. The one-page policy states exactly what leaves your network.
We run 1C 8.3 with custom modifications. Can you integrate with it?
Yes. Through OData / HTTP services or scheduled exports — we do not rewrite your 1C configuration, and your 1C programmer keeps their role. If there is no API access, we start from the exports you already make: an Excel file lands in a folder every day, and the report goes to Telegram at 08:00.
What happens after the 30 days?
Three options. One: you run the automations yourself — that is what the runbook and handover session are for. Two: a monthly retainer at an agreed rate — monitoring, fixes, a new workflow every month. Three: you stop. The code and access are yours either way.
Who owns the code and the bots?
You do. Everything is deployed in accounts registered to your company: the Telegram bot, the cloud, the database. At handover you get the repository and every credential. It keeps working without us — by design.
S-01.8Next step

Start with the free 30-minute audit.

Five questions, one call. You leave with the workflow to automate first and a cost estimate.

+ a written plan you keep · We answer within 15 minutes in working hours.