How Long Does a Website Build Actually Take? The Honest Answer
“How long will it take to build a website?” It’s one of the fairest questions a client can ask, and one of the hardest to answer honestly, particularly on smaller projects.
Most of the uncertainty around timeframes is centered around the design stage, we want to build the right website for our clients, and this means a heavy involvement and giving the client time and flexibility to have ultimate sign off and input into the design stage, it is very hard, and to the clients detriment to put a hard deadline on this (unless the hard deadline is the most important element of the build to the client of course).
Where the Uncertainty Actually Sits
Design means figuring out what the site looks like: discovery calls with the client’s team, mood boards, wireframes, and eventually a Figma file for development. Our 11 years of experience shows us this depends on how much time a client wants to invest, how many rounds of feedback they want, and how many changes come back after each one.
Putting a firm number on that up front usually helps us more than it helps the client. A confident “six weeks” sounds reassuring in a pitch, but if it doesn’t hold once the client wants a third round of homepage revisions, the number was never honest to begin with. We’d rather say the true thing, that it depends on you, than hand over a date we can’t actually stand behind.
Why the Smaller the Site, the Harder the Question
Counterintuitively, it’s the smaller builds that are hardest to put a timeline on, not the larger ones. A big website, several integrations, a large sitemap, multiple stakeholder teams, tends to have a predictable-enough scope that three, four, or five months is a reasonable estimate from which we can build a GANTT chart with timelines for amends and a projected go live date. There’s more to build, but there’s also more structure around how it gets built.
A smaller site could take one to three weeks in development. What makes it unpredictable is everything before we hand it to our dev team: how much design input a client wants, how many iterations of the Figma file they need to see before they’re happy, how much time and energy they’re able to put into the process alongside their day job. Two clients with an identical brief and an identical budget can take very different amounts of time to reach a finished design, because the real variable is the decision-making around the build, not the build itself.
Why This Mirrors How We talk About Cost
This is the same honesty we try to bring to pricing a website. When we’ve written about what a construction or property website should cost, from a smaller bespoke build to a full enterprise platform, the number always tracks real complexity: integrations, page count, the systems a site needs to talk to. Timeline works the same way, except the variable that moves the number sits with the client’s own pace through discovery and design, rather than with scope on our side.
That’s worth knowing before a project starts, not after week four. If a client wants a firm date locked in from day one, the honest answer is that a website build doesn’t work that way for anything short of the largest, most tightly scoped projects. What we can commit to is a realistic range, and a clear sense of what’s actually driving the timeline once design begins.
Every build is different, and the honest answer to “how long will mine take?” depends on your goals, your content, and how quickly decisions get made along the way. If you’d like a realistic timeline for your specific project, tell us a bit about what you’re planning and we’ll walk you through it.