How Long Does It Take to Build a Website? Where the Weeks Go

You have a date. An opening, a season, a trade show, the day the old hosting arrangement ends. You also have three quotes, and one says a weekend, one says six weeks and one says three months, for what sounds like the same site. Nothing in the quotes tells you whether that spread is scope, caution, missing information or sales talk, and you need to know before you print the date on anything. The honest answer to the question is that a website's timeline is a chain of inputs and decisions, and most of the links in that chain belong to you rather than to whoever builds it. Once you can see the chain, the three quotes stop being a mystery and the date stops being a gamble.

A build stage cannot start until its inputs exist, and the inputs mostly come from the business. The words on each page. The photographs, and the right to use them. The facts about services, hours, areas and prices. Where a form submission should go. The logins for the domain, the current hosting, the analytics. And one person who can say yes. Every quote you hold assumes those arrive on a certain day, and the quotes that promise the shortest time are usually assuming they arrive on day one.

The University of Arkansas web team, which publishes its project flow for the departments it serves, lays out research, content strategy, design, development, testing and launch as distinct stages and says plainly that a delay in approval at any phase can derail the project. That sentence is the whole subject. The date holds when the dependencies are named, dated and owned, and it slips when they are discovered one at a time in the middle of the build.

A website project moves through a fixed set of stages whatever its size, and the difference between a weekend and three months is mostly how many of them a given quote includes and how much sits behind each.

A quote that skips inventory or testing, or that leaves content as somebody else's problem, is shorter for a reason. It is not wrong. It is describing a smaller job, and the only fair comparison is between quotes that describe the same one.

Almost none of the elapsed time in a website project is somebody typing code. The weeks go to content being written and approved, to photographs being found or shot and their permissions confirmed, to review rounds, to a migration plan if a live site is being replaced, and to testing on real phones with real form submissions. Each of those has a client-side wait inside it, and the wait is where a six-week project becomes a twelve-week one.

Two figures in this subject are sourced, and both belong to Google rather than to the build. Google's site-move guidance says that after a move that changes URLs, a small or medium site can take a few weeks or more for most pages to show at their new addresses, that rankings can fluctuate temporarily, and that redirects should generally be kept for at least a year. Google's SEO starter guide says a change can take from a few hours to several months to be reflected in Search, and suggests waiting a few weeks before judging whether a change helped. Both describe what happens after the launch button, which is why "live" and "appearing in search" are two different milestones, and why neither is a ranking.

Everything else is paced by scope and inputs, so a contract carries milestone dates rather than a single duration. The milestones are the honest version of the timeline, because each one names who has to do what by when.

What the contract also says is what pauses when a milestone is missed, and what happens when scope changes, because those two clauses are where most overruns are actually decided.

A well-run project asks the owner for a small number of clear things at fixed points rather than a stream of small requests, and an owner who has them ready removes most of the waiting from the plan.

• One source of business facts: services, areas, hours, contact routes, prices or eligibility, in one document.
• Brand files: the logo in its real formats, colours, any existing photography.
• Access: the domain registrar, current hosting, analytics and any tool being connected, or a named person who holds them.
• Images you own or have licensed, each labelled by its purpose on the site. W3C's accessibility tips note that text alternatives for images usually come from the people responsible for the written content, which means the description of what a photo is for is yours to give.
• Form decisions: which questions are needed, where submissions go, who replies. W3C's forms guidance says every control needs a label and that unnecessary questions increase abandonment, so the fields are a decision rather than a default.
• One decision-maker, and one only, for approvals.

The content one is the item people most often plan to "do later". Copy decides page structure, headings, image choices, offers, form wording and the legal claims on the page, and a build that starts before the words exist is a build that gets redone when they arrive. A deliberately smaller launch, with a stated list of what is deferred, is a fine plan. A full launch with the copy coming later is a schedule with a hole in it.

Two quotes are comparable only when they describe the same job, and the duration is the least informative line on either. Compare them on page count, who writes the copy and who supplies the photography, the number of revision rounds, the platform and its recurring cost, whether migration and redirects are included, forms or payments, accessibility work, account setup, post-launch support, and what you own at the end.

The published figures for this kind of work are third parties' numbers about their own populations, and they set scale rather than a rate. Squarespace's 2026 partner survey reported that 52% of responding Circle partners charged at least $1,000 for an entry-level project, with the lowest amounts charged spread across 29% at $0 to $500, 19% at $501 to $1,000, 26% at $1,001 to $2,000 and 12% at $2,001 to $3,000. That is a self-selected survey of one platform's partners. The Bureau of Labor Statistics reports May 2025 national median wages of $104,000 for web and digital interface designers and $92,650 for web developers, and CareerOneStop's 2025 Dallas-Fort Worth-Arlington figures for designers run from $29.68 an hour at the tenth percentile through a $50.07 median to $78.99 at the ninetieth. Those are wages for employees, which convert to no quote without assumptions about hours, overhead and scope. Shopify's Basic plan at $39 a month, or $29 paid yearly, is a platform subscription rather than a build.

What moves a quote upward is more pages, custom functionality, integrations, migration and URL mapping, content creation, paid assets, commerce setup, extra review rounds, and a larger support obligation. The mechanism for adding any of those mid-project is a change order, which AIGA's standard agreement describes as a signed document stating the additional time and money. A quote whose price stays fixed while the scope grows is a quote you should read again.

