How long does it take to build a custom website?
Custom web development services and pricing
What actually consumes the time
Page count is a small factor compared to content readiness, the number of review rounds, and how many third-party integrations are involved. A ten-page site with all content ready and one review round can move faster than a five-page site where copy and images arrive late and every section gets revised twice.
A realistic week-by-week shape
Discovery and scoping usually take a few days to a week and end with a fixed quote and timeline. Design follows, with a structured review round built in. The build takes the largest share of the time and depends on custom features and integrations. QA and launch come last, to test forms, payments, speed and SEO on real devices before the site goes live. A small business website with ready content sits at the short end of the range; a web app with several integrations sits at the long end.
What slows a timeline down
Late or incomplete content is the single biggest delay. Scope changes mid-build are the second. Third-party API or integration partners with slow response times are the third. None of these are avoidable entirely, but naming them upfront in a scoping call keeps a project closer to its original estimate.
How long does each type of project take?
A single landing page with ready copy is the fastest project, often a matter of days rather than weeks. A small business website of five to ten pages usually takes a few weeks. An e-commerce store adds product setup, payments, shipping rules and testing of the checkout, which extends the schedule. Web apps and mobile apps take longest, because user accounts, data models, integrations and app store review all add work that a marketing site does not have. The scoping call is where the honest estimate for a specific project gets made.
What you can do to launch sooner
Prepare the content first: final copy for each page, a logo in vector format, brand colours and fonts, and photos at full resolution. Decide who approves the work, so feedback arrives from one person in one round instead of several conflicting messages. List every integration up front, such as the CRM, booking system or payment provider, and get access credentials ready early. Finally, separate must-have launch features from nice-to-haves. Launching a focused first version and adding the rest afterwards is almost always faster than waiting for everything at once.
What happens after launch?
Launch is the start of the site's working life, not the end of the project. The first weeks are for watching real behaviour: analytics, form submissions, Search Console coverage and Core Web Vitals field data. Small fixes and copy tweaks are normal once real visitors arrive. Search engines also need time to recrawl and reindex the new pages, so rankings usually settle over the following weeks rather than on launch day. Planning a short post-launch review into the timeline keeps these improvements from being forgotten.
How long does a website redesign take compared with a new build?
A redesign is not always faster than a new build. The design and development work is similar, and a redesign adds two jobs: reviewing and moving existing content, and protecting search rankings with redirects from every old URL that changes. If the existing content is good and the page structure stays similar, a redesign can move quickly. If the content needs rewriting or the site structure changes, plan for the same timeline as a new build plus a short migration phase before launch.
How to keep a website project on schedule
Agree the scope, page list and number of review rounds in writing before work starts. Share content in one organised batch rather than piece by piece, and nominate one person to give consolidated feedback. Treat new ideas that arrive mid-build as a second phase rather than adding them to the current one. Ask for progress you can see, such as a staging link, at regular points, so problems surface early instead of at launch. These habits matter more to the final date than the size of the site.
| Phase | What happens | What it depends on |
|---|---|---|
| Discovery | Goals, scope, fixed quote, timeline | How clear the requirements are |
| Design | Layouts and visual direction, review round | Number of unique page layouts and feedback speed |
| Build | Development, integrations, content entry | Custom features and third-party APIs |
| QA and launch | Device testing, speed, SEO, go-live | Number of forms, payments and integrations to test |
Common mistakes
- Agreeing a launch date before content is ready
- Treating every design revision request as a small change with no timeline impact
- Not accounting for third-party integration partners' own response times
Frequently asked questions
Can a website be built in under two weeks?
For a very simple, template-based site with content ready on day one, yes. For a custom build, two weeks is rarely realistic once design and review rounds are included.
Does more pages always mean more time?
Not proportionally. Ten similar pages built from one template structure add far less time than two pages with unique, complex layouts.
What's the fastest way to speed up a timeline?
Have final content and brand assets ready before the build starts, and agree on the number of review rounds upfront.
Is a website redesign faster than building a new site?
Not always. A redesign also needs content migration and redirects to protect rankings, so it often takes about as long as a new build.
How long does a website last before it needs a redesign?
There is no fixed lifespan. A site needs a redesign when it stops meeting business goals, for example because it is slow, hard to use on a phone or limits what you can do. Regular small updates delay the need.
Related work
Relevant service
Related reading
Want this done properly?
Tell me what you are building. I reply within a business day.
Start a project