15 questions to ask before hiring a web developer

Two developers can quote very different prices for what sounds like the same website. Sometimes one is more expensive because of design. Often the difference is in what has been included, what has been left for you to do and what happens after launch.

These questions will help you compare proposals on more than the headline figure.

1. What exactly will be delivered?

Ask for a list of pages, features, forms and integrations. 'Professional five-page website' is not detailed enough when the business needs different service pages or a specific booking process.

2. Who writes the website content?

Some quotes include layout and expect you to supply final text. Others include interviews, copywriting and editing. Clarify this early because missing copy can delay the entire project.

3. Who owns the domain name?

The business should know who the domain registrant is, where it is managed and how it can be renewed or transferred. Do not leave this until the relationship with a supplier changes.

4. Where will the website be hosted?

Ask whether hosting is included, for how long, what the renewal cost is and what access you receive. A website may require different resources if it handles payments, large catalogues or custom applications.

5. Can we update the website ourselves?

Identify exactly which content staff will change and how those changes are made. A simple editorial task should not automatically become a development job.

6. What happens if something breaks?

Ask who is responsible, how to report an incident and what support is included after launch. This matters especially for ecommerce checkout and booking systems.

7. Are backups included, and can they be restored?

A backup is only valuable when it is complete, accessible and restorable. Clarify frequency and storage location.

8. What is included for SEO?

The phrase 'SEO-friendly' is too broad. Ask about page titles, service-page structure, technical indexing, redirects, site maps and Search Console setup. Ongoing content and link acquisition are different tasks.

9. How will mobile usability be tested?

Ask whether critical forms, navigation, product options and checkout will be tested on real mobile layouts.

10. What counts as a revision?

Understand the number of revision rounds, what changes are in scope and what will require an additional quote.

11. Which software subscriptions continue after launch?

Premium plugins, marketing tools, integrations and payment providers may have renewal fees. Ask for an explicit list.

12. What happens to existing Google rankings?

If you have an established site, request a URL preservation and redirect plan. Replacing indexed URLs casually can create avoidable problems.

13. How will payments and integrations be tested?

For ecommerce and custom development, ask for tests covering unsuccessful transactions, duplicate events, unavailable external systems and the ability to recover.

14. What do we receive at handover?

Clarify administrator accounts, hosting credentials, documentation, source code where applicable, licences and any agreed staff training.

15. How are future changes quoted?

A project is easier to manage when there is a process for requesting features, estimating effort and approving changes before work begins.

Compare total cost, not only the build price

Include hosting, maintenance, subscriptions, content work and support. It helps to calculate the estimated cost over two or three years, particularly when comparing once-off projects with monthly website plans.

For market price benchmarks, read website design costs in South Africa. For a new build, see professional website design.

Send us your requirements for a website discussion