Outcomes in 30 days, not AI transformation
We do not sell a transformation programme. We take one workflow that costs you hours every week, replace it in 30 days, measure the difference — and only then talk about the next one.
Audit → Pilot → Scale
Three steps, each with a fixed length, a fixed list of deliverables and a number we agree to measure before we start.
- 0130 min
Automation audit
A 30-minute call in Uzbek, Russian or English. Five questions: where the hours go, which systems hold the data (1C, Excel, Sheets, 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
- One recommended pilot with scope, price and a 30-day plan
- A cost estimate for the recommended pilot, with what is in and out of scope
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
- 0230 days
Pilot 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 1C to Telegram, documents generated from one source of truth. Your team uses it from week two; 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 in the audit
- Reply time, hours saved, error rate — logged weekly, shown in one dashboard
- Anything not measured is published as "target", not as a result
- 03monthly
Scale on a retainer
When the pilot number holds for four weeks, we add the next workflow. A monthly retainer covers monitoring, fixes, small improvements and a report you can forward to your director.
Deliverables- Next workflow scoped from the audit map, same 30-day rhythm
- Uptime monitoring on every bot; alerts to our ops group
- A monthly numbers report and a quarterly review of what to automate next
What we measure- Bot uptime and reply time in working hours
- Cumulative hours saved across workflows
- Cost per workflow against the retainer
Six rules we do not bend
- 01
We sell outcomes, not tools.
ProofEvery proposal names one number — hours, reply time, error rate — and the 30-day plan to move it. If the number does not move, we say so in the report.
- 02
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.
- 03
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.
- 04
We run what we build.
ProofAcademyOS, the bus service, SD Autopilot and the AI Content Engine are in daily use and maintained by the same person who sells them to you. We know what breaks at 23:40, because it is our phone that rings.
- 05
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.
- 06
One operator can maintain it.
ProofEvery system ships with an admin, an audit log, 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 pilot, not an appendix.
AI usage policy as a deliverable
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 in the first week of the pilot.
Where your data lives
Our stack runs on Supabase (Postgres) and Vercel, hosted outside Uzbekistan. We tell you this on day one, with the region, so you can decide what goes there.
Personal-data localisation
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 / 1C as the system of record.
Minimise personal data
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.
Audit log on every admin write
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
A bot that is down is negative proof. Every bot we run reports its status; an outage alerts our ops group within minutes, and the retainer report shows uptime as a number.
Secrets and backups
API keys live only in the hosting environment — never in the repository or a chat. Databases are backed up nightly; restore is tested before the pilot closes.
Three prices, one logic
Every engagement is quoted after the audit, from its scope. The proposal has one number, not a range.
Pilot
per project · 30 daysOne or two workflows, built and measured in 30 days.
- Audit 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
- 30 days of fixes after handover
Retainer
per monthKeeps the system running and adds the next workflow at the pilot rhythm.
- Uptime monitoring and alerts on every bot
- Fixes and small improvements within the month
- Monthly numbers report
- Priority reply in working hours
- Next workflow scoped from the audit map
Export
international ratesClients outside Uzbekistan — Central Asia, the Gulf and beyond — are quoted at international rates.
- Delivery and documentation in English
- Same 30-day rhythm, same rules
- Time-zone overlap agreed in the proposal
- Invoicing in USD; terms in the proposal
Not included, on purpose
Ads, SEO retainers, logo design and "anything for a custom quote". If it is not on the services list, we will tell you who does it well.
Start with the 30-minute audit.
Five questions, one recommended pilot, a written plan. In Uzbek, Russian or English — on a call or in Telegram.