What a website costs in Kazakhstan: a breakdown by type and timeline

The first question in almost every enquiry is “what will a website cost”. The honest answer sounds dull: it depends on scope. But the ranges can be named, and here they are, with a note on what falls into each.

What makes up the price

The cost of a website is not “design plus markup”. It comes from four parts, and the most expensive one is usually not the one people expect.

Structure and content. How many sections, which scenarios, what a person is supposed to do on the site. This is where it is decided whether the site works at all.
Design. The number of unique screens and states. Ten similar catalogue pages are cheaper than three pages that look nothing alike.
Development. Responsive behaviour, animation, integrations, the admin side.
Integrations and data. CRM, payments, delivery, accounting systems, external APIs. These are what usually double an estimate — and what everyone forgets at the start.

Guide prices by project type

Landing page — from ₸160,000, 2–3 weeks

One page for a specific offer: a service, a product, a set. A form, analytics, basic SEO markup. A good choice when you need to test demand or collect enquiries from ads.

A landing page does not replace a company website. If you have five services and each needs explaining, five landing pages cost more than one proper site.

Corporate website — from ₸320,000, 4–6 weeks

Up to ten sections, content management, a blog, forms, integration with email and messengers. The standard option for a company whose site is the main storefront and entry point for clients.

Catalogue site or store — from ₸520,000, 6–8 weeks

Catalogue, filters, product pages, cart, payment and delivery. The price grows with the number of product attributes and with where stock and prices come from. A 50-item store managed by hand and a 5,000-item store synced from an accounting system are different projects.

Web application or product — from ₸750,000, from 8 weeks

A dashboard, roles, data handling, your own logic. Counting “by pages” makes no sense here: the price depends on the scenarios and on what happens to the data.

The full list with details is on the services page.

Why similar projects differ threefold

When you compare two proposals, the difference usually comes down to four things:

Template or custom build. A ready theme saves weeks but limits the product to someone else’s decisions.
Who designs it. Sometimes there is no design at all — the site is assembled from page-builder blocks and called development.
Whether integrations are included. The most common reason a cheap proposal becomes expensive mid-project.
What happens after launch. Is the code handed over, who fixes bugs, is support included.

Where to save and where not to

You can save on: the number of sections at launch, custom illustration, complex animation, rarely used integrations. All of it can be added later.

You cannot save on: structure and scenarios, loading speed, the mobile layout and analytics. Saving here always ends in a rebuild, and a rebuild costs more than doing it properly the first time.

How to work out your number before we talk

Answer three questions for yourself:

What action should a person take on the site — call, send an enquiry, place an order, register?
Where does the content come from — will you provide texts and photos, or is that part of the job?
Which systems does the site need to exchange data with?

Those three answers are enough to name a range within 20–30%. Everything else is refined during planning.

If you want a specific estimate for your task, describe it in the form and we will come back with a range and a timeline within one business day.