How long a website that converts really takes
Why two quotes are never comparable, which phase actually stalls projects, the five questions for reading a quote, and what you can cut without breaking the site.
“How long does a website take?” is a reasonable question with a useless answer. Any range someone gives you without knowing what goes inside it is an invented figure wearing a quote’s clothes.
This article is not about what a good site contains — that is in the structure of a site that works and in the landing page checklist. It is about timeline and scope: what makes a project take as long as it takes, and how to read a quote without comparing apples to oranges.
Why two quotes are never comparable
Because the price and timeline of a site do not depend on the number of pages, which is the one thing usually specified. They depend on how many decisions have to be taken, and who takes them.
Two quotes for “a six-page site” can describe completely different projects depending on whether they include:
- Copywriting, or whether you supply the text.
- Original photography and graphics, or stock imagery.
- How many revision rounds, and what happens on the fourth.
- Measurement configured, or just the analytics snippet pasted in.
- Forms connected to something, or forms that send an email.
- Content migration and redirects from the old site.
- Who ends up owning the domain and the hosting.
The last two cause the most grief later. A new site with no redirects from the old one throws away the search equity you accumulated, and a domain registered to the supplier is a problem the day the relationship ends.
The five phases, and which one actually stalls
| Phase | What happens | What stretches it |
|---|---|---|
| Definition | What the site says, to whom, and to what end | No decision having been made about positioning |
| Content | Copy, images, cases, pricing | Almost always: the phase that gets underestimated wholesale |
| Design | How it looks and how it is navigated | Revision rounds with no agreed criteria |
| Build | The site working | Scope changes halfway through |
| Measurement and launch | Analytics, events, forms, testing | Leaving it last and cutting it for time |
The pattern repeats so consistently it is worth saying plainly: the phase that stalls projects is content, and it is almost never in the plan as a phase with an owner and a date. It shows up as an assumption — “the client supplies the copy” — that nobody turned into a task with a name attached.
The phase that gets cut when the project runs late is the last one, measurement. That is exactly backwards: launching without measurement is launching without knowing whether it worked, and then every later improvement gets decided by opinion.
What delays a project is almost never the code
Ordered by how much time it consumes in practice:
- Copy that was never written. “We’ll send it next week” is the phrase that adds the most weeks to a web project.
- Decisions without an owner. If three people have to agree and none decides, every revision round costs double.
- Chained approvals. Each reviewer adds their response time, not their reading time.
- Material that does not exist. Photos of the team, the premises, the product. Producing them is its own project and is rarely on the schedule.
- Access. To the domain, the hosting, the analytics. Asking on day one saves a week at the end.
How to read a quote
Five questions that make the incomparable comparable:
- What do I supply and what do you supply? Above all copy and images.
- How many revision rounds are included, and what happens on the next one?
- What is measured on the day we launch? Forms, events, goals.
- Whose name are the domain, hosting and accounts in?
- What happens to the current site’s URLs? If redirects are not in scope, there is a hidden cost in traffic.
A supplier who answers all five without discomfort is quoting seriously. One who answers with a total and a list of pages is not necessarily.
What you can cut without breaking it
When you have to launch sooner, not everything is worth the same. These can wait:
- Secondary pages nobody will look for in the first month.
- Animation and interaction detail.
- The other language version.
- The blog, if there is nobody to write it yet.
These cannot wait, because later they cost three times as much:
- Measurement. Launching without it leaves a blind period you never get back.
- Redirects from the previous site.
- Forms arriving somewhere a person actually looks. A form emailing an inbox nobody opens is a broken form.
- Mobile speed. Fixing it afterwards means redoing structural decisions.
The first list can be added at any point. The second decides whether the site is useful or an expensive brochure.
FAQ
- Why do quotes for “the same site” differ so much? Because they are not for the same site. One includes copywriting, photography, measurement and a round of revisions; another assumes you supply all the content and approve at the first pass. Comparing the totals without comparing what is inside them tells you nothing.
- Is a template faster? To get online, yes. To convert, not necessarily: the time goes into deciding what the page says and proving it works, and a template does not decide that for you. It saves build time, not decision time.
- Can we launch with less and improve later? Usually the best call. A smaller site that is live and measured teaches you more than a big one that launches three months later. What cannot be postponed is measurement — launching without it means the improvements have nothing to aim at.
- What is the single biggest cause of delay? Content and decisions on the client side, by a wide margin. Text that has not been written, photos that do not exist, and approvals waiting on someone who is travelling stall more projects than any technical problem.