How Long Does It Take to Build a Website? By Scope
How long it takes to build a website by scope: landing page, small business site, store or web app, the phases, what slows projects and what to have ready.
Nilesh Sharma· · 14 min read

On this page
"How long does it take to build a website?" is usually the second question after "how much?", and it has the same honest answer: it depends on what you are building. A one-page offer, a five-page business site, an online store and a custom web app run on different clocks, and the biggest variable is often not the developer at all. It is how quickly the content, feedback and approvals arrive.
This guide gives you planning ranges by scope, the phases of a typical project and who owns each one, what slows projects down, how rush deadlines are usually handled, and a checklist of what to have ready before development starts. It does not repeat build prices; for those, see what the build costs by scope.
The ranges below are typical planning estimates, not promises. They match the timeline panel in my website cost calculator, and the published ranges next to them come from the dated sources linked in each row. Every real project should get its own timeline against a written scope.
The short answer: timeline follows scope, content and approvals
A focused landing page typically takes one to two weeks, a small business website around three to five weeks, an online store six to ten weeks and a custom web app MVP two to four months. Those are planning estimates with content ready. Missing copy, slow approvals and added features push every one of them out.
| Scope | Planning estimate (content ready) | Published professional range | What usually stretches it |
|---|---|---|---|
| Landing page / one-pager | 1–2 weeks | 1–2 weeks for a 1–5 page brochure site (Elementor, updated Jun 2026) | Headline and offer still being debated |
| Small business site (about 5 pages) | 3–5 weeks | 4–8 weeks for 5–15 pages with a blog and forms (Elementor) | Copy, photos, several approvers |
| Blog or content site | 3–5 weeks | Not given separately | Writing and migrating posts |
| Online store | 6–10 weeks | 8–16 weeks for 10–100 products (Elementor) | Product data, shipping, tax, payments |
| Custom web app MVP | 8–16 weeks | 4–6+ months for large custom builds (Elementor); about 5–6 months for a full agency process including choosing the firm (HubSpot, updated May 2025) | Logins, payments, integrations, changing requirements |
The planning estimate assumes the base scope in each row. In the calculator, each added feature (booking, payments, logins, integrations, multiple languages, an AI feature) adds roughly half a week to a week, needing copy written adds one to two weeks, migrating an old site adds one to two weeks, a brand-led premium design adds one to two weeks, and every ten extra pages adds about a week. That is why a "small business site" with bookings, payments and two languages can land closer to the store row than the business row.
Website development timeline: the phases and who owns each
Most website projects move through the same seven phases: discovery and scope, content, design, build, testing, launch and post-launch fixes. The developer owns design, build and testing. The client owns most of the content and every approval, and those client-owned steps are where timelines usually slip.
| Phase | What happens | Who usually owns it |
|---|---|---|
| 1. Discovery and scope | Goals, audience, page list, features, what is out of scope, a definition of done | Shared: the client brings the goals, the developer turns them into a written scope |
| 2. Content | Copy, photos, logos, product data, legal pages | Mostly the client, unless copywriting is in the scope |
| 3. Design | Layout and visual direction, then page designs or a styled prototype | Developer or designer; the client reviews and approves |
| 4. Build | Templates, pages, CMS, forms, integrations, responsive layouts | Developer |
| 5. Testing (QA) | Devices and browsers, forms, checkout, speed, accessibility basics, broken links | Developer, with a client review round |
| 6. Launch | Domain and DNS, hosting, analytics, redirects, sitemap | Developer, but the client must provide account access |
| 7. Post-launch | Fixing what real visitors find, small edits, handover | Shared |
HubSpot's breakdown of a firm-led project gives a sense of how much of the calendar is conversation rather than coding: one to three weeks for initial goal-setting, one to two weeks for an action plan, two to three weeks of design mockups and feedback, one to two months of development and one to two weeks of review (HubSpot, updated May 8, 2025). A smaller site with one decision-maker compresses those early phases a lot; a committee stretches them.
The practical takeaway: the phases you control (content and approvals) can add as much time as the phases the developer controls. Ask for a timeline that shows both, with dates for when the developer needs things from you.
Landing page vs small business site vs custom web app: different clocks
A landing page is one offer and one form, so it is mostly copy and layout. A small business site adds navigation, several page templates and more content. A custom web app adds logins, data, payments and integrations that need building and testing. Each step up adds phases, not just pages.
Landing page. The build is quick. The slow part is deciding the headline, the offer and the proof. If those are agreed, the page can move from design to launch within the one-to-two-week planning range.
Small business website. Typically home, about, services, contact and perhaps a blog. The work is a handful of templates plus the content to fill them. Whether you need a template, a builder or a custom build changes the clock as much as the page count; the small business website design guide covers choosing template, builder or custom.
Online store. The cart is rarely the slow part. Product photos and descriptions, variants, shipping rules, tax settings, payment setup and test orders are. A store with a handful of products and simple shipping is a very different project from one with hundreds of variants.
Custom web app. User accounts, roles, dashboards, payments and third-party APIs each need design, build and testing. The usual way to keep the timeline sane is to define a first version (an MVP) with a short feature list, launch it, then add the rest in planned releases.
What actually slows a website project down
The most common delays are missing copy and images, approvals that need several people, integrations such as payments, booking or a CRM that surface missing details late, and features added after design has started. Elementor's guide names unprepared content as the top reason projects stall and undefined scope as the second.
That ranking, from Elementor's 2026 timeline guide, matches how projects typically run. In more detail:
- Copy and photos. A designer can lay out placeholder text, but a page is not finished until the real words and images are in it. Copy that arrives late often changes the design too, because real headlines are longer or shorter than the placeholders.
- Approvals by committee. Each extra reviewer adds a feedback round, and conflicting feedback adds another round to resolve it. One person who can say "approved" saves more time than any tool.
- Logins and access. Domain registrar, DNS, hosting, Google Search Console, analytics, payment provider, booking tool. Waiting days for a password or an account invite is a surprisingly common launch delay.
- Integrations. Payments, bookings, CRMs and email tools each need an account, settings, test data and a test run. They also expose questions nobody asked earlier, such as refund rules or what happens when a booking is cancelled.
- Scope changes mid-build. Adding a shop, a blog, a members area or a second language after design has started is not a tweak. It is a new slice of work, and it should come with a new date.
- Feedback that arrives all at once at the end. Reviewing early designs properly is cheap. Rejecting the direction during testing means redoing finished work.
Does AI or a website builder make it faster?
Yes for first drafts, layouts, boilerplate code and placeholder content; much less for the steps that usually decide the launch date. AI and builders do not write your offer, gather your photos, approve pages, open your payment account or test your checkout. Those steps still set the timeline.
Where AI tools realistically help, in a developer's workflow:
- Scaffolding and boilerplate. Generating components, forms and repetitive page sections faster.
- First drafts. Draft copy, image alt text and FAQ ideas that a human then edits for accuracy and voice.
- Debugging and refactoring. Explaining errors, suggesting fixes and writing small tests, which the developer still has to review.
- Content migration chores. Reformatting old posts or product descriptions into a new structure.
Where they do not change much: deciding what the business offers, getting real photos, legal and privacy pages that fit your situation, decisions by the people who approve the site, setting up third-party accounts, and careful testing on real devices. The guide to AI tools for web development goes deeper on which tools help at which step.
Hosted website builders are a separate question. Filling in a builder template yourself can be quick for a simple site, but the time moves to you: Elementor puts a do-it-yourself small business site at one to two weeks, and HubSpot describes a DIY build as "a matter of weeks" rather than months. The trade-off is less customization, not just less time.
Can you build a website in two weeks? Rush timelines and cost
Sometimes. A landing page or a template-based site with ready content can fit two weeks. A larger site usually cannot without changing something: cut the scope to a smaller first version, add people or longer hours at a higher cost, or decline the deadline. Rush work rarely gets cheaper or simpler.
When a "we need it in two weeks" request comes in, these are the usual options, roughly in order of how often they make sense:
- Cut scope to a launchable first version. Launch the pages that drive enquiries or sales first, and move the blog, extra services, second language or integrations to a dated phase two. This is usually the best option because it keeps quality and budget intact.
- Pay for speed. Compressing design, build and review into fewer weeks usually means more people or longer days, and fewer feedback rounds. In my website cost calculator, a rush timeline of under three weeks adds 25% to the build estimate and shortens the estimated weeks, and it warns you when the scope normally takes longer than three weeks.
- Decline or move the date. Some scopes, such as a custom web app with logins and payments, cannot be built and tested well in two weeks. A developer who says so is protecting your launch, not losing interest.
Whatever the choice, a rush only works if the client side is fast too: content ready on day one, feedback within a day, one approver. For the cost side of speed, see the cost pillar's section on why timeline changes the bill.
Redesign timelines vs a new build
A redesign is often not faster than a new build. It usually adds content migration, a map of old URLs to new ones, redirects and checks that search traffic survives the move. A small site with few URL changes adds little; a large site with changed URLs and a new platform adds real time.
In the calculator, migrating content from an old site adds one to two weeks to the planning estimate, and a redesign that keeps the content adds up to a week. Google's own guidance on site moves recommends preparing a URL mapping, testing the new site, setting up redirects, updating sitemaps and monitoring traffic afterwards, and notes that for medium-sized sites it can take a few weeks or more for Google to show the new URLs in place of the old ones (Google Search Central, site moves, last updated Aug 20, 2026).
To keep a redesign on schedule, list what is staying (domain, platform, content), what is changing, and how many existing pages need to move or redirect. That turns "redesign" into a scope someone can put dates on.
What to have ready before development starts
Have the offer, the list of pages, the copy or a named person writing it, brand assets, access to your domain and accounts, one person who can approve work, and a written definition of done. Arriving with these typically removes the most common waiting time from a website project.
Use this as a pre-build checklist:
- The offer and audience. Who the site is for, what you sell, and the one action you want visitors to take.
- The page list. Every page at launch, plus a "later" list that is agreed to be out of scope for now.
- Copy, or a plan for it. Written copy, or a named writer and a date. Starting design with the copy for the key pages in hand saves the most rework; the rest can follow on agreed dates.
- Brand assets. Logo files, colours, fonts, and real photos of you, your team, your work or your products.
- Logins and access. Domain registrar, DNS, current hosting or builder, email provider, analytics, and any payment, booking or CRM accounts.
- Integrations and data. Which tools the site must connect to, and the products, prices, locations or team details it must show.
- Legal pages. Privacy policy, terms, cookie notice and any industry-specific wording you need.
- One approver. The person who can say "approved", plus how quickly they can reply to feedback requests.
- A definition of done. What "launched" means: pages live, forms tested, analytics working, redirects in place.
Bring this list to the first call, along with what is already written, and you will usually get a firmer timeline than "it depends".
After launch: Google indexing is not instant
Launch day is not the day a new site appears in Google. Google says it can take a few weeks to notice a new site or changes to an existing one. Submitting a sitemap and verifying the site in Search Console helps discovery, but rankings for competitive searches take longer than indexing.
Google's get your website on Google page (last updated Dec 10, 2025) lists the usual reasons a new site is missing: it has only just launched, no other sites link to it, the content is hard to crawl, or a login or block stops Google from reaching it. Build the basics into the launch checklist: a sitemap, a Search Console property, crawlable text rather than text inside images, and no leftover "noindex" from the staging site.
After launch, the ongoing costs and chores start: hosting, renewals, updates and backups. The guide to what you pay after launch covers that side, and the guide to how much SEO costs covers what ongoing search work usually involves.
How to get a timeline you can hold someone to
Ask for a dated plan against a written scope, not a single number. A good timeline names each phase, the date the developer needs content, feedback or access from you, the number of feedback rounds, and what happens to the date if scope changes. Without those, any "four weeks" is a guess.
A useful timeline proposal usually includes:
- The page list and features it covers, and what it explicitly leaves out.
- Phase dates, with the client-owned steps marked.
- How many feedback rounds each phase includes and how fast you need to reply.
- What happens to the date if content arrives late or features are added.
- What is included after launch, and for how long.
To get a rough number first, run your scope through the website cost calculator, which shows a typical timeline alongside the cost estimate. Then send the page list and what is already written, and I'll reply with a timeline tied to a written scope, including which steps depend on you.
FAQ
How long does it take to build a website?
It depends on scope and on how ready the content and approvals are. A one-page site, a small business site, an online store and a custom web app run on different timelines, so ask for a timeline against a written scope rather than a single number.
How long does it take to build a website for a small business?
Published guides usually describe a few weeks for a standard multi-page business site, but the biggest variable is how quickly copy, photos and feedback arrive. Ready content and one decision-maker shorten the project more than any tool.
What slows a website project down?
Missing copy and images, slow or multi-person approvals, third-party integrations such as payments or bookings, and features added after design has started.
Does using AI or a website builder make it faster?
It can speed up a first draft or layout, but it does not write your offer, approve pages or set up integrations for you. Those steps still decide the launch date.
What should be ready before development starts?
The offer, the list of pages, the copy or a plan for who writes it, brand assets, access to domain and accounts, and one person who can approve work.
- #how long does it take to build a website
- #website development timeline
- #how long does it take to make a website
- #how much does a website cost
- #small business website design
- #web development


