Skip to main content
Guides

How Many Hours Does It Take to Design a Website? By Site Size

Karan Singh BhakuniUpdated
  • 22 min read
  • 12 sections
  • 7 comparison tables
  • 13 questions answered

The short answer

Designing a website takes about 10 to 25 hours for one to five pages and about 24 to 60 hours for ten, depending on how many page layouts are unique. Designing, building and testing a 10-page custom site, from discovery to QA, takes about 80 to 100 hours. Those ranges come from a freelance designer’s published table (Tom Caklos, January 2025) and Sage Agency’s breakdown (January 2025); Intelivita (July 2026) puts a site of static pages at 40 to 100 hours, and in Sitejet’s 2019 survey, 60% of designers put a whole site at 11 to 40 hours. Hostinger says its AI builder can often take a single-page site from prompt to published in under an hour; checking the copy, testing the form and the launch checks come on top of that. Below: hours by site size and build route, a worked 30-hour budget, and how to turn hours into dates and cost.

Want the site rather than the reading? Try Grigora free for 14 days

Contents12 sections
Illustrated website-design cover with a fictional designer, laptop and hourglass; not a measured project result

Read nextHow Long Does a Website Redesign Take? Timelines by Scope (2026)

Website design hours by site size

Published estimates vary because they measure different scopes, so the table separates design-only work from design and build. They are agency, freelancer and survey estimates, not measured project data.

ScopePublished hoursSource and what it covers
Custom homepage, design only6 to 8Sage Agency, 2025
Landing page, design onlyAbout 10Tom Caklos, 2025
5-page site, design only25Tom Caklos, 2025
10-page custom site, design only24 to 33 (about 30)Sage Agency, 2025: includes mobile versions and file export
10-page site, design only40 to 60Tom Caklos, 2025: about 4 to 6 hours a page
Whole site from scratch, design and build11 to 40 for 60% of designersSitejet survey, July 2019
Landing page, design and build20 to 40Intelivita, 2026: layout, content placement and QA
Site with static pages, build40 to 100Intelivita, 2026: it calls these development hours; accounts or search push it into the hundreds
10-page custom site, discovery to QA80 to 100Sage Agency, 2025: discovery, design, development and QA
Website design hours by site size: published estimates from 6 to 8 hours for a homepage to 80 to 100 hours for a 10-page custom build
Published hour estimates from two agencies, a freelance designer and a 2019 survey.

The best-known survey data is old. Sitejet published it as Web Design Statistics 2020, from a July 2019 survey of 384 respondents, a mix of web designers and consumers. About one in five designers said they can build a site from scratch in 10 hours or less, 60% said 11 to 40 hours and nearly a quarter said 41 hours or more (shares rounded). It predates common AI site generators, so read it as a spread of answers, not a current benchmark.

Design hours by number of pages

The two 10-page estimates, 24 to 33 hours and 40 to 60, come from different designers and neither explains the gap; the per-page arithmetic points to how much each later page reuses the homepage. In Sage’s estimate, the homepage takes 6 to 8 hours and the other nine pages about 1 to 2 hours each (10 to 15 combined). Caklos’s table works out to about 4 to 6 hours a page, and he says four extra unique sections across 10 pages can add 20 to 30 hours. If you only need one page, a landing page can be your only page online, and his table puts its design at about 10 hours.

PagesSage Agency rates, 2025 (about 1 to 2 hours per extra page; 5-page row is our arithmetic)Tom Caklos, 2025 (about 4 to 6 hours a page)
1 page6 to 8 hours (custom homepage)About 10 hours (landing page)
5 pagesAbout 10 to 16 hours before mobile versions (6 to 8, plus four pages at 1 to 2)25 hours
10 pages24 to 33 hours, including mobile versions40 to 60 hours
20 pagesNot published80 to 100 hours
50 pagesNot published200 to 300 hours

So count unique templates, not pages: ten posts sharing one article layout take far less design time than ten custom service pages. Page count can mislead in the other direction too: Caklos says one simple healthcare onboarding page took him and UX colleagues “well over 140 hours”, an exception he mentions alongside clients who need extra UX work such as user surveys or research. Turning the designs into mobile versions and exporting the files adds 8 to 10 hours in Sage’s estimate. A short checkout can take more design work than a long informational page, because payment, failure, confirmation and fulfillment states each need a design. Mobile layout, keyboard use and readable content are part of the design, not automatic results of choosing a theme.

Where the hours go: design is about a third of a custom build

Sage Agency's breakdown shows how design fits into a whole 10-page custom build: about 4 hours of discovery (3 to 5), about 30 hours of design, 40 to 60 hours of development and 5 to 8 hours of QA, or 80 to 100 hours in total. Design is 30 to 38% of that total, about a third. So when you see a figure for “hours to design a website”, check whether it means approved design files or a working, tested site, because the second is roughly three times the first.