The paperwork worth locating before signing: named deliverables and exclusions, milestone dates and your own deadlines, review rounds, what a pause means, the payment schedule and recurring charges, the change-control method, who owns the final work and whether source files are included, who holds every credential at handoff, and the support period. The Copyright Office's work-for-hire page is clear that paying an independent contractor does not by itself make their work yours, and that a transfer of rights needs a signed written agreement. This is general information rather than legal advice, and a contract with meaningful ownership or liability terms is worth a lawyer's hour.

The fastest projects are the ones where the owner arrived with the six inputs and one approver, and that preparation is entirely within your control. Write the facts document. Pick the approver. Gather the logins. Confirm which images you actually own. Decide the form fields and where they go. Keep an asset list with each account's holder, recovery email and renewal date. Then, when staging is ready, test it as a customer would: call, submit the form, book, pay, read it on a phone.

The line sits where a shortcut touches compliance, security, data, rights, payment or a live migration. Do not draft the privacy notice from a template without knowing what data the site collects. Do not assume a photograph is licensed because it was on the old site. Do not delete old pages before the redirect plan is tested. Do not change code or account permissions without a rollback and someone who can review it. Each of those saves an hour and costs a week.

A first website and a replacement are different projects, and the replacement carries a stage the first does not: the search transition. Google's migration guidance sets the sequence. Prepare and test the new site on staging. Map every old URL to its nearest new equivalent. Configure and test the redirects. Check the canonicals and the robots rules so the new site is not accidentally blocked. Submit the sitemap. Monitor traffic and crawl errors. Keep the redirects for at least a year. Google also advises against changing the domain, the platform and the design all at once where it can be avoided, because three simultaneous changes make any drop impossible to diagnose.

The measurable obligations at launch are counts rather than promises: the old URLs listed, the destinations mapped, the redirects tested, the sitemap URLs indexed, the crawl errors, the form tests. Google's AI optimisation guide adds one more distinction worth having in writing: AI Overviews and AI Mode draw from the Search index, so eligibility there follows indexing, and appearing in either is an outcome nobody can schedule. Google says even a site that meets every requirement is not guaranteed to be indexed or shown.

Two Texas items can touch a launch, depending on the facts. If the name on the new site differs from the business's legal name, the Secretary of State's Form 503 instructions say a filing entity conducting business under another name must file an assumed-name certificate, at $25, for a term of up to ten years. A domain name does not answer that question; the name in the site's copy and the name on the filings do.

The Texas Data Privacy and Security Act, in force since July 2024, applies to covered controllers processing Texans' personal data, with notice and consumer-rights duties and a civil penalty of up to $7,500 per violation after the cure period, and the Attorney General's page says small businesses as federally defined are generally exempt except for selling sensitive data. Whether it reaches your forms is a fact-specific question, and so is the breach-reporting duty, which requires notice to the Attorney General within 30 days where 250 or more Texans are affected. Locally, the Downtown Arlington Business Improvement District, renewed in 2025, and the Chamber's SBDC advising are the rooms in which a launch date gets pressure-tested against a season or an event before it is printed.

The whole system fits on two pages. Before work begins: the one accountable approver, the content and asset deadline, the scope and the excluded work, the change-request path, every third-party account and who owns it, and the definition of the launch decision. For a replacement, the old-to-new URL map. After launch: the credentials, the renewal calendar, the sitemap and Search Console access, the evidence that forms route correctly, and a short list of open items with owners and dates.

It has worked when you can produce, without asking anyone you used to work with, the domain and DNS owner, the hosting and CMS access, the analytics and Search Console access, the current source of truth for business facts, the URL map where there is one, the record that forms route, and a written line describing where support begins and ends. Search Console will show you first-party evidence of sitemap submission, indexing, crawling, errors, impressions and clicks. It will not show you a ranking, and nothing else will either.

How long does it take to build a website from scratch?

It depends on the page count, whether the copy and images exist, the integrations, whether a live site is being replaced, the number of reviewers and the review rounds. A quote that names milestone dates and your deadlines is describing a real schedule. A single duration with no dependencies is describing a hope.

Can a small business website really be built in a weekend?

A limited template page can be, when the owner already has final copy, photographs, access and one decision-maker. A broader site, a migration, a shop, or several approvers cannot be judged by that speed.

What is a realistic website project timeline?

One expressed as milestones: asset deadline, content deadline, design review window, build complete, client QA window, launch approval, and a monitoring window afterwards. The elapsed time is the sum of those, and most of the waits are client-side.

Why do quotes for the same site differ so much?

Because they rarely describe the same site. Compare page count, content responsibility, revision rounds, migration, forms and payments, accessibility work, support and ownership before comparing weeks or dollars.

Will the site show up on Google when it launches?

Launch and appearance are different milestones. Google says a change can take hours to several months to reflect in Search, that a URL-changing move takes a few weeks or more to settle, and that indexing and serving are not guaranteed for any site.

What can I do to make it faster?

Arrive with the facts document, the brand files, the logins, images you own, the form decisions and one approver. Then test staging as a customer. Those remove most of the waiting from any plan.

The three quotes disagreed because they were describing three different jobs, and the date you need is decided less by any of them than by the day your copy, your images, your logins and your one approver are ready. Once the timeline is written as milestones with names on them, the question of how long stops being a guess.

Prepare the six inputs, read the quotes for scope, and expect two dates rather than one: the day the site is live and the weeks afterwards while Google catches up.

If you are working back from a fixed date and want the dependency list drawn up before a single quote is accepted, Arlington Website Designer does that with owners in Arlington, TX as a first step. Send the date, what exists today and who would approve the work through the contact page, and you will get back the milestones that date implies and which of them sit on your side of the table.