How long should a new website take?

“How long will it take?” is one of the first questions people ask, and the answers they get range from a fortnight to six months. That’s not because some agencies are ten times slower — it’s because “a website” can mean very different projects, and because most of the timeline is decided by things on your side, not theirs. Here’s how to think about it, and how to get yours live sooner.

Why the range is so wide

A traditional agency build often runs several weeks to a few months. A lot of that time isn’t design or code — it’s waiting: for content, for photos, for feedback, for the next slot in a queue. The actual making of a focused site is quick; the calendar fills up around it.

At Tireless we typically go from start to live in 7–10 days, because we’re an AI-operated studio with proven components and a person accountable to you at every step. But even we can’t outrun a project that’s waiting on content — which is the honest heart of the matter.

What makes a website faster

• A defined scope. Knowing exactly which pages you need before you start removes the single biggest source of drift.
• Content that’s ready. Your treatments, fees, opening hours and any photos, gathered up front, keep the build moving instead of stalling.
• One decision-maker. When one person can approve, you skip the days lost to rounding up opinions.
• Focused revisions. A couple of clear, batched rounds of changes are quick; open-ended “can we just try…” loops are where weeks disappear.

What makes it slower

• Undefined scope that grows as you go.
• Waiting on content and photography — the most common cause of delay by far.
• Many stakeholders who all need to weigh in.
• Endless revision rounds with no agreed stopping point.
• Genuinely custom features — bespoke booking flows or integrations take real time, and that’s fine, as long as you know it up front.

The fastest thing you can do for your own timeline is have your content ready and one person able to say yes.

Does “faster” mean rushed?

It’s a fair worry — plenty of “cheap and quick” sites look it. The distinction is between rushed and efficient. A rushed build skips the testing, the mobile checks, and the proofreading. An efficient one is quick because the wasteful parts are removed: no weeks in a queue, no waiting on a design team’s availability, no ten-email threads to approve a headline.

A short timeline should never shorten the checks. Every page should still be tested on a phone, the copy still proofread, and — if there’s an assistant — it should still pass its safety testing before it speaks to a customer. If an agency’s speed comes from skipping those steps, that’s the wrong kind of fast. If it comes from a focused process and proven components, days-not-months is simply less waste, not less care.

A realistic 7–10 day timeline

For a focused site, here’s roughly how the days fall at Tireless. Yours will vary with scope, but the shape holds:

Getting a date you can rely on

However long it takes, the number that matters is the one you can plan around. Ask any agency for a go-live date in writing and what happens if it slips. At Tireless we agree that date up front and back it with a delivery guarantee: if we miss it, you don’t pay for the delay — you only pay once your site is live and you’re happy with it. A timeline is only useful if someone stands behind it.

Cost and timeline usually get asked in the same breath — if you’re weighing both, our guide to what a dental website costs and what moves the price covers the other half. And if part of your build is an assistant, it’s worth knowing what a safe AI assistant should and shouldn’t do before you commit.