Start with the kind of website you are actually buying
When businesses ask how long a website project takes, they often want one clean number.
That number is rarely honest on its own.
A five-page company website, a conversion-focused redesign, and a custom build with integrations do not move at the same speed.
The better question is what kind of work the timeline needs to cover.
That usually means separating:
- discovery and planning
- content preparation
- design
- development
- QA
- launch
That is why a realistic timeline should sit alongside the commercial routes for website redesign, business websites, custom development, and the wider web design pricing context.
The route matters because the shape of the project matters.
What a realistic website timeline usually includes
Many delays happen because the quoted timeline is treated as design and development time only.
In practice, the project clock usually includes decision-making, reviews, revisions, content collection, and launch prep too.
Here is a more realistic breakdown.
| Phase | Typical timing | What happens |
|---|---|---|
| Discovery and scope | 1 to 2 weeks | goals, sitemap, page roles, feature decisions, technical notes |
| Content and inputs | 1 to 3 weeks | copy, proof, imagery, approvals, case studies, assets |
| UX and design | 2 to 4 weeks | wireframes, visual direction, page designs, revision cycles |
| Development | 2 to 6 weeks | templates, CMS setup, forms, integrations, responsive behavior |
| QA and launch prep | 1 to 2 weeks | testing, redirects, analytics, form routing, final fixes |
That does not mean every project needs twelve weeks.
It means a useful estimate should show where the time goes.
Google recommends planning site moves carefully when URLs or structures change, including URL mapping, internal-link updates, and redirects Source: Google Search Central.
That matters here because redesign timelines often stretch when migration work is treated as an afterthought instead of as part of the plan from day one.
A simpler website can move quickly
Some projects are genuinely fast.
That is usually true when:
- the sitemap is small
- the offer is already clear
- the content already exists
- one or two people can approve decisions quickly
- there are few integrations
- the project is not replacing a messy old site
In that kind of setup, a straightforward business website may move from discovery to launch in four to six weeks without feeling rushed.
The speed does not come from cutting corners.
It comes from low complexity and fast decisions.
This is also why a focused landing-page project or brochure-style site can launch much faster than a service-heavy redesign.
The number of pages matters, but the approval burden and content burden matter even more.
Redesign timelines are often slower for non-visual reasons
Businesses sometimes expect a redesign to be quicker because "the website already exists."
Sometimes that is true.
Often it is not.
A redesign may still need:
- a new information hierarchy
- rewritten service messaging
- redirect planning
- CMS cleanup
- analytics fixes
- better forms and conversion paths
- decisions about which old content deserves to survive
That is why redesign work often behaves like diagnosis plus rebuild plus migration, even when the public description sounds lighter.
If the current website already drives enquiries, the team also has to protect valuable pages during the change.
That is where site migrations, redirect management, and the basics of a redirect start affecting the timeline directly, not just the SEO plan.
What usually stretches the timeline
The most common delays are rarely dramatic engineering failures.
They are usually operational.
1. The scope is still moving
If the sitemap, page goals, or required features keep changing after the project starts, the timeline loses shape quickly.
This is one reason a proper website discovery phase matters so much.
If your business is comparing two quotes with very different timelines, ask each supplier which phase hides the most risk. That usually exposes whether the estimate is detailed or simply optimistic.
2. Content is late or incomplete
Many projects stall because the team assumed copy, case studies, testimonials, photos, or offer details would "come later."
Later usually becomes the bottleneck.
3. Too many approval layers exist
A project with four reviewers is not automatically better than a project with one reviewer.
If nobody owns the final decision, every phase slows down.
4. The old platform is more awkward than expected
This shows up when the existing CMS, hosting, templates, or data structure create more friction than anyone expected during discovery.
5. Forms, CRM, or measurement are left too late
Projects often feel nearly done until someone asks how leads are routed, how conversion events are tracked, or which team gets the submission notifications.
That late-stage uncertainty can delay launch more than the homepage design ever did.
Timeline differences between common project types
The quickest way to misunderstand a quote is to compare unlike projects.
| Project type | Typical timeline range | Why it moves at that speed |
|---|---|---|
| Small brochure website | 4 to 6 weeks | light structure, fewer stakeholders, low technical complexity |
| Business website redesign | 6 to 10 weeks | diagnosis, content refinement, migration planning, conversion improvements |
| Lead-generation site with multiple service pages | 6 to 10 weeks | more page roles, proof placement, form logic, tighter CTA planning |
| Custom website with integrations | 8 to 12+ weeks | architecture, data flow, custom workflows, QA depth |
This is also where businesses should be careful not to compare a low-detail quote against a properly scoped one as if the timelines mean the same thing.
Sometimes the shorter quote is genuinely efficient.
Sometimes it is simply less explicit about the hidden work.
How to keep the project moving without forcing it
A practical way to shorten a website timeline is not to pressure the design team harder.
It is to remove the reasons the project slows down.
That usually means:
- agreeing on scope early
- choosing one clear decision-maker
- collecting proof and content before design reviews
- approving page roles before arguing about visuals
- confirming integrations and tracking before development starts
- treating launch prep as a project phase, not a last-day task
Core Web Vitals are still Google's user-centered measures for loading, responsiveness, and visual stability Source: web.dev.
That matters because launch readiness is not only about whether the pages are live. It is also about whether the site feels stable, responsive, and dependable when people actually use it.
A practical timeline checklist before you approve the quote
Before accepting a timeline, ask:
- Does the estimate include discovery and content, or only design and build?
- Who is responsible for copy, proof, and imagery?
- How many review rounds are included?
- Are redirects, analytics, and form routing part of launch prep?
- If the site is a redesign, which old URLs and pages need continuity?
- What would most likely delay the project from this supplier's perspective?
Those questions usually reveal whether the timeline is realistic or only optimistic.
FAQs
How long should a standard business website take in South Africa?
For a straightforward business website with clear scope and ready content, four to six weeks is often reasonable. If content is missing, approvals are slow, or the project needs more custom behavior, it can take longer.
Why do redesigns often take longer than expected?
Because the work is not only visual. A redesign often includes content decisions, migration planning, technical cleanup, and conversion improvements, especially when the old site already has traffic or enquiry value.
Can a website launch faster than this?
Yes. Some sites can launch quickly if the scope is intentionally narrow and the business can make decisions fast. The risk appears when a team expects a complex project to behave like a simple one.
A realistic timeline should protect quality, not only speed
The right website timeline should help the business launch with less chaos, fewer surprises, and less rework after go-live.
If you want help scoping a project more honestly before committing to dates, book a strategy call or contact us and we can help map the phases properly.
