What drives the cost of a website, why quotes for the “same” project differ several times over, and which expenses people forget to budget for.
“How much does a website cost?” is the first question almost every client asks — and the least satisfying answer is “it depends.” Below we break down exactly what it depends on, why two quotes for the “same” website can differ fivefold, and how to avoid overpaying without ending up with a project you’ll have to rebuild in six months.
What the price is made of
A website’s price isn’t “coding some pages” — it’s the sum of hours from different specialists. A typical project involves:
- An analyst or project manager who learns your business, gathers requirements and builds the structure and plan.
- A UI/UX designer who creates prototypes and then designs all key screens for desktop and mobile.
- A frontend developer who turns the designs into a responsive layout, animations and forms.
- A backend developer who builds the admin panel, catalog, cart and integrations with payments, CRM and 1C.
- A QA engineer who tests everything across devices and browsers.
- An SEO specialist who sets up the right structure, meta tags, speed and indexing.
The more custom logic, pages and integrations, the more hours — and the higher the price.
Price guidelines
Here are our starting prices. The final figure is calculated after a brief, but this is the ballpark:
- Landing page — from 5M UZS, 2–3 weeks. One high-converting page for a specific product or ad campaign.
- Corporate website — from 7M UZS, 4–6 weeks. Multiple sections, services, case studies, blog, multilingual.
- Online store — from 10M UZS, 6–10 weeks. Catalog, filters, cart, online payments, customer account.
- Web services and CRM — from 30M UZS, 2+ months. Complex business logic, user roles, reports.
- Mobile app — from 50M UZS, 3–6 months.
What affects the price most
1. Template vs. custom design
A ready-made template is cheaper, but you get a site that looks like hundreds of others and you bend your business to someone else’s structure. A custom design costs more upfront but is built around your customers and goals — and usually converts better.
2. Number of page types
What matters is not the total number of pages but the number of different templates. 200 product pages are one template. Home, About, Services, Case study, Article and Contacts are six different templates, each needing design and development.
3. Integrations
Payme, Click, Uzum, 1C, amoCRM or Bitrix24, delivery services, SMS gateways — each integration adds days of development and testing. List them upfront, or they’ll surface mid-project and push the deadline.
4. Languages
In Uzbekistan a site often needs Russian, Uzbek and English. That’s more than “translating the copy”: you need a language switcher, separate URLs for SEO and layout checks, since Uzbek and English words differ in length.
5. Content
Copy, photos, product descriptions. If you don’t have them, someone has to create them — separate work that’s often left out of the budget.
Costs people forget
- Domain — paid yearly. Register it to yourself or your company, not to the contractor.
- Hosting or server — monthly. Cheap shared hosting won’t handle a busy store.
- SSL certificate — often free, but it must be set up and renewed.
- Support — updates, backups, small improvements. Ours starts at 2M UZS per month.
- Promotion — a site without traffic doesn’t sell. Budget for SEO or ads from month one.
Why a cheap website often costs more
The most expensive mistake is choosing a contractor on price alone. A typical story: the site is built fast and cheap, but it loads slowly, looks bad on phones, can’t be edited without a developer, and the source code stays with the contractor. Six months later it has to be rebuilt — and paid for twice.
Compare not prices, but what’s included: design, responsiveness, admin panel, SEO foundation, source code handover and warranty.
How to get an accurate quote
- Describe the site’s goal: leads, sales, brand image, customer support.
- Collect 3–5 websites you like and explain what exactly you like about them.
- List the sections, languages and integrations you need.
- Share your target deadline and budget range — it helps us propose a realistic option instead of an “ideal but three times the price” one.
For large projects it makes sense to launch in stages: first a minimal version that already makes money, then improvements based on real data.
