AI integrator · Tashkent
AI at the core of your business
We connect AI to the 1C, ERP, CRM and messengers you already run. No system replacement, no data migration.
- Deployment
- cloud, your servers, air-gapped
- Languages
- RU, UZ, EN
- First result
- pilot in 3-6 weeks
- 1C
- Bitrix24
- amoCRM
- Telegram
- PostgreSQL
- Excel
- Google Sheets
- IP telephony
- OpenAI
- Anthropic
- Llama
- Qwen
The problem
The data exists. The full picture does not.
Companies accumulate data for years, yet a simple question from the CEO is still hard to answer.
- 01
Every department has its own system
Accounting in 1C, sales in the CRM, plans in Excel, agreements in Telegram. People hold the links together.
- 02
A consolidated report takes a week
By the time the figures are reconciled by hand, they are out of date. Decisions rely on memory and gut feeling.
- 03
Skilled staff copy data by hand
Analysts and managers spend hours moving numbers between spreadsheets instead of doing their actual work.
- 04
A chatbot without data changes nothing
A bot that cannot see 1C, the CRM or contracts answers in generalities. It brings the business no value.
How it works
From scattered systems to an answer in a minute
Reconciliation
Tekstil Yug LLC-412,600,000
Due date14.10
Pipeline
Negotiation38
Invoiced21
Paid12
Q4 plan
Samarkand92%
Fergana78%
Client chat
Where is the September reconciliation?
Checking with accounting
Contract No. 47-P
Payment terms30 days
Penalty0.1% per day
Inbound 04:12
Topiclate payment
How much receivables are overdue, and with whom?
Overdue by more than 30 days
UZS 14.8 bn
| Branch | Amount | Owner |
|---|---|---|
| Tashkent | 6.2 bn | D. Karimov |
| Samarkand | 3.9 bn | N. Yusupova |
| Fergana | 2.7 bn | A. Rakhimov |
| Bukhara | 2.0 bn | Sh. Tursunova |
01Sources
We connect to what already works
1C, CRM, Excel, Telegram, scanned contracts, call recordings. Nothing is moved or replaced: we read data where it lives.
02Model
We build a model of the company
Clients, contracts, invoices, payments and owners become linked objects. One entity, however many systems describe it.
03Agents
We assign agents to processes
Each agent has a role and permissions. It sees only what it is allowed to and prepares actions rather than taking them itself.
04Answer
The executive gets an answer with sources
Figures, breakdown, owners and a link to every document. Prepared actions wait for human approval.
Signal feed
Nothing in the company goes unnoticed
Agents watch processes around the clock and alert the owner when something goes wrong. No more Friday reports.
- 12:02HR recordslowThree resignations in logistics within a month→ HR
- 11:20Telegram · CRMhigh12 requests unanswered for more than 48 hours→ Sales
- 10:32WarehousemediumM400 cement stock differs from the books by 18 t→ Warehouse
- 10:051C · ExcelmediumFergana branch margin falling for the third week in a row→ Branch director
- 09:41Contract registryhighContract No. 112 signed without legal review→ Legal
- 09:141ChighPayment to supplier Angren Cement is 3 days overdue→ Finance
Example, illustrative data
Ask in plain language
A question in words. An answer with sources.
No need to open five systems and wait for an export. Just ask the way you would ask your CFO.
Executive question
Which clients are more than 30 days late on payment, and what have we done so far?
Core answer
Five clients are over 30 days overdue, UZS 9.6 bn in total. Three of them have received no reminder.
Tekstil Yug LLC3,120,000,000
47 days · call 02.10
Samarkand Agro JSC2,480,000,000
38 days · none
Fargona Tech LLC1,760,000,000
35 days · email 09.10
Bukhoro Savdo PE1,290,000,000
33 days · none
Navoi Plast LLC950,000,000
31 days · none
Agent proposal
Send reminders to the three clients with no contact, attaching the reconciliation statement and the contract penalty clause. Copy the account managers.
Example, illustrative data
Who it is for
Everyone sees their part
I want to open my phone in the morning and see in a minute where the company is losing money.
What they get
- →A daily brief: plan vs actual, deviations, who is responsible
- →Answers about the business without exports or meetings
- →Risk signals before they reach a report
- Timeline
- First brief within 3-4 weeks of the pilot
- Risks and how we handle them
- Incomplete source data. During the assessment we check record quality and say plainly which numbers can be trusted.
- Where it works
- Telegram, web dashboard, morning email
I need numbers I can trust, not one more Excel export.
What they get
- →Control of receivables and the payment calendar across all entities
- →Primary documents reconciled with 1C without manual entry
- →Deviations explained with links to entries and contracts
- Timeline
- Receivables or documents pilot: 3-6 weeks
- Risks and how we handle them
- Recognition errors. Every record is reconciled with 1C, and disputed ones go to a person for review.
- Where it works
- 1C, Excel, Telegram, email
Connect if you must, but 1C keeps running as it does, and no data leaves the perimeter without my say.
What they get
- →Integration with no system replacement and no data migration
- →Deployment in the cloud, on your servers or air-gapped
- →A log of every agent request and action, role-based access
- Timeline
- First sources connected: 1-2 weeks
- Risks and how we handle them
- Load on core systems. We read from replicas and scheduled exports, and write only through agreed methods.
- Where it works
- 1C, PostgreSQL, Bitrix24, amoCRM, AD, your perimeter
My managers should be selling, not retyping requests from messengers into the CRM.
What they get
- →An AI sales assistant that replies to clients within a minute
- →Call reviews against your script in Russian and Uzbek
- →A daily task list built from the CRM and chats
- Timeline
- First module live in 3-6 weeks
- Risks and how we handle them
- A wrong answer to a client. The agent works from the company knowledge base and hands complex cases to a person.
- Where it works
- Telegram, WhatsApp, Instagram, CRM, IP telephony
Core modules
Five modules to start with
Each module solves one measurable task on a shared data model. Start with one, add the rest without rework.
- 01
Core Sales
An AI sales assistant in Telegram, WhatsApp and Instagram. Replies within a minute, qualifies the request and passes context to the CRM.
↳ Telegram, WhatsApp, Instagram, amoCRM, Bitrix24
- 02
Core Knowledge
A corporate assistant for policies, contracts and technical documentation. Every answer links to its document.
↳ File storage, EDMS, Google Drive, PDFs and scans
- 03
Core Executive
A daily brief for the executive: plan vs actual, deviations, overdue items and owners.
↳ 1C, ERP, CRM, Excel, Google Sheets
- 04
Core Calls
Transcription and review of sales calls in Russian and Uzbek. Scoring against your company script.
↳ IP telephony, Asterisk, cloud PBX, CRM
- 05
Core Docs
Recognises invoices, acts and waybills, reconciles them with 1C and records the data with no manual entry.
↳ 1C, email, Telegram, scanners
Industry solutions
Solutions for industry workflows
Built from core modules for a specific process. Tuned to your company’s terminology and documents.
- 01
Core Tender
Tender documentation review, requirements check, draft bid.
- 02
Core Engineering
Search across GOST, ShNK, drawings and technical documentation for engineering, oil and gas and construction.
- 03
Core Collect
Receivables control: overdue items, reminder letters, sent after approval.
- 04
Core Trade
Foreign trade: invoices, specifications, HS codes, supplier document checks.
- 05
Core HR
CV screening and an interview bot in Russian and Uzbek.
- 06
Core Translate
Documentation translation across RU, UZ, EN, CN using company terminology.
Four stages
You can stop after any of them
Each stage ends with a result that stays with you, even if you go no further.
01 · 1-2 weeks
Assessment
We study processes, systems and data quality, and calculate where AI pays off and where it does not.
What you keep
A map of processes and data, a list of tasks with estimated impact, a pilot plan
02 · 3-6 weeks
Pilot
We launch one module on one process with real data and real users.
What you keep
A working module, before and after measurements, a scale decision based on numbers
03 · 1-3 months
Integration
We connect the remaining systems, set up permissions and train the team. The pilot becomes an everyday tool.
What you keep
The core inside your perimeter, documentation, a trained team
04 · monthly
Support
We monitor answer quality, update models and extend scenarios as the business grows.
What you keep
Stable operation under SLA, a monthly quality and usage report
Security
Your data stays under control
NDA before any work
We sign a non-disclosure agreement before the assessment starts and before any data access.
No training of third-party models
Your data is never used to train third-party models. This is written into the contract.
Deployment of your choice
In the cloud, on your servers or in an air-gapped perimeter on local models with no internet access.
Role-based access
An agent sees only what the user it acts for is allowed to see.
Action log
Every agent request and action is logged with its author and time.
Human approval
Significant actions, such as client emails or changes to the books, run only after approval.
Let’s start with an assessment
In two weeks you will know where AI pays off.