Most website projects that run over time or budget do not go wrong in design or development. They go wrong earlier, when the business and the developer start building before agreeing what the website is for. A few hours of planning prevents most of that.

This checklist is the same set of questions we work through with new clients. You do not need technical knowledge to answer them, and having the answers ready will make any quote you receive far more accurate.

1. Decide what the website must achieve

"We need a website" is a starting point, not a goal. Write down the one or two things the site must do for your business. For most service businesses the answer is some version of:

  • help potential customers understand what we offer and whether it fits them;
  • make the business look credible to someone who has never heard of it;
  • turn interested visitors into inquiries by form, phone, email or WhatsApp.

A store has a different goal: sell products online. A booking-led business, such as a guest house or a clinic, wants requests for specific dates. The goal decides which pages matter most and what the main button on every page should say.

2. Describe the people who will visit

Think about the customers you most want to win, not everyone who might land on the site. What do they search for? What worries them before they buy? What would make them choose you over a competitor? Write the answers in plain language. They become the raw material for your headlines, service descriptions and FAQs.

If you plan to promote the site on Facebook or Instagram, consider how those visitors differ from people arriving from Google. Someone who clicks a social post is often discovering you for the first time and needs more reassurance; someone who searched for your exact service may be ready to ask for a quote.

3. List the pages you need, and only those

A typical small business website needs fewer pages than people expect:

  • Home: who you help, what you offer and the next step.
  • A page for each main service: one service per page works better for visitors and search engines than one long list.
  • Work or case studies: real examples with honest descriptions.
  • About: who is behind the business and how you work.
  • Contact: a short form plus your other contact options.
  • Privacy policy: required if you collect personal data or use analytics.

Add a blog only if someone will write for it. An empty blog with one post from two years ago does more harm than no blog at all.

4. Gather your content early

Content is the most common cause of delay. Designers can work around missing text for a while, but at some point the real words and photos are needed. Start collecting:

  • your logo in the best quality you have, ideally as a vector file;
  • photos of your work, premises or team (real photos usually build more trust than stock images);
  • a short description of each service: what it includes, who it is for and what happens after someone gets in touch;
  • examples of past work you have permission to show;
  • genuine reviews or testimonials, with permission to publish them.

Keep it honest. Only publish testimonials, client logos and results you can stand behind. Invented reviews or inflated numbers damage trust when they are noticed, and in many countries they also break consumer protection rules.

5. Note the features you really need

Features drive cost, so separate what you need at launch from what would be nice later. Common examples:

  • contact or quote forms, with the information you want to collect;
  • WhatsApp, phone or booking buttons;
  • an online shop, product catalog or payment options;
  • multiple languages;
  • integrations such as a newsletter tool, CRM or analytics and ad tracking.

If you are not sure whether something is needed, put it on a "later" list. A good developer will build the site so those features can be added without starting over.

6. Decide who will update the site

This one question often decides the platform. If your team will add pages, publish posts or change prices regularly, an easy-to-edit system such as WordPress is usually the right fit. If the site will rarely change, a custom-coded site can be faster and needs less ongoing maintenance. We explain the trade-offs in more detail in WordPress vs a custom-coded website.

7. Sort out the domain, hosting and email

Make sure the domain name is registered in your name or your company's name, and that you can log in to the account. The same goes for hosting. If a previous developer registered these for you, ask for the access now rather than in the middle of a launch.

8. Set a realistic budget and timeline

Website prices vary widely because the work varies widely. The main factors are the number of unique page designs, the amount of content to prepare, the features and integrations, and whether e-commerce is involved. Instead of asking "how much is a website?", share your goals, page list and features, and ask for a quote based on them. You will get a more accurate figure and a clearer view of what is included.

Plan time for your own reviews too. Most delays come from waiting on feedback or content, so block time in your calendar for those moments.

9. Plan what happens after launch

A website is not finished on launch day. Decide who will handle software updates, backups, small changes and checking that forms still work. Also decide how you will measure success: usually the number and quality of inquiries, which means setting up analytics and form tracking from the start.

A simple planning summary

Before you contact any developer, try to answer these in a few lines each:

  1. What must the website achieve?
  2. Who are the main customers, and what do they need to know?
  3. Which pages are needed at launch?
  4. What content and photos do you already have?
  5. Which features are essential, and which can wait?
  6. Who will update the site?
  7. Do you control your domain and hosting?
  8. What budget range and timeline are you working with?

With those answers, any developer can give you a clearer quote and fewer surprises. If you would like us to look at your answers, send us your project details and we will reply with questions and a suggested approach.