How long a website takes: timings stage by stage

"A site in a day" and "a site in three months" can both be true, because they describe different work. Here is what the timeline is made of and where the time actually goes.

Let's separate two things right away: the time to build a site and the time until the site is ready. The first is measured in hours; the second in how fast you reply.

What the timeline is made of

• The goal — what the site is for. Half an hour, but everything else is pointless without it;
• Copy — the longest stage. What you offer, what it costs, why anyone should trust you;
• Photos — an hour if you have them, a day of shooting if you don't;
• Assembly — hours on a builder, weeks by hand;
• Review and edits — one or two rounds;
• Domain — a .uz name can take several days; it runs in parallel.

Realistic timings

A day. Real, if the copy and photos are ready and the site is a single page. On a builder the first version appears within hours.

A week. The usual timeline for a small services site: 5–8 pages, with copy you supply or edit.

A month. A catalogue, two languages, several service pages. Most of that month goes to approvals, not assembly.

Three months or more. Usually not complexity but stalls: waiting for copy, waiting for a decision, waiting for a manager to reply.

Where the time really goes

This is the important part. In practice three things stretch the timeline, and none of them is technical.

1. No copy. "We'll fill it in later" leaves sites parked for months. Fix: launch with imperfect text and improve it afterwards;
2. Too many decision makers. If three people discuss a colour, that's a week. Appoint one owner;
3. No boundary. "Let's add one more thing" never ends. Write down what belongs in version one.

How to speed it up

• Gather before you start: logo, photos, list of services, prices, phone, address, social links;
• Start with one page. One that works beats ten that don't;
• Order the domain on day one — it registers without you;
• Send edits as a list, not one at a time;
• Aim for "launched", not "perfect". A website is not print; you can change it tomorrow.

How long it takes on a builder

On Tayyorsayt the first version is assembled from a chat conversation: you describe what you sell and get a structure and copy. Later edits go through the chat too — no waiting for a developer. Publishing is one click.

So the technical part takes hours. The rest of the time is yours: copy, photos and decisions. The honest answer is therefore not "in a day" but "a day after your materials are ready".

In short

• One page with materials ready — a day;
• A small services site — a week;
• A catalogue and two languages — a month;
• Long timelines are almost always copy and decisions, not technology;
• Launching with an imperfect but working site is the right call.