Building a website should feel like moving through a clear checklist, not wandering around a haunted house of missing passwords, mystery PDFs and emails called “final-final-v3-really-final.”
If you are planning a site for a business, artist portfolio or charity, the first question is usually not “Which font?” It is more practical than that. What happens first? How long does it usually take? What do you need to hand over early so the project does not stall in week two wearing a fake moustache?
This guide is the boring magic made useful. It walks through a realistic start-to-launch timeline, the decisions that shape scope, the materials you will be asked for, and the tiny but useful checks that prevent avoidable delays. If you want the broader service picture first, start with Latest News or review the Features of Taeko Website Design page before you begin.
Why this “latest news” matters before a project starts
A website project goes wrong in surprisingly ordinary ways. Nobody agreed on the page list. The contact route was not chosen. Brand files are scattered across four folders and one heroic old laptop. The team wants a brochure site on Monday and a donation platform with member logins by Thursday. None of this is rare. It is simply interface friction in a different costume.
The good news is that most project delays are visible early. If you know the likely milestones before you start, you can prepare the right content, answer scope questions faster and avoid paying for decisions that should have been made in plain English at the beginning.
A realistic website timeline, minus the jargon fog
The exact calendar depends on how ready your content is, how many pages you need and how quickly approvals come back. Still, most small to mid-sized website projects follow the same rhythm.
| Stage | Typical timing | What happens | What you need to provide |
|---|---|---|---|
| 1. Brief and fit check | 1–3 days | Goals, audience, page priorities and any urgent constraints are clarified. | Short project summary, current website link if you have one, and your preferred contact route. |
| 2. Scope and structure | 2–5 days | The page list, navigation, features and responsibilities are agreed. | Must-have pages, examples you like, and notes on what is missing or outdated. |
| 3. Content and assets handoff | 3–10 days | Logos, brand assets, images and draft copy are gathered. | Logo files, brand colours if known, photos, service descriptions, bios, donation copy or product details. |
| 4. Design and build | 1–3 weeks | Key layouts are designed, content is structured and the site is built responsively. | Fast answers to questions, missing content, and approval on direction. |
| 5. Review and revisions | 3–7 days | Feedback is collected, pages are tightened and any broken details are fixed. | One clear feedback round, marked-up notes and sign-off decisions. |
| 6. Launch preparation | 1–3 days | Forms, links, mobile layout, search basics and final settings are checked. | Final approval, launch contact details and any last-minute edits. |
That means a straightforward brochure-style website can often move from first enquiry to launch in roughly two to four weeks when content and approvals are ready. Add e-commerce, fundraising flows, event listings or layered approval chains, and the calendar gets longer. Not because the internet is being dramatic, although it often is, but because more decisions need actual answers.
What you will usually be asked for early
The first phase is not about dazzling creative language. It is about reducing chaos. These are the items most teams are asked for before meaningful design work can begin:
1. Your goal
A website cannot solve every business problem at once. The useful question is: what is the main action you want visitors to take? For a business, that may be an enquiry or quote request. For an artist, it could be a commission enquiry, exhibition visit or print sale. For a charity, it may be donations, volunteer interest or event sign-ups.
2. Your page list
You do not need the final menu on day one, but you do need a credible first draft. Think in pages, not vague hopes. Home. About. Services. Portfolio. Events. Donate. Contact. FAQs. A surprisingly large amount of project speed comes from naming the rooms before you discuss the wallpaper.
3. Brand assets
Logo files, preferred colours, fonts if you have them, and any brand guidelines belong here. If you do not have a formal brand pack, that is not fatal. A simple folder with your current logo, social icons and example visuals is enough to begin.
4. Content
At minimum, expect to supply short descriptions of your organisation, services, programmes or collections. If your copy is still rough, that is fine. Rough copy beats imaginary copy every time because it gives the build real shape.
5. Practical details
This includes email addresses, phone numbers, locations served, opening hours, social links, legal pages, donation platform details or shipping rules. These details are not glamorous, but they are where trust quietly lives.
If you are ready to organise these materials, the fastest route is usually the Contact page for the first hello and the Support page when you want to send the fuller project brief.
Choosing the right scope: brochure site, shop, or donation flow?
Scope is where many website projects either stay elegant or become a cupboard full of extra requirements pretending to be one simple task.
Brochure site
This is the classic information-first website: homepage, about, services or programmes, selected portfolio or case studies, and a clear enquiry route. It works well for service businesses, studios, consultants, many artists and charities that mainly need visibility, credibility and contact.
E-commerce site
This adds products, categories, checkout, delivery or fulfilment information, stock handling and post-purchase communications. The build is no longer only about presentation. It is also about operations. Even a small shop needs product photography, prices, policies and payment choices that make sense.
Donation or appeal pages
Charities often need a focused giving flow rather than a full shop. This means a clear mission statement, impact context, donation options, trust signals and a page sequence that does not bury the ask under five paragraphs of throat-clearing.
If your project begins as a simple website but is drifting toward member areas, dashboards, quoting tools or internal workflows, that is usually the moment to compare the brief against custom web development services. Not every site needs that level of build, but pretending a brochure page can do the work of an application is how timelines become interpretive dance.
What “mobile-ready” means in practice
Responsive design is not just “the site fits on a phone now, please clap.” It means the important actions still feel obvious on smaller screens.
- Headlines are short enough to read without turning into a staircase.
- Buttons are easy to tap and appear before the visitor loses patience.
- Images scale cleanly without hiding the message.
- Forms ask only for what matters.
- Navigation still makes sense when it collapses into a menu icon.
This matters for every audience type on this site. Business visitors often browse between meetings. Artists are frequently discovered first on mobile through social links. Charity supporters may be deciding whether to donate while standing in a queue with one thumb and very limited goodwill.
SEO basics you can confirm during the build
Search engine optimisation should not be treated like confetti thrown at the end of the launch party. There are a few basics you can confirm during the build itself:
- Each key page has one clear topic and one useful headline.
- Page titles and descriptions are written with real human intent in mind.
- The navigation makes sense for people and search engines.
- Images have descriptive alt text.
- Internal links connect related pages naturally.
- The site loads sensibly on mobile.
A good project workflow bakes this in while pages are being built. If you want a cleaner checklist for that side of the process, read Features of Taeko Website Design and use the homepage at Taeko Web Design as the benchmark for what needs to be obvious quickly.
How approvals usually work without everyone losing the will to live
The approval stage is where a calm process beats enthusiasm. The strongest review workflows usually look like this:
- One person collects internal comments before sending them on.
- Feedback is attached to specific pages or sections, not sent as a cloud of feelings.
- Change requests are prioritised: essential, useful, optional.
- Turnaround expectations are clear on both sides.
The most helpful notes are precise. “Please shorten this section and move the enquiry button higher” is useful. “Can we make it pop more?” is a sentence that has harmed many innocent afternoons.
If there will be multiple stakeholders, agree early on who signs off content, who signs off visuals and who approves launch. One extra decision-maker added late can stretch a two-day review into a two-week relay race.
Common causes of delay, and the boring ways to prevent them
Delay: content arrives late
Prevent it: prepare rough copy and image folders before the design phase starts. Draft material is workable; silence is not.
Delay: scope changes halfway through
Prevent it: separate “launch now” features from “phase two” ideas. Future ambition is healthy. Sneaking it into the current quote is not.
Delay: feedback comes from five directions
Prevent it: nominate one reviewer who compiles comments and sends a single version.
Delay: nobody owns the technical details
Prevent it: assign responsibility for domains, hosting access, email addresses, legal pages, analytics and platform logins before launch week.
Delay: images and brand files are inconsistent
Prevent it: keep one folder for final assets and name files sensibly. Your logo should not be hiding under new-logo-use-this-one-2-final.png, although history suggests otherwise.
Checklist: questions to ask before you sign up for web design support
- What is the main outcome this website needs to produce?
- Which pages must exist at launch, and which can wait?
- Who is supplying the copy, images and brand assets?
- What is the realistic timeline for approvals on your side?
- Will the site need e-commerce, donations, bookings or just enquiries?
- What happens after launch if you need edits or support?
- Who is the main decision-maker for content and sign-off?
- What does success look like three months after the site goes live?
A simple next step
If you are still in the “we know we need a website, but the next steps are foggy” stage, do one tiny but useful thing: write down your top five pages and the one action each page should support. That single exercise removes a remarkable amount of project haze.
Then use Contact for the initial outline or go straight to Support with your goals, timeline and existing materials. A website project becomes much less chaotic when the first checklist exists before the first mock-up.