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.
| Scope | Published hours | Source and what it covers |
|---|---|---|
| Custom homepage, design only | 6 to 8 | Sage Agency, 2025 |
| Landing page, design only | About 10 | Tom Caklos, 2025 |
| 5-page site, design only | 25 | Tom Caklos, 2025 |
| 10-page custom site, design only | 24 to 33 (about 30) | Sage Agency, 2025: includes mobile versions and file export |
| 10-page site, design only | 40 to 60 | Tom Caklos, 2025: about 4 to 6 hours a page |
| Whole site from scratch, design and build | 11 to 40 for 60% of designers | Sitejet survey, July 2019 |
| Landing page, design and build | 20 to 40 | Intelivita, 2026: layout, content placement and QA |
| Site with static pages, build | 40 to 100 | Intelivita, 2026: it calls these development hours; accounts or search push it into the hundreds |
| 10-page custom site, discovery to QA | 80 to 100 | Sage Agency, 2025: discovery, design, development and QA |

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.
| Pages | Sage 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 page | 6 to 8 hours (custom homepage) | About 10 hours (landing page) |
| 5 pages | About 10 to 16 hours before mobile versions (6 to 8, plus four pages at 1 to 2) | 25 hours |
| 10 pages | 24 to 33 hours, including mobile versions | 40 to 60 hours |
| 20 pages | Not published | 80 to 100 hours |
| 50 pages | Not published | 200 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.

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.
| Scope | Possible deliverable | What to clarify |
|---|---|---|
| Design only | Sitemap, wireframes, visual styles, responsive layouts and agreed interaction states. | Does it include research, copy, assets, clickable prototypes, revisions and developer handoff? |
| Design and build | Approved design implemented in the chosen platform with real content. | Which pages/templates, forms, integrations, states and responsive behavior are included? |
| Ready for launch | Built 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.
| Task | Illustrative hours | Definition of done |
|---|---|---|
| Scope, page map and acceptance checklist | 3 | Pages, user tasks, exclusions and approval owner are agreed. |
| Prepare supplied content/assets | 3 | Final material is organized and ready for the approved layouts. |
| Visual and responsive layout design | 5 | Representative page layouts and key states are approved. |
| Build pages and contact workflow | 8 | Approved layouts contain real content; intended form flow is implemented. |
| One agreed revision round | 3 | Consolidated in-scope feedback is resolved and recorded. |
| Accessibility/usability/browser checks and fixes | 6 | Agreed user paths and test coverage are checked; material issues are fixed. |
| Publish and hand over | 2 | Live URL is verified and access/maintenance responsibilities are documented. |
| Base hands-on total | 30 | 3 + 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.
| Route | Hands-on hours, whole site (Network Solutions, 2026) | Single-page site, elapsed (Hostinger, 2023) | Small online store, elapsed (Hostinger, 2023) |
|---|---|---|---|
| AI builder | 10 minutes to 2 hours | Under an hour, prompt to publish (vendor’s claim) | Not estimated |
| Website builder | 10 to 20 hours | 4 hours to 3 days | 1 to 7 days |
| WordPress | 20 to 40+ hours (with a template) | 2 to 8 days | 5 days to 5 weeks |
| Custom code | 60 to 200+ hours (custom-designed site) | 8 to 21 days | 11 to 36 days |

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 stage | Published calendar time | Source |
|---|---|---|
| Landing page | 1 to 2 weeks | Intelivita, 2026 (copy and visuals ready) |
| Small business site | 4 to 8 weeks, or 4 to 6 weeks | Intelivita, 2026; Ramotion, 2026 |
| Small online store (10 to 50 products, on a platform) | 3 to 6 weeks | Intelivita, 2026 |
| Custom e-commerce site | 8 to 20 weeks | Intelivita, 2026 |
| Planning stage | 1 to 4 weeks | Intelivita, 2026 |
| Design stage alone | 2 to 4 weeks, or 3 to 6 weeks | Intelivita, 2026; Ramotion, 2026 |
| Design of a simple 5-page site | 2 to 4 weeks; larger sites 4 to 16 weeks | Tom Caklos, 2025 |
| Content creation | 2 to 10 days, or 1 to 2 weeks on a DIY builder | Network Solutions, 2026; Wix, 2026 |
| Development stage | 5 to 30+ days; for custom work, front end 3 to 8 weeks and back end 4 to 8 weeks | Network Solutions, 2026; Intelivita, 2026 |
| Testing, review and launch | 1 to 3 days, or 1 to 2 weeks of review | Network Solutions, 2026; Wix, 2026 |
| Hiring a professional, start to finish | 2 to 5 months, including 1 to 4 weeks to find a developer and 1 to 3 weeks to brief them | Wix, 2026 |
| Hypothetical schedule input | Arithmetic |
|---|---|
| Hands-on work | 30 hours |
| One person’s available project time | 3 focused hours per working day |
| Work duration if tasks run in sequence | 30 ÷ 3 = 10 working days |
| Additional non-overlapping approval wait | 2 working days |
| Illustrative elapsed working time | 10 + 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.





