How long does it take to build a website?
A small site takes 2 to 4 weeks, a business site 4 to 8, a custom build 8 to 16. Here is the week-by-week reality and what actually moves the date.

A small marketing website takes 2 to 4 weeks. A typical business website takes 4 to 8 weeks. A large or heavily customized site takes 8 to 16 weeks. Those are the timelines we work to, and they have held up across the 220-plus projects we have delivered since 2012.
But the number that decides your launch date is not on that list. It is how quickly you can hand over your content. I have watched a four-week project become a four-month project without a single line of code being the reason.
What is the realistic timeline for each project size?
These are working estimates from our own projects. Every one assumes content and decisions arrive on schedule. The money side lives in how much a website costs in Minnesota, where every figure is attributed; this post is about the calendar.
| Project type | Typical build time | What moves the range |
|---|---|---|
| Starter website, 5 to 8 pages | 2 to 4 weeks | Whether the copy already exists |
| Business website, 10 to 25 pages | 4 to 8 weeks | Custom design, integrations, content volume |
| Advanced or custom site | 8 to 16 weeks | Integrations, multiple languages, migration, approvals |
| Website redesign | 4 to 10 weeks | How much old content survives and how many URLs move |
| Online store | 5 to 12 weeks | Product count, photography, shipping and tax setup |
| Internal tool or automation | 4 to 10 weeks | Scope discovery, user roles, data migration |
| Web application or portal | 8 to 24 weeks | Scope discovery, user roles, outside systems it must talk to |
| Mobile app, iOS and Android | 12 to 28 weeks | Backend work, device testing, app store review |
The three software rows are the same figures as our app-cost guide, which explains why software runs on a different clock. The short version: a website’s schedule is driven by content, and an application’s schedule is driven by decisions and by how many outside systems it has to talk to.
Why does content delay projects more than development does?
Design and build are predictable. We know roughly how long a page template takes. Writing does not work that way, because the person who has to write it already has a full-time job.
Here is the pattern, and it is a pattern rather than one specific client. A home care agency signs a contract for a 14-page site. Development is scheduled for four weeks. The owner is also the scheduler, the biller, and the person covering a shift when a caregiver calls in sick. She needs to write service descriptions for six programs, a 245D compliance page, an about page, and nine staff bios.
Realistically that is 3 to 5 hours per page for someone who does not write for a living. Call it 35 hours of writing. She has maybe two hours a week. That is four months of calendar time for a task the schedule allotted ten days to. Nobody was lazy. The estimate was wrong about who was doing the work.
The fix is to decide in week one who is actually writing the copy, and to pay for a writer if the answer is “nobody has time.” Paying a writer for a small site is almost always cheaper than three extra months of the old site staying live, because those months have a cost of their own in calls you did not get.
The same trap catches nonprofits and schools hardest, because their content has to be approved by people who are not in the project meetings. Our nonprofit website design work almost always includes a content deadline written into the schedule, not implied by it.
What does a 2 to 4 week starter site actually look like?
| Week | What we do | What you do |
|---|---|---|
| Week 1 | Kickoff call, sitemap, choose direction, set up the build | Send logo files, photos, and all page copy |
| Week 2 | Design and build every page, load your content | Review the home page direction, answer questions within 24 hours |
| Week 3 | Full site review, revisions, mobile and speed pass | One consolidated round of feedback |
| Week 4 | Final fixes, forms, analytics, domain, launch | Approve, then go tell people |
Three weeks is realistic when content is ready at kickoff. Four is realistic when it is mostly ready. If content arrives in week three, this becomes a six-week project, and that is not a scheduling penalty, it is arithmetic.
What does a 4 to 8 week business site look like?
| Week | What we do | What you do |
|---|---|---|
| Weeks 1 to 2 | Discovery, sitemap, keyword and competitor review, home page design | Provide brand assets, existing analytics, all copy or a copy plan |
| Weeks 3 to 4 | Interior page design, component build, first pages live on a staging link | Review the home page, name one final decision-maker |
| Week 5 | Build out remaining pages, load content, set up forms and integrations | Supply staff photos, service details, testimonials you have permission to use |
| Week 6 | Accessibility pass, mobile pass, speed pass, cross-browser testing | Consolidated review of the whole site |
| Week 7 | Revisions, SEO metadata, redirect map if this replaces an old site | Final approval |
| Week 8 | Launch, DNS, analytics, search console, handoff training | Watch forms come in, report anything odd |
Eight weeks is the honest default for a 15-page site with a custom design. Four weeks happens when the page count is low, the content is written, and one person approves everything. Both ends of that range are real. The deliverable list is on our web design and development page.
What does an 8 to 16 week project look like?
The extra weeks are almost never spent typing faster. They are spent on discovery, integrations, and approval cycles. A school site with a staff directory, a calendar feed, enrollment forms, a board documents section, and a translated parent section is not one website. It is a website plus four small systems.
We designed and built that shape of project for Gateway STEM Academy, a public charter school in Saint Paul, and the sequencing mattered more than the speed. If enrollment season starts in March, the enrollment pages get built and tested first, not last. The school website cost guide covers what those systems add on the budget side.
What genuinely adds weeks?
| Factor | Weeks added | Why |
|---|---|---|
| Third-party integrations: donations, scheduling, EHR | 1 to 3 | Account access, sandbox testing, vendor support queues |
| A second language: Somali, Spanish, Hmong, Oromo | 2 to 4 | Translation turnaround plus a native-speaker review pass |
| Migrating an old site with hundreds of URLs | 2 to 4 | Content audit and a redirect map so rankings survive |
| Custom photography | 2 to 3 | Scheduling the shoot, then editing and selection |
| Board or committee approval | 2 to 6 | Most boards meet monthly, so one round costs a month |
| New logo and brand identity first | 2 to 4 | The site cannot be designed until the brand is settled |
| Large product catalog, over about 100 SKUs | 2 to 4 | Product data cleanup, images, variants, shipping rules |
| Accessibility remediation on a large existing site | 1 to 3 | Every template needs testing, not just the home page |
If you are moving platforms, read how to move a website without losing rankings before you set a launch date. Migration deadlines fail more often than build deadlines.
How much of your own time will the project take?
Plan on 2 to 5 hours a week for the length of the project, and expect it to bunch up rather than spread out. The heavy weeks are the first two, when you are gathering logo files, photos, analytics access, and copy, and the review weeks near the end, when you are reading every page on a phone and a laptop and sending one consolidated list of changes.
The middle weeks are light for you and heavy for the studio. That is normal, and it is also where projects quietly stall, because a question sent on a Tuesday that gets answered the following Monday costs a week each time it happens. The single most useful thing a client can do is answer questions within 24 hours during the build weeks, even if the answer is “I need until Friday.”
Two habits save the most time. Send feedback in one consolidated round rather than a trickle of emails, because every partial round forces the same pages to be reopened twice. And name one person who can say yes. A project with three people who can each say no and nobody who can say yes does not have an approval process; it has a waiting room.
Why do schools, nonprofits, and boards take longer?
Because approval is a calendar problem, not a design problem. If your board meets the third Tuesday of the month and design has to be approved by the board, one revision round costs you 30 days no matter how fast anyone works.
Two things fix most of this. First, name one person who can approve day-to-day decisions without convening anyone. Second, schedule the board review for a specific meeting date at kickoff and build the schedule backward from it. A project that treats a monthly board meeting as an unplanned interruption will always look late.
Can you compress a timeline honestly, and what does rushing cost?
Yes, and here is the list of what actually works.
Write the content before the project starts, or pay someone to. Cut the page count and add pages after launch. Use a proven design system instead of a from-scratch visual concept. Give one person final say. Launch in phases, with the pages that make you money going live first and the rest following in a second release.
What does not work is compressing the end of the project. The last two weeks are testing, accessibility, forms, redirects, and speed. Skip them and you launch a site where the contact form silently fails or every old Google result returns a 404. That is not a faster launch. It is a slower one with an unpleasant middle. The website launch checklist is the part nobody should be allowed to trim.
A rush fee is a legitimate thing to pay when the deadline is real, because it means a studio reorders other clients and puts more hours in per week. Ask exactly what it buys. It does not compress your board, your translator, or your photographer.
When should you not hire a studio at all?
If you need a site live in under three weeks and you have five pages of straightforward information, do not hire an agency. Buy a Squarespace plan, which the company’s pricing page listed at $19 to $29 a month on annual billing when I read it in November 2026, use a template, and spend a weekend on it. No studio can beat that on speed at that price, and the do it yourself versus hire someone comparison walks through where that stops being true.
Also, do not start a project while your content situation is unresolved. If you have no copy, no photos, and nobody with time to produce either, paying a deposit today does not start the clock. It starts a bill. Sort out who is writing, then call.
Why are “three days” and “six months” both warning signs?
A studio that promises a real 15-page business website in three days is either dropping your content into a template and calling it custom, or not planning to do testing, accessibility, or redirects. Ask what happens in those three days, hour by hour. The answer is usually revealing.
A studio quoting six months for the same brief usually has a queue problem, an unclear process, or too many approval layers of its own. Six months is a legitimate answer for a web application or a multi-site system. It is not a legitimate answer for a brochure site.
The useful question is not “how fast can you go.” It is “what is the schedule, what are my deadlines in it, and what happens when one slips.” The 15 questions to ask before you hire a web designer covers the rest of that conversation.
What if you have a hard deadline?
Count backward from it and be ruthless. Take your launch date, subtract two weeks for testing and revisions, subtract the build window from the table above, and subtract two weeks for content. Whatever date that lands on is your real start date. If it is in the past, cut scope now rather than discovering it in week six.
Phased launches are underused. A home care agency that needs to be findable before a referral partner meeting can launch four strong pages in three weeks and add the other twelve over the following month. Search engines do not require a finished site to start indexing you, and the home care website guide covers which pages belong in that first four.
If you are replacing an existing site, keep the old one live until the new one passes review. There is no prize for taking the old site down early, and there is real cost to a week of downtime.
What to do next
Write your page list, mark which pages already have finished copy and photos, and name the one person who approves things. Those three answers are usually enough for a studio to put a launch date on the calendar and mean it. If a board has to approve, find its next two meeting dates before you call anyone.
If you want a second pair of eyes on the plan, tell us what you are working on and when it needs to be live. TayoPro designs and builds websites and keeps them maintained month to month, both at a fixed price quoted in writing, and we will tell you plainly if you do not need either one.
FAQ
Questions people ask about this
How long does a simple 5-page website take?
Two to four weeks if your content is ready on day one. That covers a home page, an about page, a services page, a contact page, and one or two supporting pages on a proven design system. If the copy still needs to be written, add one to two weeks. Photography adds another week or two.
Why does my web designer keep asking me for content?
Because pages cannot be designed around text that does not exist. Placeholder copy hides layout problems, and every page built on it gets rebuilt later. Real headlines, real service descriptions, and real staff bios let a designer size type, set spacing, and catch problems once instead of twice.
Can a website be built in one week?
Yes, if the scope is tiny, the content is written, the design uses an existing template, and one person makes every decision without a committee. That is a real one-week project. What cannot happen in one week is a custom multi-page site with photography, integrations, and stakeholder review. Compressing that only moves the work to after launch.
What happens if my project goes over the estimated timeline?
Ask up front how a studio handles it. Ours is simple: if the delay is on our side we absorb it. If content or approvals stall on your side, the project pauses and resumes when materials arrive, which can push the launch by more than the days lost because the schedule has to be reopened around other work.
How long does a website redesign take compared to a new site?
Usually similar or slightly longer, 4 to 10 weeks for most business sites. A redesign adds work a new build does not have. Someone has to audit the existing pages, decide what survives, migrate the content, and map redirects from old URLs to new ones so search rankings carry over.
Should I pay a rush fee to launch faster?
Only if the deadline has real money behind it, such as a grant reporting date, a conference, or a lease opening. A rush fee buys sequencing, not magic. It reorders a studio's queue and adds hours per week, so ask exactly what it covers and what it does not. It cannot make your board meet sooner or your photographer shoot faster.
Keep reading
Website Costs17 min readComplete guide
How much does a website cost in Minnesota?
A GoodFirms survey puts small-business websites at $1,000 to $15,000 and Clutch says most projects land under $10,000. Here is what moves the number.
Web Design13 min read
The website redesign checklist that protects your traffic
A before, during, and after checklist for a website redesign, including the URL mapping and redirect work that keeps your Google traffic intact.
Web Design13 min read
15 questions to ask before you hire a web designer
The pre-signing conversation with a freelance web designer: contract terms, ownership, hosting, handoff, and what happens if they disappear.


