What to Prepare Before You Start a Website Project
Most website projects lose time in the first few weeks, not the last. Designers wait for content, developers wait for access, and decisions that could have been made upfront get made one email at a time. A little preparation before the project starts changes that.
Need a hand with this?
Tell us what you're working on. We'll discuss your goals, understand your requirements, and explore how VQ Consulting can help.
Start Your Project
Start with the purpose
Before anyone talks about colors or layouts, be clear on what the website needs to do. Generate enquiries, explain a service, support existing clients, sell online. One or two main goals are enough, and they guide every decision that follows.
Six things to have ready
1. A decision-maker
Name one person who gives final approval. Feedback can come from many people, but when opinions differ, someone needs to decide. Without that, reviews turn into rounds of competing comments.
2. A realistic budget range
A range, even a rough one, lets the team propose a scope that fits. Without it, proposals are either too ambitious or too cautious, and time is spent revising them.
3. A list of pages
A simple outline of the pages you expect, and what each one is for, is the backbone of the project. It does not need to be final, but it gives everyone the same starting point.
4. Content, or a plan for it
Content is the most common reason website projects stall. Decide early who writes the text, who supplies the images, and by when. If content is not ready, plan for it as its own piece of work.
5. Access to what already exists
Domain, hosting, current website, analytics, brand files. Gathering logins and files before the project starts avoids days of waiting once it is underway.
6. A few examples you like
Two or three websites you like, with a sentence on why, communicate more than a long description. Examples you dislike are just as useful.
Agree how you will work
Once the basics are in place, agree on the working rhythm: how often you will review progress, how feedback will be collected, and how long each review round takes. Clear expectations here keep the timeline realistic.
A short checklist
- Main goals of the website, in one or two sentences.
- One person responsible for final approval.
- A budget range and a target launch date.
- A draft list of pages.
- An owner and deadline for content.
- Access to domain, hosting and brand files.
- A few reference websites, with notes.
None of this requires technical knowledge. It simply means the people building the website can start working on day one, rather than waiting for answers.
