IT procurement in Uzbekistan: November

A young woman with pink hair holds a key in front of a closed compartment on a test bench with modules and connected cables

Majento's observations on 3 and 4 November 2026 produced a slice of IT procurement in Uzbekistan covering twelve procedures with published initial prices in Uzbekistani som. Their combined total is approximately 68.7 billion UZS. The group includes platform and data warehouse implementations, production accounting, video control systems, and support for existing systems. This is the first slice of Q4 based on available announcements; a complete quarterly total will require data covering the full period. The current observation is limited to the beginning of November.

For the head of an IT company, this sample is useful as a breakdown of specific demand. It shows what work is being bundled into a single procurement and what to check before preparing a proposal. The material is not yet sufficient for estimating market size. Initial prices also say nothing about the amounts of contracts actually signed.

What is included in the slice

For this slice we used research reports from 3 and 4 November and a snapshot of the procurement sources registry. The snapshot contains 108 rows of procurement sources and a further 39 rows of vacancy sources. The registry covers Uzbekistan and international platforms and includes both primary portals and aggregators. The row count therefore cannot be used as the number of Uzbekistani tender platforms or as the number of verified procurements.

For this article a procedure was included only when it simultaneously met all of the following conditions: a unique execution procedure in Uzbekistan, an explicit procurement of software, implementation, maintenance, or information system design (including a mixed package with a stated software component), a price in som, and requirements that had been read in the report. Excluded were pure hardware, operator, and financial services; unconfirmed buyer requests; unverified repeats of failed competitions; and archived cards whose current terms had not been re-read. The procedures described in the two reports were reviewed against these conditions; this is not a complete market survey and not a quarterly export.

Twelve procedures were selected under this rule. Multiple mentions of the same procedure in different sources were counted once.

The observation date and the publication date differ. Among the included procedures there are announcements published before November that were reviewed during the November round. We do not present them as new procurements from those specific days. For the same reason this material cannot be read as the number of tenders announced during the quarter.

Vacancies, plans for future procurements, and marketplace cards for which no separate buyer request was confirmed were not counted. Outside the total are procedures denominated in foreign currency, pure hardware procurements, contact centre operator services, debt collection, and financing consultancy. Checking an aggregator helps locate an announcement but does not by itself confirm its status, price, or terms.

Twelve procedures by group and initial price

The table groups the included procedures by primary subject. Group totals are approximate and rounded independently. The overall total is calculated from the source values before the groups are rounded, so its independent rounding to 68.7 billion may not match the arithmetic sum of the rounded group figures. Two values were already rounded by the source at publication. Customer names and individual procurement numbers are omitted.

Group Number of procedures Total initial prices, billion UZS (approx.)
Data and IS design 3 about 21.6
Applied software, maintenance, and access 7 about 13.5
Video systems with software and integration 2 about 33.7
Total in selected group 12 about 68.7

These prices do not share the same tax basis. For two of the twelve procedures the report explicitly states a price inclusive of VAT; for the remaining ten the tax status was not established in the materials read. We summed the published figures without attempting to convert them to a common basis. That total describes the included cards and requires this caveat whenever it is cited.

The table also combines different compositions of obligation. One announcement has the supplier designing and implementing a system; another provides a right of use and maintenance of a platform; a third supplies a video system with software integration. Mixed packages containing both hardware and software obligations cannot be compared as prices of the same product. The final cost of the work depends on the documentation and the contract, and the price of any signed contract is not established in this slice.

Behind the technology name lies implementation work

Among the included group there are tasks that must connect with already-running systems. The procurement of an operational data store relates to an existing data warehouse. Production ERP modules must link laboratory accounting, transport, logistics, and equipment maintenance with the enterprise's current system. A separate accounting software development task explicitly provides for integrations and subsequent support.

For a supplier this changes the content of the proposal. Demonstrating a standalone module answers only part of the questions. Before scoping the work it is necessary to find out what data the customer already holds, who controls access to it, and which systems will need to exchange information. These dependencies are often invisible in a short procurement title. In the included procedures they are disclosed in the scope of work and the requirements.

The video group contains two different procurements. One combines production control with web and mobile interfaces and exchange with government data. The other is a mixed package that includes cameras, software, integration, and servicing and supplier-rights requirements; almost half the total sum of the slice belongs to this mixed package. Because the second procurement bundles equipment and software together, its full price cannot be treated as software revenue, and the equipment share within that price is not separately established in the available materials. When analysing either procurement a supplier should define its scope of responsibility for each component before preparing a proposal.

Maintenance also has its own procurement subject. The sample contains a standalone billing support procedure, while in the accounting task support is bundled with the development work. Grouping both items under the common label "new development" loses the distinction between creating functionality and servicing working software.

These observations apply to the included announcements. They do not prove that integrations are growing faster than other areas or that demand for any particular technology has increased. A conclusion of that kind requires comparable observations across several periods and consistent selection rules.

A procurement budget does not yet mean an accessible contract

