A website is often the first impression a customer has of your business, and fixing a poor build costs more than doing it properly the first time. These are the questions we would ask if we were hiring a web developer ourselves.

Start with what the website must achieve

Before you compare quotes, write down what the website needs to do. Bring in enquiries? Take bookings? Sell products? Explain a complex service? A clear goal makes proposals easier to compare and keeps the project focused.

Note who the site is for, the pages you think you need, any systems it must connect to, and your timing. You do not need a finished brief, but this list will save time in every conversation.

Look at live work, not just screenshots

Ask for links to websites the company has built and open them on your phone. Do they load quickly? Is it obvious how to get in touch? Do the buttons and forms work? A live site tells you far more than a portfolio image.

If you can, ask one or two of their clients how the project went, especially what happened after launch.

Questions to ask before you sign

  • Who will own the domain name, the hosting account and the website files? The answer should be you.
  • What exactly does the quote include, and what would cost extra?
  • Will my team be able to update text and images without a developer?
  • How is search engine optimisation handled at launch: page titles, descriptions, structured data, a sitemap and speed?
  • Who fixes problems after launch, and how quickly?
  • How is personal information from forms stored, and who can see it?

Red flags

  • A price with no written scope of work
  • No live examples you can visit
  • Your domain registered in the developer's name
  • A promise of a guaranteed first place on Google
  • No plan for updates, security or backups after launch

Ownership, privacy and POPIA

If your website collects names, email addresses or phone numbers, the Protection of Personal Information Act (POPIA) applies. You need a privacy notice, sensible limits on who can access form submissions, and secure handling of that data. A good developer will raise this without being asked.

Local or remote?

Many South African businesses work happily with developers in another city, and many businesses abroad hire South African teams. Location matters less than clear communication, a written scope and regular check-ins during the build.