How long does it take to build a website?

The short answer: a presentation website takes 2-4 weeks, an online shop 4-8, a custom application three months and up — but the clock starts when you have the content, not when you sign the contract. And the gap between those two moments is where most weeks are lost.

This article is about what happens inside those ranges, what stretches them, and what you can do to move faster.

Real timelines, by project type

These are timelines from delivered projects, not optimistic quote estimates. A shop with a thousand products and invoicing integration took longer. A presentation site with the copy ready took less.

What happens, week by week

For an ordinary presentation website:

1. Discussion and structure (2-4 days). Which pages, what each contains, what the visitor should do. Half the project's success is decided here, and this is the step most often skipped.
2. Design (4-7 days). The home page first, then the pattern for the rest. You see it, you say what you dislike, it gets corrected. Usually two rounds.
3. Build (5-10 days). The code is written, content goes in, everything is checked on phone, tablet and desktop.
4. Checks and launch (2-3 days). Forms, speed, structured data, certificate, sitemap, analytics. Then the domain points at the site.

What stretches a project — in order of frequency

1. Content that does not arrive

By far the leading reason, and almost never the fault of the company building. Service copy, team photos, correct contact details, the logo in a usable format — all depend on the client, and the client has another job.

A three-week project becomes a three-month one because "I'll send the copy next week" repeats eight times. The honest fix: either give us a date you will actually meet, or pay someone to write it.

2. Deferred decisions

"Let me discuss it with my partner." Every deferred decision stops work, and resuming costs extra time because the whole context has to be re-read. A project moves fastest when one person can say yes without asking anyone else.

3. Mid-project changes of direction

Not small tweaks — those are normal and included. Rather "I saw a site I like better, let's do it that way". Rebuilding the structure halfway effectively resets the schedule.

4. Integrations with external systems

Courier, invoicing, payments, accounting software. Each has its own documentation, its own quirks and an approval process outside anyone's control on the project. For card payments, merchant account activation alone can take two weeks — start it on day one, not at the end.

5. Internal approvals, in institutions

If you work with a public institution or a large company, the schedule is set by meetings, not developers. It is predictable, but it has to be planned for from the start.

What you can do to speed things up

• Prepare the content before we start. Even rough, even with mistakes — it gets edited. One document with the copy for each page shortens the project by weeks.
• Name a single decision-maker. How you gather opinions is your business; who answers must be one person.
• Collect the materials in one place — vector logo, good-resolution photos, company details, domain and hosting access. Hunting for the domain password on launch day is a classic.
• Start early on anything that depends on others. The payment account, the courier contract, the invoicing series.
• Batch your revisions. A list of twenty observations is resolved faster than twenty messages spread over two weeks.

About "I want it in five days"

It is possible, on three conditions: you have the content ready, you accept a customised theme rather than bespoke design, and there is a single person approving. Without all three, a five-day deadline is a promise that breaks in week two.

A deadline without stages is not a deadline, it is a hope. Ask for the schedule by phase, with what you must provide at each — that shows immediately whether it is realistic.

In short

• Presentation: 2-4 weeks. Shop: 4-8. Custom application: from 3 months.
• The clock starts with content, not with the contract.
• The number one cause of delay is content that does not arrive.
• A single decision-maker shortens a project more than anything else.
• Third-party integrations start on day one, not at the end.