# AI and machine learning, deployed

> LLM assistants, RAG over your own documents, computer vision and forecasting — deployed on your data and measured, not demoed.

Source: https://i7team.uz/en/services/ai-development
Provider: i7 Team, Tashkent, Uzbekistan

You have probably sat through the demo: the model answered five rehearsed questions beautifully and invented the sixth. Our work is what comes after: reading your real documents, measuring accuracy on questions your staff wrote, wiring it into 1C and your CRM, and being on call after. i7 Team has worked in Tashkent since 2019, and AI here sits on systems we build ourselves.

## Four jobs AI genuinely does

We do not sell «artificial intelligence» as a product. We take a process where someone re-reads or cross-checks the same thing daily and move the repetitive part to a model, leaving the judgement and the veto with the person.

Where a SQL query or a well-configured CRM pipeline would do it, we say so: a neural network there buys cost and one more point of failure.

- LLM assistants: answers from your own procedures, each citing its source
- Computer vision: number plates, people counting, PPE compliance, defect detection
- Forecasting: demand, stock, churn and shift load from your trading history
- Data extraction: invoices, delivery notes and contracts, from scans into fields

## RAG: answers from your documents, not from the internet

A model knows nothing about your internal rules. RAG is a search over your own corpus whose results go into the prompt: documents are chunked, embedded as vectors, stored in pgvector or Qdrant, retrieved by hybrid search — vectors plus classic BM25, because part numbers and surnames are what vector search handles worst.

A cross-encoder then reranks, and five to fifteen chunks reach the model rather than the whole archive. A 128k context window is no invitation to dump everything in: as context grows, so do the bill and the odds the key paragraph is lost in the middle. Locally, scans that mix Uzbek Latin, Cyrillic and Russian need proper OCR first.

## How we prove it works

Before a line of code, we build a set of 100–300 real questions with reference answers from your support history. Your staff write it, because only they know what counts as correct. That set is the acceptance test: not «it looks clever», but an agreed, measurable share of right answers.

Then we track three numbers: how many answers carry a citation, how often the system said «I don't know» and handed over, and how often it was wrong. Every model or prompt change is replayed against that set, or an «improvement» quietly breaks yesterday's work. For the first weeks it runs in shadow mode, answering to a log while a human answers the customer.

## Computer vision starts with the camera, not the model

Our advantage here is engineering, not marketing: we install the CCTV and access control ourselves, so camera and model are designed together. Reliable number-plate reading needs roughly 100–150 pixels across the plate width — that one figure fixes your focal length, standoff distance and mounting angle. No network recovers detail the sensor never captured.

We take the stream over RTSP/ONVIF and decide where inference runs: a light detector on an edge device beside the camera keeps latency low and video off the network; heavier work goes to a GPU server. The output lands where it is needed: a barrier command, an operator alarm, a stock record.

## Where your data physically stays

Uzbek personal data law requires personal data of Uzbek citizens to be processed in databases physically located in the country. So we separate the zones at the outset: what may go to an external API, and what never leaves the perimeter.

The trade-off is honest: cloud models are strongest at Russian and Uzbek, but your data travels. Open weights — Qwen, Llama, Gemma — run on your hardware: a 7–8B model quantised fits in 8–16 GB of VRAM, a 70B one needs upwards of 40 GB. Weaker in Uzbek, heavier on capital cost, but nothing leaves the building.

## What actually drives cost and schedule

Schedule is governed by the state of your data far more than by the choice of model. If procedures live in one unstructured PDF and sales history sits in three exports that will not reconcile, the bulk of the work is not machine learning but making that usable. We say so during scoping, not after signature.

Second, what the system may do: answer only, or also raise a CRM deal, reserve stock, issue an invoice. Every action is an integration and its own cost of being wrong. Third, rarely mentioned: AI has a standing cost — token bills or GPU depreciation, monthly. We show it before launch.

## Common questions

### How long does a deployment take?

A pilot on one process, with measured accuracy, usually runs to a few weeks: data review and the control set, then assembly and measurement. Production rollout with 1C, CRM and telephony integrations takes longer, and depends less on the model than on how fast we get credentials.

### What do you need from us?

Three things: access to the data — documents, exports, support history; one person with authority to decide what counts as a correct answer; and test credentials for any system the AI will write into. Without the second, projects stall: everything built, nobody to sign it off.

### What if the model gets it wrong in front of a customer?

We design so the cost of being wrong is bounded: the assistant cites its source, refuses questions outside its knowledge base, and escalates on defined rules. Anything touching money — invoices, discounts, write-offs — needs human confirmation by default.

### Who owns the code and the trained models?

You do. Source code, prompts, retrieval configuration and any fine-tuned weights are handed over with documentation; we do not lock work inside a platform you cannot leave. Licences for third-party models and cloud APIs remain their rights holders'.

### What happens after launch?

An AI system degrades more quietly than ordinary software: it does not crash, it answers worse as your range, procedures and customers' phrasing change. So after launch: a regular replay of the control set, a review of refusals and errors, knowledge-base upkeep.

### Our business runs in Uzbek — will this work?

It will, with an honest caveat: model quality in Uzbek is noticeably behind Russian, and retrieval is complicated by Latin and Cyrillic in the same text. We handle it with normalisation and embeddings chosen for your corpus, but budget more measurement time and promise no identical accuracy untested.

## Related services

- [Telegram bot and Mini App development](https://i7team.uz/en/services/telegram-bots)
- [CCTV design and installation in Tashkent](https://i7team.uz/en/services/video-surveillance)
- [Website and web platform development](https://i7team.uz/en/services/web-development)

## Start with one process

Show us where staff re-read the same material daily. In one meeting we will say whether a model solves it and what must be measured to prove it. Tashkent — info@i7team.uz, +998 77 372 21 12.

Get in touch: info@i7team.uz · +998 77 372 21 12 · https://i7team.uz/en/contact