Nine questions to ask before you hire a web developer
Most bad website experiences are not caused by bad developers. They are caused by things nobody asked about at the start.
The short version
- Ownership of the code, domain and hosting should be written down before you pay anything.
- Ask what happens after launch, in writing, with a price attached.
- A developer who asks about your customers before your colour preferences is usually the better hire.
- Being told your idea is too expensive for its likely return is a good sign, not a lost sale.
Why these questions matter
A website is one of the few things a business buys where the buyer often cannot judge the product. You can tell whether a delivery van drives. You cannot easily tell whether a site is built in a way that will still be maintainable in three years.
These nine questions close most of that gap. They are the ones clients ask us that we wish more people asked everyone.
The nine questions
- Who owns the code and the accounts when I have paid in full?The answer should be you, without conditions. Ask specifically about the domain registration, the hosting account and the source files. This is the single most important question on the list.
- What exactly is in the quote, and what is not?Look for page count, revision rounds, copywriting, images, email setup and analytics. Anything unlisted will be a later conversation.
- What are the ongoing costs after launch?Hosting, domain renewal, mailboxes, licences, maintenance. Get a monthly rand figure. A quote with no ongoing costs at all is usually incomplete.
- What is the timeline, and what do you need from me?Most delays are content delays. A developer who tells you upfront that they need your text and logo by a certain date is managing the project properly.
- How many revision rounds are included?Two or three is normal. Unlimited sounds generous and usually means the cost is built in elsewhere.
- Will it be built on a page builder or written directly?Neither answer is wrong, but it changes your future. Builders are quicker to edit yourself and tie you to a subscription. Hand-written code is faster and fully portable.
- How will I update content myself?If you plan to add posts or change prices often, say so now. Retrofitting that later is more expensive than including it.
- What happens if something breaks at 8pm on a Friday?You want a named person and a realistic response time, not a ticketing system you will never use.
- Can I speak to a client you built for last year?Last year matters more than last month. It tells you what support looks like once the excitement has worn off.
What good answers sound like
Good answers are specific and slightly boring. Vague enthusiasm is a warning sign. A few examples of the difference:
| Question | Weak answer | Strong answer |
|---|---|---|
| Ongoing costs | Very affordable, we will sort it out | R220 a month for hosting and two mailboxes, invoiced yearly |
| Timeline | A couple of weeks | Two weeks from the day I have your copy and logo, three review points along the way |
| Ownership | It is all handled on our platform | The domain is registered in your name, and I will send you the files and logins at handover |
Red flags worth walking away from
- The domain will be registered in the developer's name rather than yours.
- A large deposit is requested before any scope is written down.
- You are shown a portfolio but none of the sites are live when you check them.
- Guaranteed first place on Google. Nobody can promise that, and offering it says something about everything else you are being told.
- Pressure to decide today because of a discount that expires.
Questions they should ask you
The interview runs both ways. A developer worth hiring will want to know who your customers are, what a good enquiry looks like, what you want a visitor to do, and what has not worked before.
If the first questions are about colour preferences and how many pages you want, you are buying decoration rather than a business tool.
Try these on us
Ask Vince any of the nine and you will get a straight answer, including the ones about ownership and ongoing cost.