You've got a trade show in the spring, or a new location opening, or a slow-motion embarrassment every time someone asks for your website address. So you ask the obvious question: how long is this going to take?
The honest answer is "it depends," which is also the most irritating answer. So let's make it less vague. If you've been wondering how long does it take to build a website, the useful way to answer is phase by phase, with what happens in each stage, what tends to slow it down, and where you have more control than you think.
A note on numbers before we start. Timelines vary with the size of the site, the people involved and how fast information moves back and forth. Anything we say below is general industry experience, not a promise, and any firm date for your project should come from a conversation about your specific scope.
How long does it take to build a website? The short version
A small marketing website, built carefully, commonly lands in the range of a couple of months from kickoff to launch. A larger site with many pages, custom features or integrations takes longer, and a custom web application is a different category with a longer horizon. Rush jobs exist, but they usually trade away planning, testing or quality.
Here's the part that surprises owners: the design and development work is rarely what stretches a timeline. The waiting is. Waiting for text, photos, decisions, approvals, and the person who "just needs to look at it this weekend." If you remember one thing from this article, remember that the calendar is mostly shaped by how quickly information moves.
Phase 1: Discovery and planning
This is where a good project starts and a bad one skips ahead. In discovery, we figure out what the site is for, who it's for, what you offer, who your competitors are and what a visitor should do next.
The output is a plan: the pages you need, how they connect, what each one is supposed to accomplish and what the project includes. It's the cheapest stage to change your mind and the most expensive to skip.
What slows it down: unclear goals, a team that hasn't agreed on what the business actually wants, or a decision-maker who isn't in the room. If three people have three different ideas of what the site is for, the project will spend weeks finding out.
How to move faster: come with answers to three questions. What do you want visitors to do? What makes you different? What would make this site a success a year from now?
Phase 2: Content
Here's the phase most people forget to schedule, and it's the one that most often decides the launch date.
Content means the words, the photos, the logo files, the team bios, the service descriptions, the testimonials, the prices or the details of the offer. Every page needs it. A designer can build a beautiful frame, but a frame with placeholder text can't launch.
If you've never written a website before, the first draft takes longer than you expect, because it forces you to decide what you actually say about your business. Writing is thinking, and thinking takes time. The Nielsen Norman Group, which researches how people use websites, has long argued that clear writing is a big part of a usable site, and you can browse their findings at nngroup.com.
What slows it down: content that arrives piece by piece, in drafts, with revisions nobody tracks. Or no one writing it at all, with everyone assuming someone else is.
How to move faster:
- Decide who owns the content before the project starts.
- Gather photos and logo files early. Original photos of your real team and work almost always beat stock images.
- If writing isn't your thing, ask your web team about copywriting, so you're editing a draft instead of facing a blank page.
- Collect testimonials and case study details while you wait for other phases.
Phase 3: Design
Now the site starts to look like something. The designer builds the visual direction: layout, color, type, the look of buttons and forms, and how the pages work on a phone as well as a desktop.
Typically you'll see the homepage first, then the inner pages. You give feedback, the designer revises and the cycle repeats until you're happy.
What slows it down: feedback that's vague ("make it pop"), feedback from many people that conflicts, and big changes of direction late in the process. A new logo halfway through design is the classic example.
How to move faster: pick one person to consolidate feedback into a single round. Say what you want to change and why ("the headline doesn't mention we serve commercial clients") rather than only how it feels. And look at the design on your phone, because most visitors will.
If you want to understand what good design looks like before you start, our article on website design best practices is a helpful companion.
Phase 4: Development
This is where the approved design becomes a working website. Pages get built, the content goes in, forms are connected, and the site is made responsive, fast and ready for search engines.
If you're having us build the site, this is the phase where the calendar feels the calmest. The decisions have been made, and the team is working. It's also where a custom build takes longer than a template, since more is being created for you rather than adapted.
What slows it down: scope that grows ("while you're in there, can we also add...") and new features that weren't in the plan. Each addition is reasonable alone, but together they move the date.
How to move faster: keep a running list of nice-to-have ideas for after launch. A site that launches and then improves beats a site that waits for everything. If you're curious what the work involves, see our web design service.
Phase 5: Review and revisions
Before the site goes live, you test it. Click every link. Fill in every form. Read every page out loud. Check it on your phone and on a friend's older computer. This is also when your team sees the real thing, often for the first time, and has opinions.
What slows it down: feedback trickling in over weeks, and "one more thing" arriving after a round is closed. This phase can quietly double in length if no one owns it.
How to move faster: set a review window, such as one week, and gather everyone's comments into one document. Give clear priorities: what must be fixed before launch, and what can wait.
Phase 6: Launch
Launch day is often smaller than you'd imagine, and that's a good thing. By now, the site has been tested, the redirects are planned if you're replacing an old site, and the domain, hosting and tracking are set up.
If you're replacing an existing website, the redirects matter. They make sure old addresses send visitors and search engines to the right new pages, so you don't lose the rankings you've earned. Google Search Central explains how this works in its documentation for site moves.
After launch, expect a short period of small fixes. Real visitors always find something your testing didn't. A good team stays close for those first weeks.
What really decides your timeline
You can't control everything, but here are the things that move the date most:
- Speed of content. The biggest factor, by a lot.
- Speed of decisions. One decision-maker beats a committee.
- Scope. More pages, more features and more integrations take more time.
- Custom vs. template. Custom takes longer and fits better.
- Third parties. Waiting for a logo, a domain transfer or a vendor's information adds days you can't see coming.
A project that's well planned and well fed with content can move briskly. A project that stalls on the same questions for weeks will feel slow, no matter who builds it.
If cost is the other thing on your mind, our Price Guide explains what drives it, and the two questions are connected: the more you decide early, the faster and cheaper the project tends to go.
Plan backward from the date you need
If you have a hard deadline, start from it and work backward. Allow for content, because it's the phase that slips. Build in time for reviews. Then talk to your web team early, before you've picked a date in your head.
The best way to speed up a website is not to push the designer harder. It's to show up ready: your content gathered, your decisions made, your feedback in one place. That's the part you control, and it's the part that decides whether the answer to "how long does it take to build a website?" is a few weeks or a few months.