Start with one task, not an AI transformation
We do not sell a transformation programme. We take one workflow that costs you hours every week, automate it, measure the difference — and only then talk about the next one.
Contact us → First project → Scale
Three steps, each with a fixed list of deliverables and a number we agree to measure before we start.
Step 1
Contact us
A free conversation in Uzbek, Russian or English. Five questions: where the hours go, which systems hold the data (your accounting program, spreadsheets, Telegram), who touches each step, what a mistake costs, and what "done" looks like. No slides.Deliverables
- A one-page map of 3–5 workflows, ranked by hours lost per week
- The top workflow shown live: how it would run on its own, on your example
- One recommended first project — scope, a plan and a price set against what the manual version costs you
What we measure
- Hours per week in the chosen workflow, as you count them today
- Current reply or turnaround time
- Error rate, if anyone counts it
Step 2
First project on 1–2 workflows
We build the smallest system that removes the manual step: a Telegram bot that answers and qualifies, a daily report from your accounting program to Telegram, documents generated from one source of truth. Your team starts using it as soon as it runs; we fix what they find.Deliverables
- A working system on your data, in your language, in Telegram — where your people already are
- AI usage policy and data rules — one page, signed off with you
- One operator trained to run it; admin access; source code in your repository
What we measure
- Before → after on the number we agreed at the start
- Reply time, hours saved, error rate — logged weekly, shown in one dashboard
- Anything not measured is published as "target", not as a result
Step 3
Scale
When the first project's number holds, we add the next workflow. We keep watching what we built: monitoring, fixes, small improvements and a report you can forward to your director.Deliverables
- Next workflow picked from the process map, the same way as the first
- Uptime monitoring on every bot; alerts to our ops group
- A numbers report and a regular review of what to automate next
What we measure
- Bot uptime and reply time in working hours
- Cumulative hours saved across workflows
- What each workflow costs against the hours it saves
Five rules we do not bend
We sell outcomes, not tools.
ProofEvery proposal names one number — hours, reply time, error rate — and the plan to move it. If the number does not move, we say so in the report.
Telegram-native, because that is where the customer is.
ProofThe intercity bus product replaced a 4,000-member chat with a bot, not with an app. The AcademyOS parent portal is a Telegram Mini App. We build where people already answer within minutes.
Trilingual by default.
ProofUzbek in Latin script, Russian, English — in the interface, in the bot's answers and in support. This site is the test: three languages, zero untranslated strings.
Measured, or marked as a target.
ProofEvery number on this site carries a tag: measured or target. We publish a result only after it is counted on real data. Until then it is a target, and it says so.
One operator can maintain it.
ProofEvery system ships with an admin, a full change history, one page of rules and one trained person on your side. No workflow depends on us being awake.
Rules we write down before we write code
Data governance is one of the four barriers Uzbek businesses name when adopting AI (UNDP, 2026). So the AI usage policy and the data rules are a deliverable of every project, not an appendix.
- AI usage policy as a deliverable Default in every project
- One page: which tasks the model may do, which it may not, what a human checks before anything is sent to a customer or a regulator. Written with you at the start of the project.
- Where your data lives Disclosed in the proposal
- Our systems run on cloud servers outside Uzbekistan. We tell you this on day one, with the region, so you can decide what goes there.
- Personal-data localisation Lawyer to confirm
- Uzbekistan's personal-data law requires citizens' personal data to be stored on servers inside the country. Whether a lead form or a customer bot on foreign-hosted infrastructure needs mitigation must be confirmed by a lawyer for your case. Until then we design for the strict reading: minimal personal data abroad, or a local database or your accounting program as the system of record.
- Minimise personal data Default in every project
- We store what the workflow needs and nothing else: a name and one contact for a lead — no passport scans, no card numbers, no free text about health. Fields that are not needed are not in the schema.
- A change history on every admin write Default in every project
- Every change made by an operator — status, price, document — is logged with who, when and what changed. A lesson from FIFA compliance work: if it is not logged, it did not happen.
- Bot uptime is monitored Default on every bot we run
- A bot that is down is negative proof. Every bot we run reports its status; an outage alerts our ops group within minutes, and our report shows uptime as a number.
- Secrets and backups Default in every project
- API keys live only in the hosting environment — never in the repository or a chat. Databases are backed up nightly; restore is tested before handover.
Three prices, one logic
Every engagement is quoted after we talk it through, from its scope, and set against what the problem costs you now. One number, not a range — and if the fix costs more than the problem, we say so.
First project
By agreementper project
One or two workflows, built and measured.
Included
- Process map and a written scope with acceptance criteria
- The working system, in your language, on your data
- AI usage policy + data rules (one page)
- One trained operator, admin access, source in your repository
- Fixes after handover
Next workflows
By agreementper workflow
Once the first result holds, each next workflow is quoted the same way. How we look after what we built is agreed with you in the proposal.
Included
- Next workflow picked from the process map
- Uptime monitoring and alerts on every bot
- Fixes and small improvements
- A numbers report you can forward to your director
- Priority reply in working hours
Export
By agreementinternational rates
Clients outside Uzbekistan — Central Asia, the Gulf and beyond — are quoted at international rates.
Included
- Delivery and documentation in English
- Same steps, same rules
- Time-zone overlap agreed in the proposal
- Invoicing in USD; terms in the proposal
Not included, on purpose
Ads, SEO packages, logo design and "anything for a custom quote". If it is not on the services list, we will tell you who does it well.
Contact us.
Tell us about your process and we'll show you how it would run on its own — straight away, not in a proposal a week later. In Uzbek, Russian or English.