# Website and web platform development > We build websites and web platforms in Tashkent: Next.js, 1C and Click/Payme integrations, and the network underneath. Your code, your accounts. Source: https://i7team.uz/en/services/web-development Provider: i7 Team, Tashkent, Uzbekistan We build websites the way software gets built — architecture, strict typing, code review and a performance budget — not by assembling pages in a builder. i7 Team has done this in Tashkent since 2019, alongside the team that wires the same building's network, access control and tills. ## Engineering, not page assembly The default stack is Next.js and TypeScript in strict mode, rendered on the server or at build time. A crawler receives finished HTML, not an empty container a script fills two seconds later — the gap between a page being indexed and one heading being indexed sits right there. Everything runs through Git from day one: branches, review, CI, a preview deployment per task. You click through a live address, not a screenshot, and any release rolls back with one command. - Next.js and TypeScript with strict on; types and ESLint gate the build - Git, code review, CI and a preview deployment per branch - Canonical, hreflang, sitemap, robots and JSON-LD in the first release ## Three scripts, two search engines Uzbekistan reads in three writing systems at once: Russian Cyrillic, Uzbek Latin and English — which means reciprocal hreflang across ru, uz and en with x-default and a distinct URL per version. One consequence shows in the address bar: because the country writes in Latin script, Russian words get typed in Latin letters here — "veb razrabotka", "sayt razrabotka". Search engines do not transliterate across alphabets; they match the literal string, and the slug is where it belongs. Uzbek Latin hides a second trap: "oʻ" and "gʻ" use the modifier characters U+02BB and U+02BC, yet people type a plain apostrophe, a typographic quote, or nothing. Three different characters across the database, the URLs and the on-site search, and the catalogue stops being findable. Two search engines matter here, not one: Google takes about three quarters of the country's queries, Yandex the rest. - Reciprocal hreflang across ru / uz / en with x-default - oʻ and gʻ normalised, so products are found however the apostrophe is typed - Search Console and Webmaster, Analytics and Metrica, IndexNow from day one ## Integrations — and the hardware on the shop floor A website rarely lives alone: the catalogue and stock come out of 1C, payment goes to Click, Payme or Uzum, cards are Uzcard and Humo, enquiries land in a CRM and the sales team's Telegram. Integrations are their own layer with a queue and retries — if 1C is unreachable for ten minutes, an order is neither lost nor duplicated. Then comes the part almost nobody in Tashkent offers on one contract: NetPOS tills, access control and CCTV are installed by us, not by a subcontractor's subcontractor. When stock on the site, at the till and in the warehouse has to be one number, having no boundary between network engineers and developers removes the "whose bug is it" conversation. - 1C:Enterprise — catalogue, stock, pricing, documents - Click, Payme, Uzum; Uzcard and Humo cards - amoCRM and Bitrix24, Telegram notifications, SMS gateways - NetPOS tills, access control and CCTV on the same contract ## Speed is a specification, not an aspiration Google treats a page as fast at an LCP under 2.5 seconds, an INP under 200 milliseconds and a CLS no higher than 0.1 — measured at the 75th percentile of real visitors, not on a developer's laptop. Those thresholds go into the brief as a checkable acceptance condition. Holding them is weight discipline: fonts subset by alphabet, Cyrillic and Latin as separate files, because one file carrying every glyph weighs several times more than the page needs; images as AVIF and WebP with dimensions declared. An honest caveat — what ruins speed is rarely our kilobytes and usually someone else's. A live chat, three ad pixels and a reviews widget can push INP past 200 ms on a mid-range phone in one evening. We price each in milliseconds and leave the decision to you. ## What you get, and who owns it The repository is created inside your organisation, not ours. Domain, hosting, DNS, payment keys, analytics and CI sit on your accounts from day one; we work as invited collaborators. We do not tie clients to a bespoke panel nobody but us can open. Schema, environment variables and deployment steps are handed over in writing, so an outside developer can stand the project up by following them — which is the best test of the documentation. ## When we talk you out of it If the job is three pages, an enquiry form and no integrations, you do not need a Next.js build: a site builder will cover it for less, and we will say so on the first call. Custom development pays for itself where there is a catalogue, a customer account, pricing logic, roles or a 1C exchange — and even there, lifting one bottleneck into its own service usually beats rewriting a working site wholesale. ## Common questions ### How long does a website take? The schedule is set by how many external systems are involved and how fast decisions are made on your side, not by page count. A catalogue with no integrations clears design, build and acceptance far faster than a shop with a 1C exchange and payments, where half the calendar goes on credentials and test keys. ### What drives the cost? How many distinct page types must be designed, how many systems must be connected, whether editors need a content interface, and how many languages it lives in. The most underestimated factor is your data: a clean 1C export and a messy one differ by a large multiple in effort. ### What do you need from us to start? A clear view of who your buyer is and what they should do on the site, plus someone empowered to decide. Then domain access, brand materials, a contact for your accountant or 1C integrator, and where the content comes from — copy and photography derail schedules more often than anything technical. ### Who owns the code, and what if we change supplier? The code is yours. The repository sits in your organisation from the outset, and domain, hosting, payment dashboards and analytics are on your accounts. Handing over to another supplier means granting repository access — nothing to buy back, no export to wait for. ### What happens after launch, and what if something breaks? Three separate things follow a launch: warranty fixes, technical maintenance — dependency updates, certificates, backups, uptime monitoring — and further development. The first is part of the project; the other two are agreed separately. Monitoring goes in immediately: an outage is better reported by a system than by a customer. ### Do we need an Uzbek version? Usually yes, if you sell to consumers, to the regions or into the public sector: Uzbek is the language of most of the country's audience, and queries such as "sayt yaratish" lead to pages Russian-only sites do not have. ## Related services - [Mobile app development in Tashkent](https://i7team.uz/en/services/mobile-development) - [Telegram bot and Mini App development](https://i7team.uz/en/services/telegram-bots) - [IT outsourcing and support](https://i7team.uz/en/services/it-outsourcing) ## Let's scope your project Tell us what has to happen on the site and which systems it must talk to. You will get an architecture, a realistic range for the schedule and a costing based on examined scope — before any contract. info@i7team.uz, +998 77 372 21 12. Get in touch: info@i7team.uz · +998 77 372 21 12 · https://i7team.uz/en/contact