# How Long Does a Website Take? > Published 2026-10-25 ยท Canonical: https://goodglyph.com/en/blog/how-long-a-website-takes The real ranges by project type, the stages where the time goes, and the part quotes rarely mention: the calendar depends on decisions and content, your side of the project, more than on the supplier. Plus how to plan backwards from a deadline that will not move. A presentation website with a clear scope and content nearly ready takes, as a working range, two to four weeks. A complete website, with strategy, design made for your business and texts written along the way, takes four to eight weeks. An online store or a project with special functionality goes past two months. The ranges come from our own projects, they are calendar weeks, approvals and waiting included, and the order of magnitude holds with almost any supplier who works in an organized way. The second half of the answer matters more than the numbers: in the calendar of a website project, the actual building occupies the small part. The large part goes to decisions and to content, which sit on your side of the table. That is why two companies with identical projects on paper can finish a month apart, with the same supplier and the same budget. The rest of this article shows you where the time goes and which part of it you can shorten yourself. ## How long does a website take, by project type? The bands below assume two things: an organized supplier and a client who answers within a few days at each handover. With either one missing, every range stretches. - **Presentation website with a clear scope: two to four weeks.** A handful of pages, a clear offer, texts and photos that already exist. It moves fast because the big decisions were made before the start. - **Complete website, with strategy and dedicated design: four to eight weeks.** This adds positioning, a structure built around what your clients search for, design from scratch and content written along the way. The extra time buys exactly the part that brings clients. - **Online store: from two months up.** Alongside the pages come the product catalog, payments, shipping and client accounts, each with its own setup and testing. Migrating products out of an old system adds time of its own. - **Special functionality: estimated separately.** Bookings, a client portal, integration with an internal system. The timeline only comes out of analysis, and a supplier who promises one before doing that analysis is telling you something important about how they will work. Money is the twin conversation, and the two get decided together; we wrote about the figures separately, in [how much a presentation website costs](https://goodglyph.com/en/blog/how-much-a-presentation-website-costs). And for software with product logic, where the ranges look different, there is [how long an app takes to build](https://goodglyph.com/en/blog/how-long-app-development-takes). ## Where does the time actually go, stage by stage? A website project passes through the same big stages whatever its size: strategy, structure, design, build, launch. We described how we run them on checkpoints, with your approval at every step, in [how a design project actually runs](https://goodglyph.com/en/blog/how-a-design-project-actually-runs); here we only look at where the time goes. - **Strategy and structure take the first part.** Conversations about audience and offer, the architecture of the pages, what each page says and what action it asks of the visitor. The stage looks poor in deliverables and in fact decides whether everything after it flows or gets redone. - **Design takes the middle.** The visual direction, the key pages, then the rest. Here the calendar breathes at the rhythm of your feedback: every round adds its days, and rounds left without an answer add weeks. - **The build is the predictable part.** With structure and design approved, implementation holds few surprises, and many pieces run in parallel. This stage shortens only when everything before it is settled, and stretches badly when the design changes midway. - **Launch has its own week, which everyone forgets.** Tests on phones, speed, forms that actually send, connecting the domain, redirects from the old site. Skipped, it gets paid for in the first month, with mistakes found by clients instead of the team. ## Why does the calendar depend more on you than on us? Two bottlenecks stretch almost every website project, and both sit on the client side. We name them plainly, because known in advance they are easy to avoid. **First: content.** Texts about your services, photos, company details, access to the domain and the hosting. Design can advance for a while on placeholder texts, but final approval happens on real content, and pages without texts stand still however good they look. In our projects, content delivery is by far the most frequent cause of delay. **Second: decision speed.** One person with a mandate answers within a day. A committee of three partners answers within a week, sometimes with three opinions that first have to settle among themselves. Every round of "let us think it over" adds exactly as many days as it lasts, and the project collects them quietly. The quote measures the work; the calendar measures the work plus the waiting between steps. To be fair, suppliers cause delays too: overbooked agencies, weeks of silence, "almost there" with no date attached. A serious supplier shows in the first quote: a calendar in weeks, with the dependencies named, meaning what they expect from you and by when. Whoever cannot show you that before the contract will not show it after either. ## What shortens a timeline honestly? - **Content prepared before the start.** The core texts about your offer, the photos, the company details, the domain access. A week of preparation before the project usually removes several weeks of waiting from the middle of it, where delay costs more. - **One person with the final say.** Colleagues can weigh in, but the answer leaves from a single person, within an agreed window. That change alone can cut whole weeks out of a project. - **Feedback within two or three working days, agreed on day one.** Tight, in writing, collected from everyone at once. Ten comments in a single message get resolved in a day; the same ten, dripping in across two weeks, keep the project open just as long. - **A standard scope.** Pages that have proven their purpose, common functionality, no first-ever experiments. Your particularity belongs in the message and the design, where it brings clients; in functionality, every first adds build time and testing time. ## What shortens it only on paper? - **Skipping strategy.** Without positioning and a thought-through structure, the site finishes fast and says little: a catalog of services with photos, which the visitor scrolls through and leaves. We have seen that version come back for a rebuild within its first year, cost included. - **A template with your logo on top.** The timeline genuinely drops, but you receive a different product from the one discussed: the same structure as everyone else, into which your offer fits as best it can. There are situations where that is a correct choice; what matters is making it knowingly, as a deliberate choice, in place of a quiet shortcut. - **"We will add the texts after launch."** A site launched empty stays empty for months, because after launch other urgencies arrive. A page published without a message works for nothing from day one. ## "Urgent by Friday": what does the rush cost you? Can a website be built in a week? It can, and we say it without irony, under three conditions: scope cut to the essentials, content delivered in full before the start, and decisions given the same day. Those conditions rarely arrive together, which is why serious one-week websites are rare too. What you lose at that speed is the invisible part: strategy compresses into one conversation, testing into one quick pass, and the texts get written overnight, which is exactly the piece your clients read. The rush gets paid for after launch, in three ways: pages rebuilt in the first months, mistakes discovered by visitors, and a site that looks finished but brings little, because the compressed part was the very part that brings. An honest short timeline comes from a smaller scope, with the stages kept: launch small and well, then extend. ## When is a deadline real, and how do you plan backwards from it? Some deadlines truly will not move: an event with a fixed date, a paid campaign about to start, the season when bookings happen, a trade fair you attend with your products. A guesthouse that wants the summer's bookings needs its site in March; in June, the same launch is worth half. For deadlines of that kind, plan backwards, in steps: 1. **Put the real date in the calendar and subtract a two-week buffer.** Something will slip; the buffer turns the slip into an inconvenience instead of a crisis. 2. **From the date that remains, subtract the band for your type of project.** Four to eight weeks for a complete website, two to four for a focused one. 3. **What comes out is the start date: contract signed and core content delivered.** From there, count further back for your own weeks of preparing texts and photos. 4. **If the start date is already behind you, cut scope, with the stages kept.** A focused version launched on time beats a complete site launched after the season. You extend later, on a site that is already working. A campaign can be moved; the season, the fair and the event date stay where they are. The less negotiable the deadline, the earlier the conversation is worth starting. ## The GoodGlyph take When you ask for quotes, ask for the timeline together with the list: a calendar in weeks has value only next to the list of what is expected from you and by when. A timeline without that list is a promise about half the project, the supplier's half. Our quote for a [presentation website](https://goodglyph.com/en/services/presentation-website) comes with both: the stages in weeks and your handovers, with dates, so you see the whole calendar before you sign. Get a quote with a timeline and judge any other quote on the same point: whoever shows you your part of the road is really showing you all of it. ## Closing "How long does it take?" has two answers. Ours is measured in weeks of work and sits written in the quote. Yours is measured in how fast you deliver the content and make the decisions, and it gets decided before the start. The projects that finish on time are the ones where both answers were taken seriously from day one. ## FAQ ### How long does a presentation website take? As a working range, two to four weeks for a clear scope with content prepared, and four to eight for a complete project with strategy and dedicated design. The exact interval comes out of the scope and the speed of your feedback. ### Why does it take that long if "it's just a website"? Because the visible part, the pages, stands on an invisible one: decisions about the offer, structure, texts, photos and testing. The building occupies the small part of the calendar; decisions and content occupy the large one. ### What can I prepare to make it go faster? The core texts about your offer, the photos, the company details, access to the domain, and one person who gives the final answer. Delivered at the start, these remove the most frequent causes of delay. ### Can a website be built in one week? Yes, under three conditions: scope cut to the essentials, content delivered in full before the start, and same-day decisions. In exchange you accept compressed strategy and reduced testing, so treat it as a starting version, to be extended afterwards. ### How long does an online store take? From two months up, because alongside the pages come the product catalog, payments, shipping and the testing of each part. Migrating products from an old system adds time of its own. ### What happens if I deliver the content late? The project goes on hold, and the deadline moves with every day of delay, sometimes by more, because the team has meanwhile started on another project. It is the most frequent real reason a "one month" website ends up taking three. ## Related - Related service: [Service](https://goodglyph.com/en/services/website-prezentare) - [Why Your Website Does Not Convert (and How to Find the Leak)](https://goodglyph.com/en/blog/why-your-website-does-not-convert) - [Restaurant Website Design: What Actually Brings Reservations](https://goodglyph.com/en/blog/restaurant-website-design) - [DIY Website or Agency: When Each One Makes Sense](https://goodglyph.com/en/blog/diy-website-or-agency)