Website design hours in a 10-page custom build: about 4 discovery, 30 design, 40 to 60 development and 5 to 8 QA hours, per Sage
One agency's published breakdown for a 10-page custom site.

Define what “design a website” includes

One person may mean a set of approved page mockups; another may mean a complete site with content, forms and a connected domain. Those are different deliverables. Write the scope before comparing hour totals, and avoid adding the same revision, testing or handoff work twice under different headings.

ScopePossible deliverableWhat to clarify
Design onlySitemap, wireframes, visual styles, responsive layouts and agreed interaction states.Does it include research, copy, assets, clickable prototypes, revisions and developer handoff?
Design and buildApproved design implemented in the chosen platform with real content.Which pages/templates, forms, integrations, states and responsive behavior are included?
Ready for launchBuilt site checked against the agreed scope, with publishing/domain tasks and handover.Who tests, approves, supplies accounts, handles redirects and owns maintenance afterward?

Gather the inputs before assigning hours

  • Purpose and audience: the main user tasks and what a completed site must allow visitors to do.
  • Inventory: pages, reusable layouts, languages, products/posts, downloads and any old URLs to preserve or redirect.
  • Content: who provides and approves final copy, contact details, prices, product data, branding and media.
  • Features: forms, booking, checkout, accounts, search, integrations and the exact third-party services involved.
  • Review: one accountable decision maker, feedback rounds, acceptance criteria and response dates.
  • Technical work: platform/account access, domain/DNS, migration, testing coverage, launch and handover responsibilities.

List the pages before you estimate. The free website page planner suggests the pages to launch with, the sections on each and a sitemap from a short description of the business, which you can then sort into unique layouts and reused ones. For the wider decisions to settle before a build, such as purpose, budget and platform, see what to consider when building a website.

Include sourcing images, licenses, cropping and compression, and accurate captions or alternatives when they are part of the work. “The client will provide images” needs an owner and a due date. If the copy or product information is unfinished, estimate its creation and review separately instead of hiding it in a vague design allowance: rewriting website copy is a task with its own hours and its own approval.

Investigate unknown integrations or a representative difficult page before promising a fixed total. Record what was actually tested and what remains unverified. A working mockup does not demonstrate that a payment provider approves the business, a form reaches the intended inbox or a migration preserves every URL. Those checks need their own tasks.

Build a task budget: a worked 30-hour example

Assume a four-page informational site built from a suitable existing template: Home, About, Service and Contact. Final copy, branding and permitted images are supplied; there is one simple contact form, one decision maker and one bounded feedback round. There is no store, account area, multilingual version, migration or custom integration. The hours are worked planning figures for these assumptions, not a measured project.

TaskIllustrative hoursDefinition of done
Scope, page map and acceptance checklist3Pages, user tasks, exclusions and approval owner are agreed.
Prepare supplied content/assets3Final material is organized and ready for the approved layouts.
Visual and responsive layout design5Representative page layouts and key states are approved.
Build pages and contact workflow8Approved layouts contain real content; intended form flow is implemented.
One agreed revision round3Consolidated in-scope feedback is resolved and recorded.
Accessibility/usability/browser checks and fixes6Agreed user paths and test coverage are checked; material issues are fixed.
Publish and hand over2Live URL is verified and access/maintenance responsibilities are documented.
Base hands-on total303 + 3 + 5 + 8 + 3 + 6 + 2 = 30 hours.

Design is only 5 of the 30 hours because the template supplies the layout system; a fully custom design would look more like Sage’s 30 design hours on their own. Replace every value with your own estimate, and include anyone else who writes copy, designs assets or reviews the site. The example has no contingency, new feature or extra review round. For uncertain tasks, record a low and a high estimate, then compare them with the hours actually spent so the next estimate is better.

How the build route changes the hours

The same scope takes very different time on an AI builder, a website builder, WordPress or hand-written code. Hostinger’s estimates (last updated July 2023) compare the routes as elapsed time; its website builder figures and its single-page WordPress figure assume the content is prepared first. It says its AI builder can often finish a single-page site in under an hour: 5 to 15 minutes to generate a first version, 15 to 45 refining it by prompt and 5 to 10 reviewing and publishing. The hours column is Network Solutions’ own estimates (published July 2026, updated September 2026), which it labels best estimates and gives no source for; its 60 to 200 or more hours for a custom-designed site is consistent with Sage’s 80 to 100 hours for 10 pages. Both companies sell website builders, so read the table as a rough comparison. Quick AI figures like these time a generated draft from prompt to publish, not a checked site.

