How to choose a web developer in Freetown: 8 questions to ask first

Hiring a web developer is easier when you know what to ask. You do not need to understand code. You need to understand what you are buying, who owns it afterwards and what happens when something breaks.

Here are the questions I would ask if I were hiring.

1. Can I see work you have actually built?

Ask for live websites or case studies, and open them on your own phone. Check that they load quickly and that the contact details work. A real developer is happy to explain what they did on each project and what the client asked for. You can look through my own portfolio as an example of what that looks like.

2. What exactly will I get, in writing?

A good proposal lists the pages, the features, the number of revisions and the delivery date. "A nice website" is not a scope. Without a written scope, every extra request becomes an argument about money later.

3. Who owns the domain, the hosting and the code?

The domain name and hosting account should be registered in your name, or at least transferred to you when the work ends. Ask whether you will receive the source code. Some developers keep everything under their own accounts, which leaves you stuck if the relationship ends.

4. How will the site be built, and can someone else maintain it?

Ask which tools they use and why. Common, well-supported tools mean you can find another developer later. A very unusual setup can lock you in.

5. Will it work well on a phone?

Most of your visitors are on mobile, often on mobile data. Ask how the developer tests on real phones and slow connections. If they only talk about how it looks on a large screen, keep asking.

6. How do we handle payments and milestones?

A common, fair pattern is a deposit to start, a payment at an agreed milestone, and the final payment on delivery. Be careful with anyone who asks for everything upfront, and agree what counts as "finished" before you start.

7. What happens after launch?

Websites need updates, backups and security fixes. Ask what is included after launch, for how long, and what ongoing support costs. Ask how quickly the developer replies when something goes wrong.

8. How do we communicate?

Agree how you will talk (WhatsApp, calls, email), how often you will get progress updates and who your contact is. Many projects go wrong because of silence rather than skill.

Red flags

• No examples of past work, or work they cannot explain.
• Pressure to pay everything immediately.
• No written agreement.
• Promises of "number one on Google" in a few days. Nobody can guarantee that.
• Refusing to hand over logins or files at the end.

Compare more than the price

The cheapest quote often leaves out things you will need later, such as hosting, revisions and support. Ask each developer to itemise what is included, such as hosting, revisions and support, so you can compare like with like.

If you would like to talk through your project, contact me and tell me what you have in mind.