How long does a website project take?
A custom small business site takes 3 to 6 weeks, a template setup 1 to 2. Here is the week-by-week timeline, what makes projects run long, and how to keep yours on schedule.
A custom small business website takes 3 to 6 weeks from kickoff to launch. A template setup takes 1 to 2 weeks. Those timelines hold when things go well. Here is what "going well" requires, and what makes projects run long.
This is part of my complete guide to hiring a web designer.
The week-by-week timeline for a custom build
Week 1: strategy and content gathering. We have a kickoff call. I learn about your business, your customers, and what the site needs to accomplish. We agree on the sitemap (which pages, in what order). You start gathering your content using a guide I provide: text for each page, photos, logos, and logins.
Week 2: homepage design. I design the homepage first because it sets the visual direction for everything else. You review it, we discuss what's working and what isn't, and I revise. This is the most important feedback round of the entire project, so take your time with it.
Weeks 3 and 4: remaining pages and functionality. Once the homepage direction is approved, the rest of the site comes together faster because the design language is established. I build out every page, connect your forms, set up scheduling or email signup integrations, and handle mobile responsiveness.
Week 5: review, SEO, and polish. You review the full site. We handle revisions, I set up page titles and descriptions for search engines, configure analytics, check every page on mobile, and test all forms and integrations.
Week 6: training and launch. I walk you through how to update text, swap images, and manage your blog. We pick a launch day, flip the switch, and I monitor for issues. Your post-launch support window starts here.
The template setup timeline
Template projects move faster because the design phase is compressed:
- Days 1 to 3: Kickoff call, template selection, branding setup (colors, fonts, logo placement).
- Days 4 to 7: Pages built with your content, forms and integrations connected.
- Days 8 to 10: Your review, revisions, SEO basics, mobile check.
- Days 11 to 14: Training, launch.
Two weeks is realistic if your content is ready. If it isn't, add however long it takes you to provide it, because that's the actual variable.
Why projects run long (and it's almost never the designer)
I want to be direct about this because it will save you real frustration: the number one cause of website project delays is client content arriving late.
Not bad content. Late content. The design is ready, the pages are built, and the project sits waiting for three paragraphs of bio text, or the team photo that was supposed to happen last week, or the decision about which services to list that requires a partner conversation nobody has scheduled yet.
This is not a complaint. Running a business is genuinely hard, and writing about yourself is one of the most difficult tasks there is. But it's worth knowing upfront: the timeline is not set by the designer's speed. It's set by how quickly you can provide what the project needs.
Other things that add time
Beyond content delays, a few legitimate factors extend timelines:
- More pages naturally take longer. A 12-page site needs more weeks than a 5-page site.
- E-commerce setup adds a week or more depending on product count and payment configuration.
- Custom code or complex integrations (a booking system, a client portal, an automated workflow) require testing and often a revision cycle of their own.
- Multiple decision-makers. If every design choice needs approval from a business partner, a board, or a committee, build in extra time. The fastest projects have one decision-maker.
- Scope changes mid-project. "Can we also add a shop?" in week 3 is fine to ask, but it resets the timeline. A good designer will tell you that clearly rather than quietly absorbing it.
How to keep your project on schedule
The whole list is short:
- Gather your content before the project starts. Not during. Before. If you hire me, I send the content guide the day you book so you have a head start.
- Set aside review time. When your designer sends something for feedback, respond within 2 to 3 business days. A one-week silence in the middle of a project is the most common timeline killer after late content.
- Appoint one decision-maker. Gather opinions if you want, but one person gives final approval.
- Resist the urge to add scope mid-build. Write it down for phase two instead. The best version-two projects come from watching how real visitors use version one.
The biggest thing you can do for your timeline: prepare your content before kickoff. And for what each tier costs, see Squarespace designer pricing.
Frequently asked questions
Can a website be built in one week?
A template setup, yes. A custom build, generally no, not if it includes strategy, proper design, SEO, and testing. "Rush" custom builds that compress everything into a few days tend to skip the parts that make a site actually perform.
What if I don't have my content ready yet?
Be honest about that upfront. A good designer can either help you shape rough drafts or recommend a copywriter. What you want to avoid is booking a project with a start date and then spending weeks figuring out what to say, because the designer's calendar doesn't pause with yours.
How many revision rounds should I expect?
Two to three rounds is standard for custom builds: one on the homepage concept, one on the full site, and one final pass. Unlimited revisions sounds generous in a proposal, but in practice it often means the project never ends. Defined rounds keep everyone focused.