RouteHands-on hours, whole site (Network Solutions, 2026)Single-page site, elapsed (Hostinger, 2023)Small online store, elapsed (Hostinger, 2023)
AI builder10 minutes to 2 hoursUnder an hour, prompt to publish (vendor’s claim)Not estimated
Website builder10 to 20 hours4 hours to 3 days1 to 7 days
WordPress20 to 40+ hours (with a template)2 to 8 days5 days to 5 weeks
Custom code60 to 200+ hours (custom-designed site)8 to 21 days11 to 36 days
Website build time by route for a single-page site: AI builder under 1 hour, website builder 4 hours to 3 days, WordPress 2 to 8 days, custom code 8 to 21 days (Hostinger)
Elapsed time by build route from one vendor’s estimates; your scope sets your number.

Online stores take longer on every route. Intelivita (July 2026) puts a small store of 10 to 50 products on a platform such as Shopify at 3 to 6 weeks, and a custom e-commerce site with its own payment gateways at 8 to 20 weeks. Compared with the 30-hour example above, a store adds rows for product data and photos, payment setup, shipping and tax rules, and test orders, including a test refund.

A website builder or AI builder mainly shortens the layout design and page-building rows of the 30-hour example (13 of its 30 hours), depending on how closely the generated pages fit your content. Scope, content, the revision round, testing and launch stay with you on any route. A generated draft still needs its copy checked, a real test submission of the form and the launch checks, as this step-by-step AI website builder tutorial shows. A platform that lacks a feature you need can add integration or migration work later.

Grigora is one such builder, and it fits sites that follow a common small-business pattern: home, about, services, contact and a blog. It drafts the pages, copy and images from a description of your business, and you change them by prompt in the AI Editor (there is no drag and drop on AI-built sites). Paid plans include hosting, SSL, a CDN and connection of a domain you already own, from $15 a month or $144 a year for one website on Starter (prices checked November 2026; see current pricing). For a redesign, Settings > Migration imports posts, pages, categories, tags and authors from WordPress, Webflow, Wix, Duda, Ghost and Blogger, and the AI builder can draft a new site from your existing site’s address. It is the wrong tool if you are handing design files to a developer, and it has no booking calendar, member logins or subscription billing. Scope, content approval, testing and launch still take your time. The 14-day free trial needs no card and covers the first site plus about five AI edits, so you can time your own pages before you commit.

Convert work hours into a realistic schedule

Effort is time spent doing the work. Duration is the time from start to finish, including availability, dependencies and waiting. A 30-hour project does not necessarily fit into three full workdays: the responsible person may have only three focused hours available each day, and feedback may arrive later. The published calendar estimates below come from Intelivita (July 2026), Ramotion (updated November 2026), Wix’s stage-by-stage timeline (April 2026), Network Solutions (updated September 2026) and Tom Caklos (January 2025). They are agencies, platform vendors and a freelance designer, so treat the ranges as typical, not promised.

Site or stagePublished calendar timeSource
Landing page1 to 2 weeksIntelivita, 2026 (copy and visuals ready)
Small business site4 to 8 weeks, or 4 to 6 weeksIntelivita, 2026; Ramotion, 2026
Small online store (10 to 50 products, on a platform)3 to 6 weeksIntelivita, 2026
Custom e-commerce site8 to 20 weeksIntelivita, 2026
Planning stage1 to 4 weeksIntelivita, 2026
Design stage alone2 to 4 weeks, or 3 to 6 weeksIntelivita, 2026; Ramotion, 2026
Design of a simple 5-page site2 to 4 weeks; larger sites 4 to 16 weeksTom Caklos, 2025
Content creation2 to 10 days, or 1 to 2 weeks on a DIY builderNetwork Solutions, 2026; Wix, 2026
Development stage5 to 30+ days; for custom work, front end 3 to 8 weeks and back end 4 to 8 weeksNetwork Solutions, 2026; Intelivita, 2026
Testing, review and launch1 to 3 days, or 1 to 2 weeks of reviewNetwork Solutions, 2026; Wix, 2026
Hiring a professional, start to finish2 to 5 months, including 1 to 4 weeks to find a developer and 1 to 3 weeks to brief themWix, 2026
Hypothetical schedule inputArithmetic
Hands-on work30 hours
One person’s available project time3 focused hours per working day
Work duration if tasks run in sequence30 ÷ 3 = 10 working days
Additional non-overlapping approval wait2 working days
Illustrative elapsed working time10 + 2 = 12 working days, before any other delay.

