Most delays in website projects don't come from design or code. They come from questions nobody has answered yet: what the site is for, who writes the content, where the logo files are. You don't need every answer before the first conversation — but the more of these you've thought about, the faster and more accurately a project can be scoped.
Start with the purpose
Write down, in a sentence or two, what you want the website to do. “Get more calls from people nearby who need a gym” is far more useful than “a modern website”. A clear purpose guides every later decision: which pages exist, what goes at the top of the homepage, and what the main button says.
Know who it's for
- Who are your typical customers, and what do they usually ask before buying?
- Do most of them visit on a phone?
- Which languages, locations or accessibility needs should the site account for?
Gather what already exists
- Logo files — ideally in SVG or high-resolution PNG format
- Brand colours and fonts, if they're defined
- Photos of your work, team, premises or products
- Existing website content, domain and hosting login details
- Social media profiles you want linked
Decide who handles the content
Content is the most common bottleneck. Decide early whether you will write the text, whether it needs help from a copywriter, or whether existing content will be adapted. Draft content — even rough — makes design far more accurate than placeholder text.
Collect examples
Find three to five websites you like and note what specifically you like about each: the layout, the tone, the photography, how easy it is to book. Examples of what you don't want are just as useful.
List the features you need
- Contact or enquiry forms
- Booking, payments or a shop
- A blog or news section you'll update
- Integrations with tools you already use
- Multiple languages
Separate must-haves from nice-to-haves. A focused first version can launch sooner, and extra features can follow once the basics are working.
Think about timing and budget
If there's a real deadline — an opening date, a launch, an event — mention it upfront. Likewise, a rough budget range helps shape a sensible proposal. Neither has to be fixed, but both help avoid scoping something that doesn't fit.
Plan for after launch
Websites need occasional updates. Think about who will make changes, how often content will change, and whether you'd like ongoing maintenance support. It's easier to plan for this from the start than to work it out later.