how long does it take to build a website? the honest timeline, and where the time actually goes

web · Sep 25, 2026 · 4 min read

ask three providers how long a website takes and you will hear a weekend, six weeks, and four months. they are not contradicting each other. they are describing three different purchases, and confusing them is how projects disappoint.

the real timelines

  • a builder, one page: a weekend. template chosen, content poured in, live by sunday. this is real, and for a professional who needs to be findable it can be enough. the timeline is short because the decisions were made by the template.
  • a template plus a designer: one to two weeks. the shapes exist; the work is adjusting colors, sections and photos, and that is bounded work.
  • a freelance, done with care: three to six weeks. not because the code takes a month. because the process includes questions, structure, real text, a round of revisions, and testing on real devices.
  • an agency: ten to twenty weeks. research, structure, content, design reviews, development, content entry, testing. the number is not padding. it is a process with more people and more handoffs.

if someone promises a serious custom site in three days, they are selling the template option at a person price. if someone quotes twenty weeks for a five-page showcase site, they are selling a process you do not need.

where the time actually goes

here is the part nobody believes until they live it: the code is never the bottleneck. the content is.

a five-page site is days of building and weeks of deciding. what the photos will be. who writes the text, and when. what the services actually are, named the way clients name them. every project stalls in the same place: the developer finished, the site is waiting for the words, and the words are waiting for an owner who is busy running a business.

the second consumer of time is the feedback loop. one round of revisions is days; five rounds of small indecisions is weeks. the projects that finish fast are not the ones built fastest. they are the ones where decisions were made once and kept.

what you can do to make it faster

  • decide the one sentence before the first call: i help [who] do [what]. everything else is detail.
  • gather the raw material early: photos, reviews, the list of services, the answers to the questions clients always ask. content readiness is the single biggest variable in the timeline.
  • name one decision maker. committees re-litigate. a project with one voice moves at the speed of the work; a project with five voices moves at the speed of scheduling five people.
  • accept good-enough v1. a site you can change is better than a site that is perfect in month four. ship small, fix in the open.

i wrote the fuller map of the three ways to build, with costs, in how do i make a website — the timeline and the price are the same trade seen from two sides.

FAQ

why does a simple site take three weeks if the code is days?

because the code is not the work. the questions, the text, the photos, the revisions and the testing are the work. when a provider quotes weeks, most of those weeks are yours, not theirs.

can it be done in a week?

yes, if every decision and every piece of content already exists on day one. this almost never happens, which is why the honest range exists.

is a longer timeline a bad sign?

not by itself. twenty weeks for a company site with research and content is normal. twenty weeks for the same site a builder could host in a weekend is a process being sold that you may not need.

the closing thought

a website timeline is mostly a mirror of decision speed. the providers who ask a lot of questions up front are not slowing you down. they are moving the weeks from the end, where they hurt, to the beginning, where they are just conversations.

near Parma, if you want the version where the questions come first and the timeline is honest: