A website project feels much calmer when it behaves like a visible control panel instead of a fog machine. This guide shows the buttons: what happens after you enquire, what you need to send, and what usually moves a project from first message to launch without unnecessary chaos.
Most people arrive with a very reasonable set of questions. What happens after I make contact? How much do I need to prepare before anything can start? What usually takes a day or two, and what tends to take longer? What does “ready to launch” actually mean? If you are a business owner, artist, or charity lead, that uncertainty is often the real friction, not the website itself.
The good news is that a web design project does not need to feel mysterious. It usually moves through a small number of clear stages: fit check, discovery, design, build, review, and launch. The exact speed depends on your content, approvals, and access details, but the structure is usually steady. Less mystery means less delay.
By the end of this article, you will know the six main stages, what you should prepare for each one, what the designer is doing in parallel, and how to spot the usual delay traps before they start chewing on the schedule. If you are ready to compare this with the broader service approach, the home page gives the quick overview.
Quick definitions before the clock starts
A few terms show up in almost every project. They sound more dramatic than they are, so here is the plain-English version.
- Fit check: the early stage where goals, scope, timing, and basic suitability are confirmed.
- Discovery: the planning stage where pages, content, priorities, and practical requirements get translated into a build plan.
- Wireframe or structure: the simple layout logic for key pages before full design details are locked.
- Revision round: one organised batch of feedback, not fifty tiny messages arriving like confetti with opinions.
- Ready to launch: pages are complete, links work, forms are tested, and final approval is in place.
The 6-stage website timeline at a glance
Here is the short version first. Think of it as the dashboard view before we open each panel. Timelines are usually shaped more by readiness than by luck. A smaller brochure site with content ready can move faster than a larger project waiting on copy, image choices, domain access, or donation and ecommerce decisions.
| Stage | Typical range | What you provide | What the designer does | Done means |
|---|---|---|---|---|
| 1. Enquiry + fit check | 1 to 3 business days | Goals, rough page ideas, timeline needs | Confirm next steps and scope fit | Both sides know whether to proceed and what information is needed next |
| 2. Discovery | 2 to 5 business days | Content, assets, priorities, access notes | Map pages, content gaps, and project needs | The plan, page list, and content requirements are clear |
| 3. Design + structure | 3 to 7 business days | Brand preferences and focused feedback | Shape layout, navigation, and visual direction | Key page structure is approved for build |
| 4. Build + essentials | 4 to 10 business days | Final content, images, technical access | Build responsive pages, forms, and core essentials | The website works across devices and core features are in place |
| 5. Review + revisions | 2 to 5 business days | One organised round of comments and approval | Apply agreed changes and test key paths | The site is accurate, complete, and launch-ready |
| 6. Launch + support | 1 to 2 business days | Final go-ahead and access confirmations | Publish, hand over, and support the next steps | The live site is available and the key admin path is clear |
The stage order is predictable. The exact duration is not. A five-page business site with prepared copy is different from an artist portfolio still waiting on image selections, and both are different again from a charity site that needs donation messaging, trustee approval, and multiple stakeholders to sign off.
Stage 1 – Enquiry + fit check
This is the first handshake, not a full excavation. After an enquiry, the usual goal is to confirm what kind of site you need, what timeline pressure exists, and whether the project is straightforward or has a few extra moving parts hiding behind the curtain.
- What usually happens: you send an enquiry, receive confirmation or next-step guidance, and answer a few practical questions about the purpose of the site.
- What you should prepare: a short description of your organisation, your audience, a rough page list, any current website link, and any existing branding or logo files.
- What the designer is doing: checking scope, identifying obvious dependencies, and deciding whether the next step is a quick clarification, a call, or a written discovery process.
- What “done” means: both sides understand the goal, the likely shape of the website, and the information needed to move into planning.
This is also where urgency gets translated into reality. If you need a quick turnaround for a campaign, exhibition, event, or launch, say that early. It does not force a magic deadline into existence, but it does help shape what gets prioritised first. If you are ready to start that conversation, the contact page is the right button to press.
Typical timing: usually 1 to 3 business days, depending on how quickly the first exchange is answered and whether the scope is clear from the outset.
Stage 2 – Discovery: goals, pages, and content needs
Discovery is where the project stops being a hopeful sentence and becomes an actual plan. The question here is simple: what job should the website do? Sell? Showcase? Collect enquiries? Explain a service? Support donations? Calm confused visitors? Sometimes the answer is “all of the above,” which is valid but slightly greedy. Discovery helps sort the priorities.
- For a business: the hero page usually needs to explain the service fast, show credibility, and make enquiry easy.
- For an artist: the portfolio or work page is often the hero, with biography, statement, and contact details supporting it.
- For a charity: the mission, impact, support path, and contact details usually need stronger prominence than decorative extras.
At this stage, the page list often becomes clearer: Home, About, Services, Portfolio or Projects, Contact, and any extras such as FAQs, donation pages, booking forms, or news updates. Discovery also reveals the content gap. You may already have a logo, photos, and approved copy. Or you may have a logo from 2017, three phone photos, and a sentence that says “we do all sorts.” That is still usable information. It just changes the timeline.
- What you should prepare: page priorities, draft copy, image folders, social links, service descriptions, bios, project summaries, or mission language.
- What the designer is doing: auditing what exists, identifying what is missing, and shaping the navigation and page structure around the real goal.
- What “done” means: the project has a defined scope, a page plan, and a clear list of content and access items still needed before build.
Typical timing: usually 2 to 5 business days. It can be shorter when content is already organised, and longer when several people need to approve the page list or messaging.
Stage 3 – Design + structure: turning pages into something usable
This is where the project starts to feel real. The menu gets logic. The home page gets hierarchy. Sections stop floating around like enthusiastic but unsupervised interns. Design is not just colours and fonts; it is the structure that helps visitors find the point quickly.
- Navigation decisions: what belongs in the main menu, what belongs lower on the page, and what can safely stay out of the way.
- Key page sections: usually hero, proof or examples, service or work overview, about context, and the main call to action.
- Brand alignment: type, colours, imagery style, tone, and spacing should support the organisation rather than dressing it in somebody else’s clothes.
- Feedback method: focused comments in one round are best. “Could section two be shorter?” is useful. “Something feels off, spiritually” is harder to build with.
If your project includes custom workflows, a private dashboard, booking logic, or other non-standard features, the timeline usually expands here because the structure needs more thought before build begins. In that kind of case, it can be useful to review examples of custom web development services alongside your design scope, simply to see how custom requirements tend to affect planning.
What you should prepare: clear feedback on priorities, any must-keep brand elements, and one decision-maker if possible.
What “done” means: the layout and structure for the key pages are approved closely enough that build can start without major guesswork.
Typical timing: usually 3 to 7 business days, depending on the number of pages and how quickly design feedback is gathered and approved.
Stage 4 – Build + essentials: the site becomes a working thing
Now the project moves from approved structure into live implementation. This is where pages are assembled, content is placed, forms are connected, and the small but important boring magic happens. Boring magic is still magic. It is just wearing sensible shoes.
- What gets built: responsive layouts, page templates, navigation, image placement, contact or enquiry forms, and the core on-page structure needed for a clean launch.
- What gets checked: mobile behaviour, link paths, form behaviour, image handling, and basic speed hygiene.
- What you should prepare: final copy, final image choices, domain or hosting access if needed, and any special requirements such as ecommerce, booking, or donation elements.
- What the designer is doing: building the approved structure, fitting content into the correct sections, and making sure the site works as a usable whole rather than a set of attractive fragments.
This stage is not the place to introduce brand-new major pages unless they are genuinely essential. Small refinements are normal. Surprise extra scope is the classic “one more tiny thing” trap that quietly adds days. If you want a broader sense of what is commonly included in a build, Features of Taeko Website Design gives a useful companion overview without turning this article into a giant technical checklist.
What “done” means: the website is functioning across key devices, major content is in place, and the core launch essentials are ready for review.
Typical timing: usually 4 to 10 business days. It can be shorter for a small brochure site with prepared content, and longer for projects with donations, ecommerce, membership features, or slow approval cycles.
Stage 5 – Review + revisions: defining “ready to launch”
This is where everyone stops squinting and starts checking. A proper review round is less about taste panic and more about accuracy, usability, and completion. The goal is not endless polishing. The goal is confidence.
- How feedback works best: collect comments in one place, send one organised round at a time, and group notes by page or issue.
- What should be reviewed: page completeness, copy accuracy, menu labels, image choices, links, forms, and the clarity of the main call to action.
- What you should prepare: one clear batch of comments, final factual corrections, and explicit approval when the site is good to go.
- What the designer is doing: applying agreed revisions, testing the key paths again, and checking that fixes have not introduced new problems elsewhere.
“Ready to launch” should mean something specific. The pages are complete, the links work, the forms have been tested, the important contact path behaves properly, and final approval has been received. If any of those items is still floating around unresolved, the site is not quite at the runway yet. It is still in the queue holding a coffee.
Typical timing: usually 2 to 5 business days, mostly depending on how many reviewers are involved and whether feedback arrives in one batch or as a long-running sequel.
Stage 6 – Launch + support: live site, handover, next steps
Launch is not the end of the story. It is the moment the site stops being a project file and starts doing its job in public. That includes a practical handover: what is live, what access exists, and what to do next if you need support, edits, or future updates.
- What usually gets handed over: live access, key admin details, the published pages, and practical guidance on how to request or handle updates.
- What you should prepare: final approval, any last access confirmations, and a note of who will be the ongoing point of contact.
- What the designer is doing: publishing, checking the live site, confirming the main paths still work, and helping with immediate post-launch questions.
- What “done” means: the live site is accessible, the key enquiry or support path works, and you know what happens if you need help after launch.
After launch, a sensible next step is to keep content current. Add updates when needed, keep contact details accurate, and use the Latest News section if you want a place for ongoing articles or announcements. If you expect help with updates or troubleshooting after go-live, the Support page exists for exactly that reason.
Typical timing: usually 1 to 2 business days for the actual go-live and immediate follow-up, assuming approval and access details are already settled.
Preparation checklist: what to gather before kickoff
If you want the timeline to move with less drama, this checklist is your friend. It is not glamorous, but neither is chasing an old hosting password two hours before review.
- Logo and brand assets: logo files, colour preferences, fonts if known, and any visual references that still fit the brand.
- Core content: home page summary, about text, service descriptions, portfolio notes, mission statement, FAQs, and any required legal or policy text.
- Images: headshots, project photos, artwork, team images, and any notes on preferred crops, usage rights, or image priorities.
- Contact details: email address, phone number, address if relevant, opening hours if relevant, and social profile links.
- Technical access: domain access, hosting access, current website login, and clarity on who manages each one if you do not manage them directly.
- Optional scope details: ecommerce needs, donation flows, booking forms, special forms, newsletter signups, or extra pages you know you need from the start.
A practical shortcut: create one shared folder with subfolders for copy, images, brand files, and access notes. That single act removes an alarming amount of avoidable confusion.
Common delays to avoid, and how to prevent them
Most delays are not mysterious. They are repetitive. The same four or five issues show up on project timelines everywhere because they feel small until they pile up together.
| Delay | What it looks like | How to prevent it |
|---|---|---|
| Late content | Pages are structurally ready but waiting on copy, image choices, or bios | Set a date for first content delivery and use placeholders only where necessary |
| Unclear goals | Too many competing priorities and no clear page hierarchy | Write one sentence that answers: what should this website do first? |
| Missing access | Domain, hosting, email, or admin details are needed but unavailable | Confirm ownership and access responsibilities during discovery, not on launch day |
| Feedback bottlenecks | Comments arrive from several people in different formats over several days | Choose one decision-maker and send one organised feedback batch per round |
| Scope creep | New pages and features appear after design approval | Agree the page count and must-have features before build starts |
There are also a few reliable warning signs. If access details are still unclear by the end of discovery, if content has no delivery date, or if feedback is coming through email, chat, voice notes, and “quick thoughts” all at once, the schedule is probably about to wobble. The fix is rarely technical. It is usually organisational: simplify the communication, confirm the owner, and lock the next decision.
A simple example for each type of client
Sometimes the timeline makes more sense when it has a face.
- Business example: a local service company with five pages, a prepared logo, and clear service text can often move quickly because the content job is already half done.
- Artist example: a portfolio site may look visually simple, but selecting final work, writing captions, and deciding image order can easily become the longest stage.
- Charity example: a support-focused site often needs more approval time because mission wording, impact statements, trustees, or donation flows may require extra checks before launch.
The pattern is consistent: the smoother the content, access, and approvals, the smoother the timeline. Design and build matter, of course, but readiness is often the true project engine.
Final takeaway: a launch timeline works best when everyone can see it
A website project does not need to feel like a riddle wrapped in a plugin wrapped in an email thread. It works better as a visible sequence: enquiry, discovery, design, build, review, launch. Each stage has a job. Each stage needs a few inputs. Each stage has a clear definition of done.
- Stage order stays fairly stable: fit check, discovery, design, build, review, launch.
- Your speed depends mostly on readiness: content, access, and approvals drive the schedule more than anything else.
- Ready to launch is specific: pages complete, links working, forms tested, and final approval received.
- Most delays are preventable: prepare assets early, keep one decision-maker, and confirm scope before build begins.
If you want to turn today’s enquiry into a clearer project path, start with the essentials: gather your content, confirm who controls the domain and hosting, and send a short project summary through Contact. A calmer launch usually starts with a calmer kickoff.