Some procedures that are interesting by subject carry requirements relating to organisational experience, headcount, or software rights. Requirements differ across the included documents: one procedure sets a minimum legal-entity age of three years; another requires only six months at the date of announcement. One announcement requires more than fifty programmers and at least three completed ERP projects. Another explicitly prohibits subcontracting and requires the participant to have at least three years of experience. For a small team a matching technical profile does not yet confirm eligibility to participate.

It is important to distinguish between the experience of the company and the experience of its staff. A requirement relating to the age of the legal entity is verified against the organisation's registration date, not the biographies of its specialists. If the documentation requires the participant's own experience, it is worth checking whether the prior-employment experience of its staff is permitted. If a supplier is counting on a partner, the relevant provision on joint participation and the rules for combining qualifications need to be found. Mentioning a consortium without those conditions leaves the question open.

For a procurement of access to a ready-made service a different question arises: does the participant have the right to supply it? A team may be capable of developing a similar solution, but that does not substitute for the right to provide access to the product named in the documents. A contract of that kind should be evaluated with the service delivery terms in mind.

Timelines and security also affect the decision. In the procedures read, advances ranged from 0 to 50 percent; in certain procedures a separate bid deposit in cash was between 1 and 3 percent of the initial price; in a number of procedures a guarantee letter was not accepted in place of a cash deposit. These are examples from the included announcements, not universal conditions applying to all procurements. Before treating an announced price as potential revenue, a supplier needs to read the payment schedule, the security requirements, and the definition of an accepted deliverable.

A young woman with pink hair adjusts schedule cards on a complete board on a workshop wall

Why the sources registry does not equal market coverage

An announcement can appear in several places. An aggregator shows a title and a sum, the primary platform holds the card, and the documentation discloses the terms. Counting each discovery as a separate procurement inflates both the procedure count and the apparent demand. For this sample the unit of account is the individual procedure, not the page found.

The reverse problem arises when a source has been read only partially. The 4 November report explicitly states that opening a page does not mean a full keyword search and review of all pages was completed. Some documents require a login; for certain sources only the accessible public section was read. The absence of a finding in such a source cannot be recorded as an absence of demand.

The vacancy sources section serves a separate purpose: it helps identify what competencies companies are seeking to hire. But a vacancy for an AI specialist does not prove that the company is procuring development from an external supplier. In this article signals from vacancy sources do not increase the procedure count and are not assigned a notional budget.

Marketplace cards deserve separate attention. The November report includes software offers for which the researcher did not confirm an independent buyer request. Excluding them makes the sample narrower, but it prevents seller listings from being mixed with procurements: without a confirmed buyer request this is a storefront, not a procurement.

The daily procurement monitor also contains vacancy sources and incomplete procedure exports. A proven count of unique IT tenders for a full quarter cannot be derived from it. The monitor data from 10 November is not mixed with the observations from 3 and 4 November. The overall quarterly count remains unknown.

A hand taking an envelope from an open archive drawer

How to use this slice when choosing a direction

Start by matching your own work to the subject of a specific procurement. A data team can work through the requirements for the data warehouse. A maintenance team can check the terms of the existing IS support contract. In both cases the next step is documentation that confirms the qualification specifically for the chosen procedure.

It is useful to keep a separate record for each announcement: the primary identifier, the date of review, the subject, the price with currency and tax status, the terms read, and open questions. When the same announcement is found again, that record is updated. If a price is absent, the field remains unknown. If the technical specification has not been read, the procedure remains incompletely analysed.

This kind of record provides a basis for the next quarterly comparison. For the comparison to be meaningful the same boundaries must be preserved: what counts as an IT procurement, how it is attributed to a period, and how amendments or repeat procedures are handled. In the current materials there is no continuous series for the quarter. The first issue therefore fixes the observations and the rules for reading the data, while the assessment of trends remains open.

Frequently asked questions

What period do the data cover?

The material uses research reports from 3 and 4 November 2026 and a registry snapshot from 4 November. This is an observation from the beginning of Q4, not statistics for the full quarter. The publication dates of the included announcements may be earlier.

Can 68.7 billion UZS be called the market volume?

This is the approximate sum of initial prices for the twelve included procedures. It does not cover all IT procurements in Uzbekistan, it contains different tax bases, it includes mixed packages with hardware, and it does not confirm expenditure under signed contracts. When citing the figure these boundaries must be preserved.

How many IT tenders have been announced in Uzbekistan in total?

These reports do not provide a proven complete count for the quarter. The article counts only the included group of twelve procedures. The sources registry helps organise the search, but a full total requires a complete procedure export with verification of duplicates, subjects, and dates.

Can the table be used to select a procurement to bid on?

The table helps identify a group for further analysis. A decision on any individual procurement requires the current primary card, the full documentation, and a check of the participant's own qualifications. The slice preserves the state of observations from the beginning of November; the current status of proposal acceptance was not verified for this article.

Discuss business process development and automation with Majento: Telegram, hello@majento.ai.

View as Markdown