One of the most common questions I get from business owners who are thinking about a new website is: how long will it take? They have often heard wildly different things. A friend who used Squarespace had something up in a weekend. A colleague hired an agency and waited four months. Someone they know paid a freelancer and the project dragged on for half a year before they gave up.
All of those stories are true. The range really is that wide. But the reason for the variation is not random. It comes down to a small number of factors that are predictable once you understand them. This post walks through realistic timelines for different types of business websites, explains what actually drives the schedule, and tells you how to move faster if speed matters to you.
Realistic timelines for building a business website
Before diving into the detail, here is the honest summary. The timeline for building a business website in 2026 depends primarily on three things: what kind of website you are building, who is building it, and how quickly you (the client) make decisions and give feedback.
With a professional using modern AI-assisted tools, a simple business website can be ready for review in 72 hours. A full marketing site takes one to two weeks. A website with custom integrations and complex functionality takes four to eight weeks. With a traditional agency, those same projects take roughly four to six times longer. With a self-service builder, you can be live in days if you are willing to accept template constraints, but getting to a polished, complete version takes most people two to four weeks of intermittent personal time.
Let us go through each scenario in detail.
A simple business website: 1 to 2 weeks
A simple business website covers the core pages most professional service businesses need: homepage, about or team, services, and contact. Maybe a short FAQ or a handful of testimonials. No booking system, no e-commerce, no members area. The goal is to establish credibility and make it easy for interested visitors to get in touch.
With AI-assisted professional development: The first version is typically ready for review within 72 hours of receiving the brief and brand assets. This is the timeline we work to at Kaizen, and it is achievable because AI handles the build mechanics quickly. A full round of revisions and the final polished version takes another three to five days. Total: five to ten working days from kickoff to a site you are proud to share.
With a freelance developer: Finding and booking a good freelancer takes one to three weeks before work even starts. The build itself takes two to four weeks. So the realistic total is three to seven weeks, assuming no significant delays.
With an agency: Most agencies have a lead time of two to six weeks before they can start. The build then takes four to eight weeks. Total: six to fourteen weeks. Not because they are slow at their jobs, but because the process involves multiple people, structured review rounds, and projects running in parallel.
With a self-service builder (Wix, Squarespace, Framer): Technically you can be live the same day. But getting from the default template to something that accurately represents your business takes time. You will write all the copy yourself, customise the design within the platform's limits, sort out your domain, set up email, test on mobile, and iterate. Most people who use this route spend two to four weeks of intermittent personal time before they are genuinely happy with the result. That personal time has a cost even if there is no invoice.
For most professional services businesses, a simple five-page site is the right starting point. It is enough to establish credibility, communicate the offer clearly, and capture enquiries. You can always add pages later. We explored what these essential pages actually need in our post on business website essentials.
A full marketing website with content: 2 to 4 weeks
A full marketing website goes beyond the basics. It might include a blog or knowledge base, case studies or portfolio pages, a detailed pricing page, multiple service pages targeting different customer segments, and more sophisticated design. The goal is not just credibility but active traffic generation and conversion.
The content is the main driver of timeline here. Writing ten to twenty pages of good copy takes time regardless of how fast the website is built. A homepage can be drafted in a day by someone who knows the business well. A detailed case study with real results and client quotes takes multiple rounds of back-and-forth to get right.
With AI-assisted professional development: The build itself takes one to two weeks. The content development (working with you to develop the messaging, drafting copy, incorporating your case studies and testimonials) typically takes another one to two weeks. If you arrive with all your content already written and approved, the site can be finished in ten to twelve working days. If content is being developed alongside the build, plan for three to four weeks total.
With a traditional agency: A full marketing website is typically a twelve to twenty week project at most agencies. They will run a discovery phase to understand your business and competitors, a strategy phase to develop the messaging architecture, a design phase with multiple concept presentations and revisions, a build phase, and a content production phase. Each phase has its own review cycle. The result can be excellent, but the timeline is long.
The key lever you control: How ready is your content? If you come to the project with clear copy for every page, a library of approved photography or illustrations, and quick decision-making on design, a full marketing website can be done in two weeks. If content is vague, assets are missing, and stakeholders disagree on the messaging, the same project takes three months regardless of who is building it.
We covered what makes a high-performing marketing website in our post on five landing page principles. The principles apply whether you are building a single page or a twenty-page site.
A complex website with integrations: 4 to 8 weeks
Some business websites need to do more than present information. They connect to booking systems, payment processors, CRM platforms, email marketing tools, or custom databases. They might have a client portal, a members area, or a form that triggers a workflow. They might pull in dynamic content from a headless CMS. The more moving parts, the longer the project.
Typical complexity drivers:
- Booking or scheduling integration (Calendly, Acuity, custom booking logic)
- Payment processing (Stripe, PayPal, direct bank integrations)
- CRM synchronisation (HubSpot, Salesforce, Pipedrive)
- E-commerce with product catalogue and checkout
- Members-only content areas with login and access control
- Multi-language or localised content
- Advanced SEO requirements with programmatic content generation
Each integration adds a fixed time cost: not because the code is especially difficult, but because integrations require account setup, configuration, testing across edge cases, and often some back-and-forth with the third-party provider's support team. A Stripe integration, done properly with full testing of payment flows, cancellations, and refund handling, takes two to three days. A full CRM sync with lead scoring and custom field mapping takes a week.
With AI-assisted professional development: A complex website with two or three integrations typically takes four to six weeks. The build is faster than traditional development, but the integration testing and quality assurance still take real time. Rushing integration testing is where subtle bugs get introduced that cause problems in production.
With a traditional agency: Eight to sixteen weeks is typical. The extra time comes from the structured process (more review rounds, more stakeholders involved, more documentation) and from agencies running your project alongside others.
If you are wondering whether a complex integration is actually necessary for your first version of the site: it often is not. A contact form that sends an email is sufficient for capturing leads. You do not need a full CRM integration until you are handling more enquiries than you can manage manually. Starting simpler and adding integrations later is almost always faster and cheaper than building everything at once.
What actually takes time when building a business website?
Understanding the true bottlenecks helps you set expectations and take the actions that actually shorten the timeline.
Content development. Writing the copy for a website is harder than most people expect. It is not just describing what you do. It is framing your offer in terms your ideal customer finds compelling, addressing the objections they have before they voice them, and making every word earn its place. A good homepage takes multiple drafts. Service pages need to be specific enough to be useful but broad enough not to exclude edge cases. If you want a website that actually converts visitors into enquiries, the copy is where most of the thinking lives. This is consistently the biggest bottleneck in website projects: not the build, but the words.
Decision-making and approvals. Every ambiguity in the brief becomes a decision during the project. What colour palette? Which photos to use? Should this section come before or after that one? For a solo business owner, these decisions are fast. For a business with multiple stakeholders (a partner, a marketing manager, a CEO who needs to approve the final version), each round of feedback can take days to collect and consolidate. The website project effectively pauses while you wait. At Kaizen we see this pattern regularly: the build is done, but the site sits in review for two weeks while internal consensus builds.
Photography and visual assets. A website is only as good as its images. Stock photos are a compromise at best and actively undermine trust at worst. If your site needs original photography (and most service businesses benefit enormously from real photos of their team, their space, or their work), scheduling a shoot, getting the images edited, and selecting the final set adds at least a week to the timeline. This is worth planning for before the website project starts.
Domain and technical setup. If you are using an existing domain, transferring it or pointing DNS records correctly usually takes a few hours and can cause a half-day delay. If you are registering a new domain, that is straightforward. If you are also setting up professional email addresses, configuring SSL certificates, or integrating with existing tools, those configurations add a day or two.
Revision cycles. After you see the first version of the site, you will have feedback. That is expected and healthy. The question is how many rounds of revision are needed and how quickly you can provide consolidated, specific feedback. "Change the font" takes ten minutes to implement. "The whole homepage feels wrong" requires a conversation about what is not working before anything can be fixed. If feedback is vague or contradictory, revision cycles multiply.
What does not take time anymore (thanks to modern tools)
It is worth understanding what has changed, because the timelines I quoted above for AI-assisted professional development would have been impossible five years ago. The things that used to eat weeks are now near-instant.
- Coding the layout and components: A homepage with a hero, testimonials, a services grid, a contact form, and mobile responsiveness takes hours to build, not days. AI generates clean, working code from a description of what is needed.
- Responsive design: Making a website look right on mobile, tablet, and desktop used to be a separate phase that added a week. Now it is handled as a standard part of the initial build.
- First-draft copy: AI can generate a serviceable first draft for every page based on a brief. It is not the final copy (a professional still needs to refine it to sound like you and serve your specific audience) but it compresses the blank-page problem dramatically.
- Standard integrations: Contact forms, analytics setup, basic SEO configuration, and cookie consent are now templated. They are done in minutes rather than half-days.
- Deployment: Publishing a website used to require server configuration, FTP uploads, and a checklist of technical steps. Modern platforms (Cloudflare Pages, Netlify, Vercel) deploy in seconds from a single command. DNS propagation still takes a few hours, but the active work is minimal.
The cumulative effect of these improvements is dramatic. A project that would have taken a traditional developer four weeks of work now takes an AI-assisted developer four to six days of work. The calendar time is shorter too, because the work happens in concentrated bursts rather than being stretched across a month of part-time attention.
Calendar time vs actual work time: why agencies quote months
There is an important distinction that confuses a lot of clients: the difference between how much work a project requires and how long it takes on the calendar.
When an agency quotes "twelve weeks" for a website project, they do not mean twelve weeks of full-time focused work on your site. They mean twelve weeks of calendar time, during which your site gets some fraction of someone's attention. The actual work hours are much lower: perhaps fifty to eighty hours of genuine development and design time across the twelve weeks.
Why does twelve weeks of calendar time contain so little actual work? Because the agency is running multiple projects simultaneously. Your project sits in a queue while other clients' feedback rounds are being processed. Your designer works on your homepage for two days, then switches to another client's rebrand for three days, then comes back to your site. There is overhead in context switching, in the handoffs between team members, in the approval layers that exist in any multi-person organisation.
A smaller shop or a solo professional using AI tools can compress this dramatically because the context switch cost is low and the work hours required are fewer. When I work on a website project at Kaizen, it gets concentrated attention until it is done. There is no multi-week queue, no hand-off between a designer and a separate developer, no account manager layer. The result is that fifty hours of work happens in five concentrated days rather than twelve calendar weeks.
This is why our claim of a first look in 72 hours is not a gimmick. It reflects the actual work hours required for a focused professional using modern tools. You can read more about how the economics of this work in our post on AI builder vs agency.
Five ways to make your website project faster
Regardless of who builds your website, these five things will shorten your timeline more than any other factor.
1. Write a clear brief before kickoff. A good brief answers: who is the site for, what do you want them to do, what are the core pages, what is the tone and style, and what does success look like. A brief does not need to be long. Two pages of specific, honest answers to those questions will save a week of back-and-forth during the project.
2. Prepare your content before the build starts. If you can hand over a Word document with the copy for every page before the developer touches the code, the site will be faster and better. The copy does not need to be perfect. It needs to be real: actual words that represent what you do and who you are for. Placeholder text ("Lorem ipsum" or vague descriptions like "we provide excellent services") cannot be designed around properly.
3. Sort out your visual assets in advance. Know what photography you are using. Have your logo in a usable format (ideally SVG, at minimum a high-resolution PNG). Have any brand colours and fonts documented. Tracking these things down mid-project is a reliable source of delays.
4. Be available for quick feedback. The fastest website projects are the ones where the client can give feedback within a few hours of receiving a draft. If you disappear for a week every time you receive something to review, the project timeline grows by a week each time. You do not need to be on call. You just need to prioritise the feedback moments when they arrive.
5. Cut scope to the minimum that serves the goal. Every additional page, every extra feature, every "while we are at it" request adds time. Define the smallest version of the site that would let you launch confidently, build that, get it live, then add the rest. A five-page site that is live is worth more than a twenty-page site that is still in development. We covered the strategic case for this in our post on launching your business online.
Why some businesses get a website in 72 hours
At Kaizen, we offer a first look within 72 hours of kickoff. That means a real, working version of your website, built specifically for your business, visible at a preview URL, within three working days. Not a template with your logo dropped in. A site built from your brief, your content, your brand.
This is possible because of how AI-assisted development has changed the economics of building websites. A professional who can generate a well-structured, responsive homepage in two hours rather than two days can deliver meaningful output within a working day. Across the full site, five to seven days of concentrated work produces what used to take four to six weeks.
The 72-hour first look is not the finished site. It is a working draft that gives you something real to react to. Clients who see an early version of their site respond more clearly and usefully than clients who try to give abstract feedback from a brief. Seeing it built makes the decisions concrete. You know immediately whether the homepage headline feels right, whether the colour palette works, whether the layout for the services section communicates what you do.
From that first look to a finished, polished site ready to publish typically takes another three to seven working days depending on how much revision is needed. Total project time for a standard five-page business website: one to two weeks.
The businesses that move fastest through this process are the ones who have their brief ready, their content at least in draft form, and their decision-makers involved from the start. The businesses that take longer are the ones where content is being written from scratch during the project, where multiple stakeholders need to align on every decision, or where the scope keeps expanding as the project progresses.
If speed matters to you, take a look at our pricing page to understand exactly what the fixed-price package includes and how the process works. There are no surprises in the billing and no waiting months for a finished site.
The bottom line: your website timeline depends on decisions, not code
In 2026, writing the code for a business website is no longer the bottleneck. Modern AI tools handle the mechanical parts of building a site with remarkable speed. A professional using these tools can do in a day what used to take a week.
The bottleneck has shifted entirely to the human side of the project: what do you want the site to say, who is it for, what does success look like, and how quickly can you make decisions when options are presented to you. Get those things right and a website project moves extraordinarily fast. Leave them vague and even the best team in the world will slow down waiting for direction.
If you are still working out what your site needs, our post on getting a website for a new business is a good starting point. If you are weighing whether to hire someone or use a self-service builder, our post on hiring a developer vs using an AI builder gives you an honest breakdown of each option.
And if you know what you want and you want it done quickly, the fastest path is a brief conversation with us. Tell us what you do, who you serve, and when you want to launch. We will tell you what is realistic and what it costs. No obligation, no lengthy discovery process before you commit to anything.
The question "how long will it take to build my website" has a shorter answer than most people expect. It takes as long as you need it to take, and the biggest factor is you.
If you want a benchmark for what good looks like before you start: we looked at what actually determines whether a website converts visitors into leads in our post on conversion rate for small business websites. The factors that drive results are not expensive to get right. They just require clear thinking and good judgment applied from the first page.