This is a simplified scheduling example, not a prediction. At 6 focused hours a day, the same 30 hours take 5 working days, or 7 with the approval wait, so daily availability moves the date as much as the hours do. Weekends, holidays and actual start dates affect the calendar. Some tasks can overlap, while others depend on an approved layout, supplied content or an external account. Two people do not automatically finish in half the time when tasks depend on each other or require coordination.

Website design hours to calendar days: 30 hours at 3 hours a day plus 2 approval days is 12 working days; at 6 hours a day it is 7
Illustrative arithmetic for one person working in sequence; your availability and approval waits will differ.

Also worth readingWhat to Consider When Building a Website: 25-Point Checklist

Turn design hours into a budget

Multiply the hours by a rate to get a budget. The latest Bureau of Labor Statistics figure as of November 2026 puts the US median pay for web developers and digital designers at $47.85 an hour (May 2025), so the 30-hour example is about $1,436 of salaried time and Sage’s 80 to 100 hour custom build about $3,828 to $4,785. A $1,500 budget buys about 31 hours at that wage: enough for the 30-hour template example, but about a third of a 10-page custom build. A freelance or agency rate is a price, not a wage: it also covers overhead, unbilled time and tools. Sage says a designer or developer with over 10 years of experience may charge $150 an hour or more, which would make $1,500 about 10 hours. To compare an agency, a freelancer and doing it yourself from the same scope, use the free website cost calculator. If you plan to hire, this checklist for hiring someone to set up a blog covers what to agree before work starts.

How to cut design hours

  • Finish copy and photos before layout work starts. Intelivita’s landing-page estimate assumes they are ready, and Network Solutions lists content readiness as a factor in build time.
  • Start from a template or an AI draft close to the brief. In the worked example, a template keeps design to 5 of the 30 hours; Sage’s custom 10-page design takes about 30.
  • Limit unique layouts and sections. Four extra unique sections across 10 pages can add 20 to 30 design hours (Caklos).
  • Name one decision maker and fix the number of revision rounds. Caklos includes two rounds on the first mockup; each extra round costs hours.
  • Test during the build, not only at the end. MDN’s cross-browser testing guide, linked in the checks section below, recommends it.
  • Launch the must-have features first. A booking flow or checkout brings its own states and tests, so adding it after launch protects the first launch date.

Control revisions without skipping important work

Agree what reviewers are approving at each stage, using enough real content to expose real problems. Collect feedback in one place, let the decision maker settle conflicting requests, and separate a fix to agreed work from a new deliverable. For each new request:

  1. Record the change and the pages it touches.
  2. State the hours it adds and the new launch date.
  3. Agree it before work on it starts.

Reserve time for checks, launch and handover

Plan quality work throughout the project. W3C accessibility planning guidance covers assigning responsibilities and building accessibility into the project, and W3C’s Easy Checks give a quick first review of page titles, image text alternatives, headings, contrast and keyboard access. The free accessibility checker runs an automated scan of a live page as a first pass, but no scan, quick check or attractive template proves that every visitor can complete the intended task. For a US state or local government site, budget testing against WCAG 2.1 Level AA: the ADA Title II web rule requires it by April 26, 2027 for governments serving 50,000 or more people and by April 26, 2028 for smaller ones and special districts (dates as of November 2026, after an April 2026 extension).

Agree coverage across different web browsers, devices and relevant user needs. MDN’s cross-browser testing guide explains why testing should happen during development and why the supported range should be defined. The free mobile preview simulator gives a quick look at phone and tablet widths, but still test on a real phone before launch. Record actual coverage and limitations instead of promising that an untested site works everywhere.

  • Check key pages and user paths on the agreed phone/desktop/browser range, including keyboard access and useful image alternatives.
  • Test form validation, submission, error/success behavior and actual intended delivery with appropriate controlled data.
  • Verify links, titles, public visibility, domain/HTTPS and any scoped redirects; preserve a recovery route for launch.
  • Confirm who approves the live version, receives account access and maintains content, renewals and integrations.
  • Document unresolved issues and accepted exclusions honestly, then recheck the final public URLs after publishing.

To work through these before going live, use the free website launch checklist, which groups content, design, SEO, performance, security, legal and launch tasks into a list you can tick off. For the visual pass, these checks that make a website look professional cover the details visitors notice first.

If you are delivering design files rather than building the site, define the handoff: layouts, assets, states, breakpoints, behavior notes and a developer question/review allowance. Do not include an unexplained “launch” block in a design-only estimate when someone else will implement and publish the work. After release, keep maintenance and future improvements separate from the agreed project total.

Website design hours: FAQs

Get the next guide by email

Practical writing on building a site, growing an audience and sending email people open. No more than one a week.

Karan Singh Bhakuni

120 articles on the Grigora blog

More on Guides