Around four weeks is a useful starting point for a typical business website project with me. Smaller, well-defined projects can sometimes be finished in one or two weeks. Larger or more complex projects can take eight weeks or considerably longer.
The duration depends heavily on the requirements, scope and what you already have ready. A business with an established brand, approved copy and a clear service offering starts in a different place from one that still needs to work through all three.
And those four weeks are not four weeks of typing code. Much of the calendar goes into understanding the business, preparing content, making decisions and reviewing the result while you continue running your company.
The build is only part of the timeline. The rest is making sure we are building the right website, with the right information, and giving everyone enough time to examine it properly.
A realistic starting point for your timeline
These are planning ranges for a conversation, not fixed delivery promises.
| Project | Starting point for planning | What affects the schedule |
|---|---|---|
| A small, tightly defined website or landing page | One to two weeks | Ready content and branding, limited functionality and prompt feedback. |
| A typical business website | Around four weeks | Number of distinct layouts, content readiness, design requirements and review rounds. |
| A larger website or substantial redesign | Eight weeks or more | Content volume, migration, multiple stakeholders and more extensive design or development. |
| Ecommerce, multilingual websites or custom systems | A project-specific schedule, potentially several months | Product data, translations, integrations, custom functionality and testing. |
Page count alone will not explain the difference. Ten pages using an agreed layout and approved content may be straightforward. Three pages involving customer accounts, booking logic and a connection to another business system may require considerably more work.
The same distinction matters when looking at how much a small business website costs. Compare the requirements and responsibilities behind the quote, including who handles content, branding and connected services.
Also ask when the provider can start. A four-week project beginning next month does not give you a website four weeks from today.
What do you already have ready?
“Everything is ready” can mean very different things.
Do you have an established visual identity, or just a logo someone made several years ago? Is that logo available as a usable vector file, such as an SVG, or is the only copy a small image downloaded from your social profile?
Are your brand colours and typography defined? Do you have the font files or access to the fonts you intend to use? Are there clear guidelines, or will we need to make those decisions during the website project?
The same applies to content and photography. Existing material helps when it is accurate, relevant and usable. A folder containing several hundred unnamed photos and five conflicting versions of your service descriptions still needs work.
Before estimating the schedule, I want to understand:
- Brand assets:usable logos, colours, typography and any existing visual guidelines.
- Content:which pages have approved copy, which need editing and which need writing.
- Photography:what exists, what can be used and what needs to be photographed or sourced.
- Functionality:what visitors need to do and which business systems the site must connect to.
- Approvals:who makes decisions and when they can review the work.
You do not need all of this finished before speaking to me. But we need to know what is missing so the schedule includes that work.
Why an afternoon AI demo is not this project
Yes, AI can generate a first draft in minutes. With a small enough scope, you can have a website online that afternoon. I use AI in my work, and I know how much faster it makes parts of the process.
The “website in an afternoon” claim spreads quickly because it makes an impressive demonstration. You see a prompt become a page. What you cannot see is how carefully anyone examined the business, the audience, the content or the decisions behind that page.
A website tailored to your business needs time for those things. It needs questions, revisions and sometimes several people working through an answer. Generating another layout is quick. Deciding whether that layout helps your customers understand your offer takes judgment.
If you want a service that generates a website in one day and hands it over, you are in the wrong place. I do not offer that, and I have no intention of making it my approach.
I use AI to accelerate the work. I still take responsibility for the decisions.
I want your business to succeed, so I need to examine what the website should do.
Does the structure make sense for your services? Does the copy answer your customers’ questions? Does the design fit your brand? Is the interface easy to use? Does the enquiry process collect useful information without making people work too hard?
AI helps me explore, build and revise. Those decisions still need human review. I need to examine the result, and you need an opportunity to tell me where it does or does not reflect your business.
I could compress production into less time. But compressing the entire project into an afternoon would leave very little room to think properly about your business, brand, design and customers.
The time AI saves is useful. I want to use it to improve the result, not remove the thinking and review your project needs.
An AI-generated PDF is not the same as a clear brief
When I say a well-defined project can move faster, I do not mean opening an AI chat, asking for a website plan, exporting whatever it produces into a PDF and sending it over.
Please do not do that without carefully working through the result.
AI can help you organise your thoughts. But if you give it very little information about your business, it has to fill the gaps. It can overcomplicate one part of the project, barely mention another and confidently recommend things that have no useful connection to what you need.
I have had clients send me these long, disconnected documents. A fifty-page plan filled with assumptions, invented details and lists of vaguely relevant features does not give us a head start.
I have to read it, check what is true, work out what you actually want, identify contradictions and turn whatever remains into usable tasks. Sometimes the document makes the project more complicated than a thirty-minute video meeting where I ask you a dozen focused questions.
You know things about your business that a generic prompt does not contain. What customers misunderstand. Which enquiries waste your time. Which services you want to grow. Why someone chooses you. What your team can realistically manage.
That is the information I need.
If you use AI to prepare, give it proper context, review every recommendation and remove anything you cannot explain or do not want. Tell me which parts reflect your decisions and which are suggestions you would like to discuss.
A short, accurate brief is much more useful than a large document that only looks comprehensive.
Hiring someone does not reserve their next seventy-two hours
Hiring an agency or independent freelancer does not automatically mean they will work exclusively on your project for the next three days.
There is still a schedule. There are working hours, existing commitments and people who need to eat, sleep and occasionally leave their desks. Your own availability has limits too.
A four-week project may contain several concentrated periods of work, with reviews and decisions between them. That is a normal part of the process.
If someone promises a complete, tailored business website in seventy-two hours, ask exactly what makes that possible. Perhaps the scope is very small, everything is prepared and they have reserved the time. That can be legitimate.
But if the promise includes discovery, original design, copywriting, integrations, revisions and testing, all before they have properly examined your requirements, I would be sceptical. Something is being left out of the explanation.
A niche template with a new logo
They change colours, swap a few details and hand it over. Fast is possible. You should know that is the product.
Most of the site generated, little reviewed
The demo looks finished. The offer, the pages and the enquiry process have not been checked against your business.
A real reserved sprint
Small scope, everything prepared, time actually blocked. That can be legitimate. It is not the default for a tailored site.
Those approaches can produce a website quickly. You should understand which service you are buying.
A template can get you online. Decide whether that is enough.
There is nothing inherently wrong with a template. If you need a basic presence, have a limited budget and understand the trade-offs, it may be a reasonable choice.
But replacing a logo and changing colours does not automatically give you a website that communicates why your business deserves attention.
If the structure, service descriptions, page layouts and messaging could belong to any competitor, visitors have very little help understanding why they should choose you.
I want to understand what works in your market and then apply that knowledge to your business. That includes your particular services, your process, your experience, the evidence behind your claims and the questions your customers need answered.
This also gives search engines and AI systems clearer, more specific information to interpret. A custom design alone does not guarantee visibility or rankings. The substance of the website still matters.
You do not need to invent a completely new layout for every page. Familiar patterns often make a website easier to use. The work is in deciding how the structure, content and design should serve your particular business.
That takes more thought than swapping the branding on somebody else’s website. I compared that choice more directly in website builder vs web developer.
Copy, photos and decisions shape the calendar
“Send us your content” sounds like a small task until you open a blank document.
What exactly do you offer? Which customers are you trying to attract? Do you publish prices? What makes one service different from another? What should somebody do after reading the page?
Writing exposes business decisions that may still be unresolved. A short service page needs accurate information and a useful explanation, even if it contains only a few hundred words.
Hiring a copywriter gives that work an owner. Somebody inside the business still needs to supply facts and approve what the website says.
Photography has similar dependencies. A contractor may need project photos. A restaurant may need a shoot. A manufacturer may need images that clearly explain unfamiliar products. Those tasks do not become quicker because the page layout is finished.
And feedback needs a place in your calendar. You cannot necessarily review a design ten minutes after I send it.
Agree on review windows you can meet, and appoint one person to send the final, combined response. Other people can contribute, but the designer should not have to reconcile five contradictory emails.
You do not need every detail settled before work begins. You do need clear ownership and dates for the decisions that affect what comes next.
What a four-week project could look like
Consider a service business with usable branding, a clear offering, a manageable page list and one decision-maker. Core content is available, and there are no substantial custom integrations.
| Week | Main work | What the business needs to do |
|---|---|---|
| 1 | Confirm requirements, organise content and develop the main design direction | Supply assets and access, answer questions and review the direction. |
| 2 | Build the main layouts and begin implementing content | Approve key decisions and resolve remaining content gaps. |
| 3 | Complete pages and functionality, then review the full site | Provide combined feedback and check business details. |
| 4 | Make revisions, test, complete handover and launch | Approve the finished site and confirm operational readiness. |
This is an example, not a universal sequence. Some work overlaps. A project needing brand development, extensive copywriting or complex functionality needs a different schedule.
Testing also needs room for corrections. Discovering a broken form or an awkward mobile layout is exactly why testing exists. A schedule that leaves no time to fix anything is incomplete.
How to shorten the timeline without rushing the decisions
Smaller projects can genuinely be finished in one or two weeks when the preparation and scope support it.
Agree on the first version
Define the pages and functions required for launch. Keep optional additions in a separate list.
Prepare usable material
Gather the actual brand files, approved business information and selected images. A large folder of unsorted material still needs sorting.
Give content an owner
Name the person responsible for each missing item and agree on delivery dates.
Check access early
Domain, hosting and connected service accounts should be accessible before launch week.
Reserve review time
Faster delivery requires availability on both sides. Make sure the people approving the work can participate.
Define what finished means
Agree on testing, handover and launch responsibilities so “almost done” has a clear endpoint.
These are useful things to discuss when choosing a web developer. A credible timeline comes with questions and assumptions you can inspect.
Delays are not automatically the client’s fault
Content and approvals should not become a convenient excuse for poor delivery.
A provider should explain what they need, give reasonable notice and flag a dependency before it becomes a missed deadline. If copywriting is included, they need to manage that work. If an integration is uncertain, it needs investigation early.
Be cautious when a proposal has a launch date but no content plan, no defined review process or no time for testing.
Problems can happen. You should still receive a clear explanation of what remains, who owns it and how the schedule changes.
The owner has responsibilities. So does the person managing the project.
Plan around the work your business needs
Around four weeks is a useful starting point for my typical business website projects. One or two weeks can work for something smaller and well prepared. Eight weeks or more can be entirely reasonable when the requirements are larger.
The scope should determine the schedule. The promise of a fast launch should not determine how much of the work gets skipped.
A useful website needs time for informed decisions. Better tools can accelerate the work, but they do not remove the need to understand your business.
Bring your existing brand assets, explain what you want the website to achieve and show me what you already have. We can work through the missing information together. A focused conversation will usually get us further than another generic fifty-page plan.
Frequently asked questions
Can you build a business website in one or two weeks?
Yes, some smaller projects can fit that schedule. They need a tightly defined scope, usable branding, ready content, limited functionality and people available to review the work promptly.
Why plan for four weeks if you use AI?
AI speeds up parts of production. Understanding the business, checking information, making design decisions, gathering feedback and testing still require attention. Four weeks is a useful planning reference for my typical projects, not a fixed minimum.
What should I prepare before contacting you?
Bring your existing website, usable logo files, brand colours and typography, any approved copy, relevant photos and a clear explanation of what you want to achieve. You do not need a polished specification or an AI-generated strategy document.
What if I need branding or copywriting as well?
Those requirements need to be included in the scope and schedule. Some work can overlap, but a project starting without branding or content should not be estimated as though those inputs are already finished.
When should I expect eight weeks or longer?
Larger websites, substantial redesigns, content-heavy projects, multilingual sites and custom integrations can need that time or more. The estimate should explain which requirements drive the duration and what both sides need to